My master bogus list

1 post / 0 new
VE7DES
VE7DES's picture
Offline
Last seen: 23 hours 29 min ago
Joined: 2013/12/23 - 23:51
My master bogus list

Collected from my ALL_WSPR.txt.

In many cases the bogus was co-frequency with a station known to be transmitting at the time. Whenever "sufficient confidence" existed, I attributed the bogus to the co-frequency station and recorded the latter in the "remarks" column.

Where "antivirus" is noted, Windows Defender and/or AVG were known to be running.

There are a few instances (e.g. 140429) where I possibly recorded a bogus when it was actually a legitimate station with an unresolved hash, transmitting a 6-character grid locator. Sorry for this but I confess being a newbie.

Bogus 6-character locators show a curious tendency to appear in the format
LLLNLL (L letter, N number)
more often than LLNNLL and other patterns.

On 141112, the identical locator G4O1UC was decoded 7 times in a row and its <...> hash was not resolved. All these reports had large decoding pass counts (column 9). The co-frequency station KD6RF was decoded several times before and after this series. As no transmissions from KD6RF were noted during 1546-1736Z (when the boguses were occurring), KD6RF is tentatively identified with the bogus. Reported SNRs were as strong as -2 dB. The bogus traces were not seen in the waterfall because they had scrolled off by the time I checked the PC at 1900Z. No trace of EMI, which can masquerade as a WSPR, was seen, and no other boguses were noted that morning. Many other transmitters were decoded during the "G4O1UC" sequence -- in one instance, during the same frame. There was no evidence of buffer overruns or CPU resource shortages at my end.

The operator of KD6RF remarked that he is running WSPR in a Mac Book emulating a Windows PC. Nothing like this has been observed prior or since.