Log4OM

I'm sure I'm just doing something wrong but have searched through the manual and can't seem to figure this out.

In the QSO entry panel the "mode" is locked to "RTTY" regardless of how I have the padlock clicked. When the padlock shows "yellow", which appears the only way to activate the mode drop-down list, when I try to move to another mode to select something other than "RTTY" the cursor jumps back to "RTTY" by itself.

Can somebody please "educate" me?

W4ATX wrote: 27 May 2021, 19:48 I'm sure I'm just doing something wrong but have searched through the manual and can't seem to figure this out.

In the QSO entry panel the "mode" is locked to "RTTY" regardless of how I have the padlock clicked. When the padlock shows "yellow", which appears the only way to activate the mode drop-down list, when I try to move to another mode to select something other than "RTTY" the cursor jumps back to "RTTY" by itself.

Can somebody please "educate" me?

Richard,

What have you set up for "Preferred modes" at: Settings / Configuration / User Preferences ??

Have you also possibly tic'd the box for: Switch to DIGITAL mode when required? It is located at: Settings / Configuration / CAT interface

Also if you have CAT set up for your rig (I happen to use and prefer OmniRig) it will automatically change the mode.

There might be a CAT command coming from your rig that is forcing the situation you have noted.

Do you have (for example) FLDIGI enabled/running as well or is the description of your problem with Log4OM V2 only and is it connected to your rig? Meaning no other APPs linked such as WSJTx / JTDX / JTAlert or Gridtracker?

Also ... some information about your installation and setup would also be helpful such as: version of Log4OM V2, which CAT interface are you using, Rig ID/Model, computer information, etc., etc..

Well, I found out where the "RTTY" setting was coming from. It was set as the default at Settings / Hardware Configuration / CAT Interface but the checkbox for "switch to digital mode when required" is NOT selected, so I fail to understand why that setting would come into play. Based on the way it is presented in the interface, it seems as though it should not be active unless it is checked.

I changed the default mode to FT8 and it changed back in the main QSO entry panel, but I cannot change it from that mode now.

To answer your other questions:

Version 2.13.0.0
Yes, I am using Omnirig, WSJTx, JTAlertX
Not using FLDigi, though it is installed.
Yaesu FTdx3000, USB interface, Windows 10 Pro 64 bit, Dell Optiplex 3080, 6 cores, 16GB ram

W4ATX wrote: 27 May 2021, 21:09 Well, I found out where the "RTTY" setting was coming from. It was set as the default at Settings / Hardware Configuration / CAT Interface but the checkbox for "switch to digital mode when required" is NOT selected, so I fail to understand why that setting would come into play. Based on the way it is presented in the interface, it seems as though it should not be active unless it is checked.

I changed the default mode to FT8 and it changed back in the main QSO entry panel, but I cannot change it from that mode now.

To answer your other questions:

Version 2.13.0.0
Yes, I am using Omnirig, WSJTx, JTAlertX
Not using FLDigi, though it is installed.
Yaesu FTdx3000, USB interface, Windows 10 Pro 64 bit, Dell Optiplex 3080, 6 cores, 16GB ram

Richard,

For a test ... Turn off WSJTx & JTAlert, Have your rig turned on/connected to Log4OM V2 and then restart V2 and see if anything changes.

You've already noted that you do get a dropdown of options (for mode or band, etc..) when the padlock is "unlocked". A locked padlock has a red background and (as you said) won't provide the choices at that time.

I'm stepping through my UI trying to replicate your situation of not being able to select a different mode ... but so far, I'm scratching my head. Thus, I'll keep peeling away the onion.

I'm thinking there is a code/command coming from your rig that is causing the refusal to change.

In my case (I don't have a callsign in the UI) and I can manually change the mode without any issue.

Then ... I start tapping the "mode" button my my K3 and as it changes modes on the rig the mode will also change on the Log4OM V2 Main UI.

Are you using the correct "ini" file for OmniRig to communicate with your rig?