Date   

Re: Trying to load logger

Rick EA4M
 

I had the same problem and I created the file.manuakky into Logger32 directory.


It worked for me!!!!


El mar., 2 feb. 2021 8:44, w5jmw <w5jmw@...> escribió:
Hi All.I am trying to load a new logger32 program in a machine that had logger32.I deleted the app,deleted the file in directory I have reloaded the program 2 times.I pulled the logbook from another machine.When I try to pull up the logger32.I get this,,,failed to open/read the adif countries with primary subdivisions.txt file.....Then I close this out and try to bring up the log and I get this...Run=time error 5 invalid procedure call or argument...Ok what am I missing or doing wrong ??


Re: A couple of rotator questions - Version 4

John, G4DRS
 

Jim,
I checked,
yes, I do have the rotator set up in the Bands and Modes file.


John
G4DRS


Re: JTDX Control Panel

Barry GM4GIF
 

Yeah, Happy Grouseday Maestro and thanks for this great software.
73 de Barry/gm4gif


Re: JTDX Control Panel

Julian GW4JBQ
 

Happy Birthday Bob

  I hope you have a great day today and I shall be raising a large glass of Grouse to you later on tonight.

     73 de Julian  GW4JBQ 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, 2 February 2021, 00:21
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

Someone said, I don't remember who, "O ye of little faith ...". SeventyThree(s), and wish me Happy Birthday.
On 02/01/2021 6:44 PM Gary Hinson <gary@...> wrote:
 
 

OK, I was wrong.  You can start the JTDX Control Panel before or after launching JTDX using Start -> JTDX on the UDP BandMap.  It works either way.  So you can also close and then re-open the JTDX Control Panel if you like.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 02 February 2021 09:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 

 



Issue fixed

Rick EA4M
 

Hello Bob 

Issue fixed with commas!!!!!

Thanks a lot!!!!

73'de Rick EA4M


Trying to load logger

w5jmw
 

Hi All.I am trying to load a new logger32 program in a machine that had logger32.I deleted the app,deleted the file in directory I have reloaded the program 2 times.I pulled the logbook from another machine.When I try to pull up the logger32.I get this,,,failed to open/read the adif countries with primary subdivisions.txt file.....Then I close this out and try to bring up the log and I get this...Run=time error 5 invalid procedure call or argument...Ok what am I missing or doing wrong ??


a LOG CALL IN BLUE

w5jmw
 

OK,using version 4.My log is back yellow and fonts are red when qsl confirmed.Few nights ago and today.I logged a call.It is in blue.I manually confirmed it,tried to edit it(color) even tried to delete.When I stop on the line of the log where the call appears the entire row goes blank.What does the blue call mean and where is it being told to go blue...? I have checked the fonts and colors..I do not see a blue anywhere.Clues? anyone


Re: JTDX Control Panel

Bob
 

Someone said, I don't remember who, "O ye of little faith ...". SeventyThree(s), and wish me Happy Birthday.

On 02/01/2021 6:44 PM Gary Hinson <gary@...> wrote:
 
 

OK, I was wrong.  You can start the JTDX Control Panel before or after launching JTDX using Start -> JTDX on the UDP BandMap.  It works either way.  So you can also close and then re-open the JTDX Control Panel if you like.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 02 February 2021 09:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 

 


Re: JTDX Control Panel

Jim Altman
 

Yes, you should be able to open the Control Panel either before or after, as long as JTDX was started from the bandmap.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: Monday, February 1, 2021 6:44 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

OK, I was wrong.  You can start the JTDX Control Panel before or after launching JTDX using Start -> JTDX on the UDP BandMap.  It works either way.  So you can also close and then re-open the JTDX Control Panel if you like.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 02 February 2021 09:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 


Re: JTDX Control Panel

Gary Hinson
 

OK, I was wrong.  You can start the JTDX Control Panel before or after launching JTDX using Start -> JTDX on the UDP BandMap.  It works either way.  So you can also close and then re-open the JTDX Control Panel if you like.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 02 February 2021 09:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 


Re: JTDX Control Panel

Jim Altman
 

You should always use the UDP Band Map to open JTDX.  During its startup process there are essential items that make the control panel work.  Opening JTDX manually may or may not work to be controlled by the L32 Control Panel. But to be reliable you should always use the Band Map to start JTDX.  I don’t remember the version number it happened at, but changes were made to JTDX by its authors to make the L32 control panel work, so if you are on an old version, you should update to the latest.  Finally, the JTDX folks say you should ALWAYS delete your old ini file and setup JTDX from scratch with each update to JTDX.  Its not that hard.

 

It’s all completely reliable here.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: Monday, February 1, 2021 3:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 


Re: JTDX Control Panel

Gary Hinson
 

HI Bob.

 

The control panel didn’t work when I started it after JTDX … but I’ll try it again now, or rather “Now in a minute” as my Welsh grandmother used to say.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 02 February 2021 05:54
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Gary. I think you'll find that the JTDX control paned works correctly if it is started before or after JTDX. 73.

On 01/31/2021 9:44 PM Gary Hinson <gary@...> wrote:

 

 

Friends,

 

I’ve discovered that the JTDX Control Panel only works (for me) if I follow this sequence:

 

1.       Open the UDP BandMap.

2.       On the UDP BandMap menu, click Config -> Show JTDX Control Panel

3.       On the UDP BandMap menu, click Start -> JTDX … and wait for it to launch fully (it needs at least 8 seconds on my system so I have configured it to wait 10 seconds).

 

Now I can click the JTDX Control Panel buttons to change bands or modes: JTDX and the radio change quickly although the JTDX control panel button coloring takes a second or two to catch up.

 

If instead I start JTDX from its desktop icon, the JTDX Control Panel shows Control Panel not connected and doesn’t work.  Also, if I start JTDX before opening the JTDX Control Panel, the control panel looks OK (no red warning) but doesn’t work.

 

73

Gary  ZL2iFB

 


Re: ADIF Log Import

n5kd
 

Thanks Bob.

I’ve done that. DC is now a state in my shack. I actually found about 3 QSO’s in there.
Note 1 understood.

 

73’ Pete, N5KD.

 

From: Bob
Sent: Monday, February 1, 2021 6:46 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Log Import

 

Pete, as I recall, the file maps imported ARRL_SECT field to auto populate the STATE field. To accommodate the faux STATE of DC (see NOTE 1) when making a Logbook entry window entry, you probably need something like this.

 

 

And, if you're lucky, it will be logged as DC. If you're very lucky it will appear under MD for WAS. SeventyThree(s).

 

Note 1: I have no doubt that POTUS will do his utmost to make DC a State.

 

 

 

 

On 02/01/2021 1:00 PM n5kd <n5kd@...> wrote:

 

 

I’m curious now….

Does Arrlsect.db only work for imports?

 

I just modified mine to add   DC to MD  like this below, but entering a callsign (in the logbook entry pain) with DC as the state gives error message that DC is not a primary admin – which is a true statement.

 

CO  | CO

CT  | CT

DC  | MD

DE  | DE

EB  | CA

EMA | MA

 

73’ Pete, N5KD.

 

From: Bob
Sent: Monday, February 1, 2021 5:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Log Import

 

There's a file Arrlsect.db (a text file) in the \Logger32 directory. I suppose it could be edited to map DC to MD and NF to NL. SeventyThree(s).

On 02/01/2021 12:26 PM Bruce Meier <bemeier@...> wrote:

 

 

I also had an ADIF import issue after CQ 160, in addition to the DC needing to be changed to MDC.

 

CQ 160 expected NF for Newfoundland, but Logger32 wanted it to be NL.

 

Quick change – reimport – all OK!

 

73,

Bruce N1ln


--
73,
Bruce N1LN

 

 

 

Virus-free. www.avg.com

 


Re: JTDX Control Panel

Gary Hinson
 

You could be right, Julian.  JTDX c2.2.0-rc155 (with core code derived from various versions of WSJT-X) is working pretty well for me in conjunction with Logger32 v4.0.240 on Windows 8.1 with an AMD CPU and an Elecraft K3 using microcode v5.67 ………..

 

The system is so complex that I’m amazed it works at all!  It’s like watching a unicycling dog: who cares what way it’s going?  It’s a unicycling dog!!

 

Tom: with the above setup, I can flick back and forth between FT8 and FT4 using the JTDX Control Panel mode buttons every time I’ve tried so far.  Aside from changing mode, JTDX also sends the radio to the applicable frequencies on the same band.  I wonder what’s different with your setup?  Do you have ‘the applicable frequencies’ defined for each mode and each band in JTDX?   Is your radio controlled reliably & consistently by JTDX e.g. does it also always QSY when you change the mode through the JTDX menu?  On mine, the frequency pane in JTDX goes red for about a second while the radio QSYs before updating the frequency and reverting to the grey backgrund … which makes sense as I think I have the radio polling interval set to 1 second in JTDX.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Julian GW4JBQ
Sent: 01 February 2021 21:23
To: hamlogger@groups.io
Subject: Re: [hamlogger] JTDX Control Panel

 

Following past posts on this subject and having tried it, you need to use JTDX v 155 for it to work correctly. Earlier versions are a bit temperamental.

 73 de Julian GW4JBQ 


Re: A couple of rotator questions - Version 4

Bob
 

Not sure what you said Andy, but my compass is red. SeventyThree(s).

On 02/01/2021 2:19 PM Andy M0NKR via groups.io <andrewgoldsmith22@...> wrote:
 
 
I found the wedge showed up after restarting logger32.
 
My issue with the map thought is I could get bold black compass, tried everything gave up on the end.
 
73
Andy
Nkr 

 

On 1 Feb 2021, at 19:14, John, G4DRS via groups.io <g4drs@...> wrote:

Thanks, Bob.
I'll keep fiddling...


John
G4DRS


Re: A couple of rotator questions - Version 4

Andy M0NKR
 

I found the wedge showed up after restarting logger32.

My issue with the map thought is I could get bold black compass, tried everything gave up on the end.

73
Andy
Nkr 


On 1 Feb 2021, at 19:14, John, G4DRS via groups.io <g4drs@...> wrote:

Thanks, Bob.
I'll keep fiddling...


John
G4DRS


Re: A couple of rotator questions - Version 4

John, G4DRS
 

Thanks, Bob.
I'll keep fiddling...


John
G4DRS


Re: A couple of rotator questions - Version 4

John, G4DRS
 

On Mon, Feb 1, 2021 at 03:56 PM, Jim Hargrave wrote:

 

Do you have the rotator setup in the Bands and Mode chart for the bands using the rotator?

Jim,
I'll double check, but I believe so.


John
G4DRS


Re: ADIF Log Import

Didier Le Duc
 

Import look at the field name not its place. My experience with other programs.
Didier F6DXE

Le lun. 1 févr. 2021 à 17:06, Jim K2QB <nfjimc@...> a écrit :
Looking to import a contest log from N1MM. Comparing it to other .adif files I have imported, there is a difference in the sequence of the headers. In the N1MM generated adif file the STATE header appears in the fifth column right after TIME_OFF. On other adif files I have successfully imported the STATE header is three from the end. So my question is, does the import function use the actual header information regardless of where in the file it is located?

Jim K2QB


Re: ADIF Log Import

Bob
 

Pete, as I recall, the file maps imported ARRL_SECT field to auto populate the STATE field. To accommodate the faux STATE of DC (see NOTE 1) when making a Logbook entry window entry, you probably need something like this.
 
 
And, if you're lucky, it will be logged as DC. If you're very lucky it will appear under MD for WAS. SeventyThree(s).
 
Note 1: I have no doubt that POTUS will do his utmost to make DC a State.
 
 
 
 

On 02/01/2021 1:00 PM n5kd <n5kd@...> wrote:
 
 

I’m curious now….

Does Arrlsect.db only work for imports?

 

I just modified mine to add   DC to MD  like this below, but entering a callsign (in the logbook entry pain) with DC as the state gives error message that DC is not a primary admin – which is a true statement.

 

CO  | CO

CT  | CT

DC  | MD

DE  | DE

EB  | CA

EMA | MA

 

73’ Pete, N5KD.

 

From: Bob
Sent: Monday, February 1, 2021 5:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Log Import

 

There's a file Arrlsect.db (a text file) in the \Logger32 directory. I suppose it could be edited to map DC to MD and NF to NL. SeventyThree(s).

On 02/01/2021 12:26 PM Bruce Meier <bemeier@...> wrote:

 

 

I also had an ADIF import issue after CQ 160, in addition to the DC needing to be changed to MDC.

 

CQ 160 expected NF for Newfoundland, but Logger32 wanted it to be NL.

 

Quick change – reimport – all OK!

 

73,

Bruce N1ln


--
73,
Bruce N1LN

 

 


Virus-free. www.avg.com

2241 - 2260 of 84672