We have another WSJT-X hash issue now on 12 meters.  P4/WE9V is operating on 24.915 – offset 625hz - from Aruba.  His signal in Russellville is +25.  But if something other than P4/WE9V is in your DX Call window, about 60% of the time the call associated with offset 625hz is BA7LUI.  If you put P4/WE9V in the DX Call window the decode will be P4/WE9V 100% of the time.  If you put BA7LUI in the DX Call window the decode will be BA7LUI 100% of the time.  But BA7LUI is likely not decoding in Russellville with a +25 signal.  There sure are a lot of people calling that phantom callsign…

-Charles, K5CS

Sent from Mail for Windows