FLDigi Integration

[G0TED]

Hi Daniele,
I am having difficulty setting up the FLDigi Integration, as you will see from the attachment the necessary commands are missing from the right hand side of the Settings tab, any ideas please?
Keep up the good work Daniele and a very happy New Year to you and your team.
73 de Ted G0TED

[DF5WW]

Hi Ted,

you can´t use the Settings tab from Log4Om. You have to open the communicator task in the taskbar to find the correct setup commands. Open the communicator, stop it, make the settings, start communicator and minimize to taskbar (not closing). First go to the HELP menu of Log4Om "Help" .. "English" .. force manual download. Open the manual after download it. From site 150 you will find the step by step setup for the fldigi interface.

cu

[G0TED]

Hi Juergen,
Thanks very much, all sorted!

73 de Ted G0TED

[DF5WW]

Thank´s for the positive reply

[N9BBE]

I have a question. I have to start FLDigi first to get the interfacing between it and Log4OM to work. Is this normal?
I have setup Log4OM and FLDigi per the recent Log4OM help file.

[G4POP]

Yes because FLDigi is passive it has to be interrogated, however if Log4OM is started first and try changing band on the rig and it should make FLDigi respond

[N9BBE]

OK, I see that now. All is FB. Thanks again Terry...

[N9BBE]

Have another issue. I have Log4OM and FLDigi working together as far as reading the radio info but Log4 is not logging contacts made in FLDigi. The contacts are getting into the FLDigi log. Probably another oversite again on my part.

[G4POP]

Have another issue. I have Log4OM and FLDigi working together as far as reading the radio info but Log4 is not logging contacts made in FLDigi. The contacts are getting into the FLDigi log. Probably another oversite again on my part.

I know what the issue is, FLDigi is not using the default logbook named "Logbook" it is using one called "Newlog" as a result Log4om cannot find the ADIF.

Problem is that I will need to talk you through the fix on Skype, is that possible?

Next release of Log4om allows you to identify the actual file name, not just the path to Logbook.adi

[IW3HMH]

Next release of Log4om allows you to identify the actual file name, not just the path to Logbook.adi

If i remember correctly this feature is already implemented. If users has only the path (as previous version requires) i will automatically add "logbook.adi" for backward compatibility, but now you can (must, in the new release) select the ADIF file complete with his name