Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in fli_pdf focuser driver not handling AF Overscan properly #2028

Closed
johneevans opened this issue Mar 15, 2024 · 3 comments
Closed

Bug in fli_pdf focuser driver not handling AF Overscan properly #2028

johneevans opened this issue Mar 15, 2024 · 3 comments
Labels

Comments

@johneevans
Copy link

Describe the bug
The fli_pdp is quite an old driver and was probably written before AF Overscan was added to Focus. AF Overscan relies on the focuser always returning the current position as it moves to its requested position. The fli_pdp driver returns FLIFocus.steps_remaing when a move is in flight (line 343) and FLIFocus.current_pos (line 353) when the move completes. This confuses Focus and renders AF Overscan unusable.

To Reproduce
Exact steps to reproduce the behavior.

  1. Run driver
  2. Perform AF Overscan move outward, e.g. from position 1000, set overscan=100 and move to 1050. The focuser should move first to 1150, when that completes, it should automatically move in to 1050.
  3. The bug is that Focus will receive a position counting down to 0 and then trigger an inward move from 0 to -100 which will fail.

Expected behavior
As per 2. above.

Screenshots
See this thread for info... https://indilib.org/forum/ekos/14209-problem-with-af-overscan-to-handle-focuser-backlash.html?start=0#98273

Desktop (please complete the following information):

  • OS:
  • Version [e.g. 1.7.6, GIT..etc]

Log Files
See this thread for more info... https://indilib.org/forum/ekos/14209-problem-with-af-overscan-to-handle-focuser-backlash.html?start=0#98273

@johneevans johneevans added the bug label Mar 15, 2024
@crfrancis
Copy link

Another observation with this driver is that when Autofocus fails and tries to move to its original position, the focuser actually moves to position 0, which is way out of the correct zone of about 50000, and from which it cannot recover. I don't know for sure, but is likely due to the same bug.

@knro
Copy link
Contributor

knro commented Mar 17, 2024

Thank you for the report. This is an issue in 3rd party repo, not INDI core. However, I believe I submitted a fix there. Please recompile and test again.

@knro knro closed this as completed Mar 17, 2024
@crfrancis
Copy link

crfrancis commented Mar 17, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants