Thanks Roland

I  don't use SkyX, and I have my keypad set up for external connection.

What you describe sounds similar to what happened to me earlier this week when this problem first occurred. I was able to move and park the mount through APCC (I didn't try the keypad), but MaxIm was totally unresponsive and wouldn't even let me disconnect from the mount because it thought it was still slewing. I had to use the Task Master to close out MaxIm. I didn't reboot my laptop, but I closed all the programs, powered down the mount and cameras, and then restarted from the beginning. MaxIm connected to the mount OK, but locked up after the first slew, again with the status thinking that it was still slewing.

When I did the test indoors last night I had my cameras connected last night and took several "images" during my testing, but I could not duplicate the problem. I will try again this evening and do a few more moves and slews along with the images this evening.

The ironic part about all of this is that until about 1-1/2 weeks ago I had never used APCC or MaxIm to control my mount. In just the few times I was able to do so I was amazed at how much easier some of the things I had been manually doing are with these programs. In particular I like the ability to click on an image at the spot I want the mount to point.

I hope you don't mind that I passed your comments on to Doug and Colin at Diffraction Ltd.

Mike

I may have set mine up completely incorrectly because it was still using the AP-V2 Driver in the loop. Here are the steps that I took to set up:

Device Hub:


When I clicked on the Properties in the ASCOM Telescope Chooser window it opened up the ASCOM V2 Telescope Driver. I had to change the COM Port from the APCC virtual port to the IP address (since I am using an ethernet cable). After I did this, when I clicked the check port button I got the mount found message.
 

After I did this I was able to connect to the mount using the ASCOM Device Hub.


In MaxIm I did the setup as follows:


Once this was done I was able to connect to the mount with MaxIm

Hi Ray

Doug George at Diffraction Ltd asked me to try using the ASCOM Device Hub instead of APCC to see if the mount status and position was being consistently communicated to the different devices. When I set it up inside I could not replicate the error I was getting the other night (which was that after the first GoTo was executed, MaxIm continued to think that the mount was still slewing and would accept no further commands to the mount).

As I mentioned earlier, I am not sure I set it up the way he asked me to do. I keep wondering if there is a generic ASCOM driver that he wanted me to use instead of the AP-V2 Driver. Here is what he asked me to do. Please let me know if you think he was asking me to do something different.

Mike

I just completed running the previous experiment with the APCC - AP-V2 Driver - MaxIm DL configuration except this time I had the cameras connected, cooling, and imaging. I was not able to duplicate the problem that I experienced the other night where the mount status and position was not being picked up in MaxIm DL.

These kind of events don't just happen without some kind of reason. I will probably repeat this experiment a couple more times. I expect that there is something like a power surge or sudden spike in the computer processor usage that is causing MaxIm to freeze up.

Mike