Hello,
I saw that Rodolphe had committed items a few days ago and today I cloned from Git and want to report back. Both PDMRotator.ino and PDMShutter.ino compiled cleanly and upload fine. The usual stuff to get shutter working after a power off.. open a little with rocker then close with switch til it stops. On first connect to POTH after that shutter showed as Unknown. Just clicked Close and all was then well.
So far as I can tell everything if fine function wise. From ACP issuing a Home homes the dome but exactly as before leaves a lingering slew which must be stopped from ACP's control button. Failure to do this and then asking for another slew results in the Rotator having to be power-cycled to function again. I suspect something in the ASCOM driver side here. I do have workarounds in my ACP startup/shutdown/weather scripts which keep everything happy. There remains something funky in Dome.FindHome and reporting of athome. No different than before.
I also noticed that from POTH using setup rotator shows as version 2.0.0 and shutter version is blank. Also!! Now in Rotator settings the dome calibration numbers are what was in the new ino not my values. Doing a home then calibrate proceeds normally but values are not updated. Not a problem as my numbers were only 30 steps different than what is there now.
Also in POTH setup shutter both speed and accel are 0. Set does nothing.
So it does appear that the latest Git commit has ASCOM driver and the firmware slightly out of sync. I have no ill effects functionally myself but felt it important to report.
I have slewed/slaved all over the sky and run weather safety and shutdown/startup scripts mimicking an observing run and all has been fine. So my report is that all is OK with a bit of out of sync with ASCOM driver. I do not know how to compile ASCOM so will need to rely on installers as they update.
Thanks everyone for the hard work!!
Ron
Hello All,
I agree with Rodolphe! The offsets of the OTA must be entered into whatever ASCOM client is being used to slave the mount and dome. Since the scope is large they can be significant! If the dome is slaving with the mount it is not a driver issue. Geometry must be set so the scope/mount being used.
So look at your client program which ties the mount to dome. Somewhere there will be an entry..I do not use POTH for actual imaging (ACP).. But the values you see here are the same for both POTH or ACP..
If I misset any of these I see a shutter not centered on scope. When correct all is perfect. These are the values for my 8" Newt on an AP Mach1 centered in the dome.