Is the Log4OM CAT screen supposed to work when HamLib is the CAT management interface? The CAT display and change of frequency works when I have JTDX or WSJT-x running. However, I am only able to change bands and frequencies from within JTDX or WSJT-x.
If I close either of those programs, and open the CAT Control screen I cannot change the frequency, band or mode of the radio. I'm already learning to live with Log4O going 'Offline' at random times.
Marv K7IU
CAT screen control with HamLib
-
G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: CAT screen control with HamLib
Sounds like you have something set up incorrectly
AndI always reccomend using Omnirig if you want to use a WSJT program at the same time - See our user guide
Dont forget that Com port conflicts are usually caused by multiple programs trying to share the same com port this is why we use the multi threading capability of Omnirig.
My personal Log4OM set up is running 24/7 and I dont experience disconnects
AndI always reccomend using Omnirig if you want to use a WSJT program at the same time - See our user guide
Dont forget that Com port conflicts are usually caused by multiple programs trying to share the same com port this is why we use the multi threading capability of Omnirig.
My personal Log4OM set up is running 24/7 and I dont experience disconnects
73 Terry G4POP
Re: CAT screen control with HamLib
Terry,
Because I use other operating systems besides just Windows, and to make things simple and become proficient in how I have things setup, I chose to use HamLib over OmniRig. As I understand it, rigctl is the app thru which CAT commands are sent to the radio.
In any event, from what I've been able to test, it doesn't appear that Log4OM sends out any rigctl commands when the cat screen is used.
I guess I could switch over to OmniRig, but maybe you could explain how Log4OM sends CAT commands to the radio, based on the CAT interface chosen in the config. Especially when it's HamLib? My though is that my issue is related to the HamLib parameters themselves as I am starting HamLib prior to starting Log4OM and thereby using the Hamlib NET rigctl Stable RIG model and connecting to an active HAMLIB instance (using the default TCP port).
Marv K7IU
Because I use other operating systems besides just Windows, and to make things simple and become proficient in how I have things setup, I chose to use HamLib over OmniRig. As I understand it, rigctl is the app thru which CAT commands are sent to the radio.
In any event, from what I've been able to test, it doesn't appear that Log4OM sends out any rigctl commands when the cat screen is used.
I guess I could switch over to OmniRig, but maybe you could explain how Log4OM sends CAT commands to the radio, based on the CAT interface chosen in the config. Especially when it's HamLib? My though is that my issue is related to the HamLib parameters themselves as I am starting HamLib prior to starting Log4OM and thereby using the Hamlib NET rigctl Stable RIG model and connecting to an active HAMLIB instance (using the default TCP port).
Marv K7IU
