Skip to content

Navigation Menu

Sign in
Sign up

Star Tracker not sending Elevation to second Rotator Controller instance (dual-port Az/El setup) #2669

Unanswered
tajj-AI-comphw-2024 asked this question in Q&A
Discussion options

Hi all,

I'm using SDRangel 7.23.2 to control a Green Heron RT-21 Az/El rotator via Hamlib rotctld (model 405, two separate TCP instances: 127.0.0.1:4533 for Azimuth on COM3, 127.0.0.1:4534 for Elevation on COM4).

Setup:

  • Star Tracker (F:1) calculating Az/El for targets (e.g., Taurus A, Moon) — plots update correctly.
  • One Controller (Separate ports, unfortunately):
    • F:0 (Azimuth): TCP rotctld, port 4533, Az min/max
    • F:2 (Elevation): TCP rotctld, port 4534, Az min/ma
  • Both controllers have Track checked → linked to F:1 StarTracker.

Result:

  • Azimuth controller (F:0) works perfectly — Az updates and rotator moves Az axis.
  • Elevation controller (F:2) only receives/updates Az values (Reads elevation in its place) — Elevation stays at 0 or doesn't change/move.

Expected: Each controller should filter the Az/El pair from Star Tracker (Az controller ignores El, El controller ignores Az).

Screenshots attached (controller settings, Star Tracker, plots).

Is this a known limitation? Is there a way to route Az/El separately to each controller instance? Or is multi-rotator output from Star Tracker not fully supported yet?

Thanks for any help/workarounds!
Screenshot 2026年03月05日 173245
Screenshot 2026年03月05日 173215

You must be logged in to vote

Replies: 1 comment

Comment options

You might want to have a log in the log file (preferences > logging) to see what is going on

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /