At the moment:
Is there any need for mode symbol because there are no UDP frames
for decoded JTTY rows?
Somehow I would like to see at least UDP frame from decoded row that
starts with CQ and has properly formatted callsign after that.
That would help external programs to dig out from station's log is the
caller already worked this band/mode.
Now I can produce that kind of information only if caller's call is
typed/clicked into DXCall column. Then #2 Status UDP frame can
transfer callsign to external program.
But if we think about DX hunting or contesting it would be essential to
get information about worked state of all callers that can be decoded
from band without putting their callsigns one by one into DXCall column.
Because sent strings are free formatted digging out information is lot
harder than from strictly formatted FT.
I hope developers can find a way doing this.
Maybe one byte information added to CQ calls and another to reply to
those calls. But it needs then buttons "call CQ" and "answer to CQ" so
that additional
byte can be added to right transmits.
--
Saku
OH1KH
Rick Ellison via wsjt-devel kirjoitti 28.9.2026 klo 6.26:
Hi Sam..
I do not thing a string symbol has been assigned yet. When I was
working with Brian to implement things in N1MM there was not one
available yet..
73 Rick N2AMG
*From:*Sam W2JDB via wsjt-devel <[email protected]>
*Sent:* Sunday, September 27, 2026 10:08 AM
*To:* [email protected]; [email protected]
*Cc:* Sam W2JDB <[email protected]>
*Subject:* Re: [wsjt-devel] Updated docs on the UDP structures that
also includes JTTY
Hi Saku,
Thanks for the reply, I already had this version, was hoping for a
newer version that also includes the mode characters
i.e. WSJTX Mode Index = String = '$@#: &~+90'
representing WSJTX Mode Names = Array [0..9] Of String = ('JT4',
'JT9' , 'JT65', 'QRA64', 'ISCAT', 'MSK144', 'FT8', 'FT4', 'FST4',
'FST4W');
73,
Sam W2JDB
On Sunday, September 27, 2026 at 04:04:17 AM EDT, [email protected]
<[email protected]> wrote:
It seems that logging info via UDP works same way as with FT modes.
Instead there is no monitoring UDPs from decodes, but status
message #2 is there and shows same things (with target call
typed/clicked into DXCall column) as FT modes.
https://github.com/WSJTX/wsjtx/blob/master/Network/NetworkMessage.hpp
shoud hold all information, but there is no mention about JTTY
specific frames.
--
Saku
OH1KH
Sam W2JDB via wsjt-devel kirjoitti 26.9.2026 klo 23.04:
Hi,
Where and if can I find an updated UDP structure doc that also
includes JTTY
Thanks in advance,
73,
Sam W2JDB
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
