hamlib-developer — hamlib developers forum

[Hamlib-developer] GTTY a new RTTY terminal using HamLib

[Gordon Y. <gor...@pr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,
I'm Gordon, WA8Q. I've just released gtty, a GTK4/libadwaita RTTY terminal for Linux, and Hamlib is what connects it to the station, so I wanted you and the list to know about it.
https://github.com/gjyoung1974/gtty

Hamlib handles frequency and mode, PTT via CAT, DTR or RTS, TX-mode switching, and NET rigctld. The AppImage bundles Hamlib 4.6.2. Rig-side features that may interest the project: FSK keying through an ordinary USB serial adapter (custom 45.45 baud, 5N2 on TXD), and a CAT text keyer path for the Elecraft K3/K4/KX3 and Kenwood TS-890.

I'm developing against an FT-710 and would welcome reports from other rigs. If there's a place you list applications that use Hamlib, I'd be glad to be added. I'd also like to add my condolences on Mike's passing; his work is in every rig I've ever controlled from Linux.

GPL-3.0-or-later, Debian/Ubuntu .deb and AppImage on the releases page.

73s, Gordon WA8Q

Sent with Proton Mail secure email.
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsC5BAEBCgBtBYJq8hvLCRCprHln++gNbUUUAAAAAAAcACBzYWx0QG5vdGF0
aW9ucy5vcGVucGdwanMub3JnjDH+C8jCbj5ZVHPylLQWtXMzCeoTOCZan2Na
iBCfHV0WIQSqMdXCFiV8kKrbrUGprHln++gNbQAA2+cH/0d1eVVv3VJ1H6Yl
A1ycc/DbQGAoMwFFwNRhxutKpIyotWQmIbGF4soUayyaszhC7eGSWVcI3bTl
YrBT5At83RBrZ7z0QxCTKamOjCEWki8xRNAtIizuPn949PVEcG9hpQ93wl5h
zdspiNA2QPkZhPW5IzCtNiQD46cm3Hpkjofidh4kDRJryPAkh+/yB8Sy9glI
Yw3TGtRNb8hO+HGocVAscv3O6pfHSA9e3pXo1apY77MXrUFQLsxs1Q2qd1MT
g/0B+kZ2vqFWEm2ATVrQ243KZmcJP9FuLanBPoAUAf+++V6QM/k4nqsFVT5o
xH0ceKduJFruoq+TpyO2W5z4Y/A=
=nQWT
-----END PGP SIGNATURE-----

[Hamlib-developer] Hamlib error: rig_get_freq(2669): vfo_opt=0, model=1022 ft857_get_freq: called

[Michael B. <f6...@mi...>]

Hello. Receive following error trying to TEST CAT in WSJT-X 3.0.2
Hamlib error: rig_get_freq(2669): vfo_opt=0, model=1022
ft857_get_freq: called
check_cache_timeout: cache invalid
ft857_get_status: called
write_block(): TX 5 bytes
0000 00 00 00 00 03 .....
read_block_generic called, direct=1
read_block_generic(1194): retrying read timeout 1/1 timeout=100ms
read_block_generic(): Timed out 0.224269 seconds after 0 chars, direct=1
rig_get_freq(2688): freqMainA=0, modeMainA=, widthMainA=0
rig_get_freq(2688): freqMainB=0, modeMainB=, widthMainB=0
rig_get_cache(332): vfo=None, current_vfo=None
rig_get_cache(527): vfo=VFOA, freq=0, mode=, width=0
rig_set_cache_freq(172): vfo=None, current_vfo=None
1:rig_get_freq: elapsed=249ms
rig_lock: client lock disengaged
1:rig.c(2802):rig_get_freq returning(-5) Communication timed out
Communication timed out
Communication timed out
while getting current VFO frequency
Timestamp: 2026-11-07T02:12:33.883Z


NOTE: VARA HF 4.9.0.0 works just fine and controls via cat without issue.
NOTE: FT-857 is configured with front mic CAT because rear CAT is being used for FC-30 control.
NOTE: Config worked under WSJT-X 2.6.1 in June and was not updated. Currently fails. Have not used WSJTX-X since that time. After initial failure, upgraded WSJT-X to 3.0.2 and same failure occur
red. Logs taken in diagnostic mode of WSJTX-X 3.0.2 and are attached.


"Every act of art is an act of resistance." - Tom Morello

Peace and be kind,

KO4WX

Michael Boatright, M. Photog., CPP, GSD

[Hamlib-developer] TCI Client Not Working With OpenX6x00

[Al P. <k6...@ic...>]

Using WSJTx with TCI Client RX1 for audio and CAT works well with Thetis and other SDR’s like deskHPSDR. This setup gives “Rig Failure TCI SDR is not switched On” when used with an X6100 running latest OpenX6x00 TCI service. OpenX6x00 TCI works fine with RTTY-TCI, another TCI client app. The OpenX6x00 TCI client does show a momentary connection from WSJTx when “test CAT” is clicked.  I tried a few other radio clients in the latest HamLib that have network connections, but did not find one that would connect at all to the X6100/OpenX6x00 TCI service.

The same thing is true of a couple other new X6100 fw versions having TCI that I tried.

Re: [Hamlib-developer] RIG failure

[Uwe, D. <dg...@gm...>]

Hi Robert,

The following two lines in your RigControl.log file indicate that the 
COM port you selected is already in use, which would explain the Rig 
Error message:
serial_open: serial port COM12 is already open
rig.c(1278):rig_open returning2(-22) Access denied

Do you happen to have any other programs open that are also accessing 
your rig?

Otherwise: Have you tried simply restarting your computer? Because a 
ws.exe process that’s hanging—for whatever reason—could also cause 
something like this. BTW: You usually don’t need to reinstall the 
program in cases like this, since there’s a specific reason for the 
problem that needs to be identified.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB


Am 18.10.2026 um 16:12 schrieb Robert Post, Ph.D., PA via Hamlib-developer:
> PLEASE HELP! I WS was running fine. I turned off my computer to go 
> feed my dog and when I came back and turned it back on again all I get 
> is Rig ERROR.   I have checked the computer settings for baud rate all 
> is fine. The configure settings are all OK. The program is running but 
> the computer isn't connected. I have removed and reinstalled WS with 
> no help.
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

[Hamlib-developer] RIG failure

[Robert P. Ph.D.,P. <re...@ya...>]

PLEASE HELP! I WS was running fine. I turned off my computer to go feed my dog and when I came back and turned it back on again all I get is Rig ERROR.   I have checked the computer settings for baud rate all is fine. The configure settings are all OK. The program is running but the computer isn't connected. I have removed and reinstalled WS with no help.

[Hamlib-developer] [Hamlib/Hamlib] 8f17dc: ftx1: assume tuner status on when using ATAS antenna

[Terrell D. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 8f17dcb932ba1d2a12062d605c03892a8a8cca6f
      https://github.com/Hamlib/Hamlib/commit/8f17dcb932ba1d2a12062d605c03892a8a8cca6f
  Author: Miao Wang <sha...@gm...>
  Date:   2026-08-22 (Sat, 22 Aug 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1_tx.c

  Log Message:
  -----------
  ftx1: assume tuner status on when using ATAS antenna

When using ATAS antenna, there is no such concept of enabling or
disabling the tuner. We can assume that the tuner is always on when
using ATAS antenna. The user will see the tuner status as "on" and is
thus able to trigger the tune process.


  Commit: da925ab930bd11837b1eb9c3148d9a65a16ae9da
      https://github.com/Hamlib/Hamlib/commit/da925ab930bd11837b1eb9c3148d9a65a16ae9da
  Author: Terrell Deppe <62b...@pr...>
  Date:   2026-10-14 (Wed, 14 Oct 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1_tx.c

  Log Message:
  -----------
  Merge pull request #2168 from shankerwangmiao/pr-ftx-1-tuner

ftx1: assume tuner status on when using ATAS antenna


Compare: https://github.com/Hamlib/Hamlib/compare/470518f35cfd...da925ab930bd

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

Re: [Hamlib-developer] Using rigctlcom => flrig => IC-7300

[Daniele F. <iu...@gm...>]

I created https://github.com/Hamlib/Hamlib/issues/2251 to keep track
of this limitation.

-- 
73 de IU5HKX Daniele

Re: [Hamlib-developer] Using rigctlcom => flrig => IC-7300

[<gm...@bt...>]

Hi Daniele,

Thank you for getting back to me. It appears that DA was a figment of Gemini's imagination. I've looked over the thread and I couldn't find the reference to where it got that from.

The other solution could be to extend the list of values supported by MD (to a more recent Yaesu rig, maybe).

I was thinking it should be handled in rigctlcom.

There are other ways around this issue, so park it for now.

73 Phil GM3ZZA
________________________________
From: Daniele Forsi <iu...@gm...>
Sent: 11 October 2026 10:29 PM
To: Hamlib Developers Mailingliste <ham...@li...>
Subject: Re: [Hamlib-developer] Using rigctlcom => flrig => IC-7300

Hello Phil,

> As I understand it rigctlcom emulates the TS-2000 CAT interface

that's correct

> which does not have an equivalent of these data modes. It seems to have a DA 0/1; command
> that sets data mode separately but this does not seem to get combined in with the preceding Mdn; command.

I'm looking at this manual
https://www.kenwood.com/usa/Support/pdf/TS-2000-Owner-Manual.PDF
but there isn't a DA command

> If I have this wrong then please let me know. Would it be worth it if I looked at somehow concatenating the MD/DA pair?

Which software would get this modification?
How would you get your IC-7300 to switch to the correct mode?

--
73 de IU5HKX Daniele


_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

[Hamlib-developer] [Hamlib/Hamlib] 1103f9: Merge pull request #2170 from dchristle/ftx1-monit...

[dforsi <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 1103f9bd91ad59f336eaa7757cb1455efe14abc0
      https://github.com/Hamlib/Hamlib/commit/1103f9bd91ad59f336eaa7757cb1455efe14abc0
  Author: dforsi <iu...@gm...>
  Date:   2026-10-11 (Sun, 11 Oct 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1.h
    M rigs/yaesu/ftx1/ftx1_audio.c
    M rigs/yaesu/ftx1/ftx1_tx.c
    M tests/testftx1parsers.c

  Log Message:
  -----------
  Merge pull request #2170 from dchristle/ftx1-monitor-safety

fix(ftx1): prevent monitor control from keying transmitter

(cherry picked from commit 470518f35cfd6f3b1ce12a8d111e4bb2c1efd26d)


  Commit: fe03d2d3ad5669894c8f594a58f001dc22e3f183
      https://github.com/Hamlib/Hamlib/commit/fe03d2d3ad5669894c8f594a58f001dc22e3f183
  Author: dforsi <iu...@gm...>
  Date:   2026-10-11 (Sun, 11 Oct 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1.h
    M rigs/yaesu/ftx1/ftx1_audio.c
    M rigs/yaesu/ftx1/ftx1_tx.c
    M tests/testftx1parsers.c

  Log Message:
  -----------
  Merge pull request #2250 from dforsi/Hamlib-4.7

Merge pull request #2170 from dchristle/ftx1-monitor-safety


Compare: https://github.com/Hamlib/Hamlib/compare/0aa18bfd11b9...fe03d2d3ad56

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

Re: [Hamlib-developer] Using rigctlcom => flrig => IC-7300

[Daniele F. <iu...@gm...>]

Hello Phil,

> As I understand it rigctlcom emulates the TS-2000 CAT interface

that's correct

> which does not have an equivalent of these data modes. It seems to have a DA 0/1; command
> that sets data mode separately but this does not seem to get combined in with the preceding Mdn; command.

I'm looking at this manual
https://www.kenwood.com/usa/Support/pdf/TS-2000-Owner-Manual.PDF
but there isn't a DA command

> If I have this wrong then please let me know. Would it be worth it if I looked at somehow concatenating the MD/DA pair?

Which software would get this modification?
How would you get your IC-7300 to switch to the correct mode?

-- 
73 de IU5HKX Daniele

[Hamlib-developer] Using rigctlcom => flrig => IC-7300

[<gm...@bt...>]

I am using rigctlcom to provide CAT for MMSSTV running under Wine on Debian. I am using flrig to provide multiple apps access to my IC-7300 (*). MMSSTV allows me to set the frequency for the SSTV calling channels unfortunately 7 MHz is LSB and 14 Mhz and above are USB. On top of that to enable USB audio I need to set the IC-7300 into data mode (i.e. LSB-D and USB-D - aka PKT-LSB and PKT-USB).

As I understand it rigctlcom emulates the TS-2000 CAT interface which does not have an equivalent of these data modes. It seems to have a DA 0/1; command that sets data mode separately but this does not seem to get combined in with the preceding Mdn; command.

If I have this wrong then please let me know. Would it be worth it if I looked at somehow concatenating the MD/DA pair?

73 Phil GM3ZZA.

(*) Yes it's a convoluted path.
1. MMSSTV communicates with a virtual COM1 port in Wine using TS-2000 CAT commands.
2. Wine associates COM1 with one of a virtual serial port pair forwarding the command.
3. Rigctlcom listens to the other end of the virtual serial port pair.
4. Rigctlcom  converts the TS-2000 CAT commands to flrig's XMLRPC command set and sends the request over an internal IP port.
5. Flrig actions the RPC command and converts it into IC-7300 CI-V serial command sent over USB.
6. The IC-7300 converts it back to serial and executes it sending a response all the way back the way.

[Hamlib-developer] [Hamlib/Hamlib] 6a2ca9: fix(ftx1): prevent monitor control from keying tra...

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 6a2ca979ab359b4f46b5da01818af5f0473dacad
      https://github.com/Hamlib/Hamlib/commit/6a2ca979ab359b4f46b5da01818af5f0473dacad
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1.h
    M rigs/yaesu/ftx1/ftx1_audio.c
    M rigs/yaesu/ftx1/ftx1_tx.c
    M tests/testftx1parsers.c

  Log Message:
  -----------
  fix(ftx1): prevent monitor control from keying transmitter

Map Hamlib monitor control to the FTX-1 ML on/off selector.

Keep ML1 monitor gain separate and validate both response formats.

Fixes: 6362407aa967 ("Add Yaesu FTX-1 backend driver")


  Commit: 470518f35cfd6f3b1ce12a8d111e4bb2c1efd26d
      https://github.com/Hamlib/Hamlib/commit/470518f35cfd6f3b1ce12a8d111e4bb2c1efd26d
  Author: dforsi <iu...@gm...>
  Date:   2026-10-11 (Sun, 11 Oct 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1.h
    M rigs/yaesu/ftx1/ftx1_audio.c
    M rigs/yaesu/ftx1/ftx1_tx.c
    M tests/testftx1parsers.c

  Log Message:
  -----------
  Merge pull request #2170 from dchristle/ftx1-monitor-safety

fix(ftx1): prevent monitor control from keying transmitter


Compare: https://github.com/Hamlib/Hamlib/compare/7a556dbfc806...470518f35cfd

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 7e7815: fix(icom): normalize KEYERTYPE parameter values

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 7e78154e1e3c664176c5473660959c2b1b9d0645
      https://github.com/Hamlib/Hamlib/commit/7e78154e1e3c664176c5473660959c2b1b9d0645
  Author: David Christle <dch...@us...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M rigs/icom/icom.c
    M tests/testicomfallback.c

  Log Message:
  -----------
  fix(icom): normalize KEYERTYPE parameter values

Icom decodes KEYERTYPE replies as integers even though the public
parameter is string-valued. Convert valid radio values to stable numeric
strings and reject out-of-range replies before callers format them.

Cover all valid values, malformed input, and rejected transactions
through an IC-785x CI-V exchange.


  Commit: 7a556dbfc80649ddbceedf5b8f8627b990671594
      https://github.com/Hamlib/Hamlib/commit/7a556dbfc80649ddbceedf5b8f8627b990671594
  Author: dforsi <iu...@gm...>
  Date:   2026-10-03 (Sat, 03 Oct 2026)

  Changed paths:
    M rigs/icom/icom.c
    M tests/testicomfallback.c

  Log Message:
  -----------
  Merge pull request #2230 from dchristle/fix/icom-keyertype-value

fix(icom): return valid KEYERTYPE strings


Compare: https://github.com/Hamlib/Hamlib/compare/54f427aa3e67...7a556dbfc806

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 11ff52: fix(core): snapshot mode routing after acquiring t...

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 11ff5246f3d8b77c95d2b7fabb6217fc7194fcda
      https://github.com/Hamlib/Hamlib/commit/11ff5246f3d8b77c95d2b7fabb6217fc7194fcda
  Author: David Christle <dch...@us...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M src/rig.c
    M tests/testcachemode.c

  Log Message:
  -----------
  fix(core): snapshot mode routing after acquiring the API lock

Read PTT and current VFO state after API serialization so a queued mode
request observes preceding PTT and VFO changes. Retain the cache-locked
snapshot to preserve coherent routing reads.

Extend the Dummy mode tests with deterministic interleavings for PTT on,
PTT off, and current-VFO changes while a mode request waits for the lock.

Fixes: 26b1ac264 ("fix(cache): synchronize cache and routing state")


  Commit: 54f427aa3e67658eda4677a18b703b75d5b03dd5
      https://github.com/Hamlib/Hamlib/commit/54f427aa3e67658eda4677a18b703b75d5b03dd5
  Author: dforsi <iu...@gm...>
  Date:   2026-10-03 (Sat, 03 Oct 2026)

  Changed paths:
    M src/rig.c
    M tests/testcachemode.c

  Log Message:
  -----------
  Merge pull request #2232 from dchristle/fix/set-mode-routing-lock

fix(core): prevent stale PTT and VFO checks in rig_set_mode


Compare: https://github.com/Hamlib/Hamlib/compare/50b2a9310edc...54f427aa3e67

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] ce82e1: fix(dummy): bound network AGC level parsing

[dforsi <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: ce82e149e7da270673c8956cecf7ac0c2e48d3d8
      https://github.com/Hamlib/Hamlib/commit/ce82e149e7da270673c8956cecf7ac0c2e48d3d8
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M rigs/dummy/dummy_common.c
    M rigs/dummy/dummy_common.h
    M rigs/dummy/netrigctl.c
    M rigs/dummy/quisk.c
    M tests/Makefile.am
    A tests/testnetrigctl.c

  Log Message:
  -----------
  fix(dummy): bound network AGC level parsing

Peer-provided AGC level lists were parsed with a stale index and could write beyond the fixed eight-entry arrays. Share a bounded parser between the NET rigctl and Quisk backends, add regression coverage, and register the test in the 4.7 test lists.


  Commit: 6e631b81a682224c5c431e35064c8704046b70ff
      https://github.com/Hamlib/Hamlib/commit/6e631b81a682224c5c431e35064c8704046b70ff
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M tests/Makefile.am

  Log Message:
  -----------
  build(tests): compile AGC parser helper directly

Tests-subdirectory builds can reuse a stale dummy backend archive, which may omit parser helpers. Compile dummy_common.c directly into testnetrigctl so Automake rebuilds the code under test.


  Commit: 0aa18bfd11b9ad38a5b8fb47634c13141f1ea1ec
      https://github.com/Hamlib/Hamlib/commit/0aa18bfd11b9ad38a5b8fb47634c13141f1ea1ec
  Author: dforsi <iu...@gm...>
  Date:   2026-09-27 (Sun, 27 Sep 2026)

  Changed paths:
    M rigs/dummy/dummy_common.c
    M rigs/dummy/dummy_common.h
    M rigs/dummy/netrigctl.c
    M rigs/dummy/quisk.c
    M tests/Makefile.am
    A tests/testnetrigctl.c

  Log Message:
  -----------
  Merge pull request #2169 from dchristle/backport/4.7-testnetrigctl-build

build(tests): backport testnetrigctl build fix to 4.7


Compare: https://github.com/Hamlib/Hamlib/compare/3e2ef2cd646f...0aa18bfd11b9

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] d034b2: Merge pull request #2161 from dchristle/fix/usrp-i...

[dforsi <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: d034b23659ae4e82e5625e0c13723e0478c15e23
      https://github.com/Hamlib/Hamlib/commit/d034b23659ae4e82e5625e0c13723e0478c15e23
  Author: dforsi <iu...@gm...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M rigs/kit/usrp_impl.cc
    M tests/Makefile.am
    A tests/testusrp.cc

  Log Message:
  -----------
  Merge pull request #2161 from dchristle/fix/usrp-if-mix-freq-init

fix(usrp): initialize backend state safely

(cherry picked from commit 50b2a9310edc4a481d8a6ef10e948ea8554f97f9)


  Commit: 3e2ef2cd646f1b55e8c0ae5fa07fa407a8c9d8a5
      https://github.com/Hamlib/Hamlib/commit/3e2ef2cd646f1b55e8c0ae5fa07fa407a8c9d8a5
  Author: dforsi <iu...@gm...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M rigs/kit/usrp_impl.cc
    M tests/Makefile.am
    A tests/testusrp.cc

  Log Message:
  -----------
  Merge pull request #2235 from dforsi/Hamlib-4.7

Merge pull request #2161 from dchristle/fix/usrp-if-mix-freq-init


Compare: https://github.com/Hamlib/Hamlib/compare/13a7c0750f8d...3e2ef2cd646f

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] cc7741: fix(usrp): initialize backend state safely

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: cc7741ca8d7cc13c12fb1b997ac9c8429cba3655
      https://github.com/Hamlib/Hamlib/commit/cc7741ca8d7cc13c12fb1b997ac9c8429cba3655
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M rigs/kit/usrp_impl.cc
    M tests/Makefile.am
    A tests/testusrp.cc

  Log Message:
  -----------
  fix(usrp): initialize backend state safely

Initialize the USRP private state with valid defaults and retain receiver ownership through cleanup.


  Commit: 15249506e17954c78f5d9ecebe6106dad090850c
      https://github.com/Hamlib/Hamlib/commit/15249506e17954c78f5d9ecebe6106dad090850c
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M rigs/kit/usrp_impl.cc

  Log Message:
  -----------
  Fix build failure

Fixes:
usrp_impl.cc: In function 'int usrp_init(RIG*)':
usrp_impl.cc:49:5: error: 'STATE' was not declared in this scope; did you mean 'ESTALE'?
   49 |     STATE(rig)->priv = priv;
...


  Commit: 50b2a9310edc4a481d8a6ef10e948ea8554f97f9
      https://github.com/Hamlib/Hamlib/commit/50b2a9310edc4a481d8a6ef10e948ea8554f97f9
  Author: dforsi <iu...@gm...>
  Date:   2026-09-22 (Tue, 22 Sep 2026)

  Changed paths:
    M rigs/kit/usrp_impl.cc
    M tests/Makefile.am
    A tests/testusrp.cc

  Log Message:
  -----------
  Merge pull request #2161 from dchristle/fix/usrp-if-mix-freq-init

fix(usrp): initialize backend state safely


Compare: https://github.com/Hamlib/Hamlib/compare/f20d4df79d2e...50b2a9310edc

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] a8aa0e: fix(yaesu): preserve legacy NewCAT bandwidth handling

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: a8aa0e229db40f4b937167c42d50c62b1bbb348a
      https://github.com/Hamlib/Hamlib/commit/a8aa0e229db40f4b937167c42d50c62b1bbb348a
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M rigs/yaesu/newcat.c
    M tests/Makefile.am
    A tests/testnewcatwidth.c

  Log Message:
  -----------
  fix(yaesu): preserve legacy NewCAT bandwidth handling

FT-450, FT-450D, and FTDX9000 caps do not provide private
width tables. Shared width selection dereferenced the null caps before
the legacy mapping in both the mode set and get paths.

Centralize width-table selection behind a null-safe helper and cover
legacy USB and CW round trips with socket-backed tests.

Fixes: 4053430b621b ("More trading a little more data for less code")
Fixes: 6ad414dc8275 ("Start converting get_rx_bandwidth to common CW/RTTY/SSB handling")


  Commit: f20d4df79d2ea697490c801ba4320348a2ef29bf
      https://github.com/Hamlib/Hamlib/commit/f20d4df79d2ea697490c801ba4320348a2ef29bf
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M rigs/yaesu/newcat.c
    M tests/Makefile.am
    A tests/testnewcatwidth.c

  Log Message:
  -----------
  Merge GitHub PR #2158


Compare: https://github.com/Hamlib/Hamlib/compare/9e224cc54a9b...f20d4df79d2e

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] f3db09: fix(rigctld): quiesce stream feeders before rig close

[David C. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: f3db0910413a7783af0c2a0a8f95bad2ffc45fb7
      https://github.com/Hamlib/Hamlib/commit/f3db0910413a7783af0c2a0a8f95bad2ffc45fb7
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M test/test_netrigctl_stream.c
    M test/test_rigctld_stream.c
    M tests/rigctld.c
    M tests/rigctld_stream.c
    M tests/rigctld_stream.h

  Log Message:
  -----------
  fix(rigctld): quiesce stream feeders before rig close

rig_close() frees backend stream handles while rigctld feeders may still use them, allowing an idle client disconnect to trigger a use-after-free.

Centralize rig shutdown behind registry-wide feeder teardown and close client-owned streams before the last-client idle transition. Add registry and end-to-end regression coverage for abrupt disconnect and reopen.


  Commit: 96ba014a9b0f208f5ba0e8b49c06c0dac6430ed7
      https://github.com/Hamlib/Hamlib/commit/96ba014a9b0f208f5ba0e8b49c06c0dac6430ed7
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M test/test_rigctld_commands.c
    M tests/rigctl_parse.c

  Log Message:
  -----------
  fix(rigctld): guard stream handles during control calls

Feeder auto-close can free a backend stream after a registry lookup unlocks but before the public API acquires its lifetime guard. Keep the registry lock through pause, resume, and drain calls, and verify the invariant with backend probe hooks.


  Commit: 9e224cc54a9bc04f8bce8afe076e4fd2ec152995
      https://github.com/Hamlib/Hamlib/commit/9e224cc54a9bc04f8bce8afe076e4fd2ec152995
  Author: David Christle <dch...@us...>
  Date:   2026-09-21 (Mon, 21 Sep 2026)

  Changed paths:
    M tests/rigctld.c

  Log Message:
  -----------
  fix(rigctld): clean up client thread launch failures

Destroy detached-thread attributes after every initialized launch attempt. Close the accepted socket and release its connection data when attribute setup or pthread_create fails, using the portable socket helper on all early rejection paths.


Compare: https://github.com/Hamlib/Hamlib/compare/79b5e29d8d90...9e224cc54a9b

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] ea7099: make return codes negative

[dforsi <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: ea70993aa6f5ce368257fe4d644f1e39e4909038
      https://github.com/Hamlib/Hamlib/commit/ea70993aa6f5ce368257fe4d644f1e39e4909038
  Author: Jon Snow <jon...@gm...>
  Date:   2026-09-14 (Mon, 14 Sep 2026)

  Changed paths:
    M rigs/ats-mini/ats.c

  Log Message:
  -----------
  make return codes negative


  Commit: 2cdc27a209f038c117a02dc70adba097b5d74a92
      https://github.com/Hamlib/Hamlib/commit/2cdc27a209f038c117a02dc70adba097b5d74a92
  Author: Jon Snow <518...@us...>
  Date:   2026-09-16 (Wed, 16 Sep 2026)

  Changed paths:
    M HAMLIB_STREAMING.md
    M HAMLIB_STREAMING_BACKEND_GUIDE.md
    M README.developer
    M doc/man1/rigctld.1
    M include/hamlib/rig.h
    M rigs/dummy/netrigctl.c
    M src/stream.c
    M src/stream_net.c
    M src/stream_proto.c
    M src/stream_proto.h
    M test/test_dummy_stream.c
    M test/test_netrigctl_stream.c
    M test/test_rigctld_commands.c
    M test/test_rigctld_stream.c
    M test/test_stream_api.c
    M tests/rigctl_parse.c
    M tests/rigstreamtest.c

  Log Message:
  -----------
  Merge branch 'Hamlib:master' into master


  Commit: c4001176a2a07dd4e3598364a99671eeac945ad6
      https://github.com/Hamlib/Hamlib/commit/c4001176a2a07dd4e3598364a99671eeac945ad6
  Author: Jon Snow <518...@us...>
  Date:   2026-09-19 (Sat, 19 Sep 2026)

  Changed paths:
    M NEWS
    M bindings/python/test_startup.py
    M configure.ac
    M include/hamlib/rig_state.h
    M rigs/dummy/aclog.c
    M rigs/dummy/dummy.c
    M rigs/dummy/flrig.c
    M rigs/dummy/gqrx.c
    M rigs/dummy/netrigctl.c
    M rigs/dummy/quisk.c
    M rigs/dummy/sdrsharp.c
    M rigs/dummy/tci1x.c
    M rigs/dummy/trxmanager.c
    M rigs/elad/elad.c
    M rigs/guohetec/guohetec.h
    M rigs/guohetec/pmr171.c
    M rigs/guohetec/q900.c
    M rigs/icom/ic7300.c
    M rigs/icom/ic821h.c
    M rigs/icom/icf8101.c
    M rigs/icom/icom.c
    M rigs/icom/id5100.c
    M rigs/icom/xiegu.c
    M rigs/jrc/jst145.c
    M rigs/kenwood/elecraft.c
    M rigs/kenwood/flex6xxx.c
    M rigs/kenwood/ic10.c
    M rigs/kenwood/k3.c
    M rigs/kenwood/kenwood.c
    M rigs/kenwood/th.c
    M rigs/kenwood/thd72.c
    M rigs/kenwood/thd74.c
    M rigs/kenwood/tmd710.c
    M rigs/kenwood/transfox.c
    M rigs/kenwood/ts2000.c
    M rigs/kenwood/ts480.c
    M rigs/kenwood/ts590.c
    M rigs/kenwood/ts890s.c
    M rigs/kenwood/ts990s.c
    M rigs/kenwood/xg3.c
    M rigs/tci/tci2.c
    M rigs/tentec/orion.c
    M rigs/yaesu/ft100.c
    M rigs/yaesu/ft1000d.c
    M rigs/yaesu/ft1000mp.c
    M rigs/yaesu/ft736.c
    M rigs/yaesu/ft747.c
    M rigs/yaesu/ft817.c
    M rigs/yaesu/ft857.c
    M rigs/yaesu/ft891.c
    M rigs/yaesu/ft991.c
    M rigs/yaesu/ftx1/ftx1.h
    M rigs/yaesu/ftx1/ftx1_clarifier.c
    M rigs/yaesu/ftx1/ftx1_scan.c
    M rigs/yaesu/ftx1/ftx1_vfo.c
    M rigs/yaesu/newcat.c
    M rigs/yaesu/vx1700.c
    M src/cache.c
    M src/cache.h
    M src/conf.c
    M src/event.c
    M src/event.h
    M src/mem.c
    M src/misc.c
    M src/misc.h
    M src/rig.c
    M src/serial.c
    M src/settings.c
    M src/snapshot_data.c
    M src/stream.c
    M src/tones.c
    M test/test_stream_api.c
    M tests/Makefile.am
    M tests/rigctlcom.c
    A tests/testcachemode.c
    A tests/testcacherouting.c
    A tests/testcachethread.c
    A tests/testcachevfo.c
    M tests/testelecraftvfo.c
    M tests/testicomfallback.c
    M tests/testid5100.c
    A tests/testpoll.c
    A tests/testroutingaccess.sh

  Log Message:
  -----------
  Merge branch 'Hamlib:master' into master


  Commit: 79b5e29d8d903ba6882fb9febdbb3e724c434227
      https://github.com/Hamlib/Hamlib/commit/79b5e29d8d903ba6882fb9febdbb3e724c434227
  Author: dforsi <iu...@gm...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M rigs/ats-mini/ats.c

  Log Message:
  -----------
  Merge pull request #2217 from jonsnow1357/master

fix(ats-mini): make return codes negative


Compare: https://github.com/Hamlib/Hamlib/compare/6614c5268b7f...79b5e29d8d90

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 5d9471: fix(ftx1): correct DCS parser format type

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 5d9471dfbbe4f38542e5306b90d0eee91e524d23
      https://github.com/Hamlib/Hamlib/commit/5d9471dfbbe4f38542e5306b90d0eee91e524d23
  Author: David Christle <dch...@us...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1_ctcss.c

  Log Message:
  -----------
  fix(ftx1): correct DCS parser format type

The DCS getter passed an unsigned int pointer to a signed scanf conversion and logged the value with a signed format. Use int for the parsed table index to match both format conversions and the range-check helper.

(cherry picked from commit 85218f5ecb09de6aa080550af72ac97b6af8b5fb)


  Commit: 13a7c0750f8d02cfadd8d4ebf28a953902832bb7
      https://github.com/Hamlib/Hamlib/commit/13a7c0750f8d02cfadd8d4ebf28a953902832bb7
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for FTX-1 DCS fix


Compare: https://github.com/Hamlib/Hamlib/compare/182c1984d7e9...13a7c0750f8d

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 85218f: fix(ftx1): correct DCS parser format type

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 85218f5ecb09de6aa080550af72ac97b6af8b5fb
      https://github.com/Hamlib/Hamlib/commit/85218f5ecb09de6aa080550af72ac97b6af8b5fb
  Author: David Christle <dch...@us...>
  Date:   2026-08-16 (Sun, 16 Aug 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1_ctcss.c

  Log Message:
  -----------
  fix(ftx1): correct DCS parser format type

The DCS getter passed an unsigned int pointer to a signed scanf conversion and logged the value with a signed format. Use int for the parsed table index to match both format conversions and the range-check helper.


  Commit: 6614c5268b7fa7cc9f8e10b15bb169c3fc0b7047
      https://github.com/Hamlib/Hamlib/commit/6614c5268b7fa7cc9f8e10b15bb169c3fc0b7047
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M rigs/yaesu/ftx1/ftx1_ctcss.c

  Log Message:
  -----------
  Merge GitHub PR #2156


Compare: https://github.com/Hamlib/Hamlib/compare/9589c94a6dcc...6614c5268b7f

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] d3e0fc: fix(tests): clear rigctld PID after startup timeout

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: d3e0fcdf3576f8e5ca39b4ad9cea246755c13644
      https://github.com/Hamlib/Hamlib/commit/d3e0fcdf3576f8e5ca39b4ad9cea246755c13644
  Author: David Christle <dch...@us...>
  Date:   2026-08-16 (Sun, 16 Aug 2026)

  Changed paths:
    M test/test_netrigctl_stream.c

  Log Message:
  -----------
  fix(tests): clear rigctld PID after startup timeout

The timeout path reaped rigctld but left its PID visible to retry
cleanup. A second signal could then target the stale numeric PID.

Mark the child invalid immediately after waitpid consumes it.


  Commit: b31a61b7187fa079dba51a6206a0f92b303abf35
      https://github.com/Hamlib/Hamlib/commit/b31a61b7187fa079dba51a6206a0f92b303abf35
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M test/test_netrigctl_stream.c

  Log Message:
  -----------
  Merge GitHub PR #2154


  Commit: 9589c94a6dccd422ba2f34e1a9a6b8288a25466b
      https://github.com/Hamlib/Hamlib/commit/9589c94a6dccd422ba2f34e1a9a6b8288a25466b
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for clearing rigctld PID fix


Compare: https://github.com/Hamlib/Hamlib/compare/0c56dafd8fd0...9589c94a6dcc

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 99dc12: G90: fix over-claimed capabilities and RFPOWER BCD...

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 99dc1295f1088e182acee619d92876da2dee5f5c
      https://github.com/Hamlib/Hamlib/commit/99dc1295f1088e182acee619d92876da2dee5f5c
  Author: jbdubbs <ja...@we...>
  Date:   2026-09-20 (Sun, 20 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

(cherry picked from commit b61dd14d461f35f4d6143993f8cbd1386af98847)


  Commit: 182c1984d7e917b906a2e49b662afb1966ec569e
      https://github.com/Hamlib/Hamlib/commit/182c1984d7e917b906a2e49b662afb1966ec569e
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for Xiegu G90 fixes


Compare: https://github.com/Hamlib/Hamlib/compare/dcf5897c27fe...182c1984d7e9

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] b61dd1: G90: fix over-claimed capabilities and RFPOWER BCD...

[Nate B. <no...@gi...>]

  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