Protocol 1 is setting=value. Order does not matter. Can be multiline.
And is forward compatible as new values will just generate warnings on older versions
Put a looplimit on icom_get_ant_count trying to get autodetect to work
Changes to icom_get_ant_count to try and get this working
Added dummy antenna # args to rigs that don't care i.e. only have 1 antenna
This found tons of errors in rig_debug statements
So this patch cleans up all the files that were producing warnings or errors
This should fix a few segfaults when running with debug turned on
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 using separate serial port for PTT via RTS pr DTR it is
convienent to close the port when the PTT line is not asserted. This
allows other applications to share the PTT serial port.
This has been achieved by ensuring that file descriptor for the port
is set to -1 when the port is closed, this then allows the invalid FD
to be used as a PTT surrogate for the rig_get_ptt API when the port is
only being used for PTT.
This change allows the set_mode functions to leave the rig passband
unchanged if required. For the few rigs that do not have explcit
passband width control either current state is read and rewritten or a
"normal" width is chosen e.g. select a normal width when there is a
choice like CW and CW-NARROW.
Because the dummy rig provides a get_ptt function it must look at the
hardware PTT if that is being used and or that state into its result.
This issimilar to a real rig that would be in tx because of the
control line.
In response to a long standing request from Tor, N4OGW, and others, RIT
and XIT are added as members for the rig_set/get_func() members.
"RIT"/"XIT" have been added as tokens. The dummy rig backend and
testrig.c have been updated for these new functions.
Applications should test a backend with the rig_has_set/get_func() and
test for RIG_FUNC_RIT or RIG_FUNC_XIT. A non-zero result indicates
these functions are implemented by a given rig backend. It will take
some time for all backends to migrate to this new implementation. Once
implemented, RIT or XIT should be set to '0' to 'clear' the value
without deactivating the rig's RIT/XIT function. The dummy/dummy.c file
can be used as a simple guide for backend authors implementing this
behavior.
* fix bug in set/get_func
* better range checking of memory channel number
* implemented RIG_OP_TOGGLE
* frequency dependent LEVEL_STRENGTH
* some caps update
git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@2911 7ae35d74-ebe9-4afe-98af-79ac388436b8
Mikael Nousiainen