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

Lacerta MFOC Driver Hangs Up When Relative Positioning #1834

Closed
timpeKH opened this issue Feb 2, 2023 · 5 comments
Closed

Lacerta MFOC Driver Hangs Up When Relative Positioning #1834

timpeKH opened this issue Feb 2, 2023 · 5 comments
Assignees

Comments

@timpeKH
Copy link

timpeKH commented Feb 2, 2023

When I issue a relative position command in the INDI Control Panel, the Lacerta MFOC reacts with a
strange and wrong absolute position (huge, unrealistic number). Further the MFOC stops any reaction and communication with the INDI-Client. No disconnect or re-connection is possible unless the Lacerta MFOC handbox is switched off and restarted.

Setup and Software Versions Used
I use a Lacerta MFOC with firmware version 3.03. The MFOC is connected via USB to a Raspberry Pi 4, 8GB running Ubuntu Server arm64, 22.04 LTS (Jammy) as a INDI-host. So the Rapsberry Pi is where the indiserver runs. As clients EKOS or CCDCiel were used on a Laptop under XUbuntu 22.04. LTS ( KSTARS version 3.6.2 Stable Build 2022-11-30T18:14:22Z)
The driver package used on the RPI4 which provided the Lacerta MFOC driver (AFAIK) was/is :
Package: libindi1
Version: 1.9.9+202211300913~ubuntu22.04.1

To Reproduce

  1. Connect Lacerta MFOC Handbox with firmware 3.03 via USB and power on
  2. Start indiserver and run driver the process for Lacerta MFOC: indi_lacerta_mfoc_focus along with a CCD simulator driver or any minimum configuration to use an indi client and the INDI Control Panel (My indiserver runs on a RPI4, 8GB with Ubuntu Server 22.04 LTS (Jammy).
  3. connect to indiserver via EKOS client (I connect via another Laptop to the RPI4) and start INDI Control Panel
  4. In the INDI Control Panel go to the tab for the "Lacerta MFOC" and there to the "Main Control" tab. Press "connect" to connect to the Lacerta MFOC.
  5. First set a "Absolute Position" value (e.g. 3000) and send the command by pressing the "set" button
  6. Next set a "Relative Position" value (e.g. 1000) and send the command by pressing the "set" button
  7. Check what happens to the feedback status value of "Absolute Position". In my case a huge integer number appears while the "Relative Position" command does not yield any focuser motion. Now the focuser should be completely non-reactive.
  8. Try to shut down the indiserver process
  9. Check if the Lacerta MFOC driver process "indi_lacerta_mfoc_focus" was stopped together with the indiserver. In my case this process keeps running until terminated by a kill signal.

If you could reproduce this issue you will probably need to switch off and on the Lacerta MFOC handbox before being able again to connect to the Lacerta MFOC from the INDI Control Panel.

Expected behavior
When executing step 7) the expected behaviour was that the focuser moves 1000 steps in the direction indicated by the "Direction" button. Assumed the absolute position is 3000 the focuser should move either to 2000 or 4000 steps.

Screenshots
see attachments
Screenshot_2023-01-31_22-24-53

Desktop (please complete the following information):
see above

Log Files
attached (from the RPI where the indiserver is running)

indi_lacerta_mfoc_focus_21-33-16.log

@timpeKH timpeKH added the bug label Feb 2, 2023
@pawel-soja
Copy link
Contributor

4294967295 is 0xFFFFFFFF - looks like "-1"

@timpeKH
Copy link
Author

timpeKH commented Feb 2, 2023

True, but that's not what I entered as relative position change. You can see the "-1" even in the log file. But I am not sure what it means. Could be an error return code from the MFOC(?) (which was then taken as an absolute position by the client?)

@chkettu
Copy link
Contributor

chkettu commented May 7, 2023

merge request opened - should be fixed with next release!

Copy link

This issue has been inactive for 60 days and is being marked as stale.

@github-actions github-actions bot added the Stale label Mar 30, 2024
Copy link

github-actions bot commented Apr 6, 2024

This issue has been closed due to inactivity.

@github-actions github-actions bot closed this as completed Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants