There's actually another problem going on.I worked with Al a bit this afternoon
using rigctld.Al is the 2nd person I'm working with on the same
problem....after this sequence hamlib just loops around the network_flush()
routine and never returns from it causing WSJT-X to lock up.
So I'm making some debug info to track it down....hopefully have something
figured out tomorrow since Al can reproduce this easily.
This is apparently a common complaint from the Flex users between lockups and
crashes using the flex6xxx backend.
de Mike W9MDB
On Wednesday, February 6, 2019, 6:14:13 PM CST, Bill Somerville
<g4...@classdesign.com> wrote:
On 06/02/2019 20:51, Al wrote:
This is from the SSDR CAT log for the TCP port leading up to the event with TX
inhibited..
19-02-06 14:28:05.123 TCP 26001 [sent]: ZZFI01;
2019-02-06 14:28:05.123 TCP 26001 [rcvd]: IF;
2019-02-06 14:28:05.125 TCP 26001 [sent]:
IF000070740000010+0000000000090000000;
2019-02-06 14:28:35.788 TCP 26001 [rcvd]: TX;
2019-02-06 14:28:35.790 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:35.791 TCP 26001 [sent]: ID909;
2019-02-06 14:28:36.646 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:36.647 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.717 TCP 26001 [sent]: ID909;
2019-02-06 14:28:37.718 TCP 26001 [sent]: ID909;
At this point the only recourse is to kill WSJT-X with the task manager and
restart. I a normal situation the ID; following the first RX, receives an
ID909; response in 100msec and the second RX is not sent.
AL, K0VM
Hi Al,
that's interesting and surprising. The whole point of the ID commands is to
know that the "rig" has completed the prior command. Because the Kenwood style
CAT protocol that is used by SmartSDR, Elecraft and Yaesu as well these days,
has no acknowledgement of set commands; we have no way of telling when it is
safe to send another command. The ID command is used because it is very fast
and changes nothing at the rig, it is effectively a no-op with an
acknowledgement for when the prior command has been processed.
Hard to say without a trace from WSJT-X, but I would guess that the RX command
is taking some time and the timeout is too short so it is being retried.
So I have to wonder why SSDR and the Flex are taking more than one second to
respond to the command sequence "RX;ID;", that's glacial!
You can temporarily adjust the Hamlib timeout by creating a text file in the
WSJT-X log files directory ("Menu->File->Open log file directory") called
hamlib_settings.json and put the following into it:
{
"config": {
"timeout": "2000"
}
}
That will adjust the command timeout to 2 seconds (the default command timeout
for the Flex6xxx driver is 600 mS). Please give it a try and see if that stops
the hang up problem?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
