Log4OM

You are right. I control the frequency but not the PTT.
Actually I use FLdigi with Log4OM but also Win4ICOM.
Win4ICOM is connected via omnirig to Log4OM via virtual COM.
Win4ICOM allows you to create a split COM port making it available to third party software.
In practice I have a virtual COM com1 <-> com2, Log4OM speaks with omnirig with port 1. Win4ICOM listens to com2 while my Icom IC7610 is connected directly via com3 to (CAT) at Win4ICOM.
Win4ICOM uses another virtual port com5 <-> com6 to connect to FLdigi which listens on com6.
If necessary I can be more clear

I am attaching some screenshots to be clearer:

my virtual com port omnirig-log4om settings Win4Icom settings

Win4Icom 3rd party sw FLdigi settings

In general you can use any virtual serial port emulator, for example the one from Eterlogic http://www.eterlogic.com/Products.VSPE.html or com0com http://com0com.sourceforge.net/ or the one Max is using from Eltima https://www.eltima.com/de/products/vspdxp/.

I am using VSPE from Eterlogic. My Radio is connected to the USB Port of the Computer on Port 3 (Check Windows Device Manager). In VSPE I created a Splitter
Com3 = physical Port
Com1 = virtual Port

Make sure speed properties of the Splitter matches your TRX settings !

I then configured FlDigi and Log4OM (Omni-Rig) to use virtual Port COM1.
That's it. Now you can key the TRX in Fldigi and frequencies are synced between TRX, Log4Om and FlDigi.

Just installed log4om v2 on a new win 10 laptop. I have fooled around with the fldigi settings under harware ptt but no luck keying the ftdx3000. Can you be more specific on how to make this work?

Thanks, Roger

Please disregard my previous post I did not see your complete post. I still don't understand why you need to create a virtual port? Sorry for confusion not much of a computer guy.

Hi Roger,
I will try to be clearer.
For frequency and mode Log4OM already speaks with FLdigi:
- in FLDigi Configure-Rig comtrol you must select flrig. Addr 127.0.0.1 port 7362 (for example)
- in Log4OM Settings-Configuration-FLdigi the same settings and (port 7362) and select start service
- always in Log4OM Connect-FLDigi-connect
- launch FLDigi
Now you should see the same frequency.
The problem now is to send it in TX because the COM port is occupied by Log4OM.
To overcome this problem, the COM port must be split either with the system indicated by Roland HB9VQQ or with a program with the splitter for example Win4ICOM (I have an ICOM but there is also Win4YAESU).

If you use Win4ICOM, it will speak to your rig and it will divide the commands for both Log4OM and FLDigi TX included (splitter)

Same applies to Fldigi with Kenwood TS590SG - frequency display in fldigi and fldigi log reading OK but no tx control from fldigi.
OS:W10. Fldigi 4.1.09 (update shows it to be alpha version!) but same applies with 4.1.08.
System working 100% with WSJT/JS8Call.

Graham,
with the TS590 you can use the software indicated by Roland.
Create the virtual port (in case of Roland the real port is com 3 the virtual port is 1) and make it split. Use the same port (e.g. from Roland com 1) for FLdigi and omnirig

Max/Roland. Many thanks for this information which I hadn't seen when I made my original post.

I was already using VSPE splitter software but had not thought to try rigcat, it has resolved my tx issue
with my TS-590SG so again many thanks.