On 01/07/2017 13:49, Bill Somerville wrote:
Hi Dave,
thanks for your comments. I will address the last as that seems to be
the area where I think some progress on safety can be made. The last
version of the Commander TCP/IP documentation you sent us states:
++++++++++++++++++++
16. Report transmit status, e.g.
<command:9>CmdSendTX<parameters:0>
returns a single field in ADIF syntax specifying whether the
transceiver is transmitting, e.g.
<CmdTX:3>OFF
or
<CmdTX:2>ON
Not all transceivers respond to this directive.
---------------------------------
The last sentence is ambiguous. What happens if a transceiver does not
respond?
Could this exchange be modified to deal with the above scenario by
responding with OFF until directive has been sent to the rig to ask
it to transmit when it would return ON. To complement the opposite
would be needed for directives to return to receive. I ask this
because at least we could get into the ballpark of when the rig
actually goes to Tx when a sequence of directives to Commander ending
with transmit request are processed.
WSJT-X already has a dedicated thread for rig control and it can
trivially poll using this command once a request to go to Tx has been
sent, it has nothing else to do at this point. How often is acceptable
for a polling rate? We would like to be able to detect the rig PTT
event within 100ms at worst.
Does the above directive respond with ON if RTS or DTR are used to key
the rig when the rig is one that does not have the ability to report
Tx status via a CAT query?
73
Bill
G4WJS.
Hi Dave,
as a further data point. I am experimenting with the Commander TCP/IP
command CmdSendTX and I am seeing an interesting behaviour. Just using
the command after sending a CmdTX command seems to synchronize with the
actual rig PTT event. I assume this is because CmdSendTX is queued in
Commander behind the CmdTX command and the reply cannot be delivered
until the former has been actioned. This is despite the rig I am using
having no CAT command to query PTT (IC-756) so it also appears to answer
my query above about what happens in that case.
I will code a change to WSJT-X than does multiple CmdSendTX commands at
10ms intervals until the expected response occurs or 1s expires. If one
second expires WSJT-X will abort with a suitable error on the basis that
the rig is not working.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
