Swisslog's Forum

Full Version: Error message trying to import ADI from Club Log printed
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I get an error when trying to import and merge qsos from club logs OQRS printed ADI. Attaching the ADI file is not allowed and the screeshot is apparently too big. Pse indicate how I can forward it.
Hi Tom,

I think you have not read the news from version 5.99a and the updated help about the new Merge option. You CAN'T import the Club Log OQRS and printed files directly with the Import QSO and checking the Merge option. This is speciffically explained in the Import QSO chapter due to its specific features. I have added a specific function in Tools / Club Log menu that even download automatically the OQRS file. Please read carefully the detailed instructions how to proceed to handle Club Log OQRS in the Swisslog help (Other features / Club Log tools).

Best 73
That certainly helped! Smile
There was a bug in the creation of the ADIF file from Club Log, changing all FT8 RSTs to 599 instead of the dB reports, but it seems to have been fixed now, thanks to Marios, 5B4WN/G0WWW in the Club Log development team
Yes, during the development of the new function to process OQRS files I detected that RSTs were not in db format. I'm glad that now it's fixed. However, if you use the new function "Process Club Log OQRS ADIF" these fields are skipped because the only fields processed are QSL SENT and QSL_SENT_VIA. When you upload the ADIF including the printed QSO it also processes the QSL SENT DATE field.

Best 73
Today, when using the "Process OQRS ADIF file" function, no merging of qsl info happened when I used the automatic download file function. Using the function on the ADIF file that I downladed earlier when printing labels from ClubLog, the updating of data works ok-

Enclosed two ADIF files and the report from the unsuccessful import. Because the forum does not allow .adi files, I renamed them .txt

73 de Tom
Hi Tom,

I would need your database to check but I don't see any problem. In the QSO report there is one QSO processed:

Data merged with QSO: OH10X, 09/02/2019, 13.55.00, 80M, SSB
-QSL Action: OQRSBureau BEFORE: send

This is the only QSO in the source file having the Q in the QSL SENT field indicating is queued. Swisslog has done the job and has assigned OQRSBureau in the QSL Action field to show you you have a OQRS request. Keep oin mind that the OQRS file includes ALL QSOs previously requested. But because you already printed the QSL it contains Y in the QSL SENT field instead of Q. In the QSO report you have to check for QSO that QSL action has been changed to OQRSBureau or OQRSDirect. In a logbook view you can easily check all your QSO having OQRSBureau or OQRSDirect and you have not sent the QSO already (QSL SENT will be 0 or N).

Best 73