Log4OM

Hi all.

I'll keep saying a great product and so well featured. Thank for your continued work.

Hope one of you can help with niggle I can't seem to resolve.
Clicking on an entry on the cluster screen causes the radio to change frequency but at various random offsets to the cluster frequency. A second click often results in the desired result and tunes to the frequency stated on the cluster screen.
I'm guessing it's an Omnirig issue as it didn't do it on my IC7300 but does on my FTDX101MP. I've tried other Yeasu rig .ini's DX10,991 etc, same result. Just really odd that it works fine on the second click if it's Omnirig.

Win10
LOG4OM v2.28
Latest version of Omnirig 1.2 when I downloaded 2.28 L4OM (so providing you give the latest rig .ini's at that point, they are them)

I've seen one other issue like this on the forums about this but I didn't think it was resolved in the end and also the one recently where the spot feature produces a different cluster entry to the frequency spotted. Could just be coincidence.

Thanks in advance.

SIngle click in the cluster brings the call in the Callsign field, double click in the cluster let the radio change the frequency
to the spotted one and put it in the Frequency field. Think there was no change from the begin on in Log4OM.

In the last few weeks we find out that there should be a CAT problem with modern Yaesu radios but if so it must be a Yaesu
and/or Omnirig problem.

I´m sorry but i can´t do any tests so i don´t have Yaesu radios.

Marc,

I have some questions and possible suggestions

1. Which CAT connection are you using the USB on the front of the radio or the serial connection to the back.

2. Have you tried different connecting cables either to USB or serial on radio?

3. I think your radio is similar to the 7300 and has 2 CAT connections (USB and rear serial) did you set the Yaesu menu to seperate the front and rear USB and serial connections, if not please do so.

4. Do you also have an amplifier connected to the radio for CAT control?

5. What other software is running in conjunction with Log4OM?

6. Did you try different settings in the Log4OM program config to the check boxes shown below?

Thanks for the quick responses guys. I'll try to be succinct.

One click works fine and populates the call sign field perfectly.
Two click does change the frequency as expected but this can be random off frequency received by radio sometimes 1.4kHz sometimes just 500, 600 or 700Hz. The second double click polls the rig and corrects the offset issue with the right frequency.

1. Which CAT connection are you using the USB on the front of the radio or the serial connection to the back.
USB from the rear its a USB A to USB B cable and a good quality one that I use with an RSP so know it to be reliable.

2. Have you tried different connecting cables either to USB or serial on radio?
Tried different USB cables but not front USB. That's an A to A so I'll dig out a cable and try it. I don't have a serial cable, I got rid of those years ago

3. I think your radio is similar to the 7300 and has 2 CAT connections (USB and rear serial) did you set the Yaesu menu to separate the front and rear USB and serial connections, if not please do so.
I don't believe there is a separation possible. The RS232 is already separate. You just choose front or rear for USB/mic/data outputs and inputs. There are options for RPTT select for DAKY, RTS, DTR in the differing mode menus for SSB,AM,FM etc but they all appear to be at defaults and working as expected.

4. Do you also have an amplifier connected to the radio for CAT control?
No Amp connected.

5. What other software is running in conjunction with Log4OM?
Nothing else running normally. I have however tried it with WSJT-X and if I use WSJT-X to select the band, the change is spot on every time. Seems only when commanded via L4OM from the cluster with two clicks it goes wonky.

6. Did you try different settings in the Log4OM program config to the check boxes shown below?
I don't use L4OM to control the rig other than to do SSB frequency changes from the cluster screen. If I do data then that frequency CAT command comes from WSJTX to Omnirig with the log passing into grid tracker then is UDP inbound to log into L4OM. That all works fine too.
The only difference on the snip you sent was my CAT delay was 1 where yours is 0. Changed that too but no difference to off frequency change.
Changed the invert for settings and tested that they work putting USB/LSB 'wrong' for example but the frequency offset still remains along with the flipped sideband.

Not sure now it is Omnirig .ini. If WSJTX uses it the same as L4OM as WSJTX is solid in frequency change each time.
I'm using the 101D .ini file as there is no MP version in Omnirig but they are fundamentally the same rig so it shouldn't be the issue?

I'll let you know if I find anything obvious by experimentation but for now 2 sets of double clicks to change frequency it will be.

What is the Omnirig poll int?

Hi Terry. 100ms

It's not that then!

Have you tried a factory reset of the radio?

Hi. Ye, done that a few times without change. No deal breaker I'll just double double click and be cautious logging for now. I'm sure the issue will be resolved eventually by experimenting.

Hi. Ye, done that a few times without change. No deal breaker I'll just double double click and be cautious logging for now. I'm sure the issue will be resolved eventually by experimenting.

Morning Terry.
Good news, looks like your suggestion nailed it. Thank you so much.
Send mode before frequency to radio checkbox was all it appears it was.
It'll be my stupidity not seeing it yesterday as I thought as I wasn't changing modes that wouldn't matter.
It must also be that WSJT either doesn't send the mode or does it by luck in the order the radio or Omnirig likes!

The only thing I've been unable to check is that this definitely works where the frequency in the cluster ends with anything other a zero after the decimal as everyone seems to be spotting with full frequency numbers so far today.
I'll let you know if that causes the issue but as usual it look like it's sorted after you guys get involved

Thank you again
73
Marc