1. Hamlogger
  2. Topics

LOTW and Cub Log Auto upload

Rick Ellison
 

That is the latest version. If you would click Info/Debug/Debug On

Log a qso or two and when they fail turn Debug Off and close the program. In the same directory you installed the program will be a file DebugLog.txt send that to me as an attachment.

The other day I had a user that mentioned that it was not uploading and it turned out his system wanted both Logger32 and L32Logsync to be run using the Run as Administrator setting. I’m not sure if this is the same issue but none of the routines pertaining the uploading  to LOTW or ClubLog in real-time has changed..

 

73 Rick N2AMG

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ian Morrison
Sent: Wednesday, November 9, 2022 4:14 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

Thanks for the quick reply.

Version 2.0.19.5

 

73,

Ian VE3EP

 

 

Sent from Mail for Windows

 

From: Rick Ellison
Sent: November 9, 2022 2:10 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

What version number do you have??

 

73 Rick N2AMG

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ian Morrison
Sent: Wednesday, November 9, 2022 1:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

I think it started with the last upgrade to Logsync.

Logsync will not do an auto upload to either Club Log or LOTW.

Manual works fine.

I’ve checked everything I can think of.

Any ideas, anyone?

 

73,

Ian VE3EP

 

Sent from Mail for Windows

 

From: G4GIR via groups.io
Sent: November 9, 2022 9:39 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Slow to display callsigns.

 

Aki/Bob

 

Thanks for the suggestions, para 34.7.6 sorted it, turned out to be SWL Mode turned on!! Must have accidentally clicked it when erasing the Decode window.

 

Cheers

 

73

 

 

Ian G4GIR

 

----- Original Message -----

From: ja1nlx <ayoshida0205@...>

Sent: 08/11/2022 22:42:17

Subject: Re: [hamlogger] JTDX Slow to display callsigns.

Ian

 

I suppose you are talking about BandActivity window in JTDX.

If so then find JTDX.ini and delete it. JTDX now starts with it's default settings.

If not then ignore my 2 cents.

 

How to find JTDX.ini ?

Click File in JTDX menu. Click Open log directory.

You see JTDX.ini there.

 

 

73 de aki

JA1NLX

On 2022/11/09 1:14:37, G4GIR via groups.io <i.frith@...> wrote:

Anyone help with another problem?

 

JTDX is taking up to 10 seconds for callsigns to be displayed in the de-code window and the Decode light remains Blue for the same amount of time.

I tried another Logger 32 configuration for another rig and all is OK.

 

Any Ideas please.

 

73 Ian G4GIR

 

 

Virus-free.www.avast.com

 
Ian Morrison
 

Thanks for the quick reply.

Version 2.0.19.5

 

73,

Ian VE3EP

 

 

Sent from Mail for Windows

 

From: Rick Ellison
Sent: November 9, 2022 2:10 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

What version number do you have??

 

73 Rick N2AMG

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ian Morrison
Sent: Wednesday, November 9, 2022 1:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

I think it started with the last upgrade to Logsync.

Logsync will not do an auto upload to either Club Log or LOTW.

Manual works fine.

I’ve checked everything I can think of.

Any ideas, anyone?

 

73,

Ian VE3EP

 

Sent from Mail for Windows

 

From: G4GIR via groups.io
Sent: November 9, 2022 9:39 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Slow to display callsigns.

 

Aki/Bob

 

Thanks for the suggestions, para 34.7.6 sorted it, turned out to be SWL Mode turned on!! Must have accidentally clicked it when erasing the Decode window.

 

Cheers

 

73

 

 

Ian G4GIR

 

----- Original Message -----

From: ja1nlx <ayoshida0205@...>

Sent: 08/11/2022 22:42:17

Subject: Re: [hamlogger] JTDX Slow to display callsigns.

Ian

 

I suppose you are talking about BandActivity window in JTDX.

If so then find JTDX.ini and delete it. JTDX now starts with it's default settings.

If not then ignore my 2 cents.

 

How to find JTDX.ini ?

Click File in JTDX menu. Click Open log directory.

You see JTDX.ini there.

 

 

73 de aki

JA1NLX

On 2022/11/09 1:14:37, G4GIR via groups.io <i.frith@...> wrote:

Anyone help with another problem?

 

JTDX is taking up to 10 seconds for callsigns to be displayed in the de-code window and the Decode light remains Blue for the same amount of time.

I tried another Logger 32 configuration for another rig and all is OK.

 

Any Ideas please.

 

73 Ian G4GIR

 

 

Virus-free.www.avast.com

 

B7EF8A3DDD414FFB9DC41D083FFE7FA5.png

Rick Ellison
 

What version number do you have??

 

73 Rick N2AMG

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ian Morrison
Sent: Wednesday, November 9, 2022 1:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Re: LOTW and Cub Log Auto upload

 

I think it started with the last upgrade to Logsync.

Logsync will not do an auto upload to either Club Log or LOTW.

Manual works fine.

I’ve checked everything I can think of.

Any ideas, anyone?

 

73,

Ian VE3EP

 

Sent from Mail for Windows

 

From: G4GIR via groups.io
Sent: November 9, 2022 9:39 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Slow to display callsigns.

 

Aki/Bob

 

Thanks for the suggestions, para 34.7.6 sorted it, turned out to be SWL Mode turned on!! Must have accidentally clicked it when erasing the Decode window.

 

Cheers

 

73

 

 

Ian G4GIR

 

----- Original Message -----

From: ja1nlx <ayoshida0205@...>

Sent: 08/11/2022 22:42:17

Subject: Re: [hamlogger] JTDX Slow to display callsigns.

Ian

 

I suppose you are talking about BandActivity window in JTDX.

If so then find JTDX.ini and delete it. JTDX now starts with it's default settings.

If not then ignore my 2 cents.

 

How to find JTDX.ini ?

Click File in JTDX menu. Click Open log directory.

You see JTDX.ini there.

 

 

73 de aki

JA1NLX

On 2022/11/09 1:14:37, G4GIR via groups.io <i.frith@...> wrote:

Anyone help with another problem?

 

JTDX is taking up to 10 seconds for callsigns to be displayed in the de-code window and the Decode light remains Blue for the same amount of time.

I tried another Logger 32 configuration for another rig and all is OK.

 

Any Ideas please.

 

73 Ian G4GIR

 


Virus-free.www.avast.com
Ian Morrison
 

I think it started with the last upgrade to Logsync.

Logsync will not do an auto upload to either Club Log or LOTW.

Manual works fine.

I’ve checked everything I can think of.

Any ideas, anyone?

 

73,

Ian VE3EP

 

Sent from Mail for Windows

 

From: G4GIR via groups.io
Sent: November 9, 2022 9:39 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Slow to display callsigns.

 

Aki/Bob

 

Thanks for the suggestions, para 34.7.6 sorted it, turned out to be SWL Mode turned on!! Must have accidentally clicked it when erasing the Decode window.

 

Cheers

 

73

 

 

Ian G4GIR

 

----- Original Message -----

From: ja1nlx <ayoshida0205@...>

Sent: 08/11/2022 22:42:17

Subject: Re: [hamlogger] JTDX Slow to display callsigns.

Ian

 

I suppose you are talking about BandActivity window in JTDX.

If so then find JTDX.ini and delete it. JTDX now starts with it's default settings.

If not then ignore my 2 cents.

 

How to find JTDX.ini ?

Click File in JTDX menu. Click Open log directory.

You see JTDX.ini there.

 

 

73 de aki

JA1NLX

On 2022/11/09 1:14:37, G4GIR via groups.io <i.frith@...> wrote:

Anyone help with another problem?

 

JTDX is taking up to 10 seconds for callsigns to be displayed in the de-code window and the Decode light remains Blue for the same amount of time.

I tried another Logger 32 configuration for another rig and all is OK.

 

Any Ideas please.

 

73 Ian G4GIR

 

11DEC95C03E14B448E5CB749BE898102.png

1 - 4 of 4