How KI6ZHD logs things from Fldigi on Linux into both eqsl.cc and LoTW. 10/09/2011 http://www.trinityos.com/HAM/CentosDigitalModes/misc/ ------------------------------------------------------------------------------ +------------------- | TODO: LOTW on 10/02/11 was not updating after 45min | make sure things updated +------------------------------ Last logged information: +---------------------------------------------+ LOTW - | last good upload: Sun Oct 02 2011 17:44 PDT | +---------------------------------------------+ WAS: Mar 06 2011 22:15 PDT Nov 28 12:00 PDT Jul 18 13:07 PDT Apr 03, 2010 Nov 11 09 11:30 +---------------------------------------------+ Eqsl - | last good upload: Sun Oct 02 2011 17:44 PDT | +---------------------------------------------+ WAS: Mar 06 2011 22:15 PDT Nov 28 12:00 PDT Jul 18 13:07 PDT Apr 03, 2010 Nov 11 09 11:30 Others :: - CQP 2011 - uploaded Oct 02 2011 17:44 PDT - Field Day 2010 - uploaded Jul 18 2010 14:51 PDT ------------------------------------------------------------------------------ Preparation to do Fldigi exports: 1. Fldigi: Logbook --> View 2. Get the last log date from above, Check logs for dups, edit/populate all known good logs with at least first names, delete all bad ones 3. Review all other QSO systems and add entries as required: QSSTV: /home/dranch/Qsstv/Receive - use "ls -la" to look at file dates and compare to above log submission dates - use "kview ." to review and confirm if they are true SSTV QSOs - Any new entries should be put into the Fldigi log and once logged, move the .png images into the "Old-and-logged" dir ** Don't forget to convert to UTC time!! Add 8hrs for PST :: 7 for PDT ------ JT65 : /home/dranch/.wsjt/WSJT.LOG - all logs are UTC already - logged times are the END of the QSO, beginning is -5 min - add name via QRZ - 20m - 14.076Mhz - mode: JT65 ------ WPSR : don't log this, it's more of a beacon mode ------------------------------------------------------- Cabrillo Export for Contesting: 1. Fldigi: Logbook --> Reports --> Cabrillo 2. In the right-hand side, select the correct contest 3. Click on "Check All" checkboxes 4. On the left side, checkmark all the QSOs for the contest +-----------------------------------------------------------+ | TRICK: hold-down the left mouse button and pull the mouse | | down and the checkboxes will mark themselves | +-----------------------------------------------------------+ 5. Name the resulting file something like: filename: /home/dranch/.fldigi/logs/ki6zhd-2011-cqp-cabrillo.txt 6. IMPORTANT: - edit the resulting Cabrillo file to fill out the various fields - There are no comment lines in Cabrillo. You have multiple lines starting with #. - Blank lines are not part of Cabrillo. - 59 is not part of the exchange for The California QSO Party. You have 59 as part of the sent and recieved exchanges. - The sent QTH is part of the exchange. You were missing SCLA after your sent serial numbers. 7. Upload the resulting log to the proper contest authority ------------------------------------------------------- LoTW and Eqsl ADIF export: 7. (newer versions of Fdigi) : Logbook --> ADIF --> Export (older versions of FLdigi): File --> Logs --> Export ADIF - select all all new entries based *ON* the last good upload date as shown above in THIS file +-----------------------------------------------------------+ | TRICK: hold-down the left mouse button and pull the mouse | | down and the checkboxes will mark themselves | +-----------------------------------------------------------+ - Check mark all relivant fields for export (??) eQSL gracefully deals with any DUPES LOTW gracefully deals with any DUPES filename: /home/dranch/.fldigi/logs/ki6zhd-export--pst.adi note: NOTICE the .adi extention. This is *KEY* 8. Check the logs for any incompatible modes. This script will find and fix known issues cd /home/dranch/.fldigi/logs ./fix-logs.sh ------------------------------------------------------------------------------ Valid MODES: Certain digial modes logged by Fldigi are not recognized by the respective remote logging services and thus things must be changed in Fldigi's log -- manually -- before trying to upload the ADIF log: EQSL: http://eqsl.cc/QSLCard/ADIFContentSpecs.cfm CONTESTIA --> CONTESTI MFSK11 --> MSFK16 JT65A --> JT65 LOTW: https://p1k.arrl.org/lotw/faq#modes Domino --> DATA QPSK63 --> DATA CONTESTI --> DATA If any issues are found, this script will fix them and then create a NEW .adi file for that specific LOG system. For example: ki6zhd-100211-1702pst.lotw.adi ^^^^ If a new file isn't created for say eqsl, you can use the original .adi file you created above. ------------------------------------------------------------------------------ Eqsl.cc Submission 1. goto http://www.eqsl.cc/qslcard/Index.cfm and login (cached on HamPacket Firefox) 2. Pick the "Upload ADIF Log file" icon [in the middle of the top row] (looks like a document with a right pointing outgoing arrow) 3. foreground mode (if less than 5000 QSOs) 4. click on browse 5. goto ~dranch/fldigi/logs/ and point to the new export 6. click on upload 7. see results and fix any broken entries back in fldigi and to it all again ------------------------------------------------------------------------------ Eqsl.cc Confirmation 1. Open up FLdigi's logbook 2. goto http://www.eqsl.cc/qslcard/Index.cfm and login 3. Go to Inbox [left-most icon with a green arrow pointing into a folder ] --> scroll down to bottom> --> Find the left-hand texst "Entire Inbox " and to the right of that, click on the number shown These are ALL of your QSOs - scroll down and see which ones have a RED X or GREEN Check in the far right column 4, when trying confirm QSLs, do a - find you find it in the logbook and it's good, click on the QSL sent button and set it to day's date --> Click on Update - If you can't find it in the logbook, try looking in cd /home/dranch/.fldigi/logs grep -i * If you find it in the text logs, you'll need to create a new log entry ?? Should you create a new set of ADIFs ?? 5. If a QSL is confirmed/denied, make sure to checkbox the "Archive" box ------------------------------------------------------------------------------ LOTW Submission (1.11 v742 TQSL lib: 2.0) - confirmed this 2005 software is still current as of 4/03/2010!! http://sourceforge.net/projects/trustedqsl/files/ - All digital modes are generally said to be set to DIGITAL though LOTW can deal with most except onces mentioned above 0. goto ~dranch/fldigi/logs/ 1. run the TQSL GUI as user dranch /usr/bin/tqsl 2. File --> Sign an existing ADIF 3. Select KI6ZHD @ benton --> Ok 4. select the newly exported .adi and save with the default .lotw extension 5. leave the start and end date fields EMPTY as the Fldigi export selected the expected dates 6. Enter in your cert password 7. Assuming the signing goes well, exit out of the tqsl program 8. Open a browser and log into LOTW at https://p1k.arrl.org/lotwuser/default (cached on HamPacket Firefox) 9. CLick on "Upload file" in the upper right portion of the screen 10. Select the newly generated .lotw file (it should NOT be the .lotw.adi file) 11. Goto "Your Account" (far right in yellow bar) --> Your Activity to see status of previous submissions. It can take a bit (5+ minutes) for the newest submission to post ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Once done with both uploads, move the exports to the Old-exports dir cd /home/dranch/.fldigi/logs mv ki6zhd-*adi Old-exports/ mv ki6zhd-*cabrillo* Old-exports/ mv ki6zhd-*.lotw Old-exports/ Then, as root on Hampacket: /usr/src/archive/Hampacket/sync-hampacket-suite.sh ------------------------------------------------------------------------------ LOTW Confirmation - nothing to do, all done by LOTW - to see status of WAS: Awards --> "Select WAS account" --> Select type like "Basic" --> Application 2010 Field day - http://www.b4h.net/cabforms/fielddayentry.php ------------------------------------------------------------------------------ Counting your QSOs: Don't forget to use the other script from http://www.trinityos.com/HAM/CentosDigitalModes/misc/analyze-and-count-qsos-logs.sh cd /home/dranch/.fldigi/logs ./analyze-and-count-qsos-logs.sh Fldigi logbook.adif logbook analysis for user: dranch Mode Counts: ------------ CONTESTI: 5 CW: 4 DOMINO: 2 DOMEX8: 1 HELL: 3 JT65: 7 MFSK16: 1 MT63: 1 OLIVIA: 15 PHONE: 5 PSK31: 226 PSK63: 24 PSK125: 1 RTTY: 77 SSB: 276 SSTV: 1 THRB: 2 Unaccounted modes: ---------------- Total count of QSOs by mode: 651 QSOs by Band Count: ------------------- 10m: 29 12m: 5 15m: 149 17m: 9 20m: 307 30m: 1 40m: 138 60m: 1 80m: 9 160m: 1 Total QSOs count by band: 649 ============================================================================== ============================================================================== Old notes Eqsl error - Oct 24 13:49 Step #2 - Import Log into Database Error in Uploaded Log File YYYYMMDD=20090923 HHMM=0350 Call=KC0MS Band=40M MODE not ADIF compatible: THOR Step #2 - Import Log into Database finished 61 log entries were added out of 62 uploaded Logger not compliant with ADIF V2.1.9 specs due to invalid mode(s) Logger identified as: fldigi 1 log entries contained bad data, and were not uploaded. They are listed above in the table. You can make corrections in your logging program and upload the log again. Any records already uploaded will be ignored when you upload again, and only the corrected new records will be added. Or, you can manually add records by going to Manual Log Entry. NEW! Here is a copy of all rejected ADIF records. You can see all the records from all your successful uploads in your OutBox. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ LOTW error - 11/06/09 errored on QPSK63 ------------------------------------------------------------------------------