hamlogger@groups.io

Re: Update L32Logsync v 2.0.15

Arturo LU6ETB

#79125

Hi Rick,

That was the issue. I am running Logger32 as Administrator.

What happened when both program were running was that the Windows Defender put the Logger32 in quarantine.

I am running Windows 19 Version 1909.

Thanks

73 de Arturo, LU6ETB

Show quoted text

El vie., 13 mar. 2020 a las 10:48, Rick Ellison (<rellison@...>) escribió:

Arturo…
You are probably running Logger32 using the Run as Administrator setting. L32Logsync needs to be set to run that way also…

73 Rick N2AMG

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Arturo LU6ETB
Sent: Friday, March 13, 2020 12:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Update L32Logsync v 2.0.15

Hi Rick,

Thanks
I tried it. I was able to dowlnload the info from LOTW
Then I wanted to synchronize data and I received the below message.

Logger32 is running

Any idea what I am doing wrong
Logger32 is installed in D:\Ham\Logger32
L32LogSync is installed on D:\Ham\L32LogSync

Thanks
73 de Arturo, LU6ETB

El mar., 10 mar. 2020 a las 13:47, daniel lavocat (<F6FLU@...>) escribió:
Many thanks Rick
I tested the new feature to upload to QRZ.com that works fine
Thanks again
73

--
Daniel
F6FLU
Daniel Lavocat
F6FLU@...
https://f6flu.crx.cloud

F6KOP Team #1277

UFT #1277

CDXC #1632
DXCC CW #13586

keith hotchkiss a écrit le 10/03/2020 à 17:31 :

Rick,
Thank you and all the smart people who keep writing and sharing the add ons for Logger32.

Many thanks
Keith - G0FEA

Virus-free. www.avast.com

Re: Excel trying to Load during update

Anthony Buscaglia

#79124

Thanks Mike!

Show quoted text

On Mar 13, 2020, at 11:44 AM, Mike <ch25@...> wrote:

In logger32.ini
Check for Excel=No
Mike

Re: Excel trying to Load during update

Mike

#79123

In logger32.ini
Check for Excel=No
Mike

Excel trying to Load during update

Anthony Buscaglia

#79122

I have been setting L32 up on a friends PC.
When I set L32 to run as Admin, a window came up trying to load Excel.
It took a few tries but I was able to update. 
My friend is not computer savvy.  How can I stop that one before I give him the machine?

Tnx
73
Tony
K2NV

Re: Update L32Logsync v 2.0.15

Rick Ellison

#79121

Arturo…

You are probably running Logger32 using the Run as Administrator setting. L32Logsync needs to be set to run that way also…

73 Rick N2AMG

Show quoted text

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Arturo LU6ETB
Sent: Friday, March 13, 2020 12:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Update L32Logsync v 2.0.15

Hi Rick,

Thanks

I tried it. I was able to dowlnload the info from LOTW

Then I wanted to synchronize data and I received the below message.

Logger32 is running

Any idea what I am doing wrong

Logger32 is installed in D:\Ham\Logger32

L32LogSync is installed on D:\Ham\L32LogSync

Thanks

73 de Arturo, LU6ETB

El mar., 10 mar. 2020 a las 13:47, daniel lavocat (<F6FLU@...>) escribió:

Many thanks Rick
I tested the new feature to upload to QRZ.com that works fine
Thanks again
73

--
Daniel
F6FLU
Daniel Lavocat
F6FLU@...
https://f6flu.crx.cloud

F6KOP Team #1277

UFT #1277

CDXC #1632
DXCC CW #13586

keith hotchkiss a écrit le 10/03/2020 à 17:31 :

Rick,
Thank you and all the smart people who keep writing and sharing the add ons for Logger32.

Many thanks
Keith - G0FEA

Virus-free. www.avast.com

Re: Update L32Logsync v 2.0.15

Arturo LU6ETB

#79120

Hi Rick,

Thanks

I tried it. I was able to dowlnload the info from LOTW

Then I wanted to synchronize data and I received the below message.

Logger32 is running

Any idea what I am doing wrong

Logger32 is installed in D:\Ham\Logger32

L32LogSync is installed on D:\Ham\L32LogSync

Thanks

73 de Arturo, LU6ETB

Show quoted text

El mar., 10 mar. 2020 a las 13:47, daniel lavocat (<F6FLU@...>) escribió:

Many thanks Rick
I tested the new feature to upload to QRZ.com that works fine
Thanks again
73

--
Daniel

F6FLU
Daniel Lavocat
F6FLU@...
https://f6flu.crx.cloud

F6KOP Team #1277

UFT #1277
CDXC #1632 DXCC CW #13586

keith hotchkiss a écrit le 10/03/2020 à 17:31 :
Rick,
Thank you and all the smart people who keep writing and sharing the add ons for Logger32.

Many thanks
Keith - G0FEA

DX Spot Not Posting

Jim K2QB

#79119

When I post a spot to a DX Cluster with Ctrl D using the last entry in my log it posts just fine, i.e. "DX de K2QB 14074.00 XX2XX", but if I enter a callsign into the logbook entry window it does not post it as the message does not include my callsign. The message sent to the cluster is "DX 14074.00 XX2XX".
Running the latest version of Logger32...thanks!

Jim K2QB

Re: LoTW QSL receive Date

ja1nlx

#79118

Ken

Try this (You say it worked before)

1. Open Logger32 folder.

2. You see

3. Open Updatefiles for Ver3.50.408.

4. Copy ALL files and paste them in Logger32 folder.

5. If it does not work then open Updatefiles for ver3.50.407 and copy all files in Logger32 folder.

6. If it works then update to the latest version by auto update or manual update.

73

Show quoted text

On 2020/03/12 18:42, kenfilmer@... wrote:

Thanks Jim. I will read your message a couple of times more, maybe I'll understand it better.

Why I'm puzzled is that it all worked fine for years and when I upgraded L32 I couldn't open it for reasons unknown. I reloaded the latest L32 and I've had problems ever since.

I might go though the painful process of reloading it once more.

Many thanks Jim

73
Ken
G3XPO

--
73 de aki
JA1NLX

Re: upgrade.

kenfilmer@outlook.com

#79117

Thanks Jan
I haven't heard of that utility. I will have a look and maybe give it a try.
As you can see I do flag the correct LoTW QSL sent boxes and the ADIF sent to LoTW includes a Y against LoTW sent.
Maybe as Jim suggested its a synchronisation problem, but why its happening now when it didn't before I just do not know!
many thanks for your help
73
Ken G3XPO

Re: LoTW QSL receive Date

kenfilmer@outlook.com

#79116

Thanks Jim. I will read your message a couple of times more, maybe I'll understand it better.

Why I'm puzzled is that it all worked fine for years and when I upgraded L32 I couldn't open it for reasons unknown. I reloaded the latest L32 and I've had problems ever since.

I might go though the painful process of reloading it once more.

Many thanks Jim

73
Ken
G3XPO

Re: upgrade.

Jan

#79115

Hi Ken

Why do't you use the utility L32 LogSync made by N2AMG. ( www.n2amg.com )
By just 1 click it uploads all your qso's from Logger32 to LOTW
And when you want the confirmed LOTW QSO's imported into Logger32 its also 1 or 2 clicks.
Very simple.
You have to flag ofcourse the option Send LOTW QSL in the Logbook Page window and you have to use the most recent TQSL

73
Jan PA4JJ

Op 12-3-2020 om 10:22 schreef kenfilmer@...:

Checking ADIF file sent to ARRL - yes it does have a Y by LoTW QSL sent.
Does that mean I am OK and the problem lies elsewhere indicating there will be no point in me reloading L32?
Ken
G3XPO

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

Re: upgrade.

kenfilmer@outlook.com

#79114

Checking ADIF file sent to ARRL - yes it does have a Y by LoTW QSL sent.
Does that mean I am OK and the problem lies elsewhere indicating there will be no point in me reloading L32?
Ken
G3XPO

Re: upgrade.

kenfilmer@outlook.com

#79113

In a more direct answer to your question
Having checked the boxes to sent QSLs to LoTW I assume L32 puts a Y in the sent LoTW column (although on the L32 help file it notes the N is not actually changed to a Y)
So I assume the ADIF file sent shows all QSLs sent to Lotw.
The report back from LoTW says all QSOs do not have the sent to LoTW QSL.
Is that a coherent answer?
I'm trying!
73
Ken

Re: upgrade.

kenfilmer@outlook.com

#79112

Maybe I didn't explain my problem too well. Try again.
I do all the usual things, save ADIF file, sign it by TQSL upload to LoTW.
Trying to get my QSLs I download from ARRL the report which when synchronised with LoTW should show my QSLs in LoTW.
This fails and all my QSOs get put into the Mismatch file and they are mismatched because there is no LoTW QSL sent.
But as i said earlier I have checked send QSLs to LoTW.
I need to say here I am a computer idiot, so please bear that in mind.
73
Ken
G3XPO

Re: QSL_SENT_VIA

kenfilmer@outlook.com

#79111

Yep, I've checked all those fields! Makes no difference at all!
Thanks for the answer.
I'm wondering whether to reload L32 but that is a pain setting everything up again, but simpler than spending hours changing N to Y
73
Ken
G3XPO

LoTW QSL not sent

kenfilmer@outlook.com

#79110

Before reloading L32 after it went wonky everything worked fine. Now every time I try to get my LoTW confirmations I get mismatch due to LoTW QSL not sent.

In the Logging window I have checked QSLing and QSL export and flag new QSLs for export and existing QSOs to LoTW.

But whenever I send QSOs to LoTW they still come back as QSL not sent. Laboriously changing every QSO in the LoTW sent column from a N to a Y works, but I have better things to do with my life!

Can anybody help?

73

Ken G3XPO

Sent from Mail for Windows 10

Re: HamCap 2020 SSN.dat

Michael Harris

#79109

Ham Cap is a front end for the VOACAP prediction engine. I link Ham Cap to IonoProbe to get the current and 90 day SSN and SRI numbers. It still nevertheless requires an up to date SSN.dat file, presumably for the current month/year.

So we have to instal the latest SSN.dat file in a couple of years, no big deal apart from remembering to do it. Actually it's not a particularly complex file and should be easy to extend from the NOAA predictions when they become available. That is presumable all that Alex does.

Regards,

Mike VP8NO

Show quoted text

On 11/03/2020 16:23, Gerald Boutin wrote:
On Wed, Mar 11, 2020 at 03:33 PM, Gary Wilson wrote:
Fair enough, but the original program authors estimates end in 2022,
    so you get to repeat this exercise  in two years
Of course. These predictions are always being updated from time to time. They are generated by panels of experts and reported at these two sites.
http://www.sidc.be/silso/ssngraphics
https://www.swpc.noaa.gov/products/predicted-sunspot-number-and-radio-flux
You may note that there are several different methods of coming up with the predictions. I leave it to the program creator to determine which set of predictions is most compatible with the models used in the Hamcap software. Note that this data typically is only predicted a year or two in the future.
-- 
Gerald, VE1DT

Re: HamCap 2020 SSN.dat

Gerald Boutin

#79108

On Wed, Mar 11, 2020 at 03:33 PM, Gary Wilson wrote:

Fair enough, but the original program authors estimates end in 2022, so you get to repeat this exercise in two years

Of course. These predictions are always being updated from time to time. They are generated by panels of experts and reported at these two sites.

http://www.sidc.be/silso/ssngraphics
https://www.swpc.noaa.gov/products/predicted-sunspot-number-and-radio-flux

You may note that there are several different methods of coming up with the predictions. I leave it to the program creator to determine which set of predictions is most compatible with the models used in the Hamcap software. Note that this data typically is only predicted a year or two in the future.

--
Gerald, VE1DT

Re: HamCap 2020 SSN.dat

Gary Wilson <k2gw@...>

#79107

Fair enough, but the original program authors estimates end in 2022, so you get to repeat this exercise in two years

Re: No FT8 checkbox for mode

JOHN BIRKBY

#79106

Ok, I couldn’t wait. I put logger32 on my office computer and tried it out. Worked perfectly! Thanks to all!

73

Show quoted text

On Mar 11, 2020, at 7:11 AM, JOHN BIRKBY via Groups.Io <n2qlt@...> wrote:

Thanks for the helpful suggestions guys! I will give it a try when I get home tonight.

73

On Mar 10, 2020, at 8:31 PM, ja1nlx <ayoshida0205@...> wrote:

Hi

Check following steps.

1. Open Logger32 folder. Open ADIFModes.txt with text editor.

2. Put this line with Red color if there is not.

FAX
FM
FT8
FSK441
HELL =FMHELL,FSKHELL,HELL80,HFSK,PSKHELL

3. Open Setup Band/Mode table. (Click Tools)

4. Put FT8 slot in each Band like this if there are not.

<SS2020-03_033.jpg>

73

On 2020/03/11 4:25, n2qlt via Groups.Io wrote:

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!

--
73 de aki
JA1NLX