on the real rig. In rigctl_parse.c, we make sure that invalid attempts to
so so are mapped on a safe variant.
Second change to netrigctl: drain the input line before sending a new
command, to reach sync again after a timeout.
Separate FT-891 features
Fix rigctl and rigctld to not abort on function not available
Change Yaesu detection of FA length to automatic method instead of rig specific
Although there is no reasonable recovery from SIGPIPE we do not want
to terminate the server process, just the client servicing thread. We
do this by setting the disposition for SIGPIPE to ignored, this causes
an EPIPE to be returned from blocked write() and send() calls that end
up trying to send to a broken pipe/socket.
Add driver for SPID MD-01 and MD-02 in ROT2 mode. The MD-01 and MD-02
extend the command set from the original ROT2PROG and deviate slightly
from the original protocol on the set_position command.
The rig frontend may be able to emulate RIG_LEVEL_STRENGTH by using
RIG_LEVEL_RAWSTR and an S-meter calibration curve. The netrig client
doesn't know this so it must pass STRENGTH queries regardless if it
knows a RIG_LEVEL_RAWSTR query is allowed. If the server cannot oblige
it will return a -RIG_EINVAL error which should be fine.
This option is obsolete since Apple gcc 3.0, by dropping support for
gcc 2.95.x we no longer have to pass this option. By not passing this
option we sidestep an issue for Mac OS X when a GNU gcc compiler is
used to build instead Apple gcc or clang.
When the PTT serial port is not the control port the intention is to
free the port when PTT is reset so that other applications can share
it. This logic was faulty with attempts to call port functions on an
unopened port when repeatedly calling the rig_set_ptt API.
Thanks to Christoph van Wullen, DL1YCF, for finding and analyzing this
defect.
The FT817-ND only has RTTY, PSK31-L, PSK31-U, USER-L, USER-U as
possible DIG MODEs. Before this fix, the modes read by Hamlib were
completely wrong.
The RTTY mode in the FT817-ND is USB. I think that the corresponding
Hamlib mode is RIG_MODE_RTTYR but I'm not certain if this is supposed to
be USB or LSB.
This has been tested on an FT817-ND. The FT817 might be different.
The FT817-ND only has RTTY, PSK31-L, PSK31-U, USER-L, USER-U as
possible DIG MODEs. Before this fix, the modes read by Hamlib were
completely wrong.
The RTTY mode in the FT817-ND is USB. I think that the corresponding
Hamlib mode is RIG_MODE_RTTYR but I'm not certain if this is supposed to
be USB or LSB.
This has been tested on an FT817-ND. The FT817 might be different.
The FT991 only receives on VFO A, VFO B is only used for split Tx or
for exchanging with VFO A. There are no commands to set or query VFO B
mode. Added a set split mode function that saves VFO A mode and VFO b
frequency then sets the required VFO B mode into VFO A and then copies
VFO A to VFO B and restores the VFO B frequency and VFO A
mode. Bandwidth and narrow settings are not touched.
Several functins that had been implemented specifically for the FT991
have been removed because existing newcat.c functions were suitable or
there should not have been a function as the rig doesn't support it.
