4 Commity (3dbbe02b78d18fb3a69c02995d035e2bc4dfc96f)

Autor	SHA1	Wiadomość	Data
Mikael Nousiainen	3dbbe02b78	Add new levels: RFPOWER_METER, COMP_METER, VD_METER and ID_METER, supported at least by most of recent Icom rigs. Add level NOTCHF_RAW for manual notch frequency without specified unit for Icom rigs. Add level MONITOR_GAIN. Add functions DUAL_WATCH and DIVERSITY, supported now by K3/K3S. Fix VOXDELAY level commands for many Icom rigs. Add MONITOR_GAIN level for Icom rigs. Fix and add many K3 commands and add specific rig models for K3S, KX2 and KX3 -- they are very similar to K3, but have slight differences. Extend dump_caps output for rigctl: add complete details of ext levels and frequency ranges. Tests have been performed on IC-7000, IC-756ProIII, IC-7300, IC-7600 and K3.	2019-05-30 09:37:49 +03:00
Bill Somerville	b0f6955740	Added option to not use VFO XCHG command when setting split parameters. ... With Icom rigs that use MAIN?SUB VFOs there is a trade off when setting the mode or frequency of the "other" VFO. Untill now Hamlib uses the XCHG VFO command to address the "other" VFO. This has some advantages, particularly it preserves the selected VFO and it preserves memory mode of either VFO. The disadvantage is that any split command causes the Rx to glitch when the VFO/MEMs are exchanged. I have added a config parameter for Icom rigs called "no_xchg" which forces the direct addressing of VFOs to set split mode/frequency. It is a boolean option with a default of "0" (false) which equates to prior behaviour. Setting it to "1" (true) will make the backend use change VFO commands to set the "other" VFO. This means that TX on "SUB" in split is assumed, that both are in VFO mode (not MEM), and set/get split functions will leave the MAIN VFO selected.	2014-03-20 18:36:43 +00:00
Nate Bargmann	78285ab8eb	Update LGPL header in Icom source files. ... TNX to Lucian Laga, YO6PLB, for the notification.	2011-08-22 21:38:35 -05:00
Stephane Fillod	01db7a309f	Add IC-R9500	2011-03-28 18:56:05 +02:00