Hi:

Some of my 160m QSOs appear as 70cm or 17m QSOs in eQSL. My ADIF comes from the Logger32 software and I cannot see anything wrong with the ADIF entries. It occurred to me, however, that having a comma (,) as a decimal character (instead of the period) might mess things up. Europeans and North Americans interchange the use of , and . (decimal point vs. thousands separator) and my computer is set up for the European use, which is adopted here.

Any comments on my band designation problem and its possible relation to the decimal character difference? Alternatively, the band problem may be caused by the fact that some 160m QSOs have been uploaded two times (which I assumed would be OK and the duplicates ignored?).

To illustrate, I have here two ADIF entries on 160m: 9A3B appears as a 70cm QSO in eQSL while SM6CNN appears properly on 160m in eQSL. Note that 9A3B was uploaded twice, while SM6CNN has only been uploaded once:

<BAND:4>160M <CALL:4>9A3B <CONT:2>EU <CQZ:2>15 <DXCC:3>497 <FREQ:8>1,820000 <ITUZ:2>28 <MODE:2>CW <NOTES:25>Band and mode most likely <OPERATOR:5>TF3KX <QSO_DATE:8:D>19961222 <RST_RCVD:3>599 <RST_SENT:3>599 <TIME_ON:6>033000 <TIME_OFF:6>033000 <APP_LOGGER32_QSO_NUMBER:3>315 <EOR>

<BAND:4>160M <CALL:6>SM6CNN <CONT:2>EU <CQZ:2>14 <DXCC:3>284 <FREQ:8>1,823000 <ITUZ:2>18 <MODE:2>CW <OPERATOR:5>TF3KX <PFX:3>SM6 <QSO_DATE:8:D>20051216 <RST_RCVD:3>599 <RST_SENT:3>599 <TIME_ON:6>234243 <TIME_OFF:6>234243 <TX_PWR:3>100 <APP_LOGGER32_QSO_NUMBER:4>6965 <EOR>

73 - Kris, TF3KX

---

TF3KX Kristinn Andersen

That's an interesting one, Kris. I assume the same as you, that it's the comma in the Frequency field that is causing the problem. I'll ask Dave to take a look for us.

---

Tim, G4VXE

Duplicates are indeed ignored.

Normally the ADIF upload uses BAND if it finds it, and only looks at FREQ if BAND is not present.

I uploaded this file as a test, and it worked just fine for me.

The new ADIF 2 specification spells out the format for numeric data as containing optionally up to a single decimal character, and specifies it as being an ASCII 46. That would make the 1,820000 data in European format invalid. However, your logger may have been designed to meet the older original ADIF specification, which said nothing about how frequencies were to be stored, except that they be in Megahertz.

A couple of things you can do:
1. See if there is a simple switch in your logger software to change the representation from comma to decimal point;
2. If not, contact your logger publisher and mention this problem;
3. Run any ADIF logs through Rich Drake's ADIF Processor (http://users.rcn.com/rbdrake/) which will usually point out any such problems. In this case, I did, and it gave a warning that 1,820000 is not 160m;
4. If you already have this one record in your OutBox as a 70cm record, delete it and re-upload the ADIF file and see what it does.

---

Of course, that's just my opinion... I could be wrong!

73,
Dave Morris, N5UP