FAQ
- I have uploaded an incorrect QSO – how can I delete it?
From the View QSOs screen you can Delete a QSO provided it has not been verified. There is also an option on import to delete all unverified QSO.
- Can I download my QSO from Clublog, eQSL or LOTW (or most other log systems) and upload to awards?
No. These systems do not capture all of the log you uploaded - they only capture what is needed specifically for their purposes (as does the Award system). They rarely store RST or your eQSL/LOTW QSL. The upload file will have to come from your log, which hopefully has these details.
Note: Logs downloaded from QRZ logbook are OK if you are using that as your log. They support paper, eQSL and LOTW QSL as well.
- Can I upload the wsjtx_log.adi file from WSJT-X to awards?
No. The wsjtx_log.adi file is missing the DXCC and QSL received fields. You will have to load it into your log program, and have it fill in the missing DXCC field. If you use JTAlert in concert with WSJT-X,
it will automatically fill in the DXCC field (and others) in your log.
- I have uploaded my log, but I can't see any Paper and/or eQSL and/or LOTW QSL?
Your ADIF file is missing <QSL_RCVD:1>Y and/or <EQSL_QSL_RCVD:1>Y and/or <LOTW_QSL_RCVD:1>Y fields. When you export your log from your logging program, you must also export the fields that contain your claim of having a QSL. You have no QSL claims in your log, so there is nothing to verify. You need to record, in your logging program, all received QSL from all sources. Paper has to be recorded manually, but most logging programs have a way to import QSL from eQSL and LOTW. In other words, the award system cannot import your QSL from eQSL or LOTW (or paper). It can only verify one that you claim to have. Correct your log and upload again.
- How can I make my log upload up to 30 times faster?
There are two options to reduce your log file upload time - STRIP and ZIP. You can use one or other or both.
- STRIP - 80% of your log file is not used by the award system. If you strip out all the unused fields, your file will typically shrink to 20% of its original size, and it will upload 5 times faster. One program that does this is "ADIF_FILTER" by SP7DQR and can be found here. Remember to include STATION_CALLSIGN, CALL, DXCC, QSO_DATE, TIME_ON, BAND, MODE, RST_SENT, QSL_RCVD, EQSL_QSL_RCVD, LOTW_QSL_RCVD and GRIDSQUARE fields (only).
- ZIP - You can compress you log file into a zip archive and upload that. Zipping a log typically reduces it to 15% of its original size.
You can do both (STRIP then ZIP) and the resulting file will be ~3% of the original size. Using ZIP only is usually suffient, and easier.
- How long should approval of an award submission take?
Assuming there are no issues with the submission, it should take less than 2
weeks, at which time you can print your own certificate.
- When can I change my card checkers?
At any time. Anything not checked by a previously nominated checker will remain
unchecked.
- Who checks the checkers?
The WIA Award Committee will randomly, or when they have concerns, ask to see
the originals of any cards used to claim an award.
- Why is ClubLog.org used to validate callsigns and DXCC entity?
ClubLog.org is believed to contain the most complete and accurate callsign and DXCC validation data available. It is kept up to date, and validated by its many users. Its prefix to DXCC mapping tables are time based, and contain in excess of 3,500 entries. Its list of illegal operations exceeds 3,000. It also contains a list of 10,000+ time based exceptions, where people were operating outside their normal DXCC entity. It is the definative source for this data at present. This data is freely available to all, and can be challenged/corrected if required.
- Can I request a printed certificate be posted?
No.
- Do I have to ensure I just upload changes in my log since the last upload?
No. You can upload your entire log at any time – it will be merged with your
current QSO list. Details of DXCC, gridsquare and QSL received will be updated
for existing records. Records that have been verified will not be touched.
- How secure is the system?
Very.
- No persons other than, the WIA Awards Committee, and your nominated card checkers, can view your QSO data.
- Users are authenticated using memnet (VK) or username/password (DX), and the password is not decryptable.
- The eQSL username/password required to validate eQSL QSO is not stored in the system.
- The LOTW username/password required to validate LOTW QSO is not stored in the system. They are passed to LOTW using Secure Sockets layer (SSL).
- What happens if I change my callsign, take over someone else's callsign, or I have multiple callsigns?
Provided your ADIF log always has the correct value for STATION_CALLSIGN, i.e. the callsign you used when you made the QSO is stored in the log, there will be no problem. QSO data is stored against your ACMA client ID, which does not change. The STATION_CALLSIGN will need to be correct if you hope to validate the QSO.
If you have a new callsign, change the "Default Callsign" field in your profile, and all new, upgraded or updated certificates will be recorded against the new call.
- How can I load my paper log?
There is no way to manually type in a log. It is not feasible to do so. The only practical way is to enter your log into one of the many logging programs, and export an ADIF file from there.
- Can I migrate my Paper QSL from the spreadsheet system?
Yes. If you send your most recent, approved, award spreadsheet to the awards manager, the Paper (Only) QSL can be imported to this system. Note: Paper QSL's will only be migrated if your log records that a Paper QSL has been received, i.e. the QSL_RECV field is set to "Y". They should already have a grey tick in the award system. The import will turn them green. The import will NOT add QSO that aren't already in your log, only verify ones already there.
- I have a log from a DXpedition. How should I deal with that?
Not withstanding the fact that the system can cope with a log from multiple DXCC entities, it is far preferable to create an account for each separate DXCC entity. If you are a WIA member, these additional accounts are free.
- I have QSO, made from multiple DXCC entities, in my log. Can the system cope with that?
Yes. If the system detects that you have QSO from multiple DXCC entities, it will ask which of these entities you wish to filter on for determining award status. You can achieve the same award from multiple entities. Please ensure that STATION_CALLSIGN or OPERATOR has the correct value in your ADIF file.
- How is MODE supported?
All modes defined in the ADIF specification are supported including Mode & Submode. In addition, some historically used modes (e.g. Phone) are also supported. Only the mode is stored in the system. The modes/sub-modes recognised by the system are listed below.
| Mode | Submodes | Class |
|---|
| AM | | Phone |
| ARDOP | | Digital |
| ATV | | Digital |
| CHIP | CHIP64, CHIP128 | Digital |
| CLO | CLOVER | Digital |
| CONTESTI | | Digital |
| CW | A1, PCW | CW |
| DIGITALVOICE | C4FM, DMR, DSTAR, FreeDV, FREEDV, M17 | Phone |
| DOMINO | DOM-M, DOM4, DOM5, DOM8, DOM11, DOM16, DOM22, DOM44, DOM88, DOMINOEX, DOMINOF | Digital |
| DYNAMIC | VARA HF, VARA SATELLITE, VARA FM 2100, VARA FM 9600 | Digital |
| FAX | | Digital |
| FM | | Phone |
| FSK441 | | Digital |
| FT8 | | Digital |
| HELL | FMHELL, FSKHELL, HELL80, HELLX5, HELLX9, HFSK, PSKHELL, HELLSCHREIBER, SLOWHELL | Digital |
| ISCAT | ISCAT-A, ISCAT-B | Digital |
| JT4 | JT4A, JT4B, JT4C, JT4D, JT4E, JT4F, JT4G | Digital |
| JT44 | | Digital |
| JT65 | JT65A, JT65B, JT65B2, JT65C, JT65C2 | Digital |
| JT9 | JT9-1, JT9-2, JT9-5, JT9-10, JT9-30, JT9A, JT9B, JT9C, JT9D, JT9E, JT9E FAST, JT9F, JT9F FAST, JT9G, JT9G FAST, JT9H, JT9H FAST | Digital |
| JT6M | | Digital |
| MFSK | FSQCALL, FST4, FT4, FT4W, JS8, JTMS, MFSK4, MFSK8, MFSK11, MFSK16, MFSK22, MFSK31, MFSK32, MFSK64, MFSK64L, MFSK128, MFSK128L, Q65 | Digital |
| MSK144 | | Digital |
| MT63 | | Digital |
| OLIVIA | OLIVIA 4/125, OLIVIA 4/250, OLIVIA 8/250, OLIVIA 8/500, OLIVIA 16/500, OLIVIA 16/1000, OLIVIA 32/1000 | Digital |
| OPERA | OPERA-BEACON, OPERA-QSO | Digital |
| PAC | PACTOR, PAC2, PAC3, PAC4 | Digital |
| PAX | PAX2 | Digital |
| PKT | | Digital |
| PSK | 8PSK125, 8PSK125F, 8PSK125FL, 8PSK250, 8PSK250F, 8PSK250FL, 8PSK500, 8PSK500F, 8PSK1000, 8PSK1000F, 8PSK1200F, FSK31, PSK10, PSK31, PSK63, PSK63F, PSK63RC4, PSK63RC5, PSK63RC10, PSK63RC20, PSK63RC32, PSK125, PSK125C12, PSK125R, PSK125RC10, PSK125RC12, PSK125RC16, PSK125RC4, PSK125RC5, PSK250, PSK250C6, PSK250R, PSK250RC2, PSK250RC3, PSK250RC5, PSK250RC6, PSK250RC7, PSK500, PSK500C2, PSK500C4, PSK500R, PSK500RC2, PSK500RC3, PSK500RC4, PSK800C2, PSK800RC2, PSK1000, PSK1000C2, PSK1000R, PSK1000RC2, PSKAM10, PSKAM31, PSKAM50, PSKFEC31, QPSK31, QPSK63, QPSK125, QPSK250, QPSK500, SIM31 | Digital |
| PSK2K | | Digital |
| Q15 | Q15X25 | Digital |
| QRA64 | QRA64A, QRA64B, QRA64C, QRA64D, QRA64E | Digital |
| ROS | ROS-EME, ROS-HF, ROS-MF | Digital |
| RTTY | ASCI, ASCII | Digital |
| RTTYM | | Digital |
| SSB | A3J, J3E, PHONE, VOICE, LSB, USB | Phone |
| SSTV | | Phone |
| T10 | | Digital |
| THOR | THOR-M, THOR4, THOR5, THOR8, THOR11, THOR16, THOR22, THOR25X4, THOR50X1, THOR50X2, THOR100 | Digital |
| THRB | THRBX, THRBX1, THRBX2, THRBX4, THROB1, THROB2, THROB4 | Digital |
| TOR | AMTOR, AMTORFEC, GTOR, NAVTEX, SITORB | Digital |
| V4 | | Digital |
| VOI | | |
| WINMOR | | Digital |
| WSPR | WSPR-2, WSPR-15 | |
Modes defined in ADIF version 3.0.6
- Why was the system developed?
The WIA has used, for many years, a system of Excel spreadsheets. These are a
far from ideal solution, but the best technology could offer at the time. In
Feb 2013, an ADIF log import feature was added to these sheets which greatly simplified
the submission and checking process. Nevertheless, some problems remained – not
the least of which is not everyone has Excel, and there is still a lot of
manual Excel file handling involved. The ultimate WIA vision (some call it
Utopia) has always been to develop a totally online and paperless system that
is far superior to any Excel system.
- How can I get support?
No doubt there will be bugs and enhancement requests, and these can be sent to vk3ohm-at-wia.org.au. I only ask that you 1) check first that it is not operator error and read the instructions, and 2) clearly describe the problem and what you were doing when it happened. Please include your callsign. Vague support requests will be ignored.
- What's the system written in?
About 11,000 lines of php and a MySQL database, running on an Apache server
under Linux. It has http links to clublog.org, eqsl.cc, LOTW and the ACMA.
It was developed by Marc Hillman (VK3OHM) with assistance from Robert (VK3DN) & Tim Broomhead (VK3KTB).
|
