USE FLDIGI FOR GENERAL LOGGING FULL
USE FLDIGI FOR GENERAL LOGGING CODE

It is faster and more efficient that way.I log in various entry points like you - if it’s portable/SOTA/POTA i either use paper or hamlog iOS. This way I know I am always reading just one qso at a time and don’t need to adjust positioning to read the last x number of lines. My application is a gateway between Fldigi and either DXLabs DXKeeper or Logger32. At that point it gets passed to another thread that processes the file contents if anything needs to be changed and logs the qso in the other application.

If the file is there I just read in the one line in the file and then delete it. I have a timer that runs in it’s own thread that pops every 10 seconds to look to see if the file is there. According to my debug tests the process of reading the contents and deleting it takes 11ms so Fldigi should not be updating the file when I delete it. It gives me time to read the file in and then delete. I know that a qso will not get logged that fast from the last qso to the next that’s why I chose 10seconds. Each time a qso is written it adds the record to that file. So my program knows if the file exists then a new qso was written to it.įrom: [ On Behalf Of Philip Rose via groups.ioįldigi won’t stop updating it. I delete log.adif after I have read the contents so a new file is created for each qso that is logged.

USE FLDIGI FOR GENERAL LOGGING FULL

I also have a timer that watches fldigi.files/temp/log.adif That file is written to each time a qso is logged and includes the full adif output of the qso. My applications uses timers to communicate with Fldigi's XMLRPC interface. On 8/29/20 1:43 PM, Rick Ellison wrote: Fldigi interfaces to a couple of loggers that each have their own interface (MacLogger,ACLog). This email has been checked for viruses by Avast antivirus software. To: Fldigi interface to external loggers.

USE FLDIGI FOR GENERAL LOGGING CODE

However I notice in the code (fldigi/src/logbook/xmlrpc_log.cxx) it mentions an external logger, so is there another interface.įrom: On Behalf Of Philip Rose via groups.io I've had a look at those files Dave mentioned in a previous thread, and I could use the fllog XmlRpc interface as long as enabling that still allows fldigi to use its internal log.

On Aug 29, 2020, at 10:58, Philip Rose via groups.io wrote:ĭoes Fldigi have a defined interface to external loggers? Currently my logger reads logbook.adi every 60 seconds, but I would like to send the ADIF directly to my logger (as well as fldigi maintaining its own log), so that it appears in my log at once (both the logbook and the DxAtlas map I use to display contact locations). However I notice in the code (fldigi/src/logbook/xmlrpc_log.cxx) it mentions an external logger, so is there another interface. > I've had a look at those files Dave mentioned in a previous thread, and I could use the fllog XmlRpc interface as long as enabling that still allows fldigi to use its internal log. > Does Fldigi have a defined interface to external loggers? Currently my logger reads logbook.adi every 60 seconds, but I would like to send the ADIF directly to my logger (as well as fldigi maintaining its own log), so that it appears in my log at once (both the logbook and the DxAtlas map I use to display contact locations). > On Aug 29, 2020, at 10:58, Philip Rose via groups.io wrote:

See the fldigi config/logging tree to see the two loggers supported. At this point when using fllog it does not write to the internal logger. The interface is specific to each logger so there’s no general logger interface except to it’s own internal or fllog. Yes, fldigi does interface with a couple loggers.

Use fldigi for general logging