I have had this happen on occasion, and have been able to work around it by changing the pulse parameters. I have a setting now that seems to calibrate every time. Try increasing the max pulse if you get the error again.
Not sure if, and how to retrieve the Ekos log. I tried the link that leads to the tutorial, but cannot start the video (looks like some sort of format issue).
Maybe I have to wait for the next clear sky-evening (wheather forcast is not promising). Was actually wondering if an astro planetarium toy would be useful for testing indoor?
Just to follow up on the problem with the internal guider aborting after 30 attempts: I had a chance to try again, but shame on me, I failed creating a log file, just the screenshot from the client with the log entries. There (see attached screenshot), an error was reported, i.e. failed transform telescope to celestial. I do not really know what it means, but possibly the cause?
Wheather forcast is not very promising, so I was wondering if the debugging data captured in the screenshot already helps finding detecting root-cause?
Yesterday all fine, tonight the internal guider did not work out, during RA drifting reverse phase, stopping after thirty iterations.
Then I tried to create a log file, now I cannot find it. I am using my laptop as a client, and the servers are hosted on the RPi.
It seems the log would be saved on the RPi. Is there a way to save it on the laptop? If I hit the „show indi logs“ button, nothing happens.
In the profile tracking window it says it is stored in the path home/astroberry/.indi/logs... but does not exist (?) - has the „.“ ahead of „indi“any meaning?
Although I know that finding the error requires the log files, would be great if someone could have a look at my screenshot to see if there is an obvious error.
Update your RPI3 to latest libindi. Change EQMod guide rate to 0.5 instead of 0.3 (I made 0.5 the default now). Increase pulse width to 1500ms or 2000ms. Make sure you have good polar alignment. Download latest KStars 2.8.4 (Just released few minutes ago).
Would you have any idea on the log file? Can I influence that path from the windows laptop-client? Hitting the log button does not trigger anything - or is this addressed with the latest KStars update you mentioned?
Perhaps these two scripts can help gather the logs up on RPI3/Ubuntu. They are not pretty; I am not good at bash, or command line.
pkg_logs.sh - will put all the logs into a zip file
sudo zip -r ./`date +"%Y%m%d"`_kstar_ekos_logs.zip ~/.local/share/kstars/logs /root/.indi/logs ~/.indi/logs ~/PHD2
renew_logs.sh - will remove the logs, which you may wish to do to isolate reproducing something,
sudo rm -rf /root/.indi/logs
sudo rm -rf ~/.local/share/kstars/logs
sudo rm -rf ~/.indi/logs
sudo rm -rf ~/tmp/logs
sudo rm -rf ~/PHD2
I have been looking to run these are startup and shutdown scripts, and just have not got there yet.