I am getting Pluseguiding command has failed
36 views
Skip to first unread message
Keith Jones
Jan 12, 2022, 3:26:14 PM1/12/22
to Open PHD Guiding
almcl
Jan 12, 2022, 3:50:08 PM1/12/22
to Open PHD Guiding
You cannot calibrate at Dec 90°.
Try calibrating close to Dec 0° and see if that improves things.
On Wednesday, January 12, 2022 at 8:26:14 PM UTC keithandm...@gmail.com wrote:
https://openphdguiding.org/logs/dl/PHD2_logs_knpw.zipAny ideas.
Keith Jones
Jan 13, 2022, 2:48:25 AM1/13/22
to open-phd...@googlegroups.com
OK thank you. I will give it ago.
Regards Keith
On Wed, 12 Jan 2022, 20:26 Keith Jones, <keithandm...@gmail.com> wrote:
https://openphdguiding.org/logs/dl/PHD2_logs_knpw.zipAny ideas.--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/be306d30-1fee-44ee-96f9-8f7a55d95416n%40googlegroups.com.
Brian Valente
Jan 13, 2022, 9:17:10 AM1/13/22
to Open PHD Guiding
Hi Keith
Sounds like a communications problem with your mount. It could be in the ascom driver, but just as often it's a bad cable or physical connection. you might try ensuring you have the latest drivers and doublecheck/replace cabling
see the troubleshooting guide,
the specific passage here:
ASCOM Alerts
When you first connect to a mount, camera, or other ASCOM-controlled device, you may see an alert message saying that a required capability is not supported by the driver. One example would be lack of support for pulse-guiding by an ASCOM telescope/mount driver, something that can occur with outdated drivers. In these situations, your only recourse is to update the ASCOM driver. These drivers are generally available from the ASCOM web site or, in some cases, from the device manufacturer. As a rule, the best practice is to use the latest versions of these drivers so you don't encounter problems that have already been fixed.
You might also see other alert messages associated with the ASCOM driver for the mount:
When you first connect to a mount, camera, or other ASCOM-controlled device, you may see an alert message saying that a required capability is not supported by the driver. One example would be lack of support for pulse-guiding by an ASCOM telescope/mount driver, something that can occur with outdated drivers. In these situations, your only recourse is to update the ASCOM driver. These drivers are generally available from the ASCOM web site or, in some cases, from the device manufacturer. As a rule, the best practice is to use the latest versions of these drivers so you don't encounter problems that have already been fixed.
You might also see other alert messages associated with the ASCOM driver for the mount:
1. "PulseGuide command to mount has failed - guiding is likely to be ineffective." This is usually caused by a bug or timing sensitivity in the ASCOM mount driver, and there is generally no way to know if the guide command was executed properly or not. If you rarely see the alert and your guiding results are acceptable, you can probably ignore it. Despite the alert condition, PHD2 will continue to issue guide commands, so you don't need to take any immediate action. If you see the alert frequently, you should send us your debug log so we can understand the details of the problem and possibly help you describe it to the author of the ASCOM driver.
2. "Guiding stopped: the scope started slewing." This is pretty self-explanatory, but the determination that the scope was slewing is something reported to PHD2 by the ASCOM mount driver. Whether it was actually slewing isn't known to PHD2. Assuming you didn't mistakenly slew the scope with guiding active, there is probably a timing problem in the driver. If you want to sidestep the problem temporarily, you can disable the logic to check for slewing - go into the 'Guiding' tab of the Advanced Settings dialog, and un-check the box that says "Stop guiding when mount slews." This will let you continue guiding, but the results might be suspect. The debug log should provide the details needed to describe the problem to the author of the ASCOM driver.
2. "Guiding stopped: the scope started slewing." This is pretty self-explanatory, but the determination that the scope was slewing is something reported to PHD2 by the ASCOM mount driver. Whether it was actually slewing isn't known to PHD2. Assuming you didn't mistakenly slew the scope with guiding active, there is probably a timing problem in the driver. If you want to sidestep the problem temporarily, you can disable the logic to check for slewing - go into the 'Guiding' tab of the Advanced Settings dialog, and un-check the box that says "Stop guiding when mount slews." This will let you continue guiding, but the results might be suspect. The debug log should provide the details needed to describe the problem to the author of the ASCOM driver.
On Wed, Jan 12, 2022 at 12:26 PM Keith Jones <keithandm...@gmail.com> wrote:
https://openphdguiding.org/logs/dl/PHD2_logs_knpw.zipAny ideas.--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/be306d30-1fee-44ee-96f9-8f7a55d95416n%40googlegroups.com.
Keith Jones
Jan 13, 2022, 9:31:00 AM1/13/22
to open-phd...@googlegroups.com
Thank you I will try updating the drivers and make sure I have the latest PHD
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i7MKVHOwaHvqYsfMu_pHafjK4uQet6DdmuA-dHP%2BUWNmA%40mail.gmail.com.
bw_msgboard
Jan 13, 2022, 11:16:29 AM1/13/22
to open-phd...@googlegroups.com
Your mount was parked or in the process of parking when these
errors occurred. Obviously, that isn't going to work. I think you
probably need to work through the basics of working with your mount before you
try auto-guiding. It usually works best to have a specific routine for
getting started, then follow that routine consistently every night, always the
same way.
Regards,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Keith Jones
Sent: Wednesday, January 12, 2022 12:26 PM
To: Open PHD Guiding
Subject: [open-phd-guiding] I am getting Pluseguiding command has failed
Keith Jones
Jan 13, 2022, 11:29:21 AM1/13/22
to open-phd...@googlegroups.com
Cheers for the info.
Regards Keith
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/82676759B32D4F0B8C77D01BE0E7944A%40HomeDesktop.
Keith Jones
Jan 13, 2022, 4:08:11 PM1/13/22
to open-phd...@googlegroups.com
Thank you every one for your help. After an Ascom Update and repeated calibrations looking in different directions PHD sorted itself out and is now guiding. Yay.
Reply all
Reply to author
Forward
0 new messages