Date   

Lost wsjtx_log.adi

Andy VA3PL
 

Sorry it is not related much to Logger 32 but perhaps someone would help.
Due to computer crash i lost wsjtx_log.adi containing all my FT8 and FT4 QSO's from WSJT-X program.
Is there a way to restore it from Logger32, perhaps?
I do keep daily backups of all my Logger32 QSO's

73 de Andy SP9KR


Re: MKII vs high power

Bob
 

Probably another Logger32 bug. SeventyThree(s).

On November 20, 2019 at 7:17 AM sp5ewx <sp5ewx@...> wrote:


Do you think its due to wireles system ??

On Wed, Nov 20, 2019 at 10:14 AM Jan <hamlogger@...> wrote:

Hello Mike

I had the same issue transmitting on 160 with 400 W.
After changing the keyboard to a Logitec K120 the trouble was gone and it even stays away without all the ferrite chockes.
The only problem I have is that my rotor (Yeasy G-2800 DXC) console is going to move. In fact it has destroyed the variable speed so now the rotor turns at high speed only.


Op 20-11-2019 om 09:46 schreef sp5ewx:

Hello everybody
I noticed when I use high power (more than 900-1000w) application in the computer turning off( yellow flag ) and computer stops to communicate with router..radio still communicate …I can use CW ..and so on but Logger stops to communicate ..no frq reading ..Only solution is to restart program .I use good grounding system , ferret chokes on every cable.Is it .My computer is HP8200 and system WIN10 .
Any advice ??
Mike sp5ewx



--
____________________________________________________
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: FT8 bug after last update .401

Mike
 

On Wed, Nov 20, 2019 at 03:05 AM, Bob wrote:
What exactly do you want?
To have it working the way it was till 401 patch.
I'm not sure if I was clear explaining issue, I will make a video later, showing what is the difference.
Best regards, Mike


Re: MKII vs high power

sp5ewx
 

Do you think its due to wireles system ??

On Wed, Nov 20, 2019 at 10:14 AM Jan <hamlogger@...> wrote:

Hello Mike

I had the same issue transmitting on 160 with 400 W.
After changing the keyboard to a Logitec K120 the trouble was gone and it even stays away without all the ferrite chockes.
The only problem I have is that my rotor (Yeasy G-2800 DXC) console is going to move. In fact it has destroyed the variable speed so now the rotor turns at high speed only.


Op 20-11-2019 om 09:46 schreef sp5ewx:

Hello everybody
I noticed when I use high power (more than 900-1000w) application in the computer turning off( yellow flag ) and computer stops to communicate with router..radio still communicate …I can use CW ..and so on but Logger stops to communicate ..no frq reading ..Only solution is to restart program .I use good grounding system , ferret chokes on every cable.Is it .My computer is HP8200 and system WIN10 .
Any advice ??
Mike sp5ewx



--
____________________________________________________
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: Clublog sync problem

Jim Altman
 

I did send a note to clublog and what I finally figured out is that I had not added FT4 to digital modes even though I had set it up in the band plan.  So now all but the 2 digitalvoice import fine.  DV is not available to add to phone in the pick list, but I don’t know if DV is properly a digital or phone mode.

 

73

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Tuesday, November 19, 2019 9:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Clublog sync problem

 

Jim, a note to Club Log on the subject might also be in order. SeventyThree(s).

On November 18, 2019 at 7:14 PM Rick Ellison <rellison@...> wrote:

I would open up your adif file in Notepad++ or another good text editor and do a find replace. Find <MODE:4>FT4 and replace it with MODE:4>MFSK <SUBMODE:3:>FT4 after doing that save the file and reimport it to ogger32. Make sure make a copy of the adif file in case something goes sideways.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Monday, November 18, 2019 4:06 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Clublog sync problem

 

So, I think I see what’s going on.  I downloaded my log as an ADIF from Clublog.  In it, FT4 is listed as a mode, not as a submode to MFSK.   Hmmm.  What to do?

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jim Altman via Groups.Io
Sent: Monday, November 18, 2019 12:41 PM
To: hamlogger@groups.io
Subject: [hamlogger] Clublog sync problem

 

I am not sure if this is a clublog or L32 problem, but I did a LOTW DXCC credit submission today and then synced my updated credits to clublog.  Then I synced Clublog to L32.  L32 reports 210 QSO’s not updated.  208 of them were FT4 contacts and the message was “Can’t find F4HRR at 2019-07-16 19:55:02 on 20M FT4 Granted (Mode?)”  2 were Digital Voice.  All the rest updated correctly to Granted status.  These are all the FT4 contacts down to and including yesterday.

 

I am aware of the FT4 submode issues and thought this was all straightened out.  I am running the latest L32, updated yesterday or today.  Is this a stupid human problem (i.e. Equipment Superior to Operator) or have I found a lingering issue in the app?

 

73 de w4uck

 

 

 

Jim Altman

jaltman636@...

 

 

 


 


Re: No frequency and wrong mode

Ignacy Misztal
 

Turned out I accidentally unchecked "show frequency" in "Frequency". Then, in a logging windows, "set mode by radio" was unchecked. 
L32 has lots of options!
Ignacy


Re: No frequency and wrong mode

Tom Wylie
 

Is your second version of Logger 32 set to show frequency and not just Band?


Tom

On 20/11/2019 01:52, Bob wrote:
Ignacy, is Logger32 talking to the radio? Open the radio debug window - on the lower status bar, right click on the radio pane. Click the SHOW RADIO DEBUG WINDOW menu. There you will see the messages to and from the radio and at the top you will see the radio frequency and mode. What do you see. A picture would help. 73.
On November 19, 2019 at 7:51 PM Ignacy Misztal <no9e@...> wrote:

I use L32 at my regular QTH and everything works fine.

I installed it at my 2nd QTH. It is connected to a radio but the logging windows shows no frequency. But its shows correct band (e.g., 160M).  Logging QSO returns FREQ 0. Clicking on spots puts wrong mode.

Ignacy, NO9E


Re: MKII vs high power

Jan
 

Hello Mike

I had the same issue transmitting on 160 with 400 W.
After changing the keyboard to a Logitec K120 the trouble was gone and it even stays away without all the ferrite chockes.
The only problem I have is that my rotor (Yeasy G-2800 DXC) console is going to move. In fact it has destroyed the variable speed so now the rotor turns at high speed only.


Op 20-11-2019 om 09:46 schreef sp5ewx:
Hello everybody 
I noticed when I use high power (more than 900-1000w) application in the computer turning off( yellow flag ) and computer stops to communicate with router..radio still communicate …I can use CW ..and so on but Logger stops to communicate ..no frq reading ..Only solution is to restart program .I use good grounding system , ferret chokes on every cable.Is it .My computer is HP8200 and system WIN10 .
Any advice ??
Mike sp5ewx



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


MKII vs high power

sp5ewx
 

Hello everybody
I noticed when I use high power (more than 900-1000w) application in the computer turning off( yellow flag ) and computer stops to communicate with router..radio still communicate …I can use CW ..and so on but Logger stops to communicate ..no frq reading ..Only solution is to restart program .I use good grounding system , ferret chokes on every cable.Is it .My computer is HP8200 and system WIN10 .
Any advice ??
Mike sp5ewx


ODP: [hamlogger] Set System Time API

Andy VA3PL
 

Ohhh...i should better know.
Thanks Bob

Andy SP9KR


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Bob <k4cy@...>
Wysłane: środa, 20 listopada 2019 02:46
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] Set System Time API
 
Are you running Logger32 as an administrator? 73.

On November 19, 2019 at 2:14 PM Andy VA3PL <va3pl@...> wrote:

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR

 


Re: Clublog sync problem

Bob
 

Jim, a note to Club Log on the subject might also be in order. SeventyThree(s).

On November 18, 2019 at 7:14 PM Rick Ellison <rellison@...> wrote:

I would open up your adif file in Notepad++ or another good text editor and do a find replace. Find <MODE:4>FT4 and replace it with MODE:4>MFSK <SUBMODE:3:>FT4 after doing that save the file and reimport it to ogger32. Make sure make a copy of the adif file in case something goes sideways.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Monday, November 18, 2019 4:06 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Clublog sync problem

 

So, I think I see what’s going on.  I downloaded my log as an ADIF from Clublog.  In it, FT4 is listed as a mode, not as a submode to MFSK.   Hmmm.  What to do?

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jim Altman via Groups.Io
Sent: Monday, November 18, 2019 12:41 PM
To: hamlogger@groups.io
Subject: [hamlogger] Clublog sync problem

 

I am not sure if this is a clublog or L32 problem, but I did a LOTW DXCC credit submission today and then synced my updated credits to clublog.  Then I synced Clublog to L32.  L32 reports 210 QSO’s not updated.  208 of them were FT4 contacts and the message was “Can’t find F4HRR at 2019-07-16 19:55:02 on 20M FT4 Granted (Mode?)”  2 were Digital Voice.  All the rest updated correctly to Granted status.  These are all the FT4 contacts down to and including yesterday.

 

I am aware of the FT4 submode issues and thought this was all straightened out.  I am running the latest L32, updated yesterday or today.  Is this a stupid human problem (i.e. Equipment Superior to Operator) or have I found a lingering issue in the app?

 

73 de w4uck

 

 

 

Jim Altman

jaltman636@...

 

 



 


Re: FT8 bug after last update .401

Bob
 

Mike, I am thoroughly confused (it's easy to do). What exactly do you want? You want auto-lookup of callsigns when you click on a DX spot, you want auto-lookup of callsigns you manually enter in the logbook entry window, but you dont want auto-lookup of callsigns you are QSOing on WSJT-X? Do I understand correctly. 73

On November 18, 2019 at 4:08 AM Mike <ch25@...> wrote:

On Mon, Nov 18, 2019 at 09:56 AM, Bob wrote:
Try this: Click SETUP | AUTO LOOKUP and UNcheck the option AUTO INTERNET CALLSIGN LOOKUP (EXTERNAL). SeventyThree(s).
Now it does not look for qrz.com data at all.
It was working fine in .400, in .401 every time wsjtx have disabled TX logbook entry window is wiped from callsign, tx enable in wsjtx - callsign appears back. It wasn't working that way in .400
Mike

 


Re: No frequency and wrong mode

Bob
 

Ignacy, is Logger32 talking to the radio? Open the radio debug window - on the lower status bar, right click on the radio pane. Click the SHOW RADIO DEBUG WINDOW menu. There you will see the messages to and from the radio and at the top you will see the radio frequency and mode. What do you see. A picture would help. 73.

On November 19, 2019 at 7:51 PM Ignacy Misztal <no9e@...> wrote:

I use L32 at my regular QTH and everything works fine.

I installed it at my 2nd QTH. It is connected to a radio but the logging windows shows no frequency. But its shows correct band (e.g., 160M).  Logging QSO returns FREQ 0. Clicking on spots puts wrong mode. 

Ignacy, NO9E

 


Re: Set System Time API

Bob
 

Are you running Logger32 as an administrator? 73.

On November 19, 2019 at 2:14 PM Andy VA3PL <va3pl@...> wrote:

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR

 


Re: Set System Time API

Bob
 

.TheTime = GetQUInt32(data)
dim sTime as string
sTime = format$(.TheTime / 86400000, "hh:mm:ss")

SeventyThreE(s).

On November 19, 2019 at 2:14 PM Andy VA3PL <va3pl@...> wrote:

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR

 


No frequency and wrong mode

Ignacy Misztal
 

I use L32 at my regular QTH and everything works fine.

I installed it at my 2nd QTH. It is connected to a radio but the logging windows shows no frequency. But its shows correct band (e.g., 160M).  Logging QSO returns FREQ 0. Clicking on spots puts wrong mode. 

Ignacy, NO9E


Set System Time API

Andy VA3PL
 

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR


Re: TX7T location not being found

Ed Tobias
 

That fixed it, pal. Your assumption about the cause is probably correct. BTW, I managed to eek out a brief, 339, contact with JA1NUT the other evening, so the bands may be coming back. I’ll be keeping a ear out for ZM4T this weekend.

 

Ed

 

From: Gary Hinson
Sent: Monday, November 18, 2019 7:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TX7T location not being found

 

Hi Ed.

 

Same here … so I re-ran the Club Log prefix update …

 

 

… which fixed it …

 

 

Maybe Club Log had an early end date for them, which someone has kindly corrected.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ed Tobias
Sent: 19 November 2019 13:31
To: hamlogger@groups.io
Subject: [hamlogger] TX7T location not being found

 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E

 

 

 


Re: TX7T location not being found

Gary Hinson
 

Hi Ed.

 

Same here … so I re-ran the Club Log prefix update …

 

 

… which fixed it …

 

 

Maybe Club Log had an early end date for them, which someone has kindly corrected.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ed Tobias
Sent: 19 November 2019 13:31
To: hamlogger@groups.io
Subject: [hamlogger] TX7T location not being found

 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E

 

 


TX7T location not being found

Ed Tobias
 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E