Posted: 10/12/2015 9:02:03 PM EDT
|
I think I have figured out how to make LOTW work on Windows 10.
If we have had a QSO in the past & you have a LOTW account and you can figure out how to log into LOTW and see if we are confirmed, please let me know if our QSO is confirmed? Thanks. LOTW is a pain in the ass!! I do it because it is important to other Hams. |
|
I have had nothing but trouble trying to get it to work. I emailed their customer service people. They responded with an email that answered none of my questions and spoke to me like I am an idiot. I don't have any significant interest in their awards, but I know many do and want to be helpful towards them. For the record, I am not an idiot. |
|
Quoted:
I have had nothing but trouble trying to get it to work. I emailed their customer service people. They responded with an email that answered none of my questions and spoke to me like I am an idiot. I don't have any significant interest in their awards, but I know many do and want to be helpful towards them. For the record, I am not an idiot. This mirrors my experience. |
Got it! 
I had some trouble renewing my call sign certificate, a couple of weeks ago (has to be renewed every three years). It seemed to be correct, but over this past weekend I couldn't upload any QSOs to LoTW. I kept getting a message saying I didn't have a valid certificate. Got it straightened out today, but the whole thing was rather confusing. It was strange, because I didn't have any trouble setting it up the first time, three years ago. Go figure.... |
|
LoTW really isn't that complicated and once its set up it works well with most logging programs.
There is a Yahoo Group for LoTW and it will be very helpful for guys that are having trouble. https://groups.yahoo.com/neo/groups/ARRL-LOTW/info |
|
Quoted: .....log into LOTW and see if we are confirmed, please let me know if our QSO is confirmed?.... Yes and no 2015-03-15 02:21:00 30M JT65 10.13909 yes 2012-12-12 04:01:55 40M SSB 7.21400 no I found you in my HRD logbook twice, but it looks like LoTW only shows the 30m JT65 QSO . |
|
Quoted:
Yes and no 2015-03-15 02:21:00 30M JT65 10.13909 yes 2012-12-12 04:01:55 40M SSB 7.21400 no I found you in my HRD logbook twice, but it looks like LoTW only shows the 30m JT65 QSO . Quoted:
Quoted: .....log into LOTW and see if we are confirmed, please let me know if our QSO is confirmed?.... Yes and no 2015-03-15 02:21:00 30M JT65 10.13909 yes 2012-12-12 04:01:55 40M SSB 7.21400 no I found you in my HRD logbook twice, but it looks like LoTW only shows the 30m JT65 QSO . Not sure what to do with that? |
|
Well, I looked at my log, and saw that I worked another ARFCOMMER, " MeanStreaker " about 30mins before you on 80m. ....so I hunted the old 80m ARFCOM net thread and found this.... http://www.ar15.com/forums/t_10_22/639821_Tuesday_evening_80_meter_SSB_net_.html&page=78#i11310227 I said this LOL..... "... I don't hear either of you,...but me and "elcope" are almost in QSO LOL ..." Guess I logged it and you didn't ? no biggie. sounds like it was marginal, . . . . I don't remember I got you on 30m 
LoTW is cool once you go thru the setup BS. Looks like you've got it working
|
|
Quoted:
LoTW really isn't that complicated and once its set up it works well with most logging programs. There is a Yahoo Group for LoTW and it will be very helpful for guys that are having trouble. https://groups.yahoo.com/neo/groups/ARRL-LOTW/info Now that I have it associated with my QRZ logbook, all I have to do is mash one button, so, pretty easy now. 
|
|
Quoted: My HRD log is also ADIF, very common file type. just use "TrustedQSL" to sign and upload it. Quoted: Quoted: Good news: I got LOTW up and running. Bad News: I use fldigi which produces ADIF files that LOTW hates. My HRD log is also ADIF, very common file type. just use "TrustedQSL" to sign and upload it. LOTW wants a singular QSO_TIME. No amount of tinkering has made the data acceptable to LOTW. It will upload the file, but there is zero chance it will ever confirm a QSO. If I take the adif file the way fldigi exports it, LOTW turn the on time into the qso time (so it will only confirm with people who hit log at the start of a qso). If I limit the exported data to the OFF_TIME only, LOTW claims there is an error in which no time is present in the file. EDIT I think I have it resolved. However, I am not so sure it matters as I understand many people do not use LOTW. |