Log4OM

Hi:

I'm making a concerted effort to migrate from DXLab (which I like a whole lot) to Log4OM which has attracted me by its modern look and simplicity. My setup is based around a Flex-6500 and Elecraft KX3 and I use fldigi, wsjt-x/jtalert-x often.

The first question I have concerns logging in fldigi. I understand Log4OM keeps track of the .adi log in fldigi and adds new entries with a few seconds after I save them. What I found is that this happens most of the time but sometimes, for some reason, it doesn't. I don't know why this is or how to troubleshoot it but my immediate interest is in how to recover from this. Is there anything I can do at Log4OM to get it to re-read the fldigi .adi file? Or do I have to resort to a manual update? Is there anything I can look at to know if log entries will be successful or if there's a problem brewing?
My next issue concerns the cluster setup. In particular filtering. I would like to be able to filter out all spots that did not originate from NA-E. Is there a check box to tick or do I have to pick up on cluster commands?

Otherwise, I think I have everything working OK. Because SmartSDR has multiple virtual serial ports I can connect Log4OM to one port and fldigi to another port and have control of the radio from fldigi.

Working through a bit of a learning curve.

73,
Kevin K4VD

K4VD-Kevin wrote: Is there anything I can do at Log4OM to get it to re-read the fldigi .adi file?

In Log4OM import the FLDigi adi file (File/Import ADIF) duplicates will be ignored and missing QSO's added

My next issue concerns the cluster setup. In particular filtering. I would like to be able to filter out all spots that did not originate from NA-E. Is there a check box to tick or do I have to pick up on cluster commands?

Of course you can also use cluster filter commands if you so desire

OK - gotcha. If Log4OM misses an fldigi log entry I can simply re-import and let Log4OM deal with the dupes. I wonder if there's anything I can do to reduce the misses - not that it is happening often but I'd like to try and avoid it altogether. I missed the Cluster tabs. Spotter: NA is perfect. Thanks! Been through the book once and I'll need to go through a few more times it seems.

Next question...

Can I batch modify log entries? I had previously been using QRZ.com to upload logs. Log4OM does not recognize previously uploaded entries. I can search these with "QrzcomQSOUploadStatus != Y. Now, is there any way for me to change the upload status to Y for the whole batch of entries that are already there?

73,
Kev

K4VD-Kevin wrote: Can I batch modify log entries? I had previously been using QRZ.com to upload logs. Log4OM does not recognize previously uploaded entries. I can search these with "QrzcomQSOUploadStatus != Y. Now, is there any way for me to change the upload status to Y for the whole batch of entries that are already there?

See the user guide and YouTube videos regarding the QSO archive manager for full details

Excellent. Videos watched, questions answered. Thanks!

73,
Kevin K4VD

K4VD-Kevin wrote:OK - gotcha. If Log4OM misses an fldigi log entry I can simply re-import and let Log4OM deal with the dupes. I wonder if there's anything I can do to reduce the misses - not that it is happening often but I'd like to try and avoid it altogether. I missed the Cluster tabs. Spotter: NA is perfect. Thanks! Been through the book once and I'll need to go through a few more times it seems.

Next question...

Can I batch modify log entries? I had previously been using QRZ.com to upload logs. Log4OM does not recognize previously uploaded entries. I can search these with "QrzcomQSOUploadStatus != Y. Now, is there any way for me to change the upload status to Y for the whole batch of entries that are already there?

73,
Kev

Reading a text file containing ADIF is not a "perfect science". ADIF is a nightmare for modern parsing. Another way to read the file is to set in Communicator the "last bit read" to zero. This will read the file from the first bit at the next change, and then will set the last bit again.