since 2009 I've had a permanently mounted 12"LX200 Classic Meade in a domed observatory. The communication between dome and scope is by way of LesveDome driver. I believe that Pierre de Ponthiere's software (LesveDome) communicates with ASCOM (or POTH?) to make everything work.
Late last year I acquired SGPro for its full automation capabilities. I noticed the problem then, but was dealing with other issues, and am just now bringing it up.
Once the LesveDome (and now LesveDomeNet) drivers are loaded in the observatory computer, they become a "choice" in SGPro for controlling the dome. I have used both versions of LesveDome and all of the SGPro v2.3 and v2.4 since that time. I have also used an older Dell 32bit Vista O.S. and a new Dell 64bit Windows 8.1 system. All do the same thing.
In a session, SGPro will instruct the scope to move to the second target upon completion of the first - followed by the dome. After a "scope settling time", the image and guide cameras begin to do a plate solve to refine position at the second target. Unfortunately, once the dome arrives at the second target, it then reverses and returns to the previous target position. After a pause it then returns to the second target. This means that the imaging and guide cameras are imaging the inside of the dome rather than the sky.
A workaround is to extend the scope settling time (say 60 to 90 seconds) to allow the dome to wander off and then come back before imaging begins. I'll try this at the next clear night.
This behavior occurs only when using SGPro. It does not happen when manually using only the Lesvedome/ASCOM controls.
I've attached the log from the other night. The dome issue occurred after leaving the target IC1871 and moving to NGC2683. The time was 11:11:08pm, Jan.28th when the slew to NGC2683 occurred.
Are there any thoughts on what might be the cause of this problem, and a possible solution?