Hi Hams
I went back to 2.13.0.0 and the issue of uploading to LOTW completed. I think there is a bug in the new version(2.14.0.0) since after I updated I started with the problem.
I´m use JTAlert ver. 2.16.17
Regards 73"
ISSUE IN UPLOAD CONFIRMATIONS LOTW
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
I suggest that you send a support request to Lele because none of the Alpha testers or I can replicate this issue so it has to be local to your setup.
73 Terry G4POP
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
Have y'all considered trying to run your FTxx APP (JTDX or WSJTx) on a direct connection to Log4OM V2 as a test to see if the issue persists?
Meaning ... take JTAlert out of the loop?
Set up the direct connection as outlined in the most recent User Guide.
Give it a test and see what your results may (or may not) be.
Just a simple trouble-shooting technique ... simplify the installation one step at a time.
.
Meaning ... take JTAlert out of the loop?
Set up the direct connection as outlined in the most recent User Guide.
Give it a test and see what your results may (or may not) be.
Just a simple trouble-shooting technique ... simplify the installation one step at a time.
.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
How is JTAlert "in the loop" when performing a manual upload to LOTW?KI5IO wrote: ↑14 Jun 2021, 10:50 Have y'all considered trying to run your FTxx APP (JTDX or WSJTx) on a direct connection to Log4OM V2 as a test to see if the issue persists?
Meaning ... take JTAlert out of the loop?
Set up the direct connection as outlined in the most recent User Guide.
Give it a test and see what your results may (or may not) be.
Just a simple trouble-shooting technique ... simplify the installation one step at a time.
.
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
It's not but sometimes the QSO information arriving from external software contains the wrong information which when applied to a LOTW upload causes a problem..n0iai wrote: ↑16 Jun 2021, 14:33How is JTAlert "in the loop" when performing a manual upload to LOTW?KI5IO wrote: ↑14 Jun 2021, 10:50 Have y'all considered trying to run your FTxx APP (JTDX or WSJTx) on a direct connection to Log4OM V2 as a test to see if the issue persists?
Meaning ... take JTAlert out of the loop?
Set up the direct connection as outlined in the most recent User Guide.
Give it a test and see what your results may (or may not) be.
Just a simple trouble-shooting technique ... simplify the installation one step at a time.
.
73 Terry G4POP
Re: ISSUE IN UPLOAD CONFIRMATIONS LOTW
FWIW I get similar behavior when a log mismatch with LOTW station location data occurs.
Ex: log contains grid EL99ki LOTW station location specifies grid EL99lb
Start the LOG4OM2 upload and get:
INFO: ADIF File created successfully.
INFO: TQSL Version 2.5.8
No private TQSL Password set
Executing TQSL with upload
Then nothing happens, (waited overnight at least once) so force quit Log4OM2 upload
I troubleshot the issue by performing a manual upload of the same log using TQSL GUI and it returned error messages specifically stating the mismatched field issue.
Updated LOTW station location grid to match log and all is working fine with LOG4OM2 uploads to LOTW
Ex: log contains grid EL99ki LOTW station location specifies grid EL99lb
Start the LOG4OM2 upload and get:
INFO: ADIF File created successfully.
INFO: TQSL Version 2.5.8
No private TQSL Password set
Executing TQSL with upload
Then nothing happens, (waited overnight at least once) so force quit Log4OM2 upload
I troubleshot the issue by performing a manual upload of the same log using TQSL GUI and it returned error messages specifically stating the mismatched field issue.
Updated LOTW station location grid to match log and all is working fine with LOG4OM2 uploads to LOTW