HAMRS-LOTW Issue

Bugs
,
#1

When I upload my adif file to LOTW it does not accept it at all… the format of adif isn’t the same and I get errors every time.

#2

What errors is TQSL reporting?

The ADIF log requirements for LoTW are pretty simple:

  • Other op’s call sign
  • Date and time of QSO (UTC)
  • Band
  • Mode or submode

I’m pretty sure HAMRS exports all of these fields in the correct format for TQSL to recognize and import the log.

Maybe the reported error will help find the problem.

#3

I also get some errors when uploading to my logprogram Log4om … I just looked at the log file. The band:3 is only written into the first QSO. In the rest of the QSOs it is missing

Sample:

band:340m
call:5EA2DT
cnty:0
country:5Spain
freq:57.137
gridsquare:6IN92et
mode:3SSB
name:6Manuel
operator:7DD6FM/P
<qso_date:8>20210521
<qso_date_off:8>20210521
qth:2631080 - Pamplona - Navarra
<rst_rcvd:2>59
<rst_sent:2>59
state:0
<time_on:4>1649

call:6EA3EVL
cnty:0
country:5Spain
freq:57.137
gridsquare:6JN00hr
mode:3SSB
name:15PABLO PANISELLO
operator:7DD6FM/P
<qso_date:8>20210521
<qso_date_off:8>20210521
qth:3043500 TORTOSA, TARRAGONA 43500
<rst_rcvd:2>59
<rst_sent:2>59
state:0

and all the next also

#4

What version of the app are you using? Which operating system, and what log template?

I just exported ADIF files from the “Generic” and “Parks on the Air” templates, iOS, with HAMRS 0.10.4 and those files look correct.

I also use Log4OM to import my ADIFs from HAMRS for my long-term logging needs.

#5

That was with iOS HamRS 0.10.4 and generic template…

I just tested again… I made a new logbook and entered 3 calls:

Generated on 2021-06-03T08:29:32.744Z
<adif_ver:5>3.0.5
programid:5HAMRS
programversion:60.10.4

band:340m
call:5DD1IZ
cnty:0
country:7Germany
freq:57.134
gridsquare:6JN49be
mode:3SSB
name:12Mike Wypchol
operator:7DD6FM/P
<qso_date:8>20210603
<qso_date_off:8>20210603
qth:1276829 Landau
<rst_rcvd:2>59
<rst_sent:2>59
state:0
<time_on:4>0828

call:5DH2PA
cnty:0
country:7Germany
freq:57.134
gridsquare:6JN49ae
mode:3SSB
name:17Patrick Ackermann
operator:7DD6FM/P
<qso_date:8>20210603
<qso_date_off:8>20210603
qth:1476831 Eschbach
<rst_rcvd:2>59
<rst_sent:2>59
state:0
<time_on:4>0829

call:5DG1HP
cnty:0
country:7Germany
freq:57.134
gridsquare:6JN49ac
mode:3SSB
name:14Christian Kern
operator:7DD6FM/P
<qso_date:8>20210603
<qso_date_off:8>20210603
qth:16Offenbach/Queich
<rst_rcvd:2>59
<rst_sent:2>59
state:1D
<time_on:4>0829

POTA Log Discrepancies
#6

Yikes, I just tried again with a fresh Generic log on the iPad and discovered the same bug.

If you edit the first (earliest) QSO in your log (use the cog to the right), the band appears to have populated correctly. In the remaining ones, the band field is blank.

Looks like the bug isn’t in the ADIF export function; it’s in the QSO logging itself. I also noticed that Band doesn’t show in the Generic log logging screen as it does in the POTA template.

1 Like
#7

I found my issue… tqsl needed an update

#8

@N4GLE Awesome!

I think @DD6FM ‘s discovery is certainly a bug.

1 Like
#9

Thanks for the work here folks. Definitely a bug. Got it in the log and will get a fix out soon.

1 Like
#10

Thanks for your great work !

73
DD6FM - Marco

#11

JARRETT I think I have found the problem and the solution to the hamrs not loading to lotw. When you put your park number into the field it populates the grid square for the park in the my grid square location. I had to change all my grid square entries to my qth gridsquare to get my logs to upload to lotw. Hope this helps people as it worked for me.

#12

@Doug_Ledbetter_Jr Doug, you should NOT be changing your log to reflect your home QTH grid square. Instead, create a new location in TQSL with the grid square of your actual operating location, and submit the log to that one.

Otherwise, LoTW users who are chasing grid squares will have your contact logged against the wrong one.

#13

I am using version 0.11.3 on iPhone/iPad. TQSL reports error on the my grid square field. I have to strip this field for the raw .adi file and then there are no errors in uploading. I have to remember not to use the MY GRID field to avoid this error when uploading to LOTW.

Andrew N7JRR

#14

Or set TQSL to ignore QTH and then it won’t hiccup on the Grid Square.
73, Charlie - K0LAF

#15

@n7jrr Yeah, but then you are misrepresenting your location in LoTW. Anyone hunting your grid square, state, county, etc. will get credit for the wrong one when the QSOs are matched in LoTW.

It’s best to have TQSL override your station location with QTH info from your log, as @K0LAF mentioned above, or to create a new station location within TQSL that accurately reflects the location your uploaded log represents.