Date   
Re: CW machine $name$ macro

Fred Bourne
 

Working okay on my system never had any problems.

73 Fred G3YJQ


On 25 Aug 2019, at 13:04, Vince Shirley <vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

Re: CW machine $name$ macro

Vince Shirley
 

Always a pleasure to speak to you, Bob

Never mind we Brits have far worse things to worry about.  Imagine the UK not being part of Europe, what would the ADIF meisters have to say about that!  

For the avoidance  of doubt, yes the Logbook window is populated with a name, but its not sent by the macro.    

Vince G0ORC



On Sun, 25 Aug 2019 at 13:52, Bob <k4cy@...> wrote:

... maybe your free trial has expired. SeventyThree(s).

On August 25, 2019 at 8:37 AM Vince Shirley <vince.g0orc@...> wrote:

Well a mystery then,

Space before and after but doesn't work for me.

Here's a cut and paste of the macro concerned.

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

Vince G0ORC


On Sun, 25 Aug 2019 at 13:32, Bob < k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley < vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

 

 

Re: CW machine $name$ macro

Vilhjalmur Sigurjonsson
 

Vince,

I did paste your macro into my CW machine (in L32), no problem.

Now try the usual … rename Logger32.ini and cw.ini, to have a fresh start etc. Is it still broken then?

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Vince Shirley
Sent: sunnudagur, 25. ágúst 2019 12:37
To: hamlogger@groups.io
Subject: Re: [hamlogger] CW machine $name$ macro

 

Well a mystery then,

 

Space before and after but doesn't work for me.

 

Here's a cut and paste of the macro concerned.

 

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

 

Vince G0ORC

 

 

On Sun, 25 Aug 2019 at 13:32, Bob <k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley <vince.g0orc@...> wrote:

Hi all,

 

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

 

Anyone confirm this please?

 

Vince

Re: CW machine $name$ macro

Gerald Boutin
 

On Sun, Aug 25, 2019 at 09:37 AM, Vince Shirley wrote:
 
Here's a cut and paste of the macro concerned.
 
$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

 

 Vince,

Try the $name$ macro in a shorter string of text. Maybe there is a buffer overflow.

--
Gerald, VE1DT

Re: CW machine $name$ macro

Vince Shirley
 

Thanks everyone,

A new win.ini doesn't help.

If the macro consists only of $name$, the radio keys and immediately unkeys, nothing is sent.

I'm now looking through Logger32.ini to see if I can find any problems.

Vince


On Sun, 25 Aug 2019 at 14:03, Gerald Boutin <groupsio@...> wrote:
On Sun, Aug 25, 2019 at 09:37 AM, Vince Shirley wrote:
 
Here's a cut and paste of the macro concerned.
 
$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

 

 Vince,

Try the $name$ macro in a shorter string of text. Maybe there is a buffer overflow.

--
Gerald, VE1DT

Re: CW machine $name$ macro

Bob
 

This is your macro on my PC. 73.



On August 25, 2019 at 8:37 AM Vince Shirley <vince.g0orc@...> wrote:

Well a mystery then,

Space before and after but doesn't work for me.

Here's a cut and paste of the macro concerned.

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

Vince G0ORC


On Sun, 25 Aug 2019 at 13:32, Bob < k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley < vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

 

 

Re: CW machine $name$ macro

Bob
 

Vince, that's correct if there is no name Is the name appearing at the top right of the CW Machine? 73.

On August 25, 2019 at 9:10 AM Vince Shirley <vince.g0orc@...> wrote:

Thanks everyone,

A new win.ini doesn't help.

If the macro consists only of $name$, the radio keys and immediately unkeys, nothing is sent.

I'm now looking through Logger32.ini to see if I can find any problems.

Vince


On Sun, 25 Aug 2019 at 14:03, Gerald Boutin < groupsio@...> wrote:
On Sun, Aug 25, 2019 at 09:37 AM, Vince Shirley wrote:
 
Here's a cut and paste of the macro concerned.
 
$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

 

 Vince,

Try the $name$ macro in a shorter string of text. Maybe there is a buffer overflow.

--
Gerald, VE1DT

 

 

Re: CW machine $name$ macro

Vince Shirley
 

Thanks Bob,


A virgin Logger32.ini file cures the problem.

I don't really want to spend the rest of the afternoon going line by line through it, nor do I fancy re-customising things.

Any idea where I might start looking in the Logger32.ini file?

Vince

On Sun, 25 Aug 2019 at 14:15, Bob <k4cy@...> wrote:

This is your macro on my PC. 73.



On August 25, 2019 at 8:37 AM Vince Shirley <vince.g0orc@...> wrote:

Well a mystery then,

Space before and after but doesn't work for me.

Here's a cut and paste of the macro concerned.

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

Vince G0ORC


On Sun, 25 Aug 2019 at 13:32, Bob < k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley < vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

 

 

Re: CW machine $name$ macro

Bob
 

Right click on any user field on the Logbook Entry Window. Click on SETUP. Go to SETUP USER FIELDS.  Click on the top menu (user field 1). You will see this window (picture below).  Note the bottom three user options. Hopefully you have the middle one checked. SeventyThree(s).



On August 25, 2019 at 9:20 AM Vince Shirley <vince.g0orc@...> wrote:

Thanks Bob,


A virgin Logger32.ini file cures the problem.

I don't really want to spend the rest of the afternoon going line by line through it, nor do I fancy re-customising things.

Any idea where I might start looking in the Logger32.ini file?

Vince

On Sun, 25 Aug 2019 at 14:15, Bob < k4cy@...> wrote:

This is your macro on my PC. 73.



On August 25, 2019 at 8:37 AM Vince Shirley < vince.g0orc@...> wrote:

Well a mystery then,

Space before and after but doesn't work for me.

Here's a cut and paste of the macro concerned.

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

Vince G0ORC


On Sun, 25 Aug 2019 at 13:32, Bob < k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley < vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

 

 

 

 

Re: CW machine $name$ macro

Vince Shirley
 

Mystery solved.  It works

Amazing I've only been using this program since time was invented and I still find things I didn't know about.

Thanks for your help Bob and everyone...

Vince

On Sun, 25 Aug 2019 at 14:30, Bob <k4cy@...> wrote:

Right click on any user field on the Logbook Entry Window. Click on SETUP. Go to SETUP USER FIELDS.  Click on the top menu (user field 1). You will see this window (picture below).  Note the bottom three user options. Hopefully you have the middle one checked. SeventyThree(s).



On August 25, 2019 at 9:20 AM Vince Shirley <vince.g0orc@...> wrote:

Thanks Bob,


A virgin Logger32.ini file cures the problem.

I don't really want to spend the rest of the afternoon going line by line through it, nor do I fancy re-customising things.

Any idea where I might start looking in the Logger32.ini file?

Vince

On Sun, 25 Aug 2019 at 14:15, Bob < k4cy@...> wrote:

This is your macro on my PC. 73.



On August 25, 2019 at 8:37 AM Vince Shirley < vince.g0orc@...> wrote:

Well a mystery then,

Space before and after but doesn't work for me.

Here's a cut and paste of the macro concerned.

$call$ de g0orc ok $name$ tks fb info hr rig yaesu ft101d wid 1ttw to windom up 12mtrs  - wx nw rain es 10c sohw? $call$ de $mycall$ <

Vince G0ORC


On Sun, 25 Aug 2019 at 13:32, Bob < k4cy@...> wrote:

Works as advertised for me. If there is no name and the CW Machine is sending $name$, then you probably don't have a space after $name$ in your macro. SeventyThree(s).

On August 25, 2019 at 8:04 AM Vince Shirley < vince.g0orc@...> wrote:

Hi all,

It appears the $name$ macro is broken in the CW machine - seems to work OK in MMTTY FSK but not in CW...

Anyone confirm this please?

Vince

 

 

 

 

Re: rotor problem

Jim Cox
 

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF

Re: rotor problem

Bob
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF

Re: rotor problem

Jim Cox
 

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 

From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF

Re: rotor problem

Bob
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF


 


 

Re: rotor problem

Olivier F4FQH
 

Hi
 
I have the same issue here, rotor is moving alone when the sation is called.
The rotor change direction just a bit
 
73s
Olivier
F4FQH
 

From: Bob
Sent: Sunday, August 25, 2019 4:27 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF


 


 

Re: rotor problem

Bob
 

Oliver, please explain. I have no idea what you said. 73.

On August 25, 2019 at 1:27 PM Olivier F4FQH <unit365@...> wrote:

Hi
 
I have the same issue here, rotor is moving alone when the sation is called.
The rotor change direction just a bit
 
73s
Olivier
F4FQH
 
From: Bob
Sent: Sunday, August 25, 2019 4:27 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF


 


 


 


 

SAT QSO logging

Jacques RAMBAUD
 

Hello all,

What the simplest way of logging Sat QSOs like QO100 to get statistics into Logger32 and be compliant with LOTW for upload ??

Thank you

73 jacques F6BKI

Re: rotor problem

Jim Cox
 

Bob. Out of town till tomorrow. Will send exact sequence tomorrow.  Jim. K4JAF



On Aug 25, 2019, at 12:27 PM, Olivier F4FQH <unit365@...> wrote:

Hi
 
I have the same issue here, rotor is moving alone when the sation is called.
The rotor change direction just a bit
 
73s
Olivier
F4FQH
 
From: Bob
Sent: Sunday, August 25, 2019 4:27 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF


 


 

Re: rotor problem

Olivier F4FQH
 

Hi Bob,
 
Well will try to explain but next time i will check carefully the problem.
 
I’ve started to use the UDP band plan windows now, to select calls which interest me. In JTDX, it not showing correctly what is made or not, so the UDP windows is nice for this.
Nice also because when we clic a call, the system know when calling after a CQ or 73 from the station we call.
 
Before i clicked only on calls in JTDX and never saw this issue.
 
When i clic a call in the UDP windows, it fill the logbook entry, and turn the rotator in direction of the call QTH clicked. Untill this, it’s ok.
But, during the QSO the rotor move alone. Sometime it move just a bit, some degrees more or less, it seem the rotator not stopped in the good direction the first time. Somtime moving anywhere...
But this not all the time.
I will check this better, and report you a better explanation.
Or if i can i will make video and send you a link to watch it, because it will be big i think.
 
Interesting bug but all is usable, just boring,  that’s why i search on my side before asking something, but as i saw some have nearly the same issue, so i told it.
 
Will investigate a bit more Bob, my problem is i resume work tomorow so the time will be short in next days....
 
73s
 
Olivier
F4FQH
 

From: Bob
Sent: Sunday, August 25, 2019 7:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Oliver, please explain. I have no idea what you said. 73.

On August 25, 2019 at 1:27 PM Olivier F4FQH <unit365@...> wrote:

Hi
 
I have the same issue here, rotor is moving alone when the sation is called.
The rotor change direction just a bit
 
73s
Olivier
F4FQH
 
From: Bob
Sent: Sunday, August 25, 2019 4:27 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF


 


 


 


 

Re: rotor problem

Bob
 

Olivier, mon vieux, I think what you are seeing is because when you click on the UDP BandMap the callsign is loaded into the Logbook Entry Window and the beam heading is calculated based on the callsign. The antenna starts to turn. After maybe one or two seconds the lookup of the callsign adds additional data to the Logbook Entry Window - Maybe a US State or County, maybe a gridsquare. The beam heading is recalculated based on this new information ... What does the rotor do? Experiment with this ... on the Rotator setup Window (at the bottom) are options to delay the start of turning the beam ... For example, if you delay 3 seconds (maybe two, or one), them hopefully the additional data from the callsign lookup has populated the Logbook Entry Window and the calculations will be correct the first time the rotor is turned. Avoir du sens? SeventyThree(s).

On August 25, 2019 at 5:34 PM Olivier F4FQH <unit365@...> wrote:

Hi Bob,
 
Well will try to explain but next time i will check carefully the problem.
 
I’ve started to use the UDP band plan windows now, to select calls which interest me. In JTDX, it not showing correctly what is made or not, so the UDP windows is nice for this.
Nice also because when we clic a call, the system know when calling after a CQ or 73 from the station we call.
 
Before i clicked only on calls in JTDX and never saw this issue.
 
When i clic a call in the UDP windows, it fill the logbook entry, and turn the rotator in direction of the call QTH clicked. Untill this, it’s ok.
But, during the QSO the rotor move alone. Sometime it move just a bit, some degrees more or less, it seem the rotator not stopped in the good direction the first time. Somtime moving anywhere...
But this not all the time.
I will check this better, and report you a better explanation.
Or if i can i will make video and send you a link to watch it, because it will be big i think.
 
Interesting bug but all is usable, just boring,  that’s why i search on my side before asking something, but as i saw some have nearly the same issue, so i told it.
 
Will investigate a bit more Bob, my problem is i resume work tomorow so the time will be short in next days....
 
73s
 
Olivier
F4FQH
 
From: Bob
Sent: Sunday, August 25, 2019 7:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Oliver, please explain. I have no idea what you said. 73.

On August 25, 2019 at 1:27 PM Olivier F4FQH <unit365@...> wrote:

Hi
 
I have the same issue here, rotor is moving alone when the sation is called.
The rotor change direction just a bit
 
73s
Olivier
F4FQH
 
From: Bob
Sent: Sunday, August 25, 2019 4:27 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Jim, please explain what you mean by ... but not when you click on a call in FT8 Where do you click? 73.

On August 25, 2019 at 10:14 AM Jim Cox <jcox123@...> wrote:

Bob, I have the rotator box set ok in the band plan menu for FT8.  Strange behavior as sometimes the rotator will work ok but not when you click on a call in FT8 but will change directions when the station is first called and the xmitter keys..  This is evident also by the rotator debug screen.  All worked fine until a week or so ago when I first noticed this behavior.  Jim K4JAF
 
From: Bob
Sent: Sunday, August 25, 2019 8:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] rotor problem
 

Click TOOLS | SETUP BANDS & MODES. You are now looking at your personalized BandPlan. Look at the FT4 and FT8 rows ... All the way over to the next to last column is where the Rotor # goes. No number = no rotor. So, when operating FT4 or FT8 the frequency changes to the appropriate row in the table. No number = no rotor.  SeventyThree(s).

On August 25, 2019 at 9:41 AM Jim Cox <jcox123@...> wrote:

I have been having this problem with the rotator --- not sure when it started, most of the time it will not work when going to JTDX but works fine outside of the program.  I can look at the rotator debug screen and no command is sent to the rotator itself from Logger32.  Again when a station is just selected from the spots screen within Logger32 it works FB.  Any ideas.  73s Jim K4JAF