Found an error when I updated TQSL. I emailed Bart Janke, and here is his reply from the DXCC desk. Please do not shoot the messenger:
Jahnke, Bart, W9JJ
1:34 PM (1 hour ago)
to me
Okay,
Correction…
The applicable field for State Abbreviation is “My_State”. So it is failing on Missouri again – sorry ☹
LOG4OM should be notified so that they can correct the error.
73 Bart W9JJ
Change in ADIF With TQSL 2.5.1
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Change in ADIF With TQSL 2.5.1
I'll check.
There is a problem with ADIF and how ADIF itself is managed.
There is not a source of data we can use to automatically perform checks and program updates, so everything is left to the developer that should take note of each html table, extract data and fill the data in the application archives.
It's a long and tedious work we are implementing, without any automatic support or data validation tool provided by a standard (ADIF) that after 20 years or so is still unable to evolve to something that can be automatically parseable from 21th century programming languages...
There is a problem with ADIF and how ADIF itself is managed.
There is not a source of data we can use to automatically perform checks and program updates, so everything is left to the developer that should take note of each html table, extract data and fill the data in the application archives.
It's a long and tedious work we are implementing, without any automatic support or data validation tool provided by a standard (ADIF) that after 20 years or so is still unable to evolve to something that can be automatically parseable from 21th century programming languages...
Daniele Pistollato - IW3HMH
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Change in ADIF With TQSL 2.5.1
Can you kindly copy-paste here the ADIF row with issues or the value of the current MY_STATE field in the QSO?
Daniele Pistollato - IW3HMH
Re: Change in ADIF With TQSL 2.5.1
I am at work now, but will gladly send later or tomorrow. I have the email I can forward with the files Bart looked at and can forward that from my k0xm@byrg.net email. This is an issue with the new TQSL as I am experiencing it with a few other logging programs I play with. I check 4 different ones, and they made a change which is causing the issue. The ARRL that is.
Re: Change in ADIF With TQSL 2.5.1
I cannot attach the file.
#++++++++++++++++++++++++++++++++++++
# Log4OM 2 by IW3HMH version 2.4.0.0
# http://www.log4om.com
# created: Thursday, April 9, 2020
#++++++++++++++++++++++++++++++++++++
<ADIF_VERS:5>3.0.8 <PROGRAMID:7>Log4OM2 <PROGRAMVERSION:7>2.4.0.0 <eoh>
<ADDRESS:48>Po Box 3218
Valdez
Ak, 99686
United States <A_INDEX:1>4 <ANT_AZ:1>0 <STATE:2>AK <BAND:3>40m <BAND_RX:3>40m <CALL:5>WL7CG <CONT:2>NA <COUNTRY:6>Alaska <CNTY:17>AK,Valdez Cordova <CQZ:1>1 <DISTANCE:7>4268.38 <DXCC:1>6 <EMAIL:14>wl7cg@arrl.net <EQSL_QSL_RCVD:1>N <EQSL_QSL_SENT:1>N <FREQ:8>7.076070 <FREQ_RX:8>7.076070 <GRIDSQUARE:6>BP61xb <ITUZ:1>1 <LOTW_QSLRDATE:8>20200408 <LOTW_QSLSDATE:8>20200408 <LOTW_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <MODE:3>FT8 <MY_CITY:9>Grandview <MY_CNTY:7>Jackson <MY_STATE:8>Missouri <MY_COUNTRY:13>United States <MY_CQ_ZONE:1>4 <MY_DXCC:3>291 <MY_GRIDSQUARE:6>EM28ru <MY_ITU_ZONE:1>7 <MY_NAME:11>Chuck Kraly <MY_POSTAL_CODE:5>64030 <MY_RIG:7>IC-7610 <MY_STATE:8>Missouri <MY_STREET:17>6106 E 147th Terr <NAME:12>Alan J Sorum <OPERATOR:4>K0XM <OWNER_CALLSIGN:4>K0XM <STATION_CALLSIGN:4>K0XM <PROGRAMID:7>LOG4OM2 <PROGRAMVERSION:7>2.4.0.0 <QSL_RCVD:1>N <QSL_RCVD_VIA:1>E <QSL_SENT:1>N <QSL_SENT_VIA:1>E <QSL_VIA:45>DIRECT, QRZ, LOTW, EQSL and CLUBLOG (NO BURO) <QSO_COMPLETE:1>Y <QSO_DATE:8>20200408 <QSO_DATE_OFF:8>20200408 <QTH:6>Valdez <RST_RCVD:3>-13 <RST_SENT:3>-09 <SWL:1>N <TIME_OFF:6>045500 <TIME_ON:6>045400 <TX_PWR:3>100 <K_INDEX:1>2 <LAT:7>61.0615 <LON:9>-146.0016 <MY_LAT:7>38.8542 <MY_LON:8>-94.5417 <PFX:3>WL7 <QSO_RANDOM:1>Y <SFI:2>70 <CLUBLOG_QSO_UPLOAD_DATE:8>20200408 <CLUBLOG_QSO_UPLOAD_STATUS:1>Y <HRDLOG_QSO_UPLOAD_DATE:8>20200408 <HRDLOG_QSO_UPLOAD_STATUS:1>Y <QRZCOM_QSO_UPLOAD_DATE:8>20200408 <QRZCOM_QSO_UPLOAD_STATUS:1>Y <EOR>
#++++++++++++++++++++++++++++++++++++
# Log4OM 2 by IW3HMH version 2.4.0.0
# http://www.log4om.com
# created: Thursday, April 9, 2020
#++++++++++++++++++++++++++++++++++++
<ADIF_VERS:5>3.0.8 <PROGRAMID:7>Log4OM2 <PROGRAMVERSION:7>2.4.0.0 <eoh>
<ADDRESS:48>Po Box 3218
Valdez
Ak, 99686
United States <A_INDEX:1>4 <ANT_AZ:1>0 <STATE:2>AK <BAND:3>40m <BAND_RX:3>40m <CALL:5>WL7CG <CONT:2>NA <COUNTRY:6>Alaska <CNTY:17>AK,Valdez Cordova <CQZ:1>1 <DISTANCE:7>4268.38 <DXCC:1>6 <EMAIL:14>wl7cg@arrl.net <EQSL_QSL_RCVD:1>N <EQSL_QSL_SENT:1>N <FREQ:8>7.076070 <FREQ_RX:8>7.076070 <GRIDSQUARE:6>BP61xb <ITUZ:1>1 <LOTW_QSLRDATE:8>20200408 <LOTW_QSLSDATE:8>20200408 <LOTW_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <MODE:3>FT8 <MY_CITY:9>Grandview <MY_CNTY:7>Jackson <MY_STATE:8>Missouri <MY_COUNTRY:13>United States <MY_CQ_ZONE:1>4 <MY_DXCC:3>291 <MY_GRIDSQUARE:6>EM28ru <MY_ITU_ZONE:1>7 <MY_NAME:11>Chuck Kraly <MY_POSTAL_CODE:5>64030 <MY_RIG:7>IC-7610 <MY_STATE:8>Missouri <MY_STREET:17>6106 E 147th Terr <NAME:12>Alan J Sorum <OPERATOR:4>K0XM <OWNER_CALLSIGN:4>K0XM <STATION_CALLSIGN:4>K0XM <PROGRAMID:7>LOG4OM2 <PROGRAMVERSION:7>2.4.0.0 <QSL_RCVD:1>N <QSL_RCVD_VIA:1>E <QSL_SENT:1>N <QSL_SENT_VIA:1>E <QSL_VIA:45>DIRECT, QRZ, LOTW, EQSL and CLUBLOG (NO BURO) <QSO_COMPLETE:1>Y <QSO_DATE:8>20200408 <QSO_DATE_OFF:8>20200408 <QTH:6>Valdez <RST_RCVD:3>-13 <RST_SENT:3>-09 <SWL:1>N <TIME_OFF:6>045500 <TIME_ON:6>045400 <TX_PWR:3>100 <K_INDEX:1>2 <LAT:7>61.0615 <LON:9>-146.0016 <MY_LAT:7>38.8542 <MY_LON:8>-94.5417 <PFX:3>WL7 <QSO_RANDOM:1>Y <SFI:2>70 <CLUBLOG_QSO_UPLOAD_DATE:8>20200408 <CLUBLOG_QSO_UPLOAD_STATUS:1>Y <HRDLOG_QSO_UPLOAD_DATE:8>20200408 <HRDLOG_QSO_UPLOAD_STATUS:1>Y <QRZCOM_QSO_UPLOAD_DATE:8>20200408 <QRZCOM_QSO_UPLOAD_STATUS:1>Y <EOR>
Re: Change in ADIF With TQSL 2.5.1
First, you are using TQSL 2.5.1. The latest version is 2.5.2. I don't think that is the problem, just wanted to point it out.
Yes, the MY_STATE field is the problem. It should MO instead of Missouri. How did the field get the full state name in it? As a test, I changed my state in the configuration settings to California, and Log4OM still output the adif as CA. I had Log4OM upload the QSO to LOTW, and it went through with no problems.
So, once again, how did the full state name get in there? I don't think this is a problem with either TQSL or Log4OM.
73,
Jim N6VH
Yes, the MY_STATE field is the problem. It should MO instead of Missouri. How did the field get the full state name in it? As a test, I changed my state in the configuration settings to California, and Log4OM still output the adif as CA. I had Log4OM upload the QSO to LOTW, and it went through with no problems.
So, once again, how did the full state name get in there? I don't think this is a problem with either TQSL or Log4OM.
73,
Jim N6VH
Re: Change in ADIF With TQSL 2.5.1
The version was after I reverted TQSL back. It was signed and uploaded fine with 2.5.1
I have tried it and HRD with Missouri or Mo and no difference in 2.5.2
ARRL says it is the "MyState" designator.
I have tried it and HRD with Missouri or Mo and no difference in 2.5.2
ARRL says it is the "MyState" designator.
Re: Change in ADIF With TQSL 2.5.1
I think I might see what is happening. Even though I changed "CA" to California" in my configuration, that didn't change my state in the QSOs already in the log (of course). When I changed the state spelling in the configuration and then entered a new QSO, the adif now has the new state spelling. Is it possible that you have your state listed as "Missouri" in the Station Information part of the configuration settings? If so, change it to MO and see if that helps.
73,
Jim N6VH
73,
Jim N6VH
Re: Change in ADIF With TQSL 2.5.1
One other item. If your Log4OM log lists you state as "Missouri" in the log itself, you can do a bulk edit to change those entries.
73,
Jim N6VH
73,
Jim N6VH
Re: Change in ADIF With TQSL 2.5.1
Hi Dave here, N4XYZ
I am having a similar problem, TQSL version 2.5.2. When I try to upload QSO I get an error message that says: Station Location does not match QSO details. The Station Location 'US STATE' has value of VA while QSO has 'Virginia'. In tqsl location is 'Virginia' from pull down menu. In LOG4OM configuration, Station Information it is 'Virginia'. Don't know where VA comes from. I tried to upload and told it to ignore the error and LOG4OM froze in upload mode but not uploading? Do I change LOG4OM Station Information to VA for future and edit all QSOs to VA in log?
Any help would appreciated.
73
Dave
I am having a similar problem, TQSL version 2.5.2. When I try to upload QSO I get an error message that says: Station Location does not match QSO details. The Station Location 'US STATE' has value of VA while QSO has 'Virginia'. In tqsl location is 'Virginia' from pull down menu. In LOG4OM configuration, Station Information it is 'Virginia'. Don't know where VA comes from. I tried to upload and told it to ignore the error and LOG4OM froze in upload mode but not uploading? Do I change LOG4OM Station Information to VA for future and edit all QSOs to VA in log?
Any help would appreciated.
73
Dave