eQSL.cc Forum
Help!  eQSL.cc Home  Forums Home  Search  Login 
Viewing User Profile for: KB1JTB M R Kane
About Contact
Joined: Jun 14, 2010 04:44 PM
Last Post: Aug 29, 2014 02:34 PM
Last Visit: May 8, 2020 02:24 AM
Website:  
Location:
Interests:
Favorite Bands:
Favorite Modes:


Send Private Message
Post Statistics
KB1JTB M R Kane has contributed to 3 posts out of 11649 total posts (0.03%) in 5,087 days (0.00 posts per day).

20 Most recent posts:
Mobile with many QTH's » QTHes aboard a boat sailing long distance Aug 29, 2014 02:34 PM (Total replies: 16)

Quote: Can you go and modify QTH info for a record, or a group of records, after you have uploaded them? i.e. if you loaded all your contacts to LoTW from your logging program, could you then log into LoTW, select a group of records, and change the grid on them, etc.?


No. Once loaded into the LoTW database, only search or report-generation is supported. For example, 'show latest QSOs' or user-defined queries 'show all QSLs made from my QTH-X' are possible.

In effect to change an existing LoTW entry, one must upload a corrected ADIF file. Most simple errors--band, time of contact, grid--will 'overwrite' the previous entry. Changes in callsign or date will cause a new entry to be generated. This may cause the number of QSOs reported to be larger than actual. However, QSLs will only arise from matched pairs of contacts entered, so no 'extras' will occur.

In my experience, most /m LoTW users do enter the appropriate location. Also, I have verified that stations receive QTH credit for my actual location as entered in the contact--not my mailing address as shown in the FCC database or my LoTW certificate.

Note I'm only a user, not coder, so my descriptions will necessarily be simplistic (or naive.)

eQSL supports making QSL cards from electronically-entered contact data. In effect, if the other station gets my callsign, a contact can be constructed.

Unless the two entries match closely enough, in LoTW I will never know whether the other station has tried to upload the contact. LoTW allows more complete reporting, but has no provision for generating QSL cards.

Thanks--
M.R.Kane
KB1JTB/m

KB1JTB M R Kane

Mobile with many QTH's » QTHes aboard a boat sailing long distance Aug 28, 2014 10:21 PM (Total replies: 16)

Many logging programs allow direct uploading to LoTW, in addition to uploading to eQSL.

However, I haven't found a logging program which allows easy recording of my temporary qth. Therefore, I export an ADIF file from my logging program, one file from each temporary location. Then I run TQSL to sign and upload each file to LoTW.

TQSL is the engine for inputting information into LoTW, while operations within LoTW are limited to sorting QSOs and QSLs already existing in the database.

The process is 1) run TQSL, 2) choose the adif file, 3) select a station location for signing, 4) confirm signing, 5) specify dates, 6) enter password and upload.

During step 3, a previous location can be used, or a new one defined. Creating a new location involves selecting a callsign from your certificate, then giving grid square, ITU and CQ zones, IOTA ID, State and County. (Pop-up windows step one through the process.)

This is simpler than it sounds. The result is that every contact has my correct qth, so that WAS-seekers, as well as grid square or county hunters receive proper credit for our contact. Similarly, I can qualify for WAS awards honoring the 50-mile locus restriction.

M.R.Kane
KB1JTB/m


KB1JTB M R Kane
Edited by KB1JTB M R Kane on Aug 28, 2014 at 10:25 PM

Mobile with many QTH's » QTHes aboard a boat sailing long distance Aug 28, 2014 03:30 AM (Total replies: 16)

At present, I place my operating location information in the "Comments" to aid the station I contacted, but I believe neither of us can use it towards an eQSL award.

"Highly mobile" operations are not well supported by eQSL. I typically operate mobile from over 30 temporary locations each year. LoTW allows specifying the actual operating location during the process of signing and uploading contacts, under one certificate. Multiple certificates (identities) are not necessary, so long as operations are within the same DXCC entity as in the certificate.

Could a similar capability be added to eQSL?


Thanks--
M.R.Kane
KB1JTB/m

KB1JTB M R Kane