Return-Path: Received: from mtain-mb09.r1000.mx.aol.com (mtain-mb09.r1000.mx.aol.com [172.29.96.29]) by air-mc06.mail.aol.com (v129.4) with ESMTP id MAILINMC064-a9764ca7702a1c0; Sat, 02 Oct 2010 13:47:22 -0400 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mb09.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7AD0A3800009D; Sat, 2 Oct 2010 13:47:20 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1P269f-00008c-Ug for rs_out_1@blacksheep.org; Sat, 02 Oct 2010 18:45:51 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1P269V-00008T-Fr for rsgb_lf_group@blacksheep.org; Sat, 02 Oct 2010 18:45:41 +0100 Received: from out1.ip02ir2.opaltelecom.net ([62.24.128.238]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1P269V-0007Ci-AT for rsgb_lf_group@blacksheep.org; Sat, 02 Oct 2010 18:45:43 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjcFAPMMp0xcHY6j/2dsb2JhbACQVQODMI44ccIphUQEgV2Ldw X-IronPort-AV: E=Sophos;i="4.57,271,1283727600"; d="scan'208,217";a="338076889" Received: from unknown (HELO xphd97xgq27nyf) ([92.29.142.163]) by out1.ip02ir2.opaltelecom.net with SMTP; 02 Oct 2010 18:45:35 +0100 Message-ID: <00ec01cb6259$9b900730$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <001a01cb622d$41b28520$0401a8c0@xphd97xgq27nyf> <16FC3DAA0ADA46EF912264949F158380@Black> <009401cb6238$9dcc8cb0$0401a8c0@xphd97xgq27nyf> <8697834CCDAF43AC9ABC9455E962B89C@Black> Date: Sat, 2 Oct 2010 18:45:30 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: LF: Re: Re: Acty 8.97 Kcs Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E9_01CB6261.FD298EA0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_40_50,HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G x-aol-sid: 3039ac1d601d4ca770281fe4 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none ------=_NextPart_000_00E9_01CB6261.FD298EA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Markus Tnx info Strange there was a blank screen then traces appeared.=20 Wasted day on/off for me mal/g3kev ----- Original Message -----=20 From: Markus Vester=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, October 02, 2010 5:11 PM Subject: LF: Re: Acty 8.97 Kcs Mal, counting the time ticks in your Argo captures, they appear to be exa= ctly 3 minutes wide. Looking at the one from 12:23:55 UT, the intermit= tent carrier on 985 Hz had been present already at the beginning at 12= :21. However the attached screenshot from the Heidelberg grabber indic= ates that Stefan's last dash started only at 12:23:12, and increased= power at 12:24:30. Thus I would conclude that the Argo trace had not= been caused by the DK7FC transmission. Best 73, Markus ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, October 02, 2010 3:49 PM Subject: LF: Re: Re: Acty 8.97 Kcs Markus. The freq is accurate but not atomic standard, time is also accurat= e. You will have to decide if this trace is the correct transmission= on 8.87 Kcs The trace fades in/out. de mal/g3kev ----- Original Message -----=20 From: Markus Vester=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, October 02, 2010 1:47 PM Subject: LF: Re: Acty 8.97 Kcs Mal,=20 assuming your clock is accurately set in UK summertime, the firs= t screenshot would have been at 11:00 UT when Stefan was transmitting= full power. He was still off air until 12:23, then reappeared with re= duced power during your second capture, and is up at full juice since= 12:26 UT. =20 Can you do a frequency check (eg. by injecting a known carrier,= or GPS 1 pps pulses)? Positively receiving DK7FC in QRSS-3 resolution= seems a bit far fetched, so reducing the bandwidth by going to a slow= er setting would certainly help. Best 73, Markus (DF6NM) ----- Original Message -----=20 From: mal hamilton=20 To: rsgb=20 Sent: Saturday, October 02, 2010 2:28 PM Subject: LF: Acty 8.97 Kcs Observed today on 8.97 Kcs=20 see pic around 985=20 g3kev ------=_NextPart_000_00E9_01CB6261.FD298EA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Markus
Tnx info
Strange there was a blank screen then= traces=20 appeared.
Wasted day on/off for me
mal/g3kev
 
----- Original Message -----
Sent: Saturday, October 02,= 2010 5:11=20 PM
Subject: LF: Re: Acty 8.97 Kc= s

Mal,
 
counting the time ticks in you= r=20 Argo captures, they appear to be exactly 3 minutes wide.= Looking at=20 the one from 12:23:55 UT, the intermittent carrier on 985 Hz ha= d been=20 present already at the beginning at 12:21. However the attached scre= enshot=20 from the Heidelberg grabber indicates that Stefan's last dash=20 started only at 12:23:12, and increased power at 12:24:30. Thus= I=20 would conclude that the Argo trace had not been caused by= the DK7FC=20 transmission.
 
Best 73,
Markus
 
----- Original Message -----
From:=20 mal=20 hamilton
Sent: Saturday, October 02,= 2010 3:49=20 PM
Subject: LF: Re: Re: Acty= 8.97=20 Kcs

Markus.
The freq is accurate but not atom= ic standard,=20 time is also accurate.
You will have to decide if this= trace is the=20 correct transmission on 8.87 Kcs
The trace fades in/out.
de mal/g3kev
 
----- Original Message -----
Sent: Saturday, October= 02, 2010 1:47=20 PM
Subject: LF: Re: Acty 8.9= 7 Kcs

Mal,
 
assuming your clock is accurate= ly set in UK=20 summertime, the first screenshot would have been at 11:00 UT whe= n Stefan=20 was transmitting full power. He was still off air until 12:23,= then=20 reappeared with reduced power during your second capture,= and is up=20 at full juice since 12:26 UT. 
 
Can you do a frequency check (e= g. by=20 injecting a known carrier, or GPS 1 pps pulses)? Positively rece= iving=20 DK7FC in QRSS-3 resolution seems a bit far fetched, so redu= cing the=20 bandwidth by going to a slower setting would certainly=20 help.
 
Best=20 73,
Markus (DF6NM)
----- Original Message -----=
From:=20 mal=20 hamilton
To: rsgb
Sent: Saturday, October= 02, 2010=20 2:28 PM
Subject: LF: Acty 8.97= Kcs

Observed today on 8.97 Kcs
see pic around 985
g3kev
 
------=_NextPart_000_00E9_01CB6261.FD298EA0--