Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mg04.r1000.mx.aol.com (Internet Inbound) with ESMTP id CD85338000083; Tue, 12 Mar 2013 10:39:40 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UFPuY-0002cw-R8 for rs_out_1@blacksheep.org; Tue, 12 Mar 2013 14:10:38 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UFPuY-0002cn-00 for rsgb_lf_group@blacksheep.org; Tue, 12 Mar 2013 14:10:38 +0000 Received: from smtpout1.wanadoo.co.uk ([80.12.242.29] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UFPuV-0000Sn-Ob for rsgb_lf_group@blacksheep.org; Tue, 12 Mar 2013 14:10:36 +0000 Received: from AGB ([2.26.8.64]) by mwinf5d08 with ME id AeAE1l00H1NtV6A03eAEoR; Tue, 12 Mar 2013 15:10:15 +0100 Message-ID: <7F07F842239C464E8957A67E195D38FE@AGB> From: "Graham" To: References: <51311F32.3070800@iup.uni-heidelberg.de> <8A64C7EBD5AF41CB80C30CD2666C54AC@White> <51335CB8.1070709@iup.uni-heidelberg.de> <9EF0D5974920427FA620981E45AB2D67@White> <233B0B801CC14D59A1509409D9EDFD89@White> <10BD31921A884E429B3A6594FBD7989B@White> <513E3C5A.9090400@iup.uni-heidelberg.de> <7BD468EC77714986B7095F1DFF88C799@White> <9B957F2BE42447E591815BA9A7565953@White> <71F5C1E5EDC5450C8829F6AF184E3A39@White> In-Reply-To: <71F5C1E5EDC5450C8829F6AF184E3A39@White> Date: Tue, 12 Mar 2013 14:10:14 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Or There has been a glitch / momentary hang in the PC , I have seen this happen , then the sequence is no longer time-correct, normal frequency variation is not a big problem , but time is or contact Dr Who [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.12.242.29 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 4933636f78fd1782d378a0372a2e835c Subject: Re: LF: Op32 last night Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01CE1F2B.50E91370" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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: 3039ac1d60cc513f3e2c7ebb X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_0013_01CE1F2B.50E91370 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable Or =20 There has been a glitch / momentary hang in the PC , I have seen = this happen , then the sequence is no longer time-correct, =20 normal frequency variation is not a big problem , but time is=20 or contact Dr Who=20 73-G. From: Markus Vester=20 Sent: Tuesday, March 12, 2013 1:58 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Op32 last night Spiros, you'r signal is strong and consistent here in 4X, but interestingly I'm = getting multiple detections from different slices of the same = transmission. The timestamp shift seems to indicate that the match for = the later parts is 20 or 30 seconds delayed compared to the early part. = This would mean that either my receiver is too fast, or that your = transmitter is too slow by about 1%. In the latter case, I would also = expect that the conventional decoder would have difficulties to get a = decode.=20 Perhaps you might want to check the samplerate of the soundcard used for = transmitting. You could also try to measure the duration of the Opera = sequence - it should be 8.192 seconds per (half-)symbol, or 32min 46sec = for the whole sequence. 13:19:20 SV8CS 1437km 137540.091Hz 140mHz -38.9dBOp 78% 18.7dB 13:19:33 SV8CS 1437km 137540.080Hz 154mHz -37.2dBOp 98% 16.2dB 13:19:42 SV8CS 1437km 137540.080Hz 150mHz -38.0dBOp 68% 15.1dB Best73, Markus From: Markus Vester=20 Sent: Tuesday, March 12, 2013 2:14 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Op32 last night Spiros, here you are: 13:19:21 SV8CS 1437km 137540.083Hz 124mHz -38.8dBOp 48% 17.4dB This was at 13:02, after 48% of the sequence had been received. Best 73,=20 Markus From: Markus Vester=20 Sent: Tuesday, March 12, 2013 11:33 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Op32 last night Spiros, LF, several detections of your signal appeared in Northern Israel last = night, along with a couple from UA4WPF and RN3AGC. Chris who had been = running the software in Bucharest the other night got similar results.=20 I am currently leaving the receiver on during the daytime, and the noise = appears to be quite low. So if you decided to transmit this afternoon = there might be a good chance for a daylight detection. Best 73, Markus (4X/DF6NM in KM73TD) UT call distance frequency bandwidth SNR correlation 2013-03-11: 22:37:17 SV8CS 1437km 137540.006Hz 176mHz -39.0dBOp 90% 19.0dB 2013-03-12: 00:29:12 UA4WPF 2960km 137541.990Hz 2mHz -45.3dBOp 66% 16.7dB 00:50:36 SV8CS 1437km 137540.046Hz 146mHz -38.8dBOp 100% 20.4dB 02:30:24 SV8CS 1437km 137540.033Hz 159mHz -40.7dBOp 100% 18.7dB 04:10:12 SV8CS 1437km 137540.015Hz 163mHz -37.4dBOp 47% 18.5dB 05:21:24 SV8CS 1437km 137540.007Hz 136mHz -38.0dBOp 100% 19.3dB 06:18:16 RN3AGC 2534km 137557.000Hz 3mHz -50.5dBOp 83% 15.9dB From: SV8CS- Spiros Chimarios=20 Sent: Tuesday, March 12, 2013 5:42 AM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Op32 last night Captured in Op 32 23:54 136 UA4WPF de SV8CS Op32 3186 km -39 dB in ZAKYNTHOS Isl. Spiros/SV8CS ------=_NextPart_000_0013_01CE1F2B.50E91370 Content-Type: text/html; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable
Or 
 
There  has been a  glitch / momentary  hang  in = the  PC , I have  seen this  happen , then the =20 sequence  is no longer  time-correct,   
normal  frequency   variation  is not  = a =20 big  problem , but  time is
 
or  contact  Dr Who
 
73-G.
 
From: Markus Vester
Sent: Tuesday, March 12, 2013 1:58 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: Op32 last night

Spiros,
 
you'r signal is strong and consistent = here in 4X,=20 but interestingly I'm getting multiple detections from = different=20 slices of the same transmission. The timestamp shift seems to indicate = that the=20 match for the later parts is 20 or 30 seconds delayed compared to the = early=20 part. This would mean that either my receiver is too fast, or that your=20 transmitter is too slow by about 1%. In the latter case, I would = also=20 expect that the conventional decoder would have difficulties to get a=20 decode. 
 
Perhaps you might want to check the = samplerate of=20 the soundcard used for transmitting. You could also try to measure the = duration=20 of the Opera sequence - it should be 8.192 seconds per (half-)symbol, or = 32min=20 46sec for the whole sequence.
 
13:19:20 SV8CS   1437km = 137540.091Hz=20 140mHz -38.9dBOp  78% 18.7dB
13:19:33 SV8CS   1437km=20 137540.080Hz 154mHz -37.2dBOp  98% 16.2dB
13:19:42 = SV8CS  =20 1437km 137540.080Hz 150mHz -38.0dBOp  68% 15.1dB
Best73,
Markus

Sent: Tuesday, March 12, 2013 2:14 PM
Subject: Re: LF: Op32 last night

Spiros,
 
here you are:
 
13:19:21 SV8CS   1437km = 137540.083Hz=20 124mHz -38.8dBOp  48% 17.4dB
This was at 13:02, = after 48% of=20 the sequence had been received.
 
Best 73, =
Markus

Sent: Tuesday, March 12, 2013 11:33 AM
Subject: Re: LF: Op32 last night

Spiros, LF,
 
several detections of your signal = appeared in=20 Northern Israel last night, along with a couple from UA4WPF and RN3AGC. = Chris=20 who had been running the software in Bucharest the other night=20 got similar results. 
 
I am currently leaving the = receiver on=20 during the daytime, and the noise appears to be quite low. So = if you=20 decided to transmit this afternoon there might be a good chance for = a=20 daylight detection.
 
Best 73,
Markus (4X/DF6NM in=20 KM73TD)
 
   = UT   =20 call   distance  frequency bandwidth  = SNR   =20 correlation
2013-03-11:
 
22:37:17 SV8CS   = 1437km=20 137540.006Hz 176mHz -39.0dBOp  90% 19.0dB
2013-03-12:
 
00:29:12 UA4WPF  2960km = 137541.990Hz   2mHz -45.3dBOp  66% 16.7dB
00:50:36=20 SV8CS   1437km 137540.046Hz 146mHz -38.8dBOp 100% = 20.4dB
02:30:24=20 SV8CS   1437km 137540.033Hz 159mHz -40.7dBOp 100% = 18.7dB
04:10:12=20 SV8CS   1437km 137540.015Hz 163mHz -37.4dBOp  47%=20 18.5dB
05:21:24 SV8CS   1437km 137540.007Hz 136mHz = -38.0dBOp 100%=20 19.3dB
06:18:16 RN3AGC  2534km 137557.000Hz   3mHz=20 -50.5dBOp  83% 15.9dB

From: SV8CS- Spiros Chimarios
Sent: Tuesday, March 12, 2013 5:42 AM
Subject: LF: Op32 last night

Captured in Op 32
23:54    136 UA4WPF de SV8CS Op32 3186 = km=20 -39 dB in ZAKYNTHOS Isl.
 
Spiros/SV8CS
 
 
------=_NextPart_000_0013_01CE1F2B.50E91370--