www.dl2rum.de

TQSL doesn't seem to want to sign the ADIF file produced by RUMLog. The error message I get is:

Signing using CALL=KB6NU, DXCC=291
Error: Signing aborted due to errors
Error: /Applications/TrustedQSL/KB6NU-LOTW.adi: OpenSSL error: error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long on line 1

I tried attaching the .adif file, but the BBS didn't like the .adi file extension or the .txt file extension. Here are the first three lines:

<call:8>PJ2/PB2T <qso_date:8:d>20080723 <time_on:6>003000<band:3>30m <mode:2>CW <eor>
<call:5>W4EDE <qso_date:8:d>20080723 <time_on:6>021100<band:3>40m <mode:2>CW <eor>
<call:6>KA0CSW <qso_date:8:d>20080723 <time_on:6>022300<band:3>40m <mode:2>CW <eor>

It looks just fine to me.

Alternately, is there any way for me to easily change the LOW status of the QSOs listed in the ADIF file back to just W? That way, I could try to create the .tq8 file using RUMLog and skip the intermediate step of creating the ADIF file.

73, Dan KB6NU

Hi Dan,

I would say, the LoTW integration in RUMlog works perfect. Also your adif looks okay for me. The provided error message looks not like an adif file problem. I can not interpret this error. You should ask the developer.

To resent LoTW QSLs, mark all affected QSOs in the log table using the mouse and select "Menu-->QSL-->Send LoTW QSL agn". To automatize the process you have to put a copy of tqsl.app into the RUMlog folder.
When you have entered all required data into the preferences below the eQSL/LoTW tab, the signed file will be sent to the ARRL. When not, you will find the tq8 file in your RUMLog folder for manually sending.

There may be only one minor issue: tqsl asks for your password, this window may be located (invisible) behind the RUMlog window.