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

Onstep controller Indi issue #1928

Closed
1crem1 opened this issue Aug 27, 2023 · 2 comments
Closed

Onstep controller Indi issue #1928

1crem1 opened this issue Aug 27, 2023 · 2 comments
Assignees
Labels

Comments

@1crem1
Copy link

1crem1 commented Aug 27, 2023

Hello
I am currently trying to use an off the shelf Onstep controller with Kstars. I am using the LX200 OnStep driver. I can connect however once initialisation occurs I receive a repeated warning on the Indi driver control panel (in orange):

Date/time: [WARNING] Communication: Ft# error, check connection.
Date/time: [WARNING] Invalid response, check connection.

This error message repeats every second in the Indi driver control panel, however the mount appears to respond to commands using the mount control feature in the mount section of Ekos.
I haven’t yet used it in the field.

I’m not sure how to progress. The ‘connection’ tab reveals nothing that I can detect.

Thanks
Andrew

@1crem1 1crem1 added the bug label Aug 27, 2023
@azwing
Copy link
Contributor

azwing commented Aug 29, 2023

Hi,

can se continue this discussion on the OnStep Forum
https://www.indilib.org/forum/development/1406-driver-onstep-lx200-like-for-indi.html
It will be easier to manage.
At least would be helpfull to have:

  • Onstep Firmware Version
  • Indi logs
  • at a first glance the Ft# error could be related to Focuser.

@azwing
Copy link
Contributor

azwing commented Sep 11, 2023

After analysis of the issue it is clearly a firmware issue and not a driver bug.
The error messages clearly are triggered when the firmware doesn't answer to the request (in this case the Focuser Temperature).
Normal firmware behavior is to reply either with the real value or by default with 10.0# so that no error messages are issue by the driver.

I consider this issue as closed

@knro knro closed this as completed Sep 12, 2023
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