Note: groups.io will be down for maintenance on Wednesday, October 5th, starting at 9AM Pacific Time (4PM Wednesday October 5, 2022 UTC), for approximately one hour.
How is the mount being initialized? Is the keypad connected, perhaps?
If the keypad or another program has already unparked the mount, then
the ASCOM driver simply establishes communication with the mount. It
does not unpark a mount a second time that is already unparked.
Therefore, if you connect to an initialized mount, the option to enable
tracking or not is moot. Hope this helps!
Mag. 7 skies!
From: ap-gto@... [mailto:ap-gto@...] On Behalf
Of Ray Gralak
Sent: Tuesday, June 22, 2010 4:46 PM
Subject: RE: [ap-gto] Mount tracking on unpark
which I did, but on clicking OK I got the message 'One or more valuesare out of range, Please correct and click 'ok'
again.' I have
very closely looked at each parameter I have entered and they are allcorrect.
The out of range value should be highlighted. Click the "Advanced"
button in the setup dialog and check all parameters.
I have been using ASCOM V2 driver V5.99.58 and have had the problem ofthe mount tracking after I connect to ASCOM V2
ACP. I have unchecked 'Enable Mount Tracking on Unpark.' To keep thescope from hitting the mount while ACP waits for
time I have been setting the drive rate to stop or manually slewingthe mount to a safe position.
In my opinion it is the responsibility of every client application to
explicitly turn off scope tracking if that is the
desired state since I believe there are other drivers that automatically
track when connected.
V5.0.0 stops tracking when the mount gets *initialized* from park.
However, if the mount has already been initialized
and tracking then connecting with ACP (or any ASCOM client) will not
automatically stop tracking. I think that ACP
should at least try to turn off tracking.
In fact I did so some experiments with ACP over the weekend and it
looked like tracking was correctly turned off after I
unparked. That said, I'm not familiar enough with ACP to discuss with
you differences in settings that might have caused
your scenario. So, if v5.0.0 doesn't stop tracking for you I suggest you
post a question to the ACP forum. If Bob Denny
confirms the driver is doing something wrong I will definitely take a