Hi Bob,
I have some easing of bad weather here, so I've been testing my driver more, trying to locate the issue of my sending shutterState.ShutterClosed and your getting shutterState.Shutter.Error. I'm using Visual Studio and attaching the ACP process to the driver in order to be able to single step through the driver code.
The problem is not the shutter status as I described it above. The problem happens way before that in Connected Set. (i.e. Dome.Connected = True)
When I connect the telescope (and dome follows automatically) from the ACP/Telescope application menu, execution eventually drops into the Dome's Public Property Connected() Set part as it should, after connecting the telescope, and goes all the way through to the end of that Property. (This Property code is attached as Connected().txt.) I set a breakpoint at the End Set statement, I looked at the Locals variables (attached as Connected.jpg). That shows Connected = True, connectedState = true, _shutterStatus = [closed]. This is what I expected.
As soon as I click the Visual Studio "Continue" to go past the breakpoint, ACP announces "dome is connected" and simultaneously also flashes "Dome" and reports ShutterErr in the Dome control panel. After I force a close, the error clears, and the dome will operate manually by pressing Open or Close in the Dome control panel. Disconnecting telescope and dome raises no error.
I don't know how many machine cycles there are in "as soon as," a lot probably, but something is going on between the driver and ACP that my "connecting" is not connecting with you. Can you give me any clue about how to proceed debugging this further?
Funny thing is when I run the driver in Visual Studio in the debug mode, with the driver TestProgram and the real dome available, everything works perfectly - connecting, opening, closing, disconnecting.
You don't need to think about this too hard right now, but I did want to get back on your radar. Maybe we can have a phone conversation after the holidays.
Thanks.
Connected.jpg