HRDLog does not show correct locators

V2 error reports
Post Reply
DK9JC
Advanced Class
Posts: 78
Joined: 20 Jan 2019, 13:10
Location: Germany
Contact:

HRDLog does not show correct locators

Post by DK9JC »

Today when I saw my HRDLog map I wondered about the new markers, which are not set correct as they are in the center of the DXCC:
2020-04-23_09h04_31_v3.jpg
2020-04-23_09h04_31_v3.jpg (99.12 KiB) Viewed 4544 times
I went into the details of the HRDLog logbook and saw that the locator does not match the one stored in Log4OM.

Im my Log4OM I have FN46 stored (from WSJT-X):
2020-04-23_09h12_49.png
2020-04-23_09h12_49.png (12.17 KiB) Viewed 4544 times
Im my Log4OM I have QF23 stored (from WSJT-X):
2020-04-23_09h12_05.png
2020-04-23_09h12_05.png (12.24 KiB) Viewed 4544 times
I switched from Log4OM v1 to v2 2.4.0.0 only a week ago and immediately updated to 2.5.0.0.
I can say that it worked with v1 correctly.
Is it possible that no locator is sent via API and HRDlog just uses a default locator with the country?

Does it possibly also have something to do with the new duration between entry in the log and sending the data to HRDLog? I have the feeling that the new feauture may be related to the problem.

Can I somewhere check the raw api-data sent by Log4OM to external sources?
73 de John, DK9JC (AK9JC stateside)
https://www.dk9jc.de
User avatar
G4POP
Log4OM Alpha Team
Posts: 10752
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: HRDLog does not show correct locators

Post by G4POP »

In Help turn on trace mode and then either watch the realtime log or open the logfile
73 Terry G4POP
DK9JC
Advanced Class
Posts: 78
Joined: 20 Jan 2019, 13:10
Location: Germany
Contact:

Re: HRDLog does not show correct locators

Post by DK9JC »

G4POP wrote: 23 Apr 2020, 07:40 In Help turn on trace mode and then either watch the realtime log or open the logfile
Thank you, Terry.

For the log from wsjt-x to Log4OM v2.5.0.0 I get:
07:42:07.218 Debug: ##### UDP MESSAGE RECEIVED ##### :JTAlert<EOH> <CALL:5>OH3OJ<QSO_DATE:8>20200423<QSO_DATE_OFF:8>20200423<TIME_ON:6>074000<TIME_OFF:6>074100<FREQ:9>14.075922<FREQ_RX:9>14.075922<BAND:3>20m<BAND_RX:3>20m<MODE:3>FT8<DXCC:3>224<COUNTRY:7>Finland<CQZ:2>15<ITUZ:2>18<CONT:2>EU<RST_SENT:3>-03<RST_RCVD:3>-04<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<EQSL_QSL_SENT:1>R<EQSL_QSL_RCVD:1>R<GRIDSQUARE:4>KP20<DISTANCE:4>1689<TX_PWR:3>10<LAT:11>N060 30.000<LON:11>E025 00.000<COMMENT:35><NAME:14>Jukka<QTH:9>Riihimaki<PFX:3>OH3<MY_GRIDSQUARE:6>JN39MF<MY_CQ_ZONE:2>14<MY_ITU_ZONE:2>28<STATION_CALLSIGN:5>DK9JC<QSO_COMPLETE:1>Y <EOR> on UDP port 2235 (JTALERT QSO/ADIF_MESSAGE) from 127.0.0.1:61048#####
In the raw data (DB SELECT) I see "GridSquare":
[HRDLOG] Sending ON AIR message

[...]

07:43:46.764 Trace: [DbSqlite] : SELECT QsoId, Callsign, Band, Mode, QsoDate, Address, StationCallsign, DXCC, ArrlSect, QsoComplete, Age, AIndex, AntAz, AntEl, AntPath, Antenna, ArrlCheck, BandRX, CallsignUrl, Class, Cnty, Comment, Cont, ContactAssociations, ContactedOp, ContestId, Country, CQZone, Distance, EqCall, EMail, ForceInit, Freq, FreqRx, GridSquare, ITUZone, KIndex, Lat, Lon, MaxBursts, MSShower, MyAssociations, MyDxcc, MyLat, MyLon, MyCity, MyCnty, MyCountry, MyCQZone, MyGridSquare, MyITUZone, MyName, MyPostalCode, MyStreet, MyRig, MySig, MySigInfo, MyState, Name, Notes, NrBursts, NrPings, Pfx, Operator, OwnerCallsign, Precedence, PropMode, ProgramId, ProgramVersion, QslMsg, QslVia, QsoEndDate, QsoRandom, Qth, RxPwr, Sig, SigInfo, RSTRcvd, RSTSent, SatelliteQSO, SatMode, SatName, SFI, SRX, SRXString, State, STX, STXString, SWL, TxPwr, QsoConfirmations, ContactReferences, MyReferences FROM LOG WHERE QsoId = @qsoId

07:43:46.806 Info: [#=zP9Ak_P34NrL9JNWNZMeU$Dld8yiB] : [HRDLOG UPLOAD] Uploading QSO on HRDLOG: OH3OJ|23.04.2020 07:40:00|20m|FT8
[...]

In the uploaded data I do not see "GridSquare" or "Locator":
[HRDLOG UPLOAD] payload:http://robot.hrdlog.net/NewEntry.aspx payload: Callsign=DK9JC&Code=XXXApp=LOG4OM2&ADIFData=<BAND:3>20m <CALL:5>OH3OJ <COMMENT:35><DXCC:3>224 <FREQ:9>14.075922 <MODE:3>FT8 <STATION_CALLSIGN:5>DK9JC <QSO_DATE:8>20200423 <RST_RCVD:3>-04 <RST_SENT:3>-03 <TIME_ON:6>074000 <EOR>

07:43:46.924 Debug: [#=zxpoxaO_Q5llSf_fvXg==][MoveNext] : PostDataAsync: Posting data to http://robot.hrdlog.net/NewEntry.aspx. upload information:Callsign=DK9JC&Code=XXXApp=LOG4OM2&ADIFData=<BAND:3>20m <CALL:5>OH3OJ <COMMENT:35><DXCC:3>224 <FREQ:9>14.075922 <MODE:3>FT8 <STATION_CALLSIGN:5>DK9JC <QSO_DATE:8>20200423 <RST_RCVD:3>-04 <RST_SENT:3>-03 <TIME_ON:6>074000 <EOR>

[...]

[HRDLOG UPLOAD] ###### END ######
73 de John, DK9JC (AK9JC stateside)
https://www.dk9jc.de
DK9JC
Advanced Class
Posts: 78
Joined: 20 Jan 2019, 13:10
Location: Germany
Contact:

Re: HRDLog does not show correct locators

Post by DK9JC »

I just enabled tracing in v1.40.0.0 and checked which fields are sent to HRDlog there.
Unlike in v2.50. the field "<GRIDSQUARE:4>" is there in 1.40.

AdifManagement: Begin HRDLog row creation for Call: LA8OOA Date: 20200426 Time: 120700 Band: 15m Mode: FT8
Log4OMMainWindow: QSO Added via External Form for QSO : Call: LA8OOA Date: 20200426 Time: 120700 Band: 15m Mode: FT8
AdifManagement: End HRDLog row creation for Call: LA8OOA Date: 20200426 Time: 120700 Band: 15m Mode: FT8
TCPEventManager: QSO Added via AddQso from UDP for QSO : Call: LA8OOA Date: 20200426 Time: 120700 Band: 15m Mode: FT8
HRDLogManagement: upload informations:
Callsign=DK9JC&Code=[XXX]&App=Log4OM&ADIFData=<QSO_DATE:8>20200426 <TIME_ON:6>120700 <CALL:6>LA8OOA <MODE:3>FT8 <BAND:3>15m <FREQ:9>21.075996 <RST_SENT:3>+10 <RST_RCVD:3>+02 <QSL_SENT:1>R <QSL_RCVD:1>R <QSL_SENT_VIA:1>B <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>R <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>R <DISTANCE:4>1039 <STATION_CALLSIGN:5>DK9JC <GRIDSQUARE:4>JO28 <DXCC:3>266 <EOR>
HRDLogManagement: upload result 1
73 de John, DK9JC (AK9JC stateside)
https://www.dk9jc.de
User avatar
G4POP
Log4OM Alpha Team
Posts: 10752
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: HRDLog does not show correct locators

Post by G4POP »

Thank you for completing that test it saves us some time

I will report this to Lele
73 Terry G4POP
User avatar
IW3HMH
Site Admin
Posts: 2925
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: HRDLog does not show correct locators

Post by IW3HMH »

Added fields on next release. Alpha testing in progress.
Thanks a lot, i love that reports! really save me a lot of time to find and fix it (less than 5 minutes in that case)
Daniele Pistollato - IW3HMH
DK9JC
Advanced Class
Posts: 78
Joined: 20 Jan 2019, 13:10
Location: Germany
Contact:

Re: HRDLog does not show correct locators

Post by DK9JC »

G4POP wrote: 26 Apr 2020, 12:38 Thank you for completing that test it saves us some time

I will report this to Lele
Thank you, Terry. :-) That was my intention, to save you guys time.
IW3HMH wrote: 26 Apr 2020, 15:49 Added fields on next release. Alpha testing in progress.
Thanks a lot, i love that reports! really save me a lot of time to find and fix it (less than 5 minutes in that case)
Thank you, Daniele. I have a lot of experience in this field from my work. Daily business. Thank you for the quick fix. Let me know if you want me to do some tests. I will report another (small) issue soon. :-)
73 de John, DK9JC (AK9JC stateside)
https://www.dk9jc.de
DK9JC
Advanced Class
Posts: 78
Joined: 20 Jan 2019, 13:10
Location: Germany
Contact:

Re: HRDLog does not show correct locators

Post by DK9JC »

I can confirm that the bug is fixed in v2.6.1.0 and everything is now working correct. Tu for this great fix.
73 de John, DK9JC (AK9JC stateside)
https://www.dk9jc.de
User avatar
NN7D
Log4OM Alpha Team
Posts: 816
Joined: 19 Feb 2014, 19:44

Re: HRDLog does not show correct locators

Post by NN7D »

Thanks for letting us know!

Doug
W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Post Reply