¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: LogSync Update.


 

to PA4JJ Jan

Hello Jan,
Thank you very much for your help,
I found it and I will be able to send my file to Rick.
73
F5jvp
Didier


------ Message d'origine ------
De "Jan" <hamlogger@...>
Date 30/10/2024 11:49:07
Objet Re: [hamlogger] LogSync Update.

Didier
The debug is in the Logsync itself.
Go to Info and the choose Debug. Then choose Debug on
The debug file can be found in the directory where you installed Logsync.

73
Jan
PA4JJ

Op 30-10-2024 om 11:44 schreef DIDIER DIENNE:
Reply to N2AMG Rick

HelloRick,

thank you for taking a little time to help me out...
I can't start the ''debug'' mode
because my PC doesn't want to register the command? \debug
To see doc1
my problem is:? for example this QSO recording

To see doc2
ThisQSO registers well at LOTW
To see doc3

But he did not ''flag'' la line ''Confirmation envoy¨¦e par LOTW ''
As it does very well for E-QSL
Thank you
73
F5JVP
Didier
------ Message d'origine ------
De "Ken McVie" <kenmcvie2@...>
? [email protected]
Date 30/10/2024 05:42:04
Objet Re: [hamlogger] LogSync Update.

------ Message d'origine ------
De "Rick Ellison" <rellison@...>
? [email protected]
Date 29/10/2024 12:22:59
Objet Re: [hamlogger] LogSync Update.

Didier..
It should work correctly I did not touch any of the code in that routine. If you would Turn Debug on and the next time you log a qso? the info should be written to the debug file. after a couple qso's you can turn Debug off and then send me the file called DebugLog.txt and results.txt Both files will be in the directory where Logsync is installed. Just send them as attachments.
73 Rick N2AMG

On 10/29/2024 4:30 AM, DIDIER DIENNE wrote:
TO N2AMG? Rick

Hello Rick,
I don't want to bother you much, because I know that your free time is very short. First of all, I want to take advantage of the fact that you and your wife's health problems get better quickly.
I just have a quick question,
I configured logger32 to automatically send e-qsl and LOTW.
For the e-qsl there is no problem, the procedure is done perfectly.
For the LOTW, the qso arrives at LOTW but it is not noted in logger32 as confirmed by LOTW as it should be. However, I did write: ''perform the flag in logger32''.
Please tell me if this function works correctly again.
73 F5JVP Didier


------ Message d'origine ------
De "F4FQH Olivier via groups.io" <unit365@...>
? [email protected]
Date 29/10/2024 08:37:23
Objet Re: [hamlogger] LogSync Update.

Hi? Rick,

Thanks for the job even with the hard life.

Try also to make a checkbox to delete or not the olds downloaded files after the upload, maybe you don't remember, i aked you a long time ago. (asked for lotw but maybe usefull for the others too)

Big thanks

73
Olivier
F4FQH

-----Message d'origine-----
De : [email protected] <[email protected]> De la part de Rick Ellison
Envoy¨¦ : mardi 29 octobre 2024 02:52
? : [email protected]
Objet : [hamlogger] LogSync Update.

I have had a number of people ask me to release an update. I have just been lacking time due to taking care of my wife. Today I had my Grand-daughter come sit with her so I could build an update. There are a few things I was going to finish working on but this fixes the following:

v2.0.19.8
A. When LOTW is not enabled stops TQSL Update checks and News Checks.
B. When LOTW is disabled hide Update TQSL Menu from Info menu tree.
C. Changed LOTW URL's to log into LOTW website.
D. Clublog no longer allows logging into Clublog from a 3rd party app.
It now gives a tooltip explaining this and only takes you to the Clublog login page.
E. Many users complained that windows were causing errors when resizing.
I have now locked the sizing of the main form to stop this.

You should get a notice in the next 24hrs when update routine runs.

73 Rick N2AMG


-- This email has been checked for viruses by Avast antivirus software.



























-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 77.174.195.163 port 7300
pa4jj-3 77.174.195.163 port 7388

Join [email protected] to automatically receive all group messages.