Log4OM

Within Log40OM communicator, interfaces,settings,inbound, FLdigi interface, there is a box on the bottom that says "starting position."
mine says 1523747 and the manual says 104. Is that a number I should enter or is it done by some other method by the software?

Tnx Chuck

Has Fdigi been logging ok to Log4om?

No not now Terry,
It was in the early stages of my just getting started but then it stopped. When this large number appeared I do not know.

so to answer your question, no its not logging now with xml-rpc and freq in Log4OM is not being transferred to FLDigi.

Chuck

Providing there are no QSO's in FLdigi requiring transfer to Log4om then you can empty the FLdigi logbook and set the number in Log4om to 0 (zero) the number is the last line number in the FLdigi logbook - no entries = zero

I clear the Fldigi logbook, no entries. I go to FLdigi Settings within communicator and set "starting position" to zero.
I then insert a call into fldigi and save it, it saves to fldigi but does not transfer to Log4OM.

Service status' are all green in the interface box of Log4OM communicator and the very bottom of Communicator says "connected to 127.0.0.1:8081.

The Starting position number in Communicator has again gone to 1523747.

Do you have Teamviewer installed?

I have installed team view, how do we proceed?

Terry,
I am not sure what happened, it just started logging from FLdigi, why I do not know. I have not changed anything at all.
Ah well, will see what happens as the days go on. It seemed like it took about 15 seconds for the data to transfer.

Then only thing I have done was delete windows update #KB3022345 after it failed under a Scan Files Command giving me a integrity violation. This was done under a totally unrelated trouble, well unrelated as far as I was concerned. It is MS customer experience and diagnostic telemetry. Maybe a fancy name for MS spy????

73
Chuck

I had a similar problem caused by Google Chrome, when I removed Chrome the issue disappeared and the computer ran a lot better generally

The delay is not time taken to add to the log necessarily more likely a refresh delay caused by something else happening on your computer in the background

Check show log to see the times taken for different functions