开云体育

I may have stated this before (I'm getting older and I'm not sure who I've told what stories ;) ), but my coding experience comes from plugging what I want to do in Google and now ChatGPT. I have both

Hi, I can confirm similar behaviour with a Kenwood TS590S. So, flrig 2.0.05 (compiled from source) server run on MacOS and client run on MacOS. As I click on "init" in client, client crashes with a

Thanks... I think I'll use Mint until I can get more experience under my belt playing around under the hood. Joel - W4JBB

This is gonna be confusing :) Gary, all are welcome to use the zip file. Just download, open the zip file and drag it to your applications folder and double click. It should open without additional

Good morning (German time). I know that this problem is not new and I found several posts here from the past. But I could not find any real solution. What I can say is that 1.4.7 works fine and 1.4.8

Hi, Dave. I tried but after receiving the “we couldn’t verify” message the only options I had were to cancel out or delete the app. I think that there may be an issue with my Mac mini since I

At work we ran CentOS 7, and now Rocky. Private cloud, tens of thousands of compute nodes netboot Flatcar Container Linux for K8 workloads, most of the other stuff around it is CentOS/Rocky. If you

Yeah the strangest thing is that I have cat control through JS8Call and WSJT-X working fine

Fair enough. I could not get the repo download (of flrig) working.? But to test connectivity, I tried JTDX with my FTdx10 (not Flrig/Flrig - worked just fine, even though flrig did not (as a

Thanks for the reply. Yes, I am part of the dialout group. I did the chmod command also and no change. I don't believe it's a permission issue since I have this same setup working with other programs.

Riley, I may have missed it.. but - did you add your login alias to the /dialout/ group? *sudo usermod -a -G dialout $USER = *sudo usermod -a -G dialout gjensen* (*my alias being */gjensen/)* and sudo

Thank you for taking the time to help me troubleshoot this. I see other people seem to have had luck with the digirig and flrig, so I am going to continue trying to figure it out.

Is it possible that this cable works fine with software using hamlib but not flrig? I would have thought if it worked for one it would work for the other. I have not had the change to try another

whether I use /dev/ttyUSB0 for /dev/serial/by-id/... I get the same results. One thing I meant to mention is that when I click init the audio on my radio stops for a split second and I see the "CAT"

I would like to note that selecting /dev/ttyUSB0 results in the same issue.

I've attached debug_log and trace here. The output of that command is: [ 1479.789733] usb 1-5.1: SerialNumber: 0e2a0f816687ed11965525d7a603910e [ 1479.796135] cp210x 1-5.1:1.0: cp210x converter

Well I have installed 2.0.05.81 and mimic'd you settings exactly, with no luck. Not sure if it helps, but this is the trace when I click init: 04:07:47.433 : closeRig() 04:07:47.434 : close serial

Yup I can manage that. I will give it a shot tonight and report back. Do I need to remove the current version or will this overwrite what is currently installed? If I need to remove the current

I'll have to double check what version I have, I thought 2.0.04 was the most recent on the website. Thank you, I'll reply back.

details macos 15.1 macloggerdx 6.53 flrig 2.0.05 fldigi - built from git https://git.code.sf.net/p/fldigi/fldigi today, also 4.2.06.05 I think what happens is, macloggerdx reports over UDP: [Radio