开云体育

A tricky question

#sBITX_v3

HA3HZ All Messages By This Member #108755 Today I was peacefully radioing in ft8 mode on 21 MHz when the image below appeared on my screen. Since I had done the same thing 10 minutes before, only then another station called at the same time, so I answered it. I was invited again by this station with an unknown call sign, even though I know that the sbitx ft8 encoder is not capable of encoding everything, so I avoid special call signs. Special: understand /p or / prefix or more numbers and more letters than regular callsigns. So whoever deciphers it, I owe them a coffee or a drink. :-) -- Gyula HA3HZ
Ashhar Farhan All Messages By This Member #108759 Gyula, The only way to actually find out what is going on is to run wsjtx in the background as well and sew which callsign went missing. Is this v3.02? toggle quoted message Show quoted text On Mon, Feb 5, 2024, 7:26 PM HA3HZ <gyula@...> wrote: Today I was peacefully radioing in ft8 mode on 21 MHz when the image below appeared on my screen. Since I had done the same thing 10 minutes before, only then another station called at the same time, so I answered it. I was invited again by this station with an unknown call sign, even though I know that the sbitx ft8 encoder is not capable of encoding everything, so I avoid special call signs. Special: understand /p or / prefix or more numbers and more letters than regular callsigns. So whoever deciphers it, I owe them a coffee or a drink. :-) -- Gyula HA3HZ
HA3HZ All Messages By This Member #108761 Ashhar, Unfortunately, he didn't win... I run wsjt-x in the background and <...> is visible just like on the sBitx v3.02 screen. -- Gyula HA3HZ

Previous Topic Next Topic