aliljenb wrote: I'm new to Ekos and last night I spent at least 2 hours trying to get the internal guiding to work.
Whatever I did I got "cannot reach guidestar after 21 iterations..."
Finally I tried to rotate the guidecam about 90 degrees and suddenly it worked!
Should it really matter how the cam is oriented?
Guide cam: ASI 120MM-S
Guide scope: ASI60280sc using ST-4 connected to the mount (also tried through EQMount directly with same result)
Mount: HEQ5 Pro
Bart wrote: It shouldn't matter.
I've heard many people complain about the internal guider now, including myself and a colleague of me, also a tech-savvy guy.
except for a few cases where it works as intended. Best is to use PHD2, the interaction between Ekos and Phd2 is good.
starman99 wrote: OK, so I updated Indi last night and now it seems to be connecting fine again. So it probably was a mixed version or corrupted file like PDB suggested. I will double check the firmware version, but I'm pretty sure I did update to 1.4 already. Maybe this was a symptom of a corrupted file also. Big thanks to you guys for helping!
starman99 wrote: Sorry - I forgot to mention that one possibility is that I changed the variable voltage setting to '8.2' instead of '8' in the Indi driver. Looking at the windows UPB utility, it appears that it only can accept whole integers 1-12 (volts) - maybe related?
You haven’t even said if you polar aligned the scope properly first...? As if you just stuck on the ripped and fired up then that will be your issue....
Yes, it should not say encoder really, maybe RA and DEC position, as that is very confusing, although it would be fine for my mount, with the encoders....and that’s what it was written for...so hmmmm
xthestreams wrote: Yup - let's hope it gets resolved - I had a situation just tonight where I needed to home the mount and was wishing the feature worked.
For some reason the software looks for the encoders before it will autohome, even though it does not actually need them for the autohome function, so as they are not there, it throws the error....very strange....will look into it...