Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 8C3003800009A; Sat, 8 Sep 2012 17:47:22 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TASrO-0001Qh-Fd for rs_out_1@blacksheep.org; Sat, 08 Sep 2012 22:46:38 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TASrN-0001QV-Sb for rsgb_lf_group@blacksheep.org; Sat, 08 Sep 2012 22:46:37 +0100 Received: from imr-da05.mx.aol.com ([205.188.105.147]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TASrL-0006Z6-Nc for rsgb_lf_group@blacksheep.org; Sat, 08 Sep 2012 22:46:36 +0100 Received: from mtaout-mb04.r1000.mx.aol.com (mtaout-mb04.r1000.mx.aol.com [172.29.41.68]) by imr-da05.mx.aol.com (8.14.1/8.14.1) with ESMTP id q88LkQxJ006109; Sat, 8 Sep 2012 17:46:26 -0400 Received: from White (nrbg-4d073d56.pool.mediaWays.net [77.7.61.86]) by mtaout-mb04.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id EB88EE00013B; Sat, 8 Sep 2012 17:46:24 -0400 (EDT) Message-ID: <75B3865F8CAA40E098D45E95C70DDE26@White> From: "Markus Vester" To: Cc: References: <50493001.4050202@iup.uni-heidelberg.de> <16BEB82EDFAD4E4FB0A34C8BABAA6AE1@AGB> <504A14AD.2070403@iup.uni-heidelberg.de> <00ca01cd8ded$85328aa0$1502a8c0@Clemens04> <673F2A3B35F24CF894C1077CE36E2AEA@White> Date: Sat, 8 Sep 2012 23:46:30 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 X-AOL-VSS-INFO: 5400.1158/83767 X-AOL-VSS-CODE: clean DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1347140786; bh=7mtyHwiVuSW7XXhG7rcPYA08eNQIo3Yp6X7YOLnp8Ug=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=A5mFKRY4h2cCHReL+Obj0h8QLDmOatxtw455RCGbvdLBHdsYABzq7XYlU7WSsB2pO MLFbYvFNwegx5MYKvGNe7ejgeXkzyNIXxXP/9Csl63HCbftW6n6vl1R94qS851Lprn m0h78dZP7PJDMcFDdTQunabUCeN3br+TlWHEnZOA= X-AOL-SCOLL-SCORE: 0:2:425395904:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: 1.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: Graham, > This all started with WSPR yes I know... but let me suggest two points you might consider adopting in future Op versions: [...] Content analysis details: (1.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 [205.188.105.147 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_OBFU_GIF_ATTACH BODY: GIF attachment with generic MIME type 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: fcf77e2759cb043d8839e008dc214d5a Subject: LF: Dial frequency - or better not? Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_000C_01CD8E1C.2D4668F0" 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-VSS-INFO: 5400.1158/83767 X-AOL-VSS-CODE: clean X-AOL-SCOLL-AUTHENTICATION: mtain-mk05.r1000.mx.aol.com ; domain : mx.aol.com DKIM : fail x-aol-sid: 3039ac1d6189504bbce94964 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_000C_01CD8E1C.2D4668F0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_000D_01CD8E1C.2D4668F0" ------=_NextPart_001_000D_01CD8E1C.2D4668F0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Graham, > This all started with WSPR=20 yes I know... but let me suggest two points you might consider adopting = in future Op versions:=20 With WSPR v2, there is a "BFO" setting allowing to configure the RX = audio frequency range. The TX frequency can be edited as well. For = example, my LO is fixed on 135.5 kHz, and the default 1500 Hz centered = band would be useless here. When WSPR has found a signal, it adds the measured audio frequency to = the selected LO, and reports the QRG with 1 Hz accuracy in each spot. Best 73, Markus (DF6NM) From: Graham=20 Sent: Saturday, September 08, 2012 10:06 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: LF/MF night and weekend 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 ... ------=_NextPart_001_000D_01CD8E1C.2D4668F0 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable
Graham,
 
> This  all  started  with  WSPR 
 
yes I know... but let me = suggest two points=20 you might consider adopting in future Op versions: =
 
With WSPR v2, there is a = "BFO" setting=20 allowing to configure the RX audio frequency range. The TX = frequency=20 can be edited as well. For example, my LO is fixed on 135.5 kHz, = and=20 the default 1500 Hz centered band would be useless = here.
 
When WSPR has found a = signal, it adds the=20 measured audio frequency to the selected LO, and reports the QRG = with 1 Hz=20 accuracy in each spot.
 
Best 73,
Markus (DF6NM)
 
 

From: Graham
Sent: Saturday, September 08, 2012 10:06 PM
Subject: Re: LF: LF/MF night and weekend

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
 ...
------=_NextPart_001_000D_01CD8E1C.2D4668F0-- ------=_NextPart_000_000C_01CD8E1C.2D4668F0 Content-Type: application/octet-stream; name="Emoticon10.gif" Content-Transfer-Encoding: base64 Content-ID: <44B8075F2A7F4B32851F9A07D7B4A6DD@White> R0lGODlhEwATALMPAPbw4Nm8W/XZSem3KtuvMvTjVvDHOeTKj7CLMdCbMO7JbqN/KbmfZp8/H1Mf DQAAACH5BAEAAA8ALAAAAAATABMAAASq8EkJjjJjqAOmf5VhCEUhiAT3AVfplicRdJRCvq6gy/Rh FIHFIuAiCAmGFOhXWDgcC5cTikmEStMo9rkQJSy3BQCgbY67ScYIe5aeMQPEwBUcwowLZGYx0OF0 gCIZBAgXgIeBggMJDAd9gAQJDZMJehkIDABIOpINlZ0JgwgdB0gGniKCkpcMFAGmqRmycZkTAK+z s4S1HhUJlQQDkQiYNB8gBwwIC5i8ExEAOw== ------=_NextPart_000_000C_01CD8E1C.2D4668F0--