When setting position, an EasyComm I command sequence was being
sent to EasyComm II controllers. Since this sequence is not valid
for EasyComm II, controllers were forced to implement the older
format to work with rotctl. Instead, send the EasyComm I command
sequence only to EasyComm I controllers, and send a valid sequence
to EasyComm II controllers.
Passing a buffer to easycomm_transaction causes it to wait for a
response. Most commands, though, do not provide a response, so
this causes a timeout. Pass no buffer instead, so that no response
is expected.
netrigctl_transaction() returns either an error code (-ve int),
RIG_OK, or the number of characters read from the protocol stream. +ve
return values indicate successful parsing of stream data, not an
error.
The \chk_vfo command to rigctl_parse() accepts an extended response
prefix but does not act upon it, instead it is held over until the
next command. This seems unnecessary as an extended response prefix
can just as easily be added to the following command if required. By
removing this carried over state the processing of commands can be
greatly simplified as per this commit.
Add value of ackbuf into value of val instead of
the address, because isn't the same after the call
of function easycomm_rot_get_conf().
Signed-off-by: Agis Zisimatos <agzisim@gmail.com>
The conditional expression in which the speed parameter is validated
is such that it can never become true. This looks like an error
inadvertently introduced.
Signed-off-by: Vasilis Tsiligiannis <acinonyx@openwrt.gr>
This command exists on the FT-991, but the FT-891 returns
"?". Replacing this command with the ST; command that exists as per
the CAT reference, everything falls into place.
This patch enables me to use WSJT-X with rigctld.
WSJT-X was outputing a "timeout while getting VFO frequency" error.