Just about to give up, yes its FLDigi :(

[M7DJK]

Ok, i will apologise firstly - this is the end of a waste of four 8 hour days of shack time trying to sort out a logging app and three radio apps - WSJT-X, JS8Call and you guessed it FLDigi. I am just about to chuck the PC out the window now.

I thought my original desire was easy - i wanted to have the 3 apps log QSO's to a log as well as have that log show real RF info like frequency/mode etc for when i do SSB QSO's without an app. Previously i was running a log on my MAC laptop and transferred each day via ADIF export/import from each app to the log program - yes a right PITA and often got forgotten etc.

Many questions were asked on the 'net, i ended trying many log apps, even Ham Radio Deluxe which came close but only because with HRD you simply do not need FLDigi at all. However, I just couldn't justify the costs - about £80 1st year and £40/year ongoing, especially when i don't want the massive rig control side of HRD at all.

Tried N3FJP, terrible interface and failed on FLDigi.

Ended up with Log4OM which was easy to setup for WSJT and JS8 but have now spent over 16 hours trying to get FLDigi working to no real end result. I have the ADI scan feature working well, but it all falls apart when it comes to XML/CAT - ends up with both apps fighting each other or fighting the rig.

I have an Icom 7300, latest versions of all apps, all apps are running as administrator. I even blew £25 on the eterlogic serial port splitter license because i thought it might work.

I have the rig port split in VSPE, I have Omnirig running on the virtual port.

I can have Log4OM connected to omnirig and it works as expected.

I can have FLDigi connected via Hamlib and it works as expected, tried RigCat and it didn't work.

What i can not do is have Log4Om and FLDigi connected at the same time - the mode and frequency in FLDigi go nuts. I have had it switching into RTTY after every over, randomly going to CW etc. Its just a mess.

I sort of had it working where i had to set the frequency in FLDigi and then go to the log and set it again there so the rig was set, useless. Also the mode was messed up - for the 7300 it must be USB-D.

Again, sorry for the long post, is there any way to get this stuff actually working?? Has anyone succeeded ?? I have seen and followed some posts from the forum but makes no difference. What makes it worse is that I didn't make notes and cant remember which logging app would be the best option now I even had a phone chat with Terry today (thanks Terry) but after following the help it still failed.

[AE6DS]

I have all those working together but with a Flex 6600 rather than Icom. Some quick notes that might or might not help:

• I don't use the Log4OM FLDigi service and in fact i turn it off. It does not play nicely with Flex SmartSDR when running multiple simultaneous copies of FLDigi.

• For FLDigi logging, I have the ADIF Function of Log4OM follow C:\Users\YOU\fldigi.files\temp\log.adif which is a temporary file that is ADIF compliant. The fldigi logbook.adi file is not.

• For WSJT-X I have Log4OM listening on a few tcp ports so I can run multiple instances direct or aggregate them through GridTracker.

• For rig control I am using rigcat to a virtual serial port, but only because of a hamlib bug.

Since you are using VSPE and hamlib is working withing FLDigi, you could also use hamlib for rigcat in Log4OM. That may reduce some of the conflicting serial issues.

Your description of the issue sounds similar to what happened when I had both rig control and the Log4OM FLDigi service running. In my case I don't lose functionality turning off the Log4OM FLDigi service since I run the QSO from FLDigi to being with (including callsign lookup, worked before, etc), so following the temp adif log is sufficient to get the right info logged in Log4OM. [Same for WSJT where I run the QSO from the app -- the only time I am running the QSO from Log4OM is for CW, and that works fine, even in parallel with WSJT and FLDigi running simultaneously on other slices.]

[M7DJK]

Hmm, thanks for that.

Is there any chance you could scribble out rough block diagram of the interconnections for FLD, Log4OM and the rig etc, I think it will make things much clearer b

[G4POP]

One solution that might work easier for you is to take advantage of the dual CAT connections on the 7300 - NOTE I HAVE NOT TRIED THIS!

Separate the USB and remote CAT connections in the 7300 menu - Connectors/C-IV 'CI-V USB Port - Unlink from remote - This will now provide two separate com ports each with its own Com port number so no VSP required and no conflicts

Use the 7300 USB connection for Omnirig and all software that connects to it

Use the 7300 rear REMOTE CAT connection with a CI-V USB connection for FLDigi using Rigcat or hamlib if you must!

Log4OM can continue to read the FLDigi ADIF file

All software will sync with the radio freq and mode

[M7DJK]

That sounds like it could work, i'll have to find and buy a CIV/CAT cable though

Have been recommended to also try using FLRig instead of OmniRig, will see if that does anything later today.

[G4POP]

That sounds like it could work, i'll have to find and buy a CIV/CAT cable though

Have been recommended to also try using FLRig instead of OmniRig, will see if that does anything later today.

If you have to buy a cable make sure that you buy an FTDI version, check out the ones G4ZLP supplies

[M7DJK]

Just ordered one, thanks

[G4POP]

OK to put this one to bed once and for all, I have set up my IC7300 as I suggested above and it all works 100%

This setup will be added to our user guide but meanwhile here is a step by step set up in the attached file

IC7300 CAT control.pdf

(118.52 KiB) Downloaded 380 times

[M7DJK]

Thanks Terry, appreciate your time on this.

That does soundalike the best way to go, i have ordered the FTDI cable and will not bother messing with the setup any more until it arrives just in case it compounds matters

Hopefully this will sort it all out once and for all.

[M7DJK]

OK to put this one to bed once and for all, I have set up my IC7300 as I suggested above and it all works 100%

This setup will be added to our user guide but meanwhile here is a step by step set up in the attached file

IC7300 CAT control.pdf

While waiting for my CIV cable to arrive i had one of those 'coffee moments'....

When connected with two cables, i can see how things should play more happily but how does the Icom USB-D mode play out in Log4OM - I don't recall seeing USB-D as a mode listed, probably as its not an ADIF mode???

Did this show up in your tests Terry???