Message-ID: <53F900B4.4030605@freenet.de>
Date: Sat, 23 Aug 2014 22:59:32 +0200
From: wolf_dl4yhf <dl4yhf@freenet.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <BDDC39C2F2C2471DA59F7DC5A96EDB2A@KKneu>
In-Reply-To: <BDDC39C2F2C2471DA59F7DC5A96EDB2A@KKneu>
Subject: Re: LF: MF WSPR please
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Hello Klaus,

Thanks for the information.
So DK2CH "produces" his over with the JO52GD six-character locator by 
leaving the callsign away,
and WSPR is somehow able to 'guess' it (or retrieve it from a previous 
over) - so everything inside angle brackets has 'not really been 
transmitted in that over' ?

 From consecutive decodes (as on 2044 and 2046 below), it looks like 
exactly that was happening: Once with the call 'really' been 
transmitted, and (the 2nd part) with the 6-char locator.

2040 -16 -0.1   0.475652  0 F5WK JN18 27
2040  -7 -0.3   0.475740  0 PA3ABK/2 27
2040 -27 -1.1   0.475763  0 <DK2CH> JO52GD 27
2044 -23  4.1   0.475606  0 IW4DXW JN64 27
2044 -24  0.5   0.475704  0 F1AFJ JN06 30
2044 -26 -1.0   0.475764  0 DK2CH JO52 27
2046  -9 -0.6   0.475751  0 DH5RAE JN68 23
2046 -23 -1.0   0.475764  0 <DK2CH> JO52GD 27

(copied from the local WSPR decoder output).


73,
   Wolf DL4YHF .


Am 23.08.2014 22:32, schrieb KKorn:
> Wolf
> just to drop in my bit of "knowhow" regarding missing callsigns in WSPR
> transmissions:
> WSPR can only convey in ONE transmission a FOUR digit locator, not JO52GD!
> If you want to send such information, WSPR can and must split this up into
> two consecutive transmissions. If you happen to receive just one ... you
> miss the whole show! This is also true if you have to send a long callsign
> ("/p" or other indicators).
>
> Grüße / Greetings
> Klaus
> DJ6LB
>
>
>
>