Menu
▾
▴
[Hamlib-developer] [Hamlib/Hamlib] b61dd1: G90: fix over-claimed capabilities and RFPOWER BCD...
|
From: Nate B. <no...@gi...> - 2026-09-20 14:10:42
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b61dd14d461f35f4d6143993f8cbd1386af98847 https://github.com/Hamlib/Hamlib/commit/b61dd14d461f35f4d6143993f8cbd1386af98847 Author: jbdubbs <ja...@we...> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M rigs/icom/xiegu.c M simulators/simxiegug90.c Log Message: ----------- G90: fix over-claimed capabilities and RFPOWER BCD decode Corrects rigs/icom/xiegu.c only. Backend version .11 -> .12. New G90_ALL_RX_MODES/G90_FUNCS/G90_LEVELS/G90_MEM_CAP macros, replacing the shared X108G_* macros for the G90 only. Removed: - RIG_FUNC_NR / RIG_LEVEL_NR: no NR on this rig - RIG_LEVEL_VOXDELAY, RIG_FUNC_ARO: not implemented on this rig - RIG_LEVEL_MICGAIN/PBT_IN/PBT_OUT/NOTCHF_RAW/VOXGAIN/ALC/BKINDL/COMP: undocumented 0x14 subcommands, manual states these return a fixed 255 - VHF/UHF + 6m/2m/70cm ranges: HF+60m only, 0.5-30MHz. Max power 100W -> real 20W. - RIG_MODE_WFM: not a real mode on this rig Kept: - RIG_LEVEL_RF, RIG_MODE_FM: undocumented but confirmed working - RIG_MODE_FMN: same CI-V byte as FM (0x05), not a distinct mode Added/fixed: - RIG_FUNC_TUNER: built-in ATU (0x1C/0x01) - g90_get_level() override for RIG_LEVEL_RFPOWER: clamps to 1.0 against a non-conformant BCD byte (0x5f) the rig sends at full power - Simulator: malformed-BCD RFPOWER repro at max power Commit: 0c56dafd8fd0a042717cccd5da0610914cfb80a9 https://github.com/Hamlib/Hamlib/commit/0c56dafd8fd0a042717cccd5da0610914cfb80a9 Author: Nate Bargmann <n0...@n0...> Date: 2026-09-20 (Sun, 20 Sep 2026) Changed paths: M rigs/icom/xiegu.c M simulators/simxiegug90.c Log Message: ----------- Merge GitHub #2153 Compare: https://github.com/Hamlib/Hamlib/compare/bfea1769f3ad...0c56dafd8fd0 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
