Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-db05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 9D7EC380000B4; Sat, 8 Sep 2012 16:07:53 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TARIt-0000HF-NS for rs_out_1@blacksheep.org; Sat, 08 Sep 2012 21:06:55 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TARIt-0000H6-22 for rsgb_lf_group@blacksheep.org; Sat, 08 Sep 2012 21:06:55 +0100 Received: from smtpout3.wanadoo.co.uk ([80.12.242.59] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TARIq-00066G-Ud for rsgb_lf_group@blacksheep.org; Sat, 08 Sep 2012 21:06:53 +0100 Received: from AGB ([2.26.45.146]) by mwinf5d32 with ME id wk6r1j00639DqMu03k6rKJ; Sat, 08 Sep 2012 22:06:52 +0200 Message-ID: From: "Graham" To: References: <50493001.4050202@iup.uni-heidelberg.de> <16BEB82EDFAD4E4FB0A34C8BABAA6AE1@AGB> <504A14AD.2070403@iup.uni-heidelberg.de> <00ca01cd8ded$85328aa0$1502a8c0@Clemens04> <673F2A3B35F24CF894C1077CE36E2AEA@White> In-Reply-To: <673F2A3B35F24CF894C1077CE36E2AEA@White> Date: Sat, 8 Sep 2012 21:06:51 +0100 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: This all started with WSPR , 'we' had to introduce the the idea of ' Dial set usb' or half the LF/MF Rx stations where off frequency , as the mode expected a normal ssb /tx/rx ..then came the PIC coders and things soon got out of hand .as we had work out offsets . now cw operators are using 'semi-data' and we start all over again .. [...] 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.59 listed in list.dnswl.org] 0.0 T_OBFU_GIF_ATTACH BODY: GIF attachment with generic MIME type 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 571129b349252c35b2bc09d7a1c6d0f3 Subject: Re: LF: LF/MF night and weekend Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_0024_01CD8E05.DDD0C600" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,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-VSS-INFO: 5400.1158/83767 X-AOL-VSS-CODE: clean x-aol-sid: 3039ac1d4059504ba5994a77 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_0024_01CD8E05.DDD0C600 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0025_01CD8E05.DDD0C600" ------=_NextPart_001_0025_01CD8E05.DDD0C600 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable This all started with WSPR , 'we' had to introduce the the idea = of ' Dial set usb' or half the LF/MF Rx stations where off = frequency , as the mode expected a normal ssb /tx/rx ..then = came the PIC coders and things soon got out of hand .as we had = work out offsets . now cw operators are using 'semi-data' and we = start all over again .. In normal use , Op anti-collision system ( 2.5 Hz space) places the = carrier in the lowest s/n slot , as determined in the last 2 = seconds before the Tx is keyed , so the frequency will change = from each over ..=20 We are all appliance operators now .. , 'Appliance of Science' ! G.. From: Markus Vester=20 Sent: Saturday, September 08, 2012 8:43 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: LF/MF night and weekend Clemens, Stefan is actually transmitting on 478.70 kHz... I would generally prefer exchanging real RF frequencies rather than a = "dial frequency" setting, which I find more confusing than helpful. It = would also be nice if the web reports would mention the precise receive = frequency. After all, we wanna be real radio amateurs and not black box = users (aka appliance operators ;-). Best 73 and good luck, Markus (DF6NM) From: Clemens Paul=20 Sent: Saturday, September 08, 2012 8:12 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: LF/MF night and weekend >I just started my TX in OP4 mode on 477 kHz dial. Will run in until = sunday evening Stefan, wouldn't it be better to choose a slightly different qrg to avoid = interfering with the carrier of the 'RP' NDB beacon (which is BTW masking your signal here)? Perhaps 500Hz up or down would be fine. 73 Clemens DL4RAJ ----- Original Message -----=20 From: Stefan Sch=E4fer=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Friday, September 07, 2012 5:37 PM Subject: Re: LF: LF/MF night and weekend MF! I just started my TX in OP4 mode on 477 kHz dial. Will run in until = sunday evening. BTW the PA was not damaged, it was just a = under-dimensioned fuse which i used for the first tests and forgot to = replace it by its actual value. Now the transmission should work without = interruptions, i hope. Would be interesting to have some 24 hour monitoring data of the = complete saturday, so if you like to take a part in this "study", pse = run the RX during that time :-) Tnx and 73 to all, Stefan/DK7FC Am 07.09.2012 14:19, schrieb Graham:=20 First demonstration that what go's East , not always go's = West !=20 Spectacular s/n levels in the Moscow area but nothing showing=20 TA ?=20 G.. G.., It was probably due to thunderstorms in the US and SA. YV7MAE had = to QRT due to heavy lightnings... E-Mail ist virenfrei. Von AVG =FCberpr=FCft - www.avg.de Version: 2012.0.2197 / Virendatenbank: 2437/5254 - Ausgabedatum: = 07.09.2012=20 ------=_NextPart_001_0025_01CD8E05.DDD0C600 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable
This  all  started  with  WSPR  , = 'we' =20 had  to introduce the  the  idea of  ' Dial = set =20 usb'  or  half the LF/MF  Rx  stations =20 where  off  frequency  , as the  mode =20 expected   a  normal   ssb /tx/rx  = ..then =20 came  the  PIC coders  and  things  soon  = got out=20 of  hand .as  we  had work out  offsets   . now  cw = operators =20 are  using  'semi-data'  and we start all  = over  again=20 ..
 
In normal  use , Op anti-collision  system  ( 2.5 Hz = space)  places the  carrier in the  lowest   = s/n =20 slot  , as  determined  in the  last  2 = seconds =20 before the  Tx  is  keyed , so the  frequency =20 will  change  from  each over ..
 
We are  all  appliance  operators now .. =  ,=20 'Appliance of  Science'  !
 
G..

From: Markus Vester
Sent: Saturday, September 08, 2012 8:43 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: LF/MF night and weekend

Clemens,
 
Stefan is actually transmitting on = 478.70=20 kHz...
 
I would generally = prefer exchanging real RF=20 frequencies rather than a "dial frequency" setting, which I find = more=20 confusing than helpful. It would also be nice if the web reports would = mention=20 the precise receive frequency. After all, we wanna be real radio = amateurs and=20 not black box users (aka appliance operators ;-).
 
Best 73 and good luck,
Markus (DF6NM)
 
Sent: Saturday, September 08, 2012 8:12 PM
Subject: Re: LF: LF/MF night and weekend

>I just started my TX in OP4 mode on 477 kHz dial. = Will=20 run in until sunday evening
 
Stefan,
 
wouldn't it be better to choose a slightly different qrg to = avoid=20 interfering with the carrier
of  the 'RP' NDB beacon (which is BTW masking your signal = here)?
Perhaps 500Hz up or down would be fine.
 
73
Clemens
DL4RAJ
 
 
 
----- Original Message -----
From:=20 Stefan = Sch=E4fer
Sent: Friday, September 07, = 2012 5:37=20 PM
Subject: Re: LF: LF/MF night = and=20 weekend

MF!

I just started my TX in OP4 mode on = 477=20 kHz dial. Will run in until sunday evening. BTW the PA was = not=20 damaged, it was just a under-dimensioned fuse which i used for the = first tests=20 and forgot to replace it by its actual value. Now the transmission = should work=20 without interruptions, i hope.

Would be interesting to have = some 24=20 hour monitoring data of the complete saturday, so if you like to take = a part=20 in this "study", pse run the RX during that time :-)


Tnx = and 73 to=20 all, Stefan/DK7FC





Am 07.09.2012 14:19, schrieb = Graham:=20
First  demonstration  that  what  = go's =20 East  , not  always  go's   West !=20

Spectacular s/n levels  in the  Moscow   = area=20 but  nothing  showing
TA ?=20

G..


G.., It was probably due to = thunderstorms=20 in the US and SA. YV7MAE had to QRT due to heavy = lightnings...

E-Mail ist = virenfrei.
Von AVG=20 =FCberpr=FCft - www.avg.de
Version: 2012.0.2197=20 / Virendatenbank: 2437/5254 - Ausgabedatum: 07.09.2012=20

------=_NextPart_001_0025_01CD8E05.DDD0C600-- ------=_NextPart_000_0024_01CD8E05.DDD0C600 Content-Type: application/octet-stream; name="Emoticon10.gif" Content-Transfer-Encoding: base64 Content-ID: <6A7400A605FD4581919BD8320D3493F2@AGB> R0lGODlhEwATALMPAPbw4Nm8W/XZSem3KtuvMvTjVvDHOeTKj7CLMdCbMO7JbqN/KbmfZp8/H1Mf DQAAACH5BAEAAA8ALAAAAAATABMAAASq8EkJjjJjqAOmf5VhCEUhiAT3AVfplicRdJRCvq6gy/Rh FIHFIuAiCAmGFOhXWDgcC5cTikmEStMo9rkQJSy3BQCgbY67ScYIe5aeMQPEwBUcwowLZGYx0OF0 gCIZBAgXgIeBggMJDAd9gAQJDZMJehkIDABIOpINlZ0JgwgdB0gGniKCkpcMFAGmqRmycZkTAK+z s4S1HhUJlQQDkQiYNB8gBwwIC5i8ExEAOw== ------=_NextPart_000_0024_01CD8E05.DDD0C600--