Skip to content

Fleshed out the get/set status commands#1

Open
we7u wants to merge 31 commits intobjorgan:masterfrom
we7u:master
Open

Fleshed out the get/set status commands#1
we7u wants to merge 31 commits intobjorgan:masterfrom
we7u:master

Conversation

@we7u
Copy link
Copy Markdown

@we7u we7u commented Jun 24, 2021

Asgeir,

I have a need to mount an SDA-100 controller remotely so started working on your code after forking it. I fleshed out the commands nicely, decoding everything and providing new commands to exercise all of the functionality. The only thing I didn't fully decode was which motors were currently busy from the motor_busy byte, but I don't have a need for that currently. One can tell if ANY motors are busy, which for me is good enough. More to come!

we7u added 30 commits June 24, 2021 13:35
Several commands were added, fleshing out the complete command and
status encoding/decoding that the docs allow. Most commands tested
with the exception of:
  set_serial_update_ON()
  set_serial_update_OFF()
  retract_antenna()
  calibrate_antenna()
Added loops around the major commands and checking status in the loop to
assure that each command takes. Also added timers so that commands won't
be sent to the controller at too high of a rate. Tested all of the commands.
This version can be inserted between various clients and linHPSDR
in the CAT stream. GUI buttons will command the SteppIR but programs
such as WSJT-X changing the frequency won't cause a change to the
SteppIR controller yet: Serial communication to the SteppIR controller
is too slow and messes up the CAT communication. I'll need to put the
serial comms into a separate thread to fix this.
Created a 4th thread to do serial communications. Serial was too slow
to be able to do it inside the other threads, so had to implement in a
separate thread. The program now changes the SteppIR SDA-100 controller's
frequency if AUTOTRACK is on and the CLIENT changes the frequency via
the CAT port.
New thread which queries the radio's frequency iff there's no CAT
controller attached.
The RadioQueryLoop thread, if run in conjunction with a CAT controller
connected to the listening port, will interfere with the CAT controller.  I've
disabled the thread for now. The correct implementation for this thread would
be to have it started if and only if there is nothing connected to the
listening port, and to kill the thread when something connects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant