Message

JO28WJ 10 1 1= 0 The question I suppose is what was LA3EQ/M using to generate the trans= missions, WSPR on a PC, or something homebrew for /M use? 73, Lee M0LMH. ------=_NextPart_000_0192_01CA9167.17DED920 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message

Special Message Formats

Normal WSPR messages consist of a callsign, 4-digit gr= id locator,=20 and power level in dBm. These messages are always preferred when appro= priate.=20 However, compound callsigns (i.e., callsigns with add-on prefix or suf= fix)=20 cannot fit into the 28 bits allocated in a standard message. Similarly= , 6-digit=20 locators cannot fit into 15 bits. Messages using these components are= therefore=20 sent using a two-transmission sequence. For example, if the callsign= is=20 PJ4/K1ABC, the 6-digit grid locator is FK52UD, and the power level 37= dBm, the=20 following messages will be sent in alternating transmissions:=20

PJ4/K1ABC 37 <PJ4/K1ABC> FK52UD 37

If you have special need to use a 6-digit locator with= a normal=20 callsign, check the box Force transmission of 6-digit= =20 locator. If the callsign is K1ABC, the 6-digit grid= locator FN42AX,=20 and the power level 37 dBm, the following messages will then be sent= in=20 alternating transmissions:

K1ABC FN42 37 <K1ABC> FN42AX 37

Callsigns enclosed in angle brackets are actually sent= as 15-bit=20 hash codes. If such a code is received by another station before the= full=20 callsign has been received, it will be displayed as <...> on the decoded= text line. Once=20 the full callsign has been received, the decoder will thereafter recog= nize the=20 hash code and fill in the blanks. Two very different callsigns might= have the=20 same hash code, but the 15-bit hash-code length ensures that in practi= ce such=20 collisions will be rare.

Please note that messages with compound callsigns or= 6-digit=20 locators will not be properly decoded by WSPR versions earlier than 2.= 0. Further=20 details on message formats can be found in Appendix B, and in the WSPR= source=20 code.

From: Lee Hudson<= /A>

Sent: Saturday, January 09, 2010 6:21 PM

To: rsgb_lf_group@blacksheep.org=20

Subject: LF: WSPR LA3

Hi Klaus,

Yes= I'm using=20 V2

Ho= wever:

1001= 09=20 1456   9 -22 2.4   0.503919 LA3/O28WJJ= =20 10          -3  = ; =20 13    0
100109 1500   7 -24 1.6 = ; =20 0.503921 LA3/O28WJJ=20 10         =20 -1     1    0
100109 1502 &= nbsp; 6=20 -25 1.8   0.503919 <...> JO28WJ=20 10         0   = =20 3    0
100109 1506 13 -18 1.7  = ;=20 0.503918 <...> JO28WJ 10     &nbs= p; =20 -1     1    0
100109 1508 = 17=20 -14 1.7   0.503916 LA3/O28WJJ=20 10          =20 0     1    0
100109 1510 = 16=20 -16 1.8   0.503915 <...> JO28WJ=20 10         0   = =20 1    0
100109 1512 11 -20 1.8  = ;=20 0.503915 LA3/O28WJJ=20 10          =20 0     1    0
100109 1516 = 14=20 -16 1.7   0.503896 LA3/O28WJJ=20 10         =20 -1     6    0
100109 1518 = 15=20 -15 1.8   0.503895 <...> JO28WJ=20 10         0   = =20 1    0

1001= 09 1520 15=20 -15 1.7 0.503896 LA3EQ/M=20 10 &n= bsp; =20 1 1 0
100109 1522 = 11=20 -19 1.8 0.503898 <LA3EQ/M> JO28WJ=20 10 1 1 &nbs= p;=20 0

<= /FONT>

The question I=20 suppose is what was LA3EQ/M using to generate the=20 transmissions,

WSPR= on a PC,=20 or something homebrew for /M use?

73= ,

Lee= =20 M0LMH.

&n= bsp;

------=_NextPart_000_0192_01CA9167.17DED920--