Wednesday, December 7, 2022 12:56 UTC
|Welcome New User|
Honda Takuya from JAPAN
| If you want a Platinum membership, get it before December 31. We will st...
15M: RA3GEH, YT22YOTA,
Most eAwards: EA3ZD,F6ECI,ZL1BQD,4Z4DX,N6AR...
Power Users: AA3B,DL4ME,N2BJ...
Latest Authenticity Guaranteed
Charter Members: 2E1AVX,AF4LL,EA1BPO...
Earliest QSOs in the database
Some of our members' ancient QSL card collections!
If you have a ham radio oriented business, take a look at our advertising opportunities!
|Amateur Radio Products|
Shop Online for amateur radio books and other items!
Zip Codes - Free zip code lookup and zip code database download.
We accept up to ADIF V3.1.3 logs
New Submodes supported: C4FM,DMR,DSTAR,VARA FM 1200,VARA FM 9600,VARA HF,VARA SATELLITE
26Dec2019 We are now capturing SAT_NAME as well as SAT_MODE
If you are writing a logging application and need information on all the eQSL.cc interfaces available,
bookmark the www.eQSL.cc/Programming page
Logs imported into the eQSL.cc global database must be in ADIF format.|
The specifications for this format are at http://adif.org.uk/adif
However, those specifications do not define the CONTENT that is acceptable, the minimum required fields, and the maximum field lengths.
So, here are our requirements:
|ADIF CONTENT SPECIFICATIONS|
|We accept up to ADIF V3.1.3 logs|
Only ADIF format files can be imported. Cabrillo, Excel, or "Comma Delimited" files cannot be uploaded, and will be rejected.
The filename or extension are not important.
What is important is proper format of the tags within the file, defining the fields
per the ADIF specification (see hyperlinks above), with each record ending in an EOR tag.
|Minimum valid record contents|
|TIME_ON||only HH and MM are used|
|CALL||invalid if > 13 characters|
|MODE||must be one of table below|
|BAND or FREQ or SAT_MODE||must be one of table below (Sat_Mode not supported in .NET real-time import)|
|Optional fields that will be imported if present|
|FREQ||In Megahertz. Only one decimal point is permissible. Optional field unless BAND is missing, in which case it is mandatory. We do not check for agreement between BAND and FREQ. (Not supported yet in .NET real-time import)|
|Prop_Mode (new in ADIF 2)||MANDATORY for IRLP ("IRL"), EchoLink ("ECH"), Satellite ("SAT"), EME, CQ100 (should read "INTERNET", as should all other Internet-assisted or VOIP protocols), and other special propagation modes - Truncated to first 3 characters. See Enumerated List in the ADIF 2 spec for valid codes (Not supported yet in .NET real-time import)|
|LOG_PGM or PROGRAMID in the header||Contains the name of the logging software - If it matches the "Software Title" from our Logger Listing, then statistics will be accumulated on it. So please make sure we have your logger in our database!|
|QSLMSG||Truncated after 240 characters (Note: The field called 'COMMENT' is normally used only for private comments and is NOT printed on the eQSLs|
|RST_SENT||maximum 8 characters|
|SUBMODE||See the MODES table below for valid contents|
|SAT_MODE||See the SAT_MODES table below for valid contents|
|SAT_NAME||Maximum 15 characters, but we reserve the right to standardize satellite names to allow easier matching between incoming and outgoing eQSLs (i.e. XW-2A vs CAS-3A, etc.)|
|MY_CNTY||US County from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into! See FAQ for details|
|MY_GRIDSQUARE||Grid Square from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!|
|MY_LAT||Latitude from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!|
|MY_LON||Longitude from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!|
If you want to verify that your log file is in ADIF format, and you have used NotePad or WordPad or a similar text editor before,
you can use one of them to read your log file (it may have a .ADI extension but does not need to).
Look for lines like the ones below. They can all be on the same line or on different lines, and there will be one set for each QSO.
There may also be other information such as Name or Freq or Comments, all of which are permissible.
<QSO_DATE:8>20000409 <TIME_ON:4>1130 <CALL:6>WB4WXX <BAND:3>20M <MODE:3>SSB <RST_SENT:2>57 <EOR>
VARA FM 1200,
VARA FM 9600,
|IMPORTING ADIF FILES EARLIER THAN V3.0.4|
|FOR NOW, log uploads and real-time imports of logs that use formats older than ADIF V3.0.4 that included many of today's SUBMODEs in the MODE field will be converted automatically
|ADIF V3.0.4 was published in 2013. If your logger is older than that, now would be a good time to upgrade!|
|MODE CONVERSIONS - NO LONGER FUNCTIONAL!|
|Standard||Through June 2017, any modes in this right-hand column were converted to the Standard Mode at left. These were not ADIF compliant and are now finally phased out. Make sure your logger is compliant with the latest revisions of the ADIF specification at http://adif.org.uk/adif
|SSB||A3J, J3E, USB, LSB, PHONE, VOICE|
|Any content not matching either of these 2 columns will be rejected and require manual intervention to fix|
|BAND||If BAND not specified, FREQ contents below will convert to BAND|
|2190m||0.136 to 0.137|
|560m||0.501 to 0.504|
|160m||1.8 to 2.0|
|80m||3.5 to 4.0|
|60m||5.2 to 5.5|
|40m||7.0 to 7.3|
|30m||10.0 to 10.15|
|20m||14.0 to 14.35|
|17m||18.0 to 18.168|
|15m||21.0 to 21.45|
|12m||24.0 to 24.99|
|10m||28.0 to 29.7|
|6m||50 to 54|
|4m||70 to 71|
|2m||144 to 148|
|1.25m||222 to 225|
|70cm||420 to 450|
|33cm||902 to 928|
|23cm||1240 to 1300|
|13cm||2300 to 2450|
|9cm||3300 to 3500|
|6cm||5650 to 5925|
|3cm||10000 to 10500|
|1.25cm||24000 to 24250|
|6mm||47000 to 47200|
|4mm||75500 to 81000|
|2.5mm||119980 to 120020|
|2mm||142000 to 149000|
|1mm||241000 to 250000|
|1 These Old Bands have been deprecated||...used to be converted to this|
1 If neither BAND nor FREQ was specified, but SAT_MODE was specified, we will perform this conversion:
|SAT_MODE||Converts to this BAND|
1 SATELLITES: Prior to the SAT_MODE tag, we allowed specification of that mode inside a BAND tag,
but after ADIF 3.1 we no longer support that. Use the SAT_MODE tag instead.
Also be aware that if a SAT_MODE tag is supplied, then the PROP_MODE will automatically be set to SAT.
It is possible to commit the error of supplying conflicting BAND and SAT_MODE tags, in which case the BAND overrides SAT_MODE.
If you need to specify a different mode than one of those listed above, please contact eQSL.cc technical support.
Important note for .NET real-time logger imports: SAT_MODE and PROP_MODE are not yet supported in the .NET interface.
U/S and U/V were just added 18Dec2005. Other new modes will be added soon.
Sat_Name import only began on Christmas Day, 2019.