Hi, thanks for the reply, I also figured that a reset of the alignment of the mount after flip may help, I have the flip in 45min, we will see now
Meanwhile I attach the log of that session, it seems to me that ekos sends the command slew but the mount won't do it for some reason.Hi, thanks for the reply, I also figured that a reset of the alignment of the mount after flip may help, I have the flip in 45min, we will see now
Meanwhile I attach the log of that session, it seems to me that ekos sends the command slew but the mount won't do it for some reason.
Hi all, my setup worked flawlessly for the last 3 months (remote observatory), but over the last 3 nights it had a disappointing behavior after the meridian flip: its slews across the meridian and then it loops into aligning without actually re-centering the target.
Apparently this happens only with high altitude targets but I did not set any mount limits in Ekos.
At first I believed in a mechanical issue of the HEQ5 mount (some backlash or telescope hitting a tripod leg), but I physically went to inspect the setup and this is not the case.
When the issue happens, Kstars/Ekos correctly show where the scope is pointing in the sky, plate solving works and the target object is set, therefore Ekos correctly calculates the alignment error.
Kstars shows the marker where the scope is pointing and this matches the plate solve rectangle.
When Ekos tries to "slew to target" due to error accuracy not met, scope does not move, nor expected scope position marker moves in Kstars.
This behavior seems to lead into a software problem rather than electrical or mechanical (I would see the scope position moving in Kstars then).
Do you have any idea where to look into finding the problem?
I just upgraded to SM 1.6 and I have issues using python scripts both in Capture module and Dome Scripting Gateway module.
I use these scripts to operate a DIY servo actuated flat-cap straight from RPI GPIO pins.
Servocap motor is controlled with gpiozero, EL panel for flats with RPi.GPIO.
All the scripts work perfectly if launched in Shell, and used to work just fine with previous SM 1.5.
I tried all troubleshooting I could imagine but I am stuck and I would be really grateful if someone could help, thanks!
Hi Jasem, you just nailed the problem, all scripts now run just fine in ekos, thanks a lot!
sudo systemctl stop pigpiod did not change the behaviour:
- script runs ok from shell with "python3 script.py" (both as stellarmate and root)
- same script fails in capture/scheduler/dome module with error message in INDI Control Panel messages box
I agree that it seems a permission issue but I do not understand why this is happening only though ekos
I just tried, both commands return this error:
v3d fec00000.v3d: MMU error from client L2T (0) at 0x5621000, pte invalid
Yes, gpiozero is installed in its latest version 1.6.2-1
Sorry Jasem, it was just a typo, I already use "python3 open.py" command
Hi Jasem and thanks for the reply,
I use very simple scripts to open/close the cap of the telescope and turning on/off the flat EL light, I attach the code for opening the cap (please unzip as I cannot enclose .py files).
This code is running without issues if I launch from shell with command "python2 open.py" therefore I don't think I miss packages to install...
Thanks for your help!
I just updated to SM 1.6 and I have issues with python scripts running raspberry GPIO pins.
I use gpiozero to move a DIY servo dust cap and rpi.gpio to operate an EL panel with PWM commands for flats.
These scripts work just fine if launched in shell and until SM 1.5 also worked in Scheduler, Capture and Dome Scripting modules.
I tried all I could to thoubleshoot this issue, I hope that someone may halp figuring out what it might be... thanks!