Hi Bob,
Backyard Observatories roll-off with Elk m1OASYS. I can currently control the roof using the M1toGo desktop app and eKeypad Pro app for iOS. Should ACP's dome control button enable after configuring ACP's preferences, dome control? I have the latest ASCOM and m1 ASCOM driver from Backyard Observatories installed, and have programmed the m1's tasks. Screen capture attached. Can you please point me to what I should check next? Thank you sir.
Well, a "duh" moment occurred - in ACP the telescope must be connected for the Dome Control button to enable, which it did once ACP launched SkyX. This leads to my next question. SkyX is showing tracking off once ACP launches it. The roll-off will not open when selected in ACP Dome Control. It reports "scope is unsafe". The scope is still in its park position. The park sensors are operational; if I slew the scope out of position, the Elk M1toGo app will not allow the roof to move.
Hi Vance, I'm just another ACP customer.
Is this a new setup or one that has been working for a while?
ACP normally leaves the tracking OFF until the scope has a task to perform, eg from the Scheduler. Otherwise it might wrap its cables or smack into something if it just sat there tracking.
Have you checked the configuration settings for the dome and telescope in ACP?
I suspect it thinks you might have a situation like a roll-off-roof where it could decapitate the scope if it is pointed up (like at Polaris).
Also, if you are using TSX ASCOM2X adapter, check its settings.
Also check TSX safety limits for the mount, assuming its a Paramount.
Otherwise, you need to share a bunch more info.
Thanks Colin -- Spot on for info on tracking and questions. I believe it is a new setup, and yes in ACP the mount and dome are "joined at the hip" since ACP is calculating the dome position based on the mount's position and geometry. And yes he has a low hanging roof with a safety system (M1). So far things look like they are working as they should.
For visibility for the M1 owners, after modifying rules and tasks in ElkRP for the M1 ASCOM driver, a reboot of the M1's system board is required. I have that scheduled for tomorrow morning and will update the thread on roof control with the setting for roof sensors enabled.
Be careful having ACP launch TheSky X. Although it may have been fixed, in the past that would lead to an "Index Error" from TheSky. If that appears, then the problem was regressed. Hand start TheSky by double clicking etc. before connecting to the Paramount and you'll be safe.
Noted. Thanks Bob. I tracked it down. I was missing my rule in the M1 configuration for the ASCOM driver to check the status of each scope park sensor. Works like a charm now.
In the M1, the text "09xx00200B5^M" queries scope safe status. You'll create two separate rules that when this text is received, will check the park sensor and then reply with a separate text. One rule will reply with 0FXX002Secure0081^M (message sent by m1 when scope is safe) and the second rule will reply with 12XX002NotSecure0063^M (message sent by m1 when scope is NOT safe). In my case, I have two piers so each rule has two AND statements that reference the zones for each park sensor input. Screen capture attached of this from ElkRP.
Attachment 9232
Excellent Vance, thank you very much for getting back on this. Someone else will benefit.
I'm going to move this to the Hardware/Driver section since it is not an ACP issue.