On 12/05/2020 22:16, runninge...@gmail.com wrote:
Hi,
thanks one more time for all the dedicated work with yet another big step
forward in decoding weal signals . !
Let me report that I am no longer able to CAT control my SparkSDR with the
"Hamlib NET rigctl" network server.
My settings are : "localhost:51111" for Network server, which should connect
to my first (out of four) virtual transceiver in SparkSDR (which is
connected to a Hermes Lite II).
Substituting "localhost" with its IP address or hostname does not solve the
problem neither.
The same settings work fine with WSJT-X 2.1.2.
Some more observations :
- The "C:\WSJT\wsjtx\bin>rigctl-wsjtx -m 2 -r localhost:51111 F 7253500 M
LSB 0" command correctly sets the VFO and mode.
- Overwriting the 3 rigctl executables with the release 2.1.2 binaries
yields the same result (sorry but I could not withstand doing this .).
This is on a windows 10 - 64 bit config.
73's and best regards,
Erik
ON4PB
Hi Erik,
I see no mention of you running any form of rigctld, this makes me think
that SparkSDR has hijacked the Hamlib internal network protocol and is
acting as a fake rigctld. If that is so then the authors of SparkSDR
probably need to update their software to conform with the latest Hamlib
network protocol. It may well be that WSJT-X is sending commands that he
fake rigctld server does not understand. Do you get an error from
WSJT-X, if so what is it including the details? Does SparkSDR have an
way of tracing the commands sent to it?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
