Hi Saan, I’m sorry you’re having all this trouble. But this is really a mess, it looks to me like the mount isn’t behaving correctly at all – it certainly isn’t a PHD2 issue. To start, the pointing info indicates you’re doing calibrations at an hour angle of -7.3 hours, which would mean you’re probably pointing below the horizon. I really doubt that was the case – roughly where was the scope pointing relative to the east or west horizon? Is it possible the mount hasn’t been correctly initialized? Next, you have very different guide speed settings for RA and Dec. Perhaps in your experiments with the guide speed, you were changing only the RA axis. That’s not a good idea. I think you should go back to the very basics at this point:
1. Make sure the mount is correctly initialized and knows where it’s pointing. Point the telescope at your typical Dec=20 position and within 10 degrees of the celestial meridian – you want the scope pointing at least 60 degrees above the east or west horizon.
2. Make sure it’s tracking at the sidereal rate
3. Re-apply all the EQASCOM settings discussed in this document: https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings. Having taken this scorched Earth approach to trouble-shooting, you will now have to manually check every single setting in every single app – you can’t assume that anything you set in the past will still have the correct value.
4. Set the EQASCOM guide speed settings to the same values for both axes – try 0.75x for now.
5. Connect to the mount with PHD2 and start looping with 2-sec exposures. Use the Manual Guide tool in PHD2 to move the mount in all 4 directions sequentially. Use a manual pulse size of 1200 or 1500ms and issue 7-10 pulses sequentially in each direction. Watch the PHD2 image display and see if the stars in the field move in all 4 directions. In your calibrations, the movement was apparently only in one axis.
6. If you can see the stars moving in all 4 directions, let PHD2 try to do a calibration.
If you can’t get through these steps successfully, you will probably have to discuss the problem on an EQ-specific forum or with the mount vendor. FWIW, I wish you had asked about this when you first saw the problem so we could have advised you to not start tearing apart the software configuration on your computer. At this point, once the mount is working correctly, it may take you some time and effort to get everything put back together.
Good luck,
Bruce
--
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/8a5d63da-6d43-4ca9-be76-6e1ab5542587%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd...@googlegroups.com.
I had realised part way through launching PHD2 that the date and time was way off on my laptop and consequently changed it in the windows settings. Could that have led to the hour angle of -7.3 hours?
When you say make sure the mount is initialized do you mean that it is parked in home and knows what the home position is?
How do I make sure its tracking at sidereal rate and what does this mean?
Yes, that calibration looks fine to me. Generally, if you don’t see an alert message in calibration, you should be good to go.
Good luck,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Shaan Ahmed
Sent: Thursday, October 10, 2019 5:40 PM
To: Open PHD Guiding <open-phd...@googlegroups.com>
--
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/a646c890-e270-43ab-b68e-b333c47f5b8b%40googlegroups.com.