Cannot connect Log4Om to Win4Icom

[W2JAZ]

I’ve tried every which way to connect log4OM to Win4Icom without success. I’m using an IC-705 and trying to connect the logger and Win4Icom using OmniRig and a com0com pair set up in Win4Icom. I tried getting support from Tom creator of Win4 suites but nothing seems to work. I also tried connecting using Hamlib and a virtual comport pair without success. Has anyone encountered and solved this problem?

Rick, W2JAZ

[KI5IO]

Rick,

One of the threads that I found in this search of the Forum might help provide a response.

https://forum.log4om.com/search.php?key ... %5B0%5D=31

[W2JAZ]

I’ll try running the direct usb connection at the higher baud rate but I’m not counting on this solving the problem.

Thanks
Rick, W2JAZ

[N6VH]

Rick,

Possibly a dumb question - is Win4Icom connecting to the rig, without using Log4OM? If not, that's a separate issue. If it does connect, here is my setup. I use Win4Yaesu, but the setup should be similar.
I have Win4Yaesu connecting to my rig via USB, using the USB drivers supplied by Yaesu (Icom in your case).
I have several comport pairs set up for Win4Yaesu. For L4OM I use ports 10 & 11. L4OM connects to port 11.
Hope this helps.

73,

Jim N6VH

[W2JAZ]

To answer your questions I’m setup the same way you are - direct USB connection from win4Icom to radio. I then set up com0com pair for omnirig to use to connect to log4Om. It just not work with my IC-705. I can connect log4Om via OmniRig to the radio as long as I don’t use win4Icom. I’ve tried different comport pairs and nothing seems to work when using Win4Icom and Log4OM and OmniRig. It’s one of the other but not both.

Rick, W2JAZ

[N6VH]

Rick,

One more question. Do you have Omnirig set to connect to the 2nd number of the pair? IOW, my pair is 10 and 11. Omnirig connects to 11.

73,

Jim N6VH

[W2JAZ]

Yes when I create a pair I always list the outside app to use the higher number. This really stumps me as I’ve had no problem at the home QTH setting up my log4om with win4Yaesu and FTDX101D.

Rick, W2JAZ

[kd7mw]

Set up Com0Com when none of the other programs are running. Also be sure that the port names in Com0Com are changed to regular COM port names. And that the ports you select don't show up in red. That means that the port is already in use. Sometimes a port you used a long time ago is still in Windows setup. You can see if that's the case by going into Device Manager and clicking View, Show Hidden Devices, and then open the Ports COM and LPT list. To clear an unused Com port from the list, right click on it and select Uninstall. You may have to uninstall the driver as well.

Run the connection between the radio and Win4Icom at 115200 baud (Win4 settings 1st tab--"Hardware & User Preferences"). Run the connection between Log4OM and Win4Icom at 38400 baud (Win4 Settings, 2nd tab--"3rd party SW/HW." Be sure the baud rates are the same in Log4OM and Win4Icom. Be sure to click the Connect button below the baud rate and Tag fields in the column for the appropriate port.

Once you set things up, click the Save button in Win4Icom. Then close all the programs and restart them. Also be sure that the radio itself is set at 115200 baud, and in the radio settings, that CI-V USB port is set to Unlink from [Remote] (it's just above the baud rate in the menu. And don't mess with the Com0Com settings--the defaults should be fine.

I believe I've read that in OmniRig, Radio #2 has problems in some situations, so it's better to use Radio 1 if at all possible.

I was "bitten" by the previously used port issue, and by not closing all the programs while setting up Com0Com. It can get confusing because there are so many factors, and everything has to be done in the correct order. And if you switch between running things with vs. without Win4Icom, several speed settings need to be changed. Once I realized all the above, I got everything working, and it's been working perfectly ever since.

[W2JAZ]

Thanks for these tips. I’ll be away from that QTH for a couple weeks and will try your suggestions when I get back. It could very well be he result of what I call ghost ports. I’ll check that first.

73
Rick, W2JAZ