Hi everyone,
I’m facing an issue where SGP aborted my sequence due to a horizon limit, even though I’ve defined and activated a Custom Horizon that should have allowed the target.
Here’s what happened:
- My user profile includes a Custom Horizon, enabled under “Use a custom horizon”.
- The active profile is called Siersdorf, and it allows targets down to 10° altitude in the direction of the target.
- The Planning Tool shows the target (NGC 6888) well above the custom horizon at the scheduled time (13.6°).
- However, SGP aborted the sequence shortly before 1:00 AM on April 4th, 2025.
Relevant log excerpt:
[04/04/25 00:59:03.102][DEBUG][Sequence Thread][SQ;] Error slewing telescope: Cannot complete slew! The requested position RA: 20,20; DEC: 38,35 is currently at altitude 13,59. Horizon for this user profile is 22,00.
[04/04/25 00:59:03.195][DEBUG][Sequence Thread][SQ;] Aborting sequence: Slew to target failed
This strongly suggests that SGP did not use the custom horizon, but instead applied the default simple horizon limit of 22°, despite the custom settings.
What I’ve checked:
- The correct profile (Siersdorf) was selected and marked as default.
- “Use a custom horizon” was definitely enabled in the user profile.
- Planning Tool uses the correct custom horizon and shows the target above the limit.
- The slew failed during the actual sequence, not during planning.
My question:
Is this a known issue? Could there be a reason why the custom horizon was ignored during the actual sequence execution?
Any help would be greatly appreciated!
Thanks,
David
