Hi Mike. I think you’ve pretty much figured this out for yourself. The old Meade ASCOM drivers don’t behave like ASCOM hubs, which means only one app at a time can connect to them. But that’s exactly the problem that POTH was written to handle, so you can use that. You can run the POTH app manually, go into Setup, then choose the Meade mount driver. Make sure the COM port is correctly identified in the Meade ASCOM driver. If you don’t have a serial port on the computer, you can use a USB-serial adapter. Once POTH is connected and is able to report the pointing position, you are good to go. In PHD2, you can choose the POTH driver as your aux-mount. Once you go through this drill once, you should be done with it – all the settings will be remembered.
Hope this helps,
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.
For more options, visit https://groups.google.com/d/optout.
Hi Mike. Any application you want to use – SGP, PHD2, whatever – should connect to POTH. None of them should connect directly to the Meade ASCOM driver, that will be done only by POTH. POTH makes sure there aren’t collisions between commands that go to the mount. I suspect that the Meade mounts have to be initialized and not in a parked or home state in order to correctly report pointing position. Your best bet is probably to find a routine that works with getting the mount initialized and then having the apps connect to it at the right time. Once you get that roadmap, always follow it. If you starting changing the order of things or get sloppy with the routine, you could end up getting error messages and problems that won’t make much sense to you.
Good luck,
Thanks for the contribution, Manning. I think the best advice usually comes from someone who has dealt with the same set-up and found a way to make it work. J
Bruce