I'm locking this topic as this so called problem is non-existent.

Please would people reporting problems with non-standard callsigns read the User Guide first.

73
Roger
GW4HZA
moderator

All was going well, with no apparent issues with either FT4 or FT8, until I called a station with the callsign 3Z95PRK. My outgoing transmission was truncated and showed only '3Z95PRK G0H' This happened every time I called 3Z95PRK.

Hi Martin

From User Guide 7.5. Nonstandard Callsigns:

"Compound callsigns like PJ4/K1ABC or K1ABC/3 and special event callsigns like YW18FIFA are supported for normal QSOs but not for contest-style messages."

73, Reino OH3mA

Running v2.6.0-rc5 on a 64-bit Win 10 (21H2) PC, 3.0GHz i7-9700 CPU and 16G RAM.

I'm participating in the FT Roundup contest that's running this weekend (3/4 Dec) so am using a configuration that uses the 'FT Roundup' option in the 'Special operating activity' settings.

All was going well, with no apparent issues with either FT4 or FT8, until I called a station with the callsign 3Z95PRK. My outgoing transmission was truncated and showed only '3Z95PRK G0H' This happened every time I called 3Z95PRK.

I've just checked my ALL.TXT file and the entries in there for my FT4 calls to 3Z95PRK are also truncated, and show:

221204_074030 14080 Tx FT4 0 0.0 2540 3Z95PRK G0H

Note that there's an extra space between the callsign of the station being called and the first letter of my callsign - in all the other entries in ALL.TXT for my transmissions there's only a single space.

I never did manage to work 3Z95PRK!

--
Martin G0HDB