Hi Ken,
The PRA and PDEC values show the Physical Step counting in the respective axes. Their upper limit is the amount of steps for a complete circle. You can watch these values changing in the Status web page, as well as the Safety Limits, the GoTo target positions and so on. These steps are counted by the ARM processor as well as by the servo PIC processors.
At a Cold Start, both PRA and PDEC are set to half circle values. With a scenario where you start the mount in 4x precision and then change the stepping to 1x you can easily raise this "Out of range" error condition, since in 1x mode the maximum amount of steps is only one quarter compared to 4x mode. This is the reason that you have to power off/on and do Cold Start the mount after changing important setup values like mount type or gearing or change the hemisphere. This is essential to proper operation.?
¸é±ð²Ô¨¦
Am 16.01.25 um 19:32 schrieb Oberon510 via groups.io:
Hi,
?
Last night I was trying to park the mount and I kept getting "PDEC out of range" errors popping up from the ASCOM Gemini driver. The mount wouldn't park so I turned it off and will level it today.
?
Any thoughts on this error as I have not seen it before and I only saw one other reference in a groups.io thread. I have the latest firmware and ASCOM driver (GeminiTelescope) installed?
?
As I have recently had some issues that I ended up thinking was a lan cable, I am kinda guessing this may be related to a faulty DEC cable or connection.
?
Any triage thoughts appreciated.
?
Ken
?
