search

drexjj / sbitx

An improved version of the sBITX application and operating system for the HF Signals sBitx hardware.
http://w9jes.com/
16 stars 4 forks source link

Add the ability to store and send callsigns that contain a / #68

Open ec1oud opened 1 week ago

ec1oud commented 1 week ago

I'm American, and operating under the CEPT agreement in Norway. So my callsign for now is LA/K7IHZ. Apparently some validation code somewhere is removing the slash when I use the /mycallsign command; therefore I can't use the built-in FT8 mode here. I was just using the American callsign for a while, until I knew better...

I'm working on getting a Norwegian callsign, but it will take a while. And there are many other cases where slashes are used in callsigns anyway. European countries are small, and hams routinely travel across borders and need to use prefixes. Then there are the numeric suffixes.

drexjj commented 1 week ago

This has been assigned to the dev team to resolve in a future release.

ec1oud commented 1 week ago

I found that if I change #mycallsign in the .ini file, the UI shows the callsign correctly. I attempted FT8 on 20m that way, and made no contacts; so I wonder if the packets are formatted wrong, and thus everybody was ignoring them. (Although activity showed up on pskreporter.info somehow.) I don't yet have another rig to receive and decode my own transmissions. But I had better luck making contacts with jtdx on a sota peak last night (and needed to take along an extra screen to have enough space for that).

MolKa51 commented 1 week ago

Unfortunately, the / sign is not recognized and all complex call sign formats are not recognized by the sbitx ft8 decoder, so if you have an external hdmi monitor, use an external application (jtdx, wsjtx) installed on the 64-bit image. Once I realized this, I've been using it to access complex callsigns ever since. Gyula HA3HZ