115200 baud for Win4Icom spectrum display

[kd7mw]

Does Log4OM not "like" 115200 baud?

I've had had a stable setup for some time now, with JTDX connected as in the Log4OM manual, and FlDigi via the dual cable method. They both play nicely (separately, of course). But now I'm having one problem adding Win4Icom to the mix--the onscreen spectrum display only works at 115200 baud.

I can connect my Icom 7300 to Win4Icom (with no other programs running) on COM7 (USB port), and it will run all day at 115200 baud with the spectrum display. But if I add Log4OM, eventually the setup freezes and I have to restart the programs. It's happened even when I don't transmit, just listen and play with the onscreen buttons. But if I run everything at 19200 baud, omitting the spectrum display, all appears well.

The radio is on COM7 and Win4Icom talks directly to it on COM7. I set up a COM16/17 pair with Com0Com, and connect Win4Icom's first "virtual radio" on COM16 with Log4OM on COM17. The cables are connected directly to the computer, not via a screen USB hub.

Windows 11, Dell XPS i5 PC, 16 GB RAM, solid state drive. Log4OM 2.23.0.0. Trend Micro Internet Security (virus checker). Spyder screen calibrator, which adds a color lookup table to the video display (I also do photography). The PC has both USB 2 and USB 3 ports, if that makes any difference.

[kd7mw]

To answer my own question... Why Log4OM appears to not "like" running at 115200 baud doesn't matter in my case. The solution is to only run the "hard" connection (on a physical USB port) between Win4Icom and the radio at 115200. The "virtual radios" that use comport pairs created by com0com can run at Win4Icom's default speed of 38400 baud, including the virtual connections to Log4OM and digital mode software. So far I've set this up with Log4OM and JTDX, WSJT-X and FlDigi. The latter three run only one at a time. Everything's working nicely. I'm very impressed with Win4Icom, which probably applies to the other "Win4-" control programs as well.