RX/TX will show correct answers at startup based on rig current status
This sequence is for the dummy device
Rig command: F RX
Frequency: 14500000
Rig command: F TX
Frequency: 14500000
Rig command: V VFOB
Rig command: F 16000000
Rig command: V VFOA
Rig command: S 1 VFOB
Rig command: V TX
Rig command: f
Frequency: 16000000
Rig command: S 0 VFOA
Rig command: f
Frequency: 145000000
What should this behavior be? Return VFOA or VFOB or error?
Rig command: S 0 VFOB
Rig command: f
Frequency: 16000000
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.