The period seems too short to be periodic error. My guess is vibrations, possibly wind.
When setting the Telescope focal length on the Mount Tab, you must click on the Save Telescope Info button for it to be applied. Verify it is correct with expected FOV in the alignment tab. It should update the telescope info in the INDI driver at the same time, so save the INDI driver configuration for next time.
Simulators aren't particularly useful for testing the polar align assistant either because by default they don't have much, if any, error.
Do, take the time to get your real mount, camera and guide camera connected and working and try it with real stars. 90% of the time, failed solves have to do with missing indexes, incorrect telescope and camera information, wrong scope/camera combo selected, underexposed frames or bad focus. There are also different solver profile defaults, try them all to see which works best for your equipment.
Sometimes it helps to uncheck Use Scale in the options. This will be slower, but more reliable if your telescope info is inaccurate. Once it tells you what the focal length truly is, you can save the updated telescope info and re-enable Use Scale.
There is a mount control window built into KStars. Should be accessible form one of the toolbars.
I had recently contacted the Firecapture Devs regarding ARM 64 version of Fire Capture. This is the reply I received. JAVA does appear to be an issue they need to resolve.
*****@hotmail.com schrieb am 22.06.2021 23:56 (GMT +02:00): I am running an INDI setup on a Raspberry Pi running, 64 bit Raspberry OS. Can you release a ARM 64bit version for it? Thank you kindly.[/code/ [code]El 24 jun 2021, a las 23:07, email@example.com escribió: Andrew, I put Rafael on CC because we both can thank him for providing the RPi FC distro. AFAIK the reason here so far was finding a working Java 64bit JRE for the RPi. Rafael, please correct if I'm wrong. Regards, Torsten
Yes, this is one of the problems. Rafa
Restore these lines of code to prevent lockup of the motor on the first run after system boot
Line 91 DRV8825_SelectMotor(MOTOR1); Line 92 DRV8825_Stop();
Ok. New information. It wasn't that the profile didn't load. I've noticed it will always engage the motor regardless the first time the indi driver is started after rebooting the system.
It didn't used to do that.
I took care of the motor running hot on system start already with the pull-up resistor.
I believe the pull-up resistor is an overall better solution because it saves the motor even when the Pi is shutdown but still connected to power.
This time I believe it was when the focus driver started with the default configuration, which for me I noted was to engage to motor on the Revision 1 board. As seen here.
I didn't catch it this time because I assumed it was all saved and loaded correctly. But I do recall my preset positions were empty. So I'm quite certain that is what happened.
So, I guess I had an oopsie. Looks like the saved driver config did not load one time I had it powered on for other tests and the motor ran hot. Gonna have to reprint it's housing.
The default mode seems to be to set the pin Low. Which on the original board is the powered on state.
1. Step delay was reset to 0.
2. Save driver configuration at setting the new board revision option.
3. Motor is wired incorrectly/to wrong driver.
4. Burned out motor or controller if the coils were left powered due to revision changes.
Can you move the motor with Waveshare sample code?
I once discovered that overclocking the GPU interfered with my adafruit gps adapter.
If this is something you have done, I suggest undoing it in /boot/config.txt
All I do it make sure Polaris is close to center in the polar scope view then use the Polar Align Assistant with my guide scope to nail it.
Don't really need to worry about the illuminator at that point.
Not really a solution, but..
The brightness is stored on the HEQ5 mainboard. Once set by the hand controller, or presumably ASCOM EQMOD, forget about it.
EKOS is already able to recognize when an instance of the INDI server is still running after a KStars crash. We're given the option to stop and restart INDI or ignore it. Why not have an option to take back control of it?