Howdy!
I went to troubleshoot my logs this morning and I was pleasantly surprised to see a patch being offered for "meridian flip" issues. I've installed your beta and I'll take it for a ride tonight.
For clarity's sake, here is the precise issue that has been manifesting for me the past several nights. Let's first observe the logs for a successful night of imaging M16 in hydrogen.
2025/06/25 23:36:04 [AutoFocus|End] Auto focus succeeded
2025/06/25 23:36:05 [Guide] ReSelect Guide star
2025/06/25 23:36:06 [Guide] Start Guiding
2025/06/25 23:36:08 [Guide] Guide Settle
2025/06/25 23:36:10 [Guide] Settle Done
// ...successful exposures...
2025/06/26 00:33:32 Stop Tracking
2025/06/26 00:33:33 [Meridian Flip|Begin] Wait 12min48s to Meridian Flip
2025/06/26 00:46:21 Meridian Flip 1# Start
I began imaging at 11:30pm and the merdian flip was executed at 12:30am.
Now let us observe a failed night attempting to capture LRGB stars in M16.
2025/06/28 23:33:14 [AutoFocus|End] Auto focus succeeded
2025/06/28 23:33:17 [Guide] ReSelect Guide star
2025/06/28 23:33:18 [Guide] Start Guiding
2025/06/28 23:33:19 [Guide] Guide Settle
2025/06/28 23:33:21 [Guide] Settle Done
// ...successful exposures...
2025/06/28 23:35:40 Stop Tracking
2025/06/28 23:35:40 [Meridian Flip|Begin] Wait 0s to Meridian Flip
2025/06/28 23:35:40 Meridian Flip 1# Start
// It then enters into a loop of attempting recentering until it bails out on the plan
2025/06/28 23:38:10 [AutoCenter|Begin] Auto-Center 1#
2025/06/28 23:38:10 Mount slews to target position: RA:18h20m11s DEC:-13°47'11"
2025/06/28 23:38:11 Exposure 5.0s
2025/06/28 23:38:17 Plate Solve
2025/06/28 23:38:26 Solve succeeded: RA:18h20m11s DEC:-13°47'16" Angle = 174.629, Star number = 4312
2025/06/28 23:38:26 Pierside is wrong
2025/06/28 23:38:26 [AutoCenter|End] The target is centered`
It began the meridian flip an hour before it was suppose to. I can also confirm this via Stellarium.
I presume that what "Pierside is wrong" is saying here is...
Hey. I did the meridifian flip and I'm dead center on the target, but I landed in the same spot where I started. There's no way that's right.
I will add some gratitude to this thread.
You folks are taking a lot of heat for this buggy release. Because it is a buggy release. However, I am a software engineer myself and I can say that I have worked with too many developers that would have let the above scenario spiral out of control and destroy thousands of dollars worth of equipment. The fact that it deteced this bizarre fault and behaved appropriately is not lost on me.
You folks likely won't remember this release fondly. Although, I am quite appreciative of the defensive programming that your developers practiced in order to keep our equipment safe while we sleep.