|
|
Post by OH8EJW, Mikko on Apr 16, 2022 13:00:38 GMT
I have problems with my second op callsign witch is OG16M. When using it, i cant make directiolan CQs at all. Even ai add DX, AS what ever and press GenMsgs nothing happend at all. It does only CQ OG16M, also noticed location info also missing. IF i remove number 1 or 6 and callsign is OG6M or OG1M directional CQ does what is supposed to do. Have any one else noticed this or can someone else try what ever callsign what have TWO numbers after prefix will it do same thing? Is this bug or what. See attachment.
OH8EJW/OG16M
Attachments:
|
|
|
|
Post by Arvo ES1JA on Apr 16, 2022 16:17:53 GMT
OG16M is nonstandard callsign, and this has own limits in use, including no normal directional CQ-s and also no locator in CQ. Nothing can't be done.
Simpler way is to get ride of this callsign when You want use FT8 or similar digital modes without restrictions. Despite I will try to modify Gen messages function as "CQ DX OG16M" is in general possible to transmit as Free text (until 13 char) message.
|
|
|
|
Post by Wolfgang OE1MWW on Apr 16, 2022 17:19:12 GMT
... my second op callsign witch is OG16M ...
OH8EJW/OG16M
It's in the FT8 protocol - and JTDX has to follow those rules, otherwise no one could decode ;-) For FT8: "A standard amateur callsign consists of a one- or two-character prefix, at least one of which must be a letter, followed by a digit and a suffix of one to three letters."
It says 'followed by a digit' and not, as in your case, two digits. More details can be found in FT8 PROTOCOLS
Btw., the discussion about special call signs - even all of them 'legal' assigned - is going on since ever. But there is no way out.
73's de OE1MWW Wolfgang
|
|
|
|
Post by Arvo ES1JA on Apr 17, 2022 8:03:31 GMT
I made changes to message composing ( high level to enable generated CQ messages with nonstandard callsign as free messages when possible)
072030 Tx 2127 ~ CQ DX OG16M (success)
072600 Tx 2127 ~ CQ OG16M (attempted CQ OG16M KP24, but grid is truncated by message packer, it looks bug there as message is 13 char and should be possible te send as free text message)
074430 Tx 2127 ~ CQ OG16 KP24 (success nonstandard calsign with grid OK but there length is 12 chars)
074630 Tx 2127 ~ CQ DX OG16MMM (success nonstandard callsign 13 chars )
Same results are when transmitting with WSJT-X
Conclusion, message packer should have one +-1 bug when looking to transmit CQ message with grid as free text.
Even we fix this packing issue in JTDX this will raise incompatibility between other FT8 programs.
|
|
|
|
Post by OH8EJW, Mikko on Apr 18, 2022 8:35:16 GMT
WSJTX can do this (without KP) so have to go to it. Standard or not, thanks anyway
|
|
