SotA Log ADIF Band wrong Format

#1

Hi
I uploaded the first time my SotA log to the upload Server and got a error message … look in screenshot.
I looked on other Adif‘s that work and found the error :

Output HAMRS :
freq:17

Output other log software ( work ) :

freq:914.285000

73 / DD6FM - Marco

image
image1284×2778 256 KB

Unable to upload SOTA template
#2

Marco,

How does SOTA normally display the Band? Is it supposed to show as “40” or “40m” or is it supposed to show the frequency in MHz?

HAMRS exports your log in standard ADI format so I’m not sure how things are getting mangled when you attempt to upload.

Can you take a screen shot of a couple of entries in your ADI file and post it here?

Also, what version of HAMRS are you using?

If you want to send your ADI file to me I’d be glad to look at it. Use my call sign at ARRL.net.

1 Like
#3

Hi
Tnx for reply !

I wonder that no one has reported this problem yet because it is the official Server for uploading the logs. I send you here a screenshot of a file I did make with an other logging app CloudLogOffline … HAMRS 1.05 iPhone

image
image2778×1284 391 KB

Screenshot and adi file :

<ADIF_VERS:5>3.1.0
<PROGRAMID:15>CloudLogOffline
<PROGRAMVERSION:13>Version 1.0.9
<EOH>

<call:5>DH2PA<station_callsign:7>DD6FM/P<band:3>40m<mode:3>SSB<freq:8>7.099000<qso_date:8>20220420<time_on:6>042900<time_off:6>042900<rst_rcvd:2>59<rst_sent:2>59<stx:1>1<my_sota_ref:9>DM/RP-305<country:7>Germany<qth:14>76831 Eschbach<gridsquare:6>JN49ae<name:17>Patrick Ackermann<comment:0><eor>
#4

Thank you for that.

Can you also post your ADI file directly from HAMRS for the same QSO, so I can compare the two?

1 Like
#5

Thanks …

Here it is with HAMRS :

image
image2778×1284 420 KB

Generated on 2022-04-20T07:04:45.118Z
<adif_ver:5>3.0.5
programid:5HAMRS
programversion:51.0.5

band:340m
call:5DH2PA
country:7Germany
freq:17
gridsquare:6JN49ae
mode:3SSB
<my_sota_ref:9>DM/RP-305
name:17Patrick Ackermann
operator:5DD6FM
<qso_date:8>20220420
<qso_date_off:8>20220420
qth:1476831 Eschbach
<rst_rcvd:2>59
<rst_sent:2>59
<time_on:6>070200

band:320m
call:5DD1IZ
country:7Germany
freq:214
gridsquare:6JN49be
mode:3SSB
<my_gridsquare:6>JN49ah
<my_sota_ref:9>DM/RP-305
name:12Mike Wypchol
operator:5DD6FM
<qso_date:8>20220420
<qso_date_off:8>20220420
qth:1276829 Landau
<rst_rcvd:2>59
<rst_sent:2>59
<time_on:6>070435

#6

Can you screen shot it or paste it in as a quote so the tags don’t get mangled?

Also, how are you entering the frequency? Are you entering one digit only (MHz) or are you adding the kHz fraction? Commas or decimals as separators?

I did a test in the SOTA template and here is what I got:

image
image775×1266 82.5 KB

1 Like
#7

Oh i think it was my mistake … I only input the frequency as 7 or 14 … my other Programm seems to convert it … well if I put in 14.200 it works …
i done this every time in my PotA log files and the PotA log server has no problem with it … but the SotA has … so the problem is solved then … I will write in the full frequency and should have no problems then …

Thanks for the help !
73
DD6FM - Marco

#8

Awesome!

POTA doesn’t care because it ignores the frequency. The POTA uploader only uses the band (e.g. 40m).

It’s odd that the SOTA server won’t accept “7” or “14” because those are valid frequency entries per the ADIF specification.

Regardless, it works now so that’s great.

1 Like