Manual Rotator Tolerance Ignored?

Issue #1066 closed
Bill Richards created an issue

[ X] Is the issue reproducible? I believe so.
[X ] Are all prerequisites that are mentioned inside the manual met? I believe so.

Which Version are you running? 2.0BETA019

Description

I have the “Rotation Tolerance” defined to be 0.75 degrees, but when I used the Framing Assistant last week to align my equipment with an image captured previously, it continued to report rotation errors after the error was well below the defined tolerance. It reported rotation errors as low as 0.1 degrees. I eventually had to disable “Rotate Target” in the Target Option” section of the Sequencer to proceed.

Steps to Reproduce

  • Configure your profile to have a manual rotator and define a Rotation Tolerance to be 1 degree or so.
  • In the Framing Assistant, load a previously captured image and click on “Add target to sequence”.
  • In the Sequencer, ensure that “Slew to target”, “Center target”, and “Rotate target” are all enabled.
  • Start the sequencer and when it reports the rotation error, adjust the optice to try to align within the defined tolerance.

Expected behaviour

Once the rotational error is less than the defined tolerance, the Sequencer should accept the adjustments and proceed.

Actual behaviour

The Sequencer continues to report rotational errors even when the error is less than the defined tolerance.

Here are a couple NINA log file excerpts showing when this happened:

  • 2022-01-30T18:43:33.6314|INFO|CenterAndRotate.cs|Execute|163|Rotator not inside tolerance 0.75 - Current 96.04446° / Target: 275.79° - Moving rotator relatively by -0.254425°
  • 2022-01-30T18:46:50.6324|INFO|CenterAndRotate.cs|Execute|163|Rotator not inside tolerance 0.75 - Current 95.96626° / Target: 275.79° - Moving rotator relatively by -0.1762238°
  • 2022-01-30T23:36:02.0354|INFO|CenterAndRotate.cs|Execute|163|Rotator not inside tolerance 0.75 - Current 271.324° / Target: 91.22° - Moving rotator relatively by -0.1040344°

Comments (3)

  1. Stefan B repo owner

    Hi,

    Your Beta Version is outdated and this issue should already be fixed. If the issue is still reproducable on the latest beta version, please reopen the issue again with updated details.

  2. Log in to comment