Re: Pier Crash - need help diagnosing #ASCOM_V2_Driver
toggle quoted messageShow quoted text
You can simply verify it by manually slewing the mount in RA to the counterweight up position (past meridian). At 5 degrees past the meridian the mount will stop responding to a west button move, bounce back a small amount and park itself. You will not be able to move it further west, either by button move or tracking.
If you have the keypad, you can move it back east via the buttons, and once it is back in the counterweight down position it will automatically start tracking again. You can also move it out of the limits by simply issuing any object move command from the keypad objects list. The keypad also now has a flip command that allows you to flip to the other side and acquire the same object again. The keypad will automatically unpark the mount either way and the mount will then slew to the correct side with counterweight up. The only thing you cannot do is to move it via the buttons further past the limit.
If you use an external planetarium program to control the mount, you will first need to unpark the mount. SkyX will prompt you to unpark before it lets you slew the mount to another object. Other programs may need to re-start the mount.
From: Jeffc <jeffcrilly@...>
Sent: Mon, Oct 26, 2020 11:31 am
Subject: Re: [ap-gto] Pier Crash - need help diagnosing #ASCOM_V2_Driver
> On Oct 26, 2020, at 8:54 AM, uncarollo2 <chris1011@...> via groups.io <firstname.lastname@example.org> wrote:
> So, if you have your whits about you and are certain that the mount is set up correctly,
For the non-encoder mounts, could this command have a “manual verify” feature?
Eg after mount startup a slew is done and if it stops then the user knows the command is setup properly. If it doesn’t stop then the user can stop it.
But yes.. I can also see where even this “verify” seems like an opportunity for lots of support calls/emails.