Thank you Dave,
That's very interesting. But,
1. Right now I clicked on that QSO in my LPD, and the country code says 291; also the "rx band" field (in the Aux panel) says "6M". This QSO was logged to DXK from WSJT-X. I'm not surprised it contained incorrect info - I've run into that problem before. I don't understand why it is now correct in DXK.
2. Before the KD2KJU QSO I made other QSOs on 6M and 30M today. I uploaded these QSOs in very small batches to LotW, waiting a bit and then doing Sync LotW QSOs. Each time that I did this, the Aux panel appeared. These times were before the KD2KJU QSO existed. I checked these previous QSOs and they all appear correct regarding country code and rx band. I also clicked the Broke button, with a null result in the LPD.
73, John W1JA
toggle quoted message
Show quoted text
-----Original Message-----
From:
[email protected] [mailto:
[email protected]] On Behalf Of Dave AA6YQ
Sent: Tuesday, April 7, 2020 3:40 PM
To: john@...
Cc:
[email protected]Subject: Re: [DXLab] DXKeeper: Aux panel appears after Sync LotW QSOs operation
Thanks for the errorlog.txt file, John. Here's the relevant fragment:
2020-04-07 16:58:11.524 > DXLogMain.ValidFields: KD2KJU
2020-04-07 16:58:11.525 > DXLogMain.ValidField: theDXCCID = 248, CorrectDXCCPrefix = I, DXLogMain.Fieldbox(DXCCPrefixField) = K
2020-04-07 16:58:11.525 > DXLogMain.ValidFields: not valid: DXCCID = 248
2020-04-07 16:58:11.526 > DXLogMain.ValidField: FreqRX = 50.314111, BandRX unspecified
2020-04-07 16:58:11.527 > DXLogMain.LogFrameSelect_Click, Index = 0
2020-04-07 16:58:11.527 > DXLogSetup.LogFrameVisible_Click, Index = 0, MakeVisible = True, LogFrameVisibleShift = 0
2020-04-07 16:58:11.528 > Main window height = 9525
2020-04-07 16:58:11.528 > Log grid height = 4158
2020-04-07 16:58:11.529 > DXLogMain.ValidField: enabling panel 0: BandRX error
Your logged QSO with KD2KJU as its DXCC country code set to 248 (Italy) but its DXCC Prefix set to K. Also, its BandRX item is empty though its FreqRX specifies a 6m frequency.
The combination of two different errors in the same QSO may be the reason that a label is not flashing to highlight what's wrong; I will investigate.
73,
Dave, AA6YQ
