Re: Using the Antenna ROTOR with JT modes.
toggle quoted messageShow quoted text
I have not noted that condition. Give me some time to see if I can duplicate.
Jim – w5ifp-
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Jim Cox
Sent: Monday, August 26, 2019 4:30 PM
Subject: Re: [hamlogger] Using the Antenna ROTOR with JT modes.
I see discrepancies in the actions of the rotator in JTDX here. Using 2.0.1 rc115.
Scenarios: 1. I click on spot in UDP map (monitoring with Rotator Debug Screen), nothing happens to rotator, then when xmitter is started because I double click on call in JTDX, the rotator will start to swing to correct position.
Same as 1. above but nothing ever happens with rotator.
Same as 1. above but rotator starts as soon as clicking on the spot even before double clicking in JTDX.
Same as 1, but rotator begins movement maybe on second time JTDX tries to call the spotted station.
All of these actions are verified by rotator debug screen.
I have everything apparently correct in band plan for rotator and frequency, mode, etc. I use a 2 second delay in rotator screen.
Any thoughts? Jim K4JAF
From: Jim Hargrave
Sent: Monday, August 26, 2019 12:41 PM
Subject: [hamlogger] Using the Antenna ROTOR with JT modes.
There is a lot of confusion surrounding what should have a simple solution.
Given: The Logger32 Rotor module does not know about JTDX/WSJT. All Rotor setup is within Logger32.
To avoid more confusion, I will provide a simple setup process for the rotor.
1) Configure the Rotor module in Setup/Rotor/Setup rotator #1. Sample below is my setup’
Open Rotor port automatically,
3 second delay (for Callsign lookup) May vary, depends on lookup source/Internet connection/speed
2) Tools/Setup bands and Modes: Rotor number is the rotor that is configured under Setup/Rotor #(x)
At this point, verify that the Rotor is operating as expected.
3) Open the UDP port and select
With the above setup, the following things happen.
a) The selected FT program started by UDP selection
b) Logger32 automatically closes the Logger32 radio port and switches radio control to the JT program.
c) Logger32 re-opens the radio port when JTDX/wsjt-x is closed
d) Logger32 maintains full control of the rotor.
e) Callsign is placed in the Log Entry CALL field by any of following methods.
2) DX Spot selection
3) UDP band map selection
4) Cherry Picker selection
f) Following is initiated by bLogger32
1) Callsign lookup in logbook/on-line as user configured.
2) Bands & Mode chart scanned for Mode/Radio /Rotor options
Opening and closing JTDX/wsjt-x is accomplished from within the UDP Bandmap START/STOP options. This keeps all the changeover actions in sync.
I hope this helps de-mud the water.
Jim – w5ifp-