Re: Pier Crash - need help diagnosing #ASCOM_V2_Driver
toggle quoted messageShow quoted text
It appears that the scope tracked past the meridian and continued until it was past the west side upside down. Apparently you do not have the limits turned on, so there is nothing that would stop the mount from continuing on its way.
Since the scope is now underneath the mount, I strongly suggest that you return the RA axis by either slewing or manually (clutches loose) bring the RA axis back, in counterclockwise rotation, to counterweight down position. Place the scope in Park3 and re-start the mount from Park3.
If you continue to rotate the RA axis clockwise, you will most likely twist the internal motor-encoder cables, which will eventually damage them if you allow the mount to rotate clockwise past the lowest point again and again.
I strongly urge you to NOT turn off the internal limits so that the mount cannot continue past the meridian indefinitely, especially if you are not there to catch the problem.
From: Joel Short <buckeyestargazer@...>
Sent: Tue, Oct 6, 2020 1:11 pm
Subject: [ap-gto] Pier Crash - need help diagnosing #ASCOM_V2_Driver
I have an AP1100GTO CP4 and use the ASCOM driver for mount control, with SGP and PHD2. Last night I had a pier crash and it is really puzzling as to what happened and I could use some help figuring it out. The guide star was lost around 11:10pm and for some reason SGP recovery didn’t work properly. The really strange thing is that the scope was on the EAST side of the pier pointing down at the ground, but pointing on the west side of the pier. If the scope was tracking properly it would have just continued moving west, so something strange happened to to cause the scope to crash into the EAST side of the pier. Another strange thing is that the AP1100 ASCOM driver reported that the scope was parked this morning.
I also have Mount Watcher activated to shut down the mount if it gets too far past the meridian or too far CW up. That failed as well. I really have no clue what caused this. Here is a link to the ASCOM_V2_Driver log. Any ideas as to what happened would be appreciated.