lukepower

Hi Bill, during a test run of Scheduler last night I had the exact same issue you described. Did the workaround work for you? This is quite an annoying thing...

Interesting... I wonder if this new version is supposed to automate itself the image acquisition (at least from the screenshot, it looks somewhat like an imaging plan for the whole night), or if it integrates in solutions like ACP (which I personally would prefer)...

Hi Gerald, this looks very good, I think I'll get one and see how it works. Thanks! Lukas

Hallo Michael, I also have a networked camera for visual check, but this is not a solution for an unattended setup. On the other side, up to now Autoslew always ran without problems.

Hi there, I am wondering if somebody has found a good solution to check if the mount (in my case a DDM85XL) is parked without software. I could attach a reed contact (or similar) to my dome controller so that I could have a backup roof-closure-system in case ACP goes gaga. I was considering one of those ultrasound distance sensors from Sharp, I guess that - if mounted at the right distance - they would set their output to logical 1, which in turn would trigger the input to my controller. Any experience on this? Lukas

Alright, for the records, I found the setting I wanted It's under "Control" -> "Misc settings". "Power motors on when Autoslew starts" is indeed quite obvious

As I am in the process of getting ACP (and its Scheduler) to work fully automatic and remotely, I was wondering if there is a (good) way to power up the motors when Autoslew starts. I can see that there is a setting to let the mount perform an Auto-Home when unparked (which is not bad, in this sense), but is there a way to tell Autoslew to start up the motors right away? My plan would be the following: Give power to mount and camera (works) Let ACP connect to the mount and camera (works) Autoslew starts, should power on its motors, but DO NOT do a homefind (as the roof is still closed (not working) As soon as the weather permits, let the roof open and unpark the scope (will result in an auto-home, works) When the observatory shuts down, it would also be great to find a way to close Autoslew before taking away the power. When ACP disconnects from Autoslew, it still stays active (which is usually cool). I could kill it, but then it complains on the next start that it has been shut down improperly Maybe there could be an option to shut down Autoslew when the number of connected ASCOM-Clients reaches zero (?). Alternatively, it should accept the fact that I could take away power for a longer period of time (without complaining with plenty of USB errors ). Thanks for your ideas Lukas