Log4OM and WSJT-X

[WB7SWW]

Been fighting several days trying to get v2 to activate CAT control for my IC-7610. The problem is both programs want to access the radio
and two devices cant do that at same time. So Im running v2 with no CAT Display. Posted this in case anyone is having same problems......oh well, the rest of it is working.

[SQ5TDZ]

If you use omnirig, set it to wsjtx omnirig , not your radio icom 7610

[KI5IO]

Been fighting several days trying to get v2 to activate CAT control for my IC-7610. The problem is both programs want to access the radio
and two devices cant do that at same time. So Im running v2 with no CAT Display. Posted this in case anyone is having same problems......oh well, the rest of it is working.

Allen,

Post above is good advice. In WSJT-x select OmniRig as your CAT choice. I assume that you have your rig configured in as OmniRig 1.

You can test all your connections and make Q's w/o V2 at this point and time. Q's will be save in the WSJT-x ADIF log.

Once that is confirmed/worked then turn on Log4OM2 and follow the User Guide settings to ensure your have all set for proper communications between WSJT-x and V2. You might have to confirm the settings in WSJT-x to be sure the UDP ports are coordinated between the two APPs.

I'll assume that you have already set up CAT in V2 using OmniRig 1 to communicate with your rig and that you have that working FB just for the sake of CW and SSB, etc..

Once all your WSJT-x and V2 settings (from User Guide) are made restart both WSJT-x and V2 and start making Q's, logging them and have a blast.

I usually run WSJT-x is what we call "solo" mode in that I don't use JTAlert between WSJT-x and V2. I let WSJT-x do the communicating with my K3. I don't need to have V2 do any talking to the rig during my FT8 sessions. Sometimes I leave the V2 CAT on and often I just go to Connect / CAT and select Stop CAT to shut it off when working FT8 in this fashion.

I do NOT run WSJT-x, OmniRig or Log4OM2 with Administrative privileges with the working arrangement I noted above.

Iron out the hiccups and you will be good to go.

Thanks for using Log4OM V2.

[N6VH]

For multiple connections to the rig, I use Win4Yaesu, which handles connections to the rig from multiple sources (software) at once. There is also a version for Icom. Yes, it costs $60, but, to me at least, it is well worth it. It also has an on-screen control panel for the rig.

It can be found here:

https://icom.va2fsq.com/

73,

Jim N6VH

[ka4ahu]

I am having a similar problem

Running Win4icom, WSJT-x, JT Alert, and log for Log4om. I am really struggling to get them all playing nicely together. At this point I have given up on Log4OM and WSJT-X talking to the radio at the same time via win4icom because of the Omnirig requirement. I did not have this issue with DXKeeper as it all played well but DXkeeper did not require Omnirig only a Com port.

I am at the point of just accepting no cat control when I am using FT-8, which is a shame as I am on FT-8 90% of the time. Now if I can get all the UDP stuff playing nicely between WSJT-X, JT Alert and Log4OM, which is a bit of astruggle as well....

[N6VH]

This shouldn't be a problem. Set Omni-Rig to connect to an unused port in the Win4Icom 3rd Party HW/SW section. That's the way I have it set for my Yaesu FTDX 5000, and it should work for the Icom as well. Incidentally, when you are running WSJT-X, you don't need to have Log4OM connected to the rig. WSJT-X does the rig control, and sends the band and frequency to Log4OM. Using Win4Icom, you can have both Log4OM and WSJT-X connected at the same time, as I already indicated.

73,

Jim N6VH