|
Posted by John Davis on January 08, 2023 at 22:16:40.
In Reply to: Non standard callsigns WSPR posted by Jay KD4BPZ on January 08, 2023 at 13:51:05.
Hi, Jay. I perceive that you are asking two different questions here. One involves call signs that are embedded in the transmitted signal itself, while the other is not in the signal, but merely identifies the reporter to WSPRnet when the reports are uploaded. Let's take the easier (second) part first.
For example I see WLO, KFS and others when I search the WSPR database. If you'll notice, WLO, the various KFS receivers, SWLEM3, and other non-ham formats are mainly in the Reporter column of the database results. Their decoding and reporting software doesn't care about the reporter ID format, except for possible maximum length, and neither does WSPRnet.In fact, I have seen reporter IDs up to 9 characters long on WSPRnet. Lots of flexibility there! Then there's the anonymous mystery op, EZ1, who both reports spots and also transmits a non-ham identifier on 22 m. Which leads us to the other side of the coin...
How does one receive non standard call signs on 22m WSPR? This is the trickier part, because it involves limitations built into the decoding software. The KiwiSDR decoder seemingly doesn't care at all what the sender's Call field contains; it just says "I calls 'em like I sees 'em."The various "official" K1JT approved decoders have treated call formats differently over the years, partly to reduce the risk of erroneous decodes causing excess confusion. The previous version of WSJT-X was said to be pretty strict, but I hear the more release candidates are less so. You might want to read all three posts in this recent thread for more information: Message 13207
|
Follow Ups:
|