Date   

Re: Settings for Rotor, Logger32

Steph, F5NZY
 

Jim,

 

My rotor Is on a distant site, in Normandy. I am in Paris, but I connect my computer (Normandy) thru Teamviewer or VNC.

 

Thus, I am connected “locally”, but of course I can’t check if the rotor turns manually (I’ll be in Normandy next week-end).

 

But I think so, because, from Paris, I can turn the antenna with HRD_ROTATOR.

 

73 de Steph, F5NZY

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 20:47
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Looking at your Rotor debug pane, Logger32 sends a poll command, however, your rotor is not returning the antenna position.

When they are talking to each other, the  Received should  look like this:

 

Check your cable connections.

Can you rotate the antenna manually with your rotor control box:?

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 11:49 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Settings for Rotor, Logger32

 

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


Re: Settings for Rotor, Logger32

Steph, F5NZY
 

Hi Bob,

 

You’re right (I’ve read too fast), there’s no Yaesu G-450C, but Yaesu GS232A and Yaesu GS232B, there’s also GS232B A AZ/AZ A and GS232B AZ/AZ B

 

I tried all the Rotor type, including External.

 

You’re right, Yaesu G-450C has not a serial port. I use a ERC Interface who permits me to control the Rotor thru HRD_ROTATOR.

 

But, what I would like now, is when I type a call sign into L32, the antenna moves to the right path.

 

73 de Steph, F5NZY

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 6 novembre 2019 20:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph, I am confused (It is easy to do). You said this:  My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list? I double checked the list of rotors supported by Logger32, I don't see Yaesu G-450C on the list. Then I Googled Yaesu G-450C and the information I found indicates it does not have a serial port interface built in. Steph, then you say you use HRD_ROTATOR and remoterig. Is HRD_ROTATOR from Ham Radio Deluxe? If so, and it works, why are you messing around with Logger32? 



Steph, You have configured Logger32 for a GS232B AZ/AZ B rotor. I don't know what RS-232 interface device you are using, but I suspect is uses the GS232B protocol and not the GS232B AZ/AZ protocol. Try changing the rotor type in Logger32. SeventyThree(s).

On November 6, 2019 at 12:48 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>

 

 


 


Re: Settings for Rotor, Logger32

Bob
 

Steph, I am confused (It is easy to do). You said this:  My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list? I double checked the list of rotors supported by Logger32, I don't see Yaesu G-450C on the list. Then I Googled Yaesu G-450C and the information I found indicates it does not have a serial port interface built in. Steph, then you say you use HRD_ROTATOR and remoterig. Is HRD_ROTATOR from Ham Radio Deluxe? If so, and it works, why are you messing around with Logger32? 

Steph, You have configured Logger32 for a GS232B AZ/AZ B rotor. I don't know what RS-232 interface device you are using, but I suspect is uses the GS232B protocol and not the GS232B AZ/AZ protocol. Try changing the rotor type in Logger32. SeventyThree(s).

On November 6, 2019 at 12:48 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>

 



 


Re: Settings for Rotor, Logger32

Jim Hargrave
 

Steph,

Looking at your Rotor debug pane, Logger32 sends a poll command, however, your rotor is not returning the antenna position.

When they are talking to each other, the  Received should  look like this:

 

Check your cable connections.

Can you rotate the antenna manually with your rotor control box:?

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 11:49 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Settings for Rotor, Logger32

 

Hello Jim,

 

1)      Already checked, this Is the good port

2)      9600 Is the correct baud rate

3)      Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

1)      Make sure Windows has assigned the rotor to the right Com port (See Device manager)

2)      Verify that 9600 is the correct baud rate for the rotor.

3)      Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


Re: Settings for Rotor, Logger32

Steph, F5NZY
 

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


Re: Settings for Rotor, Logger32

Jim Hargrave
 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

1)      Make sure Windows has assigned the rotor to the right Com port (See Device manager)

2)      Verify that 9600 is the correct baud rate for the rotor.

3)      Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


Re: Settings for Rotor, Logger32

Steph, F5NZY
 

Hi Harold and Bob,

 

It’s better, but the rotor still does not move.

 

73

 

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Harold Miller
Envoyé : mercredi 6 novembre 2019 16:29
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

You also need to set the Band Plan to show a rotor is used on a particular band… I had the connection problem earlier…

 

It is in the help file…

 

Hal, KB1ZQ

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Wednesday, November 06, 2019 9:11 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Settings for Rotor, Logger32

 

Steph, I do not know the correct settings fpr the serial port to the rotor. But first you must get Logger32 to poll the rotor. Change the map to be like this

 

 

The rotor debug window will now look like this

 

 

For me there is nothing received because there is no rotor connected. You will have to experiment with the serial port settings and find out why you can not talk to the rotor.  The help file says to use these settings, but I don't know if they are correct. I think you are using the GS232B AZ/AZ A, so select that as the rotor type. 73.

 

On November 6, 2019 at 9:38 AM "Steph, F5NZY" <f5nzy@...> wrote:

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


 


Re: Settings for Rotor, Logger32

Harold Miller
 

You also need to set the Band Plan to show a rotor is used on a particular band… I had the connection problem earlier…

 

It is in the help file…

 

Hal, KB1ZQ

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Wednesday, November 06, 2019 9:11 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Settings for Rotor, Logger32

 

Steph, I do not know the correct settings fpr the serial port to the rotor. But first you must get Logger32 to poll the rotor. Change the map to be like this

 

 

The rotor debug window will now look like this

 

 

For me there is nothing received because there is no rotor connected. You will have to experiment with the serial port settings and find out why you can not talk to the rotor.  The help file says to use these settings, but I don't know if they are correct. I think you are using the GS232B AZ/AZ A, so select that as the rotor type. 73.

 

On November 6, 2019 at 9:38 AM "Steph, F5NZY" <f5nzy@...> wrote:

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


 


Re: Settings for Rotor, Logger32

Bob
 

Steph, I do not know the correct settings fpr the serial port to the rotor. But first you must get Logger32 to poll the rotor. Change the map to be like this



The rotor debug window will now look like this



For me there is nothing received because there is no rotor connected. You will have to experiment with the serial port settings and find out why you can not talk to the rotor.  The help file says to use these settings, but I don't know if they are correct. I think you are using the GS232B AZ/AZ A, so select that as the rotor type. 73.


On November 6, 2019 at 9:38 AM "Steph, F5NZY" <f5nzy@...> wrote:

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


 


Settings for Rotor, Logger32

Steph, F5NZY
 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>


Re: Error Msg #503

Gary Hinson
 

OK!

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 06 November 2019 09:28
To: hamlogger@groups.io
Subject: Re: [hamlogger] Error Msg #503

 

Simple Gary, it works perfectly, and does exactly what I wanted. SeventyThree(s).

On November 5, 2019 at 3:21 PM Gary Hinson <Gary@...> wrote:

So how about changing the backup strategy to avoid all that file-renaming shenanigans e.g. sequentially number each new backup, or use a date-time stamp as part of the file name, save it then delete older backups leaving the most recent 10? 

 

Perhaps even amend the deletion process to give a structured grandfather-father-son scheme allowing us to restore to any day within the past week, any week within the past month [5 weeks], or any month within the past year [12 months]? 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 06 November 2019 08:46
To: hamlogger@groups.io
Subject: Re: [hamlogger] Error Msg #503

 

I suppose it would be more accurate to say something like this:

 

NOTE: It is recommended you NOT backup directly to a cloud/remote drive. Create a \Backup directory on a local drive, change file path on your Logger32 backup window to point to this directory. Then after the backup is completed, move the complete \Backup directory to the cloud drive. 

 

After making several backups, you will notice that Logger32 maintains the 10 most recent backup - files named <whatever>-001.zip, -002.zip, etc. 010 is the most recent. When you have the full compliment of 10 backups and you make another one, it is temporarily called 011. Then the fun starts that often causes the cloud to Chernobyl ... 001 is deleted, 002 is renamed 001, 003 is renamed 002, 004 is renamed 003, etc. until 011 is renamed 010 and we once again have out 10 most recent backups. SeventyThree(s).

On November 5, 2019 at 2:31 PM Bob <k4cy@...> wrote:

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

 

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).

 

On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,

I keep getting the following error #503 msg.

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

 

Program works just fine otherwise.

 

Any suggestions?

 

Thanks,

 

Bob K9DT

On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 

 


 


 


 

 

 


 


Re: Error Msg #503

Bob
 

Simple Gary, it works perfectly, and does exactly what I wanted. SeventyThree(s).

On November 5, 2019 at 3:21 PM Gary Hinson <Gary@...> wrote:

So how about changing the backup strategy to avoid all that file-renaming shenanigans e.g. sequentially number each new backup, or use a date-time stamp as part of the file name, save it then delete older backups leaving the most recent 10? 

 

Perhaps even amend the deletion process to give a structured grandfather-father-son scheme allowing us to restore to any day within the past week, any week within the past month [5 weeks], or any month within the past year [12 months]? 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 06 November 2019 08:46
To: hamlogger@groups.io
Subject: Re: [hamlogger] Error Msg #503

 

I suppose it would be more accurate to say something like this:

 

NOTE: It is recommended you NOT backup directly to a cloud/remote drive. Create a \Backup directory on a local drive, change file path on your Logger32 backup window to point to this directory. Then after the backup is completed, move the complete \Backup directory to the cloud drive. 

 

After making several backups, you will notice that Logger32 maintains the 10 most recent backup - files named <whatever>-001.zip, -002.zip, etc. 010 is the most recent. When you have the full compliment of 10 backups and you make another one, it is temporarily called 011. Then the fun starts that often causes the cloud to Chernobyl ... 001 is deleted, 002 is renamed 001, 003 is renamed 002, 004 is renamed 003, etc. until 011 is renamed 010 and we once again have out 10 most recent backups. SeventyThree(s).

On November 5, 2019 at 2:31 PM Bob <k4cy@...> wrote:

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

 

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).

 

On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,

I keep getting the following error #503 msg.

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

 

Program works just fine otherwise.

 

Any suggestions?

 

Thanks,

 

Bob K9DT

On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 

 


 


 


 

 



 


Re: Error Msg #503

Gary Hinson
 

So how about changing the backup strategy to avoid all that file-renaming shenanigans e.g. sequentially number each new backup, or use a date-time stamp as part of the file name, save it then delete older backups leaving the most recent 10? 

 

Perhaps even amend the deletion process to give a structured grandfather-father-son scheme allowing us to restore to any day within the past week, any week within the past month [5 weeks], or any month within the past year [12 months]? 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 06 November 2019 08:46
To: hamlogger@groups.io
Subject: Re: [hamlogger] Error Msg #503

 

I suppose it would be more accurate to say something like this:

 

NOTE: It is recommended you NOT backup directly to a cloud/remote drive. Create a \Backup directory on a local drive, change file path on your Logger32 backup window to point to this directory. Then after the backup is completed, move the complete \Backup directory to the cloud drive. 

 

After making several backups, you will notice that Logger32 maintains the 10 most recent backup - files named <whatever>-001.zip, -002.zip, etc. 010 is the most recent. When you have the full compliment of 10 backups and you make another one, it is temporarily called 011. Then the fun starts that often causes the cloud to Chernobyl ... 001 is deleted, 002 is renamed 001, 003 is renamed 002, 004 is renamed 003, etc. until 011 is renamed 010 and we once again have out 10 most recent backups. SeventyThree(s).

On November 5, 2019 at 2:31 PM Bob <k4cy@...> wrote:

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

 

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).

 

On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,

I keep getting the following error #503 msg.

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

 

Program works just fine otherwise.

 

Any suggestions?

 

Thanks,

 

Bob K9DT

On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 

 


 


 


 


Re: Error Msg #503

Bob
 

I suppose it would be more accurate to say something like this:

NOTE: It is recommended you NOT backup directly to a cloud/remote drive. Create a \Backup directory on a local drive, change file path on your Logger32 backup window to point to this directory. Then after the backup is completed, move the complete \Backup directory to the cloud drive. 

After making several backups, you will notice that Logger32 maintains the 10 most recent backup - files named <whatever>-001.zip, -002.zip, etc. 010 is the most recent. When you have the full compliment of 10 backups and you make another one, it is temporarily called 011. Then the fun starts that often causes the cloud to Chernobyl ... 001 is deleted, 002 is renamed 001, 003 is renamed 002, 004 is renamed 003, etc. until 011 is renamed 010 and we once again have out 10 most recent backups. SeventyThree(s).

On November 5, 2019 at 2:31 PM Bob <k4cy@...> wrote:

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).


On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 

 


Re: Error Msg #503

Bob
 

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).


On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 


Re: Error Msg #503

Bob
 

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

If the message was Cannot open zip file, then your problem is that Logger32 can not see the I drive. SeventyThree(s)

On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 


Re: Error Msg #503

ROBERT JURISH <k9dt@...>
 

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT

On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 


Re: ADIF Editing

Gary Hinson
 

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF


Re: New version 3.50.399 and FT4/FT8 - how obtain QSL_Via and windows Worked/Confirmed

Jerzy Smietanski SP9AUV
 

Hello Bob !
Thank you for a help and detailed description of cooperation with Logger32 on FT4 / FT8 emissions

                          73 de Jerzy SP9AUV
                        http://sp9auv.com/EN

W dniu 2019-11-04 o 22:07, Bob pisze:
Many questions in one message ... In this picture the cherry-picker has just made a QSO with K8MU and it is logged automatically. If I want to make a DX Spot, than I click on the Cherry-picking event viewer SPOT menu. Nothing else to do.



Now in this picture I need additional information about K8MU to decide if I want to QSL and how. In my example I use HamQTH, but it is the same if you use QRZ.com. All I do is left click the mouse on K8MU on the Logbook Page window and I see this:



With this additional information, I can decide what I want to do. SeventyThree(s).

On November 4, 2019 at 3:47 PM Jerzy Smietanski SP9AUV <sp9auv@...> wrote:

Hello Bob !

You are do a new version 3.50.399
Support added to allow DX Spots from FT4/FT8 Event viewer windows

Can you more describing this update .
I' m look for a version to obtain personal data from a QRZ.COM via my external lookup , especially
for a QSL_Via data , also when working on FT4/FT8 . Then I can determine , if I need send QSL and if I need send it via DIRECT .
Also is very usefull will be then window Worked/Confirmed with filling proper data .
Based on this data I can determine if  I need do this QSO , because it is a new country for me .

                                               Best regards de Jerzy SP9AUV


Wolny od wirusów. www.avast.com

 



Wolny od wirusów. www.avast.com


Re: ADIF Editing

Dave Hobro
 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

7821 - 7840 of 85811