@G4POP -
Just a note Terry that for folks in the US - you cannot change your QRZ address data as it is pulled directly from the FCC database update.
73 de Larry N1FG
Strange WAS award problem
Re: Strange WAS award problem
I have noticed this issue here, and it is not just 80 meters. It is also not a result of an incorrect state in QRZ. I normally don't have Log4OM getting information from QRZ (or any other similar service) in any way. The stations in question were confirmed by LOTW, and their LOTW info shows WV as their state.
This seems to have started in 2021, possibly 2020.
73,
Jim N6VH
This seems to have started in 2021, possibly 2020.
73,
Jim N6VH
Re: Strange WAS award problem
Here is some information I sent to a JTAlert list:
Here are some examples:
K3JT 3 Jan 2021 20m RTTY
K3JT 11 Jul 2021 40m CW
WV8DX 23 Nov 2020 12m FT8
WV8DX 5 Dec 2020 20m FT8
The earliest problem entry in my log is Nov 2020. I don't have very many QSOs with WV in that time frame, so very few examples.
Two of those QSOs were in contests where the state was part of the exchange, and transferred directly from N1MM+ to Log4OM (one FT8 and one RTTY).
All QSOs were confirmed via LOTW, so it seems that Log4OM is making some changes in the state when the LOTW info comes in. to the log. So far, I haven't seen any other states mentioned in the Log4OM forums.
Here is an example from one of the QSOs as it is listed in Log4OM:
The county is listed as "WV,RITCHIE // Ritchie", but the state shows it as "Virginia"
I am using Log4OM 2.17.0.0
However, the QSOs in question were logged to 2.15.0.0, 2.11.0.0 and 2.10.0.0. The QSOs were confirmed within a few days, so would have been confirmed using the same versions. It is possible this has been fixed in later versions, although I didn't see any information to that effect in the Log4OM release notes.
As a test, I downloaded LOTW confirmations for the latest 12 months, and the errors are still in Log4OM.
73,
Jim N6VH
73,
Jim N6VH
Here are some examples:
K3JT 3 Jan 2021 20m RTTY
K3JT 11 Jul 2021 40m CW
WV8DX 23 Nov 2020 12m FT8
WV8DX 5 Dec 2020 20m FT8
The earliest problem entry in my log is Nov 2020. I don't have very many QSOs with WV in that time frame, so very few examples.
Two of those QSOs were in contests where the state was part of the exchange, and transferred directly from N1MM+ to Log4OM (one FT8 and one RTTY).
All QSOs were confirmed via LOTW, so it seems that Log4OM is making some changes in the state when the LOTW info comes in. to the log. So far, I haven't seen any other states mentioned in the Log4OM forums.
Here is an example from one of the QSOs as it is listed in Log4OM:
The county is listed as "WV,RITCHIE // Ritchie", but the state shows it as "Virginia"
I am using Log4OM 2.17.0.0
However, the QSOs in question were logged to 2.15.0.0, 2.11.0.0 and 2.10.0.0. The QSOs were confirmed within a few days, so would have been confirmed using the same versions. It is possible this has been fixed in later versions, although I didn't see any information to that effect in the Log4OM release notes.
As a test, I downloaded LOTW confirmations for the latest 12 months, and the errors are still in Log4OM.
73,
Jim N6VH
73,
Jim N6VH
Re: Strange WAS award problem
Here is some more information:
As a test, I set up a new log in Log4OM 2.17.0.0 and imported about a year's worth of QSOs. I changed one of the QSOs with the incorrect state to show no LOTW confirmation, and set the state to West Virginia. I deleted any information in the County field in Log4OM. I then used the Log4OM QSL Manager to download LOTW confirmations from the same time period. Log4OM put the correct state and county in in the County field, but changed the state in the State field to "VA".
73,
Jim N6VH
As a test, I set up a new log in Log4OM 2.17.0.0 and imported about a year's worth of QSOs. I changed one of the QSOs with the incorrect state to show no LOTW confirmation, and set the state to West Virginia. I deleted any information in the County field in Log4OM. I then used the Log4OM QSL Manager to download LOTW confirmations from the same time period. Log4OM put the correct state and county in in the County field, but changed the state in the State field to "VA".
73,
Jim N6VH
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Strange WAS award problem
Jim
From that I conclude that its LOTW feeding us with incorrect information?
From that I conclude that its LOTW feeding us with incorrect information?
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Strange WAS award problem
Log4OM updates the "state" field according to the LOTW data, that are assumed as the "most accurate" (by the way, the state is used by WAS, so it's a good choice to use the same info coming from the award issuer...)
If you use DEBUG mode (help -> log level) you will see in the download log (from lotw download screen) a message that indicates "Received STATE xxx for QSO <QSO DATA>"
This means Log4OM is forcing the state according to LOTW data.
This happens for PFX, CQ ZONE, ITU ZONE, DXCC, STATE and MY STATE, COUNTY, GRIDSQUARE and SAT NAME.
You can try enabling the debug mode and check if the info is coming from LOTW file.
In DEBUG mode the downloaded file is also saved in the LOTW temporary folder (in LOTW settings) or in the Log4OM temporary folder if the LOTW one is not set (Log4OM temporary folder is reachable from HELP MENU -> OPEN CONFIGURATION FOLDER then search for /TEMP)
If you use DEBUG mode (help -> log level) you will see in the download log (from lotw download screen) a message that indicates "Received STATE xxx for QSO <QSO DATA>"
This means Log4OM is forcing the state according to LOTW data.
This happens for PFX, CQ ZONE, ITU ZONE, DXCC, STATE and MY STATE, COUNTY, GRIDSQUARE and SAT NAME.
You can try enabling the debug mode and check if the info is coming from LOTW file.
In DEBUG mode the downloaded file is also saved in the LOTW temporary folder (in LOTW settings) or in the Log4OM temporary folder if the LOTW one is not set (Log4OM temporary folder is reachable from HELP MENU -> OPEN CONFIGURATION FOLDER then search for /TEMP)
Daniele Pistollato - IW3HMH
Re: Strange WAS award problem
Sorry for the delay in responding. I have been out of town.
LOTW is not sending incorrect information. Here is part of my log showing QSOs with K3JT. Notice that the two QSOs in 2021 show VA as the state. Before a LOTW download they were listed as WV. Notice the state in the county field is correct. In both cases, these two QSOs came into Log4OM via N1MM+, and the states were correct originally. As a further test, I edited the QSOs in question, and changed the states in Contact Details to West Virginia. I then did another LOTW download, using QSL manager. The states were changed back to VA (West Virginia in the Contact Details).
Here are the entries from the LOTW download using debug mode. I only included the header and the two QSOs in question.
ARRL Logbook of the World Status Report
Generated at 2021-10-04 18:36:46
for n6vh
Query:
QSL ONLY: YES
QSO SINCE: 2021-01-02 00:00:00
QSO UNTIL: 2021-07-30 23:59:59
QSL RX SINCE: (empty)
<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2021-09-01 17:43:39
<APP_LoTW_NUMREC:4>1161
<eoh>
<APP_LoTW_OWNCALL:4>N6VH
<STATION_CALLSIGN:4>N6VH
<CALL:4>K3JT
<BAND:3>20M
<FREQ:8>14.08551
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20210103
<APP_LoTW_RXQSO:19>2021-01-07 01:25:10 // QSO record inserted/modified at LoTW
<TIME_ON:6>222136
<APP_LoTW_QSO_TIMESTAMP:20>2021-01-03T22:21:36Z // QSO Date & Time; ISO-8601
<QSL_RCVD:1>Y
<QSLRDATE:8>20210110
<APP_LoTW_RXQSL:19>2021-01-10 23:28:26 // QSL record matched/modified at LoTW
<DXCC:3>291
<COUNTRY:24>UNITED STATES OF AMERICA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:2>K3
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>EM99XO
<STATE:2>WV // West Virginia
<CNTY:13>WV,MONONGALIA // Monongalia
<CQZ:2>05
<ITUZ:2>08
<eor>
<APP_LoTW_OWNCALL:4>N6VH
<STATION_CALLSIGN:4>N6VH
<CALL:4>K3JT
<BAND:3>20M
<FREQ:8>14.08551
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20210103
<APP_LoTW_RXQSO:19>2021-01-07 01:25:10 // QSO record inserted/modified at LoTW
<TIME_ON:6>222136
<APP_LoTW_QSO_TIMESTAMP:20>2021-01-03T22:21:36Z // QSO Date & Time; ISO-8601
<QSL_RCVD:1>Y
<QSLRDATE:8>20210110
<APP_LoTW_RXQSL:19>2021-01-10 23:28:26 // QSL record matched/modified at LoTW
<DXCC:3>291
<COUNTRY:24>UNITED STATES OF AMERICA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:2>K3
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>EM99XO
<STATE:2>WV // West Virginia
<CNTY:13>WV,MONONGALIA // Monongalia
<CQZ:2>05
<ITUZ:2>08
<eor>
Notice in both cases, the states are listed as <STATE:2>WV // West Virginia
73,
Jim N6VH
LOTW is not sending incorrect information. Here is part of my log showing QSOs with K3JT. Notice that the two QSOs in 2021 show VA as the state. Before a LOTW download they were listed as WV. Notice the state in the county field is correct. In both cases, these two QSOs came into Log4OM via N1MM+, and the states were correct originally. As a further test, I edited the QSOs in question, and changed the states in Contact Details to West Virginia. I then did another LOTW download, using QSL manager. The states were changed back to VA (West Virginia in the Contact Details).
Here are the entries from the LOTW download using debug mode. I only included the header and the two QSOs in question.
ARRL Logbook of the World Status Report
Generated at 2021-10-04 18:36:46
for n6vh
Query:
QSL ONLY: YES
QSO SINCE: 2021-01-02 00:00:00
QSO UNTIL: 2021-07-30 23:59:59
QSL RX SINCE: (empty)
<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2021-09-01 17:43:39
<APP_LoTW_NUMREC:4>1161
<eoh>
<APP_LoTW_OWNCALL:4>N6VH
<STATION_CALLSIGN:4>N6VH
<CALL:4>K3JT
<BAND:3>20M
<FREQ:8>14.08551
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20210103
<APP_LoTW_RXQSO:19>2021-01-07 01:25:10 // QSO record inserted/modified at LoTW
<TIME_ON:6>222136
<APP_LoTW_QSO_TIMESTAMP:20>2021-01-03T22:21:36Z // QSO Date & Time; ISO-8601
<QSL_RCVD:1>Y
<QSLRDATE:8>20210110
<APP_LoTW_RXQSL:19>2021-01-10 23:28:26 // QSL record matched/modified at LoTW
<DXCC:3>291
<COUNTRY:24>UNITED STATES OF AMERICA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:2>K3
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>EM99XO
<STATE:2>WV // West Virginia
<CNTY:13>WV,MONONGALIA // Monongalia
<CQZ:2>05
<ITUZ:2>08
<eor>
<APP_LoTW_OWNCALL:4>N6VH
<STATION_CALLSIGN:4>N6VH
<CALL:4>K3JT
<BAND:3>20M
<FREQ:8>14.08551
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20210103
<APP_LoTW_RXQSO:19>2021-01-07 01:25:10 // QSO record inserted/modified at LoTW
<TIME_ON:6>222136
<APP_LoTW_QSO_TIMESTAMP:20>2021-01-03T22:21:36Z // QSO Date & Time; ISO-8601
<QSL_RCVD:1>Y
<QSLRDATE:8>20210110
<APP_LoTW_RXQSL:19>2021-01-10 23:28:26 // QSL record matched/modified at LoTW
<DXCC:3>291
<COUNTRY:24>UNITED STATES OF AMERICA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:2>K3
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>EM99XO
<STATE:2>WV // West Virginia
<CNTY:13>WV,MONONGALIA // Monongalia
<CQZ:2>05
<ITUZ:2>08
<eor>
Notice in both cases, the states are listed as <STATE:2>WV // West Virginia
73,
Jim N6VH
Re: Strange WAS award problem
I've been researching this while the team is looking into it.
I reached out to the ARRL LOTW team. They looked at my log files and checked it against their server data.
Yet, I can repeat this for every 75m WV contact
Their response is shared below.....
Jahnke, Bart, W9JJ
1:55 PM (9 minutes ago)
Hi Bob,
Since our export file shows West Virginia for all 3, LoTW is acting correctly – nothing is being output as VA from LoTW that I can see/find.
I reached out to the ARRL LOTW team. They looked at my log files and checked it against their server data.
Yet, I can repeat this for every 75m WV contact
Their response is shared below.....
Jahnke, Bart, W9JJ
1:55 PM (9 minutes ago)
Hi Bob,
Since our export file shows West Virginia for all 3, LoTW is acting correctly – nothing is being output as VA from LoTW that I can see/find.
Re: Strange WAS award problem
Bob,
Yea, that goes along with what my tests have shown. LOTW is sending the correct information, but Log4OM is changing it. It isn't just 75. In my log it happens on several bands, and CW, RTTY and FT8.
I am using Log4OM 2.17.0.0.
73,
Jim N6VH
Yea, that goes along with what my tests have shown. LOTW is sending the correct information, but Log4OM is changing it. It isn't just 75. In my log it happens on several bands, and CW, RTTY and FT8.
I am using Log4OM 2.17.0.0.
73,
Jim N6VH
Re: Strange WAS award problem
Noted. I posted this, just in case that the info would be of interest to the team. They have many projects and a personal life, so we just need to be patient.