You’ll have to forgive the regional inaccuracy, but the error here not -15,6 (-15.6), but rather -15642,1 (15642.1) pixels in RA. The reason appears to be that the mount is failing to converge to diminish the error (because SGPro is unable to sync with the mount to tell it its actual pointing position). When we attempt to sync we get:
[04.12.2016 21:01:32] [DEBUG] [Telescope Thread] ASCOM Telescope: Invalid Operation Exception in Sync : Sync matching failed. (System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. —> System.Runtime.InteropServices.COMException: Sync matching failed.
An interesting observation is that the request to sync with your mount does not always fail.
Anyhow, not 100% sure this is the root cause but I can say the mount is not going where SGPro asks it to go:
- Reference frame solved at center:
[04.12.2016 21:00:40] [DEBUG] [Telescope Thread] Astrometry.NET - RA: 4,05244682633333
[04.12.2016 21:00:40] [DEBUG] [Telescope Thread] Astrometry.NET - DEC: 36,391966524
- SGPro requests slew to this location:
[04.12.2016 21:00:41] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 4,03331761463556 (04h01m59,94s) Dec: 36,3433304996433 (36°20’35,99")
- Verify the position the scope ended up at:
[04.12.2016 21:01:32] [DEBUG] [Telescope Thread] Astrometry.NET - RA: 5,0356676794
[04.12.2016 21:01:32] [DEBUG] [Telescope Thread] Astrometry.NET - DEC: 36,367546221
About 15 degrees from where SGPro requested. We’d really need to see the mount’s logs to correlate what is going on here.