Hi there,

I am trying to record my own messages coming from WSJT-X for logging purposes and found that I had to write a small patch. This just adds a new utf8 field, tx_message, at the end of the UDP status packet.

On a related note, the status message seems to be whitespace padded when I use m_currentMessage. Is this normal? Also, has anyone seen "a1" or "a2" at the end of messages coming over UDP? They sometimes show up like that in the UI too.

73,
Morgan

Hi Morgan

Very interesting, I was looking for a way to control a custom Arduino transmitter and realized the UDP interface does not provide the current TX message.
I am parsing the status messages to get the DX call and the transmit status but I need to infer the current TX message and this is a problem for example when calling CQ.

I will try your solution to see if it fits my needs. I think this would be a good addition to the UDP protocol.

Regards
Agustin - LU2HES

Is there a better way I can get this patch visibility? :-)

@LU2HES I've got a Python project in progress that receives WSJT-X UDP messages. Should have something on Github reasonably soon.

Also, the "a1" or "a2" is, as many know, the AP decoding in action. I was just surprised to see it in the output messages! Currently I've got a regex that looks for a run of spaces to parse this out.

73,
Morgan

Hi Morgan

I don't know, I'm new to the community but I think it's a good addition to the UDP protocol.

I used your patch and built everything from source. I'm using this Python library to get the UDP fields:
https://github.com/rstagers/WSJT-X

I added the new fields to the file WSJTXClass.py



Everything is working fine and I'm able to obtain the TX messages for my transmitter!

Thank you!

Regards
Agustin - LU2HES

On 23/11/2020 19:32, Morgan wrote:

Hi there,

I am trying to record my own messages coming from WSJT-X for logging purposes and found that I had to write a small patch. This just adds a new utf8 field, tx_message, at the end of the UDP status packet.

On a related note, the status message seems to be whitespace padded when I use m_currentMessage. Is this normal? Also, has anyone seen "a1" or "a2" at the end of messages coming over UDP? They sometimes show up like that in the UI too.

73,
Morgan

Hi Morgan,

a change based on your patch will be in the next release of WSJT-X. Thanks for your contribution.

WSJT-X messages for block modes like FT8 are fixed length which is why they are space padded on the right.

The information appended to some decoded messages relates to decoder information, e.g. aN and the optional '?' are documented in the WSJT-X User Guide here:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.3.0-rc2.html#_ap_decoding

73
Bill
G4WJS.

Hi Morgan, Bill

Excellent, this is a good feature.

I managed to integrate my custom Arduino transceiver into WSJTX using this. I wrote a small python server that retrieves the status using the UDP interface and then encodes the TX message and send it to the Arduino using the serial port.

I can believe it's working!



Regards
Agustin - LU2HES