Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
Re: DigiRig, flrig, and a Yaesu FT-747GX
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" symbol on the radio come on for about a second then turn back off. |
Re: DigiRig, flrig, and a Yaesu FT-747GX
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 detected ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.798963] usb 1-5.1: cp210x converter now attached to ttyUSB0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.875170] usb 1-5.2: new full-speed USB device number 10 using xhci_hcd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.966047] usb 1-5.2: New USB device found, idVendor=0d8c, idProduct=0012, bcdDevice= 1.00 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.966079] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.966094] usb 1-5.2: Product: USB Audio Device ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? [ 1479.966106] usb 1-5.2: Manufacturer: C-Media Electronics Inc. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1479.990453] input: C-Media Electronics Inc. USB Audio Device as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.3/0003:0D8C:0012.0003/input/input14 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [ 1480.042983] hid-generic 0003:0D8C:0012.0003: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-0000:00:14.0-5.2/input3 ? ? ? |
Re: DigiRig, flrig, and a Yaesu FT-747GX
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 port 04:07:47.434 : ClosePort(): fd = 14 04:07:47.439 : serial port closed 04:07:47.439 : clear frequency list 04:07:47.440 : initialize title bar 04:07:47.440 : start tranceiver serial port 04:07:47.442 : /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0e2a0f816687ed11965525d7a603910e-if00-port0 opened: fd = 14 04:07:47.447 : D: startXcvrSerial:? Serial port: ? ? Port ? ? : /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0e2a0f816687ed11965525d7a603910e-if00-port0 ? ? Baud ? ? : 4 ? ? Stopbits : 2 ? ? Retries ?: 2 ? ? Timeout ?: 50 ? ? Loop ? ? : 250 ? ? RTSCTS ? : 0 ? ? CATptt ? : 0 ? ? RTSptt ? : 0 ? ? DTRptt ? : 0 ? ? RTS+ ? ? : 0 ? ? DTR+ ? ? : 0 04:07:47.448 : initialize transceiver 04:07:47.449 : selrig->initialize() 04:07:47.449 : init_rig() 04:07:47.449 : selrig->check() 04:07:47.449 : get info S: ? ?R: ? 04:07:47.449 : WriteBuffer: ?00 00 00 00 10 04:07:47.602 : ReadBuffer [51.143000 msec]:? 04:07:47.604 : S: ?00 00 00 00 10 ?R: ? 04:07:47.604 : FAILED |
Re: DigiRig, flrig, and a Yaesu FT-747GX
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 version, can you tell me how to do that? I always get confused as to how to uninstall software on Linux. |
Re: fldigi fights with frequency changes from radio or API
On 15/11/2024 23:30, Dave, G?WBX via groups.io wrote:
OK.? AFICR, no other software other than the Flsuite was mentioned originally.detailsCould you list *All* the software you wish to use together, and of the OS running it all.macos 15.1 macloggerdx 6.53 flrig 2.0.05 fldigi - built from git today, also 4.2.06.05 Especially version numbers, for all software items you wish to run together. I know nothing to little about Apple Mac's and their software, but I do know others on this list do know that stuff.I think what happens is, macloggerdx reports over UDP: [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, fldigi reads that and parses it in parse_maclog() using parse_report() function. That function reads frequency if ((p = str.find("RxMHz:")) != std::string::npos) mclg_rxhz = get_freq(str.substr(p)); and then at the end of parse_report() show_mac_strings() is called which requests frequency change to flrig: void show_mac_strings() { SET_THREAD_ID(MACLOGGER_TID); if (mclg_txhz > 0) REQ(maclogger_set_qsy); That calls maclogger_set_qsy() which requests outdated frequency (sendFreq(hz);) to be applied to the radio. Outdated because macloggerdx sends reports not too often and fldigi assumes them to be "current" (which is wrong; the frequency is already different due to changes on radio knob or via flrigi freq display). Why fldigi requests frequency changes based on maclogger radio report - no idea. For spots, with "Tune to Rx Spot" being on that makes sense, for regular radio report - it doesn't IMO. All the best.-- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) |
Re: fldigi fights with frequency changes from radio or API
OK.? AFICR, no other software other than the Flsuite was mentioned originally. Could you list *All* the software you wish to use together, and details of the OS running it all. Especially version numbers, for all software items you wish to run together. That will help a lot. I know nothing to little about Apple Mac's and their software, but I do know others on this list do know that stuff. All the best. Dave G0WBX. |
Re: DigiRig, flrig, and a Yaesu FT-747GX
That's what I'm trying to get to. I want to get the radio communicating with flrig, and then I will communicate through flrig to each other program.
?
To my knowledge the radio will not power on over CAT, there is a latching button on the radio that is pressed to turn it on and off. |
Re: DigiRig, flrig, and a Yaesu FT-747GX
WSJT-X uses hamlib and one of the "radios" is flrig. I use flrig as a concentrator. WSJT-X, FLdigi and my logger all connect to my rigs through flrig. Phil Does the Yaesu have the capability of being powered on using the CAT interface? Phil GM3ZZA On 15 November 2024, at 19:25, "Riley Gossling, KF0QMQ via groups.io" <rjayg1979@...> wrote: Yes, I believe WSJT-X uses Hamlib.
?
Getting flrig to work is what I'm trying to do. I cannot get it to communicate with my radio. |
Re: DigiRig, flrig, and a Yaesu FT-747GX
Riley I use flrig with an FT857. and I find connecting a tad finicky.? Have you tried to start flrig, then the FT747? FT747 on and then?flrig?started? then ft747 off/on? For me it seems like different?methods work at different?times.? I keep?my Ubuntu PC up 24/7 for months, once I do connect I keep the rig on for a long time and it stays connected. Have you tried FLrig with WSJTX? That is start FLrig, start wsjtx and set rig as flrig.? It's worked for me , I dont recall if connection?is finicky.? Thanks Dan KC2STA On Fri, Nov 15, 2024 at 10:58?AM Riley Gossling, KF0QMQ via <rjayg1979=[email protected]> wrote:
--
Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX |
Re: fldigi fights with frequency changes from radio or API
On 15/11/2024 17:47, Arek M., SP2AM via groups.io wrote:
Anyway disabling "Tune to Rx Spot" and the problem went away.That was too fast. No - it doesn't make it go away. Added: diff --git a/src/logbook/maclogger.cxx b/src/logbook/maclogger.cxx changing freq on radio and: progdefaults.maclogger_spot_rx 0 mclg_txhz = 7245000, maclogger_set_qsy: 7245000 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7247280, maclogger_set_qsy: 7247280 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7249560, maclogger_set_qsy: 7249560 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7254380, maclogger_set_qsy: 7254380 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7254380, maclogger_set_qsy: 7254380 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7255740, maclogger_set_qsy: 7255740 progdefaults.maclogger_spot_rx 0 mclg_txhz = 7256960, maclogger_set_qsy: 7256960 so it does sendFreq(hz) every short time. Just hz it has is sometimes old value (radio already has been set to new freq) which makes it tell flrig to go back to old freq. Shouldn't it just do maclogger_set_qsy() { ... if (!progdefaults.maclogger_spot_rx) return; ? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) |
Re: fldigi fights with frequency changes from radio or API
On 15/11/2024 17:13, Arek M., SP2AM via groups.io wrote:
Tracked it down.If WITH FlRig and FlDigi running, and you change the frequency (or mode) at Flrig, does FlDigi follow those changes.When changing frequency on flrig then fldigi tries to follow but with the same "revert" problem, sometimes, as when changing frequency on radio. Frequency was being changed in maclogger_set_qsy(). I had "Tune to Rx Spot" turned on and fldigi reacted on: [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100] These look like a kind of "current status report" and not "spot" for me. Anyway disabling "Tune to Rx Spot" and the problem went away. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) |
Re: fldigi fights with frequency changes from radio or API
On 15/11/2024 11:23, Dave, G?WBX via groups.io wrote:
Hi.Yes. Flrig alone and: - flrig frequency display follows frequency changes made at radio - same for the other way - frequency changes made at flrig are applied to radio correctly - changes made via flrig xmlrpc api are applied to radio correctly flrig works reliably for me. If it does, then something is wrong in how FlDigi, interacts with Flrig.Ok, so I didn't miss any special option. If WITH FlRig and FlDigi running, and you change the frequency (or mode) at Flrig, does FlDigi follow those changes.When changing frequency on flrig then fldigi tries to follow but with the same "revert" problem, sometimes, as when changing frequency on radio. I assume the radio follows FlRig.Yes. Debug log with rig i/o, server and client on: - fldigi started with freq 14078100 being on its display - (mouse) clicked *fldigi* third freq digit from right ("1") down, it changed frequency to 14078000, good, flrig follows, radio follows - now started clicking fourth digit down on *flrig* - one click -> fldigi went to 14077000 - second click -> fldigi went to 14076000 - and then fldigi went back itself to 14077000 Regards. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) |
Re: Linux Recommendation - Work is a RHEL/Windows Shop
¿ªÔÆÌåÓýJoel, any version of Linux is a good version of GNU/Linux, at least in someone's opinion. If your works is using RHEL, then Fedora has a lot in common. For the Broadcom drivers, you could also try liberating/borrowing/otherwise acquiring a USB-to-Ethernet adapter and using a good old wired network connection for the initial installation. As an alternative, Ubuntu is more liberal with hardware drivers, and others have reported success, see . HTH, 73, Robin, G8DQX On 13/11/2024 10:16, Joel Black - W4JBB
via groups.io wrote:
|