I was able to do some tests today. I connected ASCOM Dome Control to MaxPoint and to LesveDomeNet. I connected SGP to MaxPoint.
At first I tried telling SGP “No observatory”, but I got an error. When I acknowledged the error, I got a pop-up saying the dome would not be slaved; was I OK with that? I said Yes because I wasn’t asking SGP to slave the dome, but when I clicked OK, I got the original error back again. So, since it just seemed to be an endless do-loop, I told SGP the observatory was a simulator. Then SGP didn’t complain.
When I slaved the dome in ASCOM Dome Control, it rotated to the parked scope position. Fine. I ran a sequence and the telescope slewed to the target. After the scope and software confirmed it had reached the target by beeping, then the dome rotated. Apparently ASCOM Dome Control acts synchronously. I think MaxIm DL operates the scope and dome asynchronously. Note to self: I have to be careful then to not move great distances to targets or I may run into a problem with the shutter cables hitting the scope.
In fact, I had to abort the dome move in the first test just because of the danger of running into the shutter cables. Perhaps because of that, when I resumed the test, the scope and dome were not aligned properly. I disconnected dome and scope, parked the scope, and used the LesveDomeNet UI to re-home and park the dome.
Then, I did three more tests with different targets and the dome successfully aligned with the scope in each case.
During none of the tests did the dome behave in the erratic way it had when slaved in SGP. So, even with the small number of successful tests, I think I may have an arrangement that will work.
Now on to testing the automation of all the other functions: camera exposure, focusing, plate solving, centering, filter operation, guiding, etc.!