¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Topics

flrig stopped working on my Mac -- any suggestions?

 

I've had flrig working on my MacBook Air (M2, running macOS 15.2) for a few days with my Xiegu X6200 (using the X6100 rig choice in prefs). With the exception of needing to reboot between usages of it and the radio, it was working fine. The reboots were required because after shutting down flrig and the radio, the next time I started up the radio and flrig, it would tell me that the serial port was in use by another program (it wasn't, as far as I can tell).
?
Suddenly, last night, every time I would start up flrig, it would freeze with the "Initializing" progress bar showing. I would eventually have to kill the process ("killall flrig") to get it to stop. I tried rebooting multiple times with no change. Today, I removed the .flrig folder in case the config files had somehow become corrupted. When I set up the config and hit the "Init" button, it once again froze up on me. A little while ago, I downloaded the signed (notarized) version of 2.0.5.85 from another thread in this group and installed it. Deleted the .flrig folder once again so I was starting with no pre-existing config, but this version also freezes when I hit the "Init" button.
?
Before deciding to give flrig a try, I had previously used HamLib's rigctld to control the radio. To verify that the radio is "talking" fine through the specified serial port, I ran rigctld just now and connected to the radio through JTDX. After reconfiguring JTDX to use HamLib, it connected perfectly. So it appears that it's not a problem with the USB serial port, nor does it appear to be a problem with the radio.
?
I'd *really* like to be able to use flrig because I have never figured out a way to make RUMlogNG work with HamLib/rigctld but it worked perfectly with flrig until flrig stopped working for me. Any suggestions?
Thanks,
Marc nz9a
 

On 19/12/2024 23:53, Marc Brown (nz9a) via groups.io wrote:
I've had flrig working on my MacBook Air (M2, running macOS 15.2) for a few days with my Xiegu X6200 (using the X6100 rig choice in prefs). With the exception of needing to reboot between usages of it and the radio, it was working fine. The reboots were required because after shutting down flrig and the radio, the next time I started up the radio and flrig, it would tell me that the serial port was in use by another program (it wasn't, as far as I can tell).
lsof from homebrew can verify that:

$ lsof /dev/cu.*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
flrig 45225 arekm 9u CHR 9,5 0t0 12413 /dev/cu.SLAB_USBtoUART
flrig 45225 arekm 13u CHR 9,7 0t5102928 12429 /dev/cu.SLAB_USBtoUART3

Suddenly, last night, every time I would start up flrig, it would freeze with the "Initializing" progress bar showing.
Have many USB ports xiegu x6200 provides to the macos?

With ft-710 for example there are two ports appearing in the system ("standard" and "enhanced") BUT the order of them appearing in the macos is always random. It depends on some usb enumeration timing.

So in my case one time "cu.SLAB_USBtoUART" is "standard" port and "cu.SLAB_USBtoUART3" is "enhanced" and other time it's the other way around.

That broke flrig (my fldigi talks to flrig) connection randomly since I always had "cu.SLAB_USBtoUART3" set in flrig.

Maybe it's the same problem with x6200?


Marc nz9a
--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )
 

Thanks for the response! In the case of the X6200, it shows 4 ports. Two "cu.*" ports and two "tty.*" ports. The correct ones to use with the X6200 are the tty ports. And they never appear to flip (or at least they never have in the past). Before I started working with flrig, I had a script that ran at login that started rigctld and it always used the same port.?
?
Right now I'm using wfview to interface with the radio, having found a suggestion for making it work with RUMlogNG. It's using the same tty port that I was trying to use with flrig before I posted my first message and is working fine.
--Marc nz9a
 

I mentioned in my previous post that the X6200 creates two sets of two ports (two "cu.*" ports and two "tty.*" ports). Previously, the higher numbered tty.usbmodem port was the one that was working. This afternoon I decided to try out the higher of the cu.usbmodem ports instead (in the past, this froze whatever program I was attempting to connect to the radio via this port). Oddly enough, flrig worked with the "cu" port this time! So I'm back up and running.
--Marc nz9a

1 - 4 of 4