Date   
WSJT-X

Bob
 

For those who care, Logger32 auto-update 3.50.393 includes a new FT4 feature. First some background - WSJT-X ver 2.1.0 has incorporated some of the capabilities of JTDX it is now possible to send UDP Reply messages for events other than simply replying to a CQ (as it was before). Unfortunately, they only implemented this for FT4 and not FT8. Also, WSJT-X abandons all retries once a QSO is logged ... It make no effort to get that final precious '73'. 


While playing with WSJT-X FT4, I noticed that frequently after a station was logged I would not automatically receive the '73', but a repeat of his previous message. And, because WSJT-X doesn't attempt to recover, it simply went to sleep and no '73' was received.  I added code that attempts to re-synchronize the messages and get the '73'. See the picture below. It is not needed for JTDX, and only works for WSJT-X FT4. SeventyThree(s).



Satellite QSO to Logger32

Jacques RAMBAUD
 

Hello all,

What the simplest way of logging Satellite  QSOs  into Logger 32 and also be compliant with LOTW for upload ??

Thank you

73 jacques F6BKI

Re: Logger 32 won't start

Bob
 

Ken, in the Logger32 directory there will be folders like this (picture below) the updates folders are automatically created every time you upgrade. You don't have any? 73.



On August 26, 2019 at 3:57 AM Ken McVie <kenmc@...> wrote:


Hi Bob, I don't have the option of clicking on a ver 3.50.392 !
Attached  is a screen shot of the Rollback dir. when I open the
Logger32Rollback.exe

73
Ken ZL4NR

On 26/08/2019 6:30 PM, Bob wrote:
There is a file in the Logger32 directory called Logger32Rollback.exe. Run it, check the Ver 3.50.392 option, then click Rollback. SeventyThree(s).
>> On August 25, 2019 at 11:52 PM Ken McVie <kenmc@...> wrote:
>>
>>
>> I tried to do the update for Logger 32 today from the website. It didn't
>> work, & I now have a small error window showing --
>>
>> "File Error Loading C:\Logger32\ADIF.TXT
>>            Subscript out of range
>>
>> I initially get a very quick flash of the L32 opening screen, & then
>> this error comes up. If I click on the OK at the bottom of the error
>> window I get a blank L32 screen, with all the icons along the top, but a
>> blank page beneath.
>>
>> I also tried a "Restore Point " on the computer, but that didn't help.
>> Logger 32 has been running without problems for many years, so this is a
>> surprise.
>>
>> Any help Please?
>>
>> 73
>> Ken ZL4NR
>>
>>
>>
>


Re: Logger 32 won't start

Ken McVie <kenmc@...>
 

Hi again Bob, I managed to get the rollback to finally work, & am now on
ver. .392. So my screen is back to normal again, & I'll wait to see if
it comes up with an update over the next few days.

Thanks for the help -- much appreciated!!

73
Ken ZL4NR

On 26/08/2019 6:30 PM, Bob wrote:
There is a file in the Logger32 directory called Logger32Rollback.exe. Run it, check the Ver 3.50.392 option, then click Rollback. SeventyThree(s).

On August 25, 2019 at 11:52 PM Ken McVie <kenmc@...> wrote:


I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range

I initially get a very quick flash of the L32 opening screen, & then
this error comes up. If I click on the OK at the bottom of the error
window I get a blank L32 screen, with all the icons along the top, but a
blank page beneath.

I also tried a "Restore Point " on the computer, but that didn't help.
Logger 32 has been running without problems for many years, so this is a
surprise.

Any help Please?

73
Ken ZL4NR


Re: Logger 32 won't start

Ken McVie <kenmc@...>
 

Hi Bob, I don't have the option of clicking on a ver 3.50.392 !
Attached  is a screen shot of the Rollback dir. when I open the
Logger32Rollback.exe

73
Ken ZL4NR

On 26/08/2019 6:30 PM, Bob wrote:
There is a file in the Logger32 directory called Logger32Rollback.exe. Run it, check the Ver 3.50.392 option, then click Rollback. SeventyThree(s).

On August 25, 2019 at 11:52 PM Ken McVie <kenmc@...> wrote:


I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range

I initially get a very quick flash of the L32 opening screen, & then
this error comes up. If I click on the OK at the bottom of the error
window I get a blank L32 screen, with all the icons along the top, but a
blank page beneath.

I also tried a "Restore Point " on the computer, but that didn't help.
Logger 32 has been running without problems for many years, so this is a
surprise.

Any help Please?

73
Ken ZL4NR


Re: Logger 32 won't start

Bob
 

There is a file in the Logger32 directory called Logger32Rollback.exe. Run it, check the Ver 3.50.392 option, then click Rollback. SeventyThree(s).

On August 25, 2019 at 11:52 PM Ken McVie <kenmc@...> wrote:


I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range

I initially get a very quick flash of the L32 opening screen, & then
this error comes up. If I click on the OK at the bottom of the error
window I get a blank L32 screen, with all the icons along the top, but a
blank page beneath.

I also tried a "Restore Point " on the computer, but that didn't help.
Logger 32 has been running without problems for many years, so this is a
surprise.

Any help Please?

73
Ken ZL4NR


Re: Logger 32 won't start

Ken McVie <kenmc@...>
 

Hi Gerald, mine looks exactly like yours, I went through them both 3 times, & renaming it did nothing to fix the problem.

Cheers
Ken

On 26/08/2019 4:39 PM, Gerald Boutin wrote:
On Mon, Aug 26, 2019 at 12:52 AM, Ken McVie wrote:
I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range
Ken,

It would seem that there might be something wrong with the ADIF.txt file. As a test, I renamed my ADIF.txt file and started L32. It didn't have the same error message that you saw, but your description was what I saw here as well.

It is only a small text file. Take a look at your version for problems. Here are the contents of my working version.

ADDRESS
DISTANCE
ARRL_SECT
BAND
CALL
CNTY
COMMENT
CONT
CONTEST_ID
CQZ
USER_1
DXCC
FREQ
GRIDSQUARE
IOTA
ITUZ
USER_2
USER_3
MODE
NAME
NOTES
OPERATOR
PFX
PROP_MODE
QSLMSG
QSLRDATE
QSLSDATE
QSL_RCVD
QSL_SENT
QSL_VIA
QSO_DATE
QTH
RST_RCVD
RST_SENT
RX_PWR
SAT_MODE
SAT_NAME
SRX
STATE
STX
K_INDEX
TEN_TEN
TIME_OFF
TIME_ON
TX_PWR
SFI
QSO_NUMBER
eQSL_QSL_SENT
eQSL_QSL_RCVD
LOTW_QSL_SENT
LOTW_QSL_RCVD
FREQ_RX
BAND_RX
A_INDEX
SOTA_REF
 
--
Gerald, VE1DT

Re: Logger 32 won't start

Gerald Boutin
 

On Mon, Aug 26, 2019 at 12:52 AM, Ken McVie wrote:
I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range
Ken,

It would seem that there might be something wrong with the ADIF.txt file. As a test, I renamed my ADIF.txt file and started L32. It didn't have the same error message that you saw, but your description was what I saw here as well.

It is only a small text file. Take a look at your version for problems. Here are the contents of my working version.

ADDRESS
DISTANCE
ARRL_SECT
BAND
CALL
CNTY
COMMENT
CONT
CONTEST_ID
CQZ
USER_1
DXCC
FREQ
GRIDSQUARE
IOTA
ITUZ
USER_2
USER_3
MODE
NAME
NOTES
OPERATOR
PFX
PROP_MODE
QSLMSG
QSLRDATE
QSLSDATE
QSL_RCVD
QSL_SENT
QSL_VIA
QSO_DATE
QTH
RST_RCVD
RST_SENT
RX_PWR
SAT_MODE
SAT_NAME
SRX
STATE
STX
K_INDEX
TEN_TEN
TIME_OFF
TIME_ON
TX_PWR
SFI
QSO_NUMBER
eQSL_QSL_SENT
eQSL_QSL_RCVD
LOTW_QSL_SENT
LOTW_QSL_RCVD
FREQ_RX
BAND_RX
A_INDEX
SOTA_REF
 
--
Gerald, VE1DT

Re: Logger32 wont start

Ken McVie <kenmc@...>
 

I should add that I was running the previous version of L32 [398 I think] before I tried this update.

73
Ken ZL4NR

Logger 32 won't start

Ken McVie <kenmc@...>
 

I tried to do the update for Logger 32 today from the website. It didn't
work, & I now have a small error window showing --

"File Error Loading C:\Logger32\ADIF.TXT
           Subscript out of range

I initially get a very quick flash of the L32 opening screen, & then
this error comes up. If I click on the OK at the bottom of the error
window I get a blank L32 screen, with all the icons along the top, but a
blank page beneath.

I also tried a "Restore Point " on the computer, but that didn't help.
Logger 32 has been running without problems for many years, so this is a
surprise.

Any help Please?

73
Ken ZL4NR

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


 


 


 


 


 


 

Re: rotor problem

F4FQH Olivier
 

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

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


 


 

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

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


 


 


 


 

Re: rotor problem

F4FQH Olivier
 

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
 

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

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
 

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
 

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