Thanks everyone for the comments. I have configured WSJT-X with my callsign, VK3FDLL, and when transmitting in WSPR, I can see that it send the following messages: 1. VK3FDLL QF22 30 2. <VK3FDLL> QF22NE 30
When I attempt to decode these messages from another receiver, it never decodes message #1, but will decode message #2 missing the callsign (instead showing "<...>") I just wanted to make sure it wasn't a PEBKAC issue (problem exists between keyboard and chair) or if it's a limitation in WSPR that I just have to live with until I can change my callsign to less than 7 characters. On Mon, 24 Feb 2020 at 08:25, Fons Adriaensen <f...@linuxaudio.org> wrote: > On Fri, Feb 21, 2020 at 11:34:51AM +0000, Bill Somerville wrote: > > > where I say non-standard I mean within the constraints of the digital > source > > encoding used by the various modes in the WSJT suite of software. That > does > > not exactly align with all callsigns issued around the World, to do so > would > > greatly impact the efficiency, and hence the sensitivity, of the various > > weak signal modes. > > Would it ? > > Seven characters in the set [ 0-9A-Z] would require 37 bits, 9 more > than the current 28. So for e.g. WSPR, the number of data bits would > be 59 instead of 50. Scaling the number of FEC bits by the same ratio > and keeping the total transmitted energy for a message the same, > the Es/No would decrease by 0.7 dB. > > How many of the currently received WSPR messages would be lost ? > I suspect that would be a tiny fraction, as almost all are more > than 0.7 dB above the threshold. I don't think it would affect > the functionality of WSPR in any significant way. > > Ciao, > > -- > FA > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
