I've been using my sBitx v3 for one and a half months and am pretty happy with it. However, I noticed strange behavior.
When I try to start QSO with a station that uses nonstandard callsign (e.g., longer than usual or prefixed or suffixed with something), its callsign is displayed as <...>. The same "<...>" is output to the log. This form seems to be used even in responses, so the recipient does not accept them, and the QSO gets broken.
Up to now, I'm simply limiting my QSOs to the stations with standard callsigns.?
However, spring and summer approach, and I hope to use my site v3 in SOTA and POTA activities or use it during my holidays abroad.
In those cases, my callsign will need to be suffixed (e.g., with "/P") or prefixed (e.g., with "OE/" when in ?sterreich).
Is my sBitx v3 going to handle that situation properly, or I won't be able to make any QSO?
How can I fix that issue?
?
73,
Wojtek SP5DAA
?
?
