Problem with SYNC / MOVE during autocentering
Posted: Fri Aug 23, 2024 10:03 pm
Hi Robin,
tonight I wanted to test my sequence for automatic centering in 3 steps (using Altair as an example) for the first time...
Up to a certain point everything works perfectly, with each step the centering becomes more precise, but after the last plate solving in step 3 (where the position of the mount is apparently also correctly recognized) it suddenly slewes with high speed to a completely absurd position that was not saved at all.
When browsing through the SharpCap log, it is noticeable that in the last centering-step the mount-position before the SYNC with R.A. 19:50:47.2 / DEC +08:49:40 (time: 22:19:57.439495 & 22:19:57.450512) still seems to be correct, but after the SYNC the position suddenly changes to R.A. 19:27:18 / DEC +12:17:11 (time: 22:19:58.027560 & 22:19:58.038598).
So it's no wonder that such a large correction movement suddenly takes place at the end!
However, I can't explain this sudden deviation! According to the protocol, the SYNC is still working with the correct coordinates!
Did I forget something in the sequence or program it incorrectly?
StarFlea
tonight I wanted to test my sequence for automatic centering in 3 steps (using Altair as an example) for the first time...
Up to a certain point everything works perfectly, with each step the centering becomes more precise, but after the last plate solving in step 3 (where the position of the mount is apparently also correctly recognized) it suddenly slewes with high speed to a completely absurd position that was not saved at all.
When browsing through the SharpCap log, it is noticeable that in the last centering-step the mount-position before the SYNC with R.A. 19:50:47.2 / DEC +08:49:40 (time: 22:19:57.439495 & 22:19:57.450512) still seems to be correct, but after the SYNC the position suddenly changes to R.A. 19:27:18 / DEC +12:17:11 (time: 22:19:58.027560 & 22:19:58.038598).
So it's no wonder that such a large correction movement suddenly takes place at the end!
However, I can't explain this sudden deviation! According to the protocol, the SYNC is still working with the correct coordinates!
Did I forget something in the sequence or program it incorrectly?
StarFlea