logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Clublog LoTW
N6IE
#1 Posted : Sunday, January 15, 2012 8:48:59 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 50
Location: California

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
I am uploading my .adi files to Clublog (www.clublog.org) as part of local club project. When uploading QSO's from LOGic 8 that have been confirmed via LoTW and downloaded into LOGic 8, the confirmations do not register in Clublog and the QSO is shown only as "worked". It's necessary to merge an adif file generated by LoTW to get the confirmations to show using the procedure shown here:

http://www.clublog.org/d...e.action?pageId=1638480

Can this be fixed in the new version or is there some easy way to do it in version 8?

Ron
N6IE
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
W5GA
#2 Posted : Monday, January 16, 2012 7:02:01 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 365
Location: Missouri

Thanks: 66 times
Was thanked: 110 time(s) in 97 post(s)
Probably because some of the info in your LOGic output isn't recognized by Club Log (as in there may be extra fields). The easiest thing to do is probably by following the instructions on their website, and download the file from LOTW, that way you know it has the info needed without extra fields. An alternative would be to open your LOGic .adi file in Notepad or some other text editor and remove what's not needed.
WN4AZY
#3 Posted : Tuesday, January 17, 2012 10:01:04 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,057
Man
Location: Auburn, GA

Thanks: 969 times
Was thanked: 484 time(s) in 399 post(s)
Ok, I don't understand how they tell, when you upload a QSL, if it has been thru LoTW or not. Do they want a separate file of JUST LoTW confirms? If so, that is easy. When making your ADIF file, filter and set LOTW_RCVD equals F (fulfilled).

If they merely want you to INCLUDE LoTW QSOs along with everything else, there is nothing to do. It normally exports them unless you filter otherwise.

Let me know exactly what they want.

Quote:
Probably because some of the info in your LOGic output isn't recognized by Club Log (as in there may be extra fields).


Any program comsuming ADIF data should ignore the extra fields it is not interested in. However, in tools/setup/log fields, you can turn on and off any field for import and export, as well ac change the name used for ADIF.


Tnx & 73,

Dennis WN4AZY
N6IE
#4 Posted : Tuesday, January 17, 2012 11:40:01 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 50
Location: California

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
When LOGic imports LoTW QSL's, the QSO is marked as confirmed via LoTW in LOGic, but that confirmation is not passing through to Clublog. The ADIF log that LOGic produces needs to have a field LOTW_QSL_RCVD as shown in this link:

http://www.clublog.org/d...e.action?pageId=2785282

Thanks,

Ron
N6IE
WN4AZY
#5 Posted : Tuesday, January 31, 2012 12:59:29 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,057
Man
Location: Auburn, GA

Thanks: 969 times
Was thanked: 484 time(s) in 399 post(s)
This update fixes that. Just set the ADIF NAME for LOTW_RCVD to LOTW_QSL_RCVD

Tnx & 73,

Dennis WN4AZY

http://hosenose.com/Foru...install-this-update.aspx
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.023 seconds.