I haven't connected PemPro to my mount for about a year now. I have been regularly updating the PemPro releases though. I connect to a MI-250/Gemini L4 mount. I tried last night to connect to the mount and camera two night's ago to gather new data while the moon was still impeding regular imaging. I get a an error message when I try to connect to the mount. No problems connecting to the camera. I didn't write down the error number and there is no log entry to read since I can't connect. The error said that the "value" was outside the specified range. The value was something like 21541..... What is interesting is that the value in Basic Configuration - Worm Cycle Period was 215.41 instead of the proper 239.34 for a Gemini system. I tried to correct the number but it could not be changed. I created a new mount definition and tried again but it still would not connect. I downloaded the latest release, (went from 83 to 88) but it had no effect. I was connecting to the ASCOM driver by itself. No other programs accesssing the driver. I can connect to the mount fine with either TheSky6 or MaxIm, just can't connect PemPro 2 now. Any ideas? I didn't completely remove the program and reinstall yet.

Keith

Hi Keith,

Double check the Gemini ASCOM settings. Something probably is set wrong there.

-Ray

Hi Ray, I've double checked the ASCOM settings multiple times. As stated, the same ASCOM settings work for every other program I use to access and drive the mount. Both MaxIm and TheSky6 have no issues connecting to the mount. If it was something simple, I would have discovered and corrected the problem. I'm at a loss why PemPro no longer can connect to the mount. I deleted and created the mount numerous times to no avail. Thus I resort to asking for help on the forum.

Keith,

Nothing has changed in PEMPro's Gemini interface in a long time. You could try reinstalling just in case something got corrupted.

Also,

1) Is there anything different about your mount?

2) Can you post a screen shot of the error message?

3) How about the exact version of the Gemini driver you are using.

4) Which version of Gemini firmware are you running?

Also, it would be nice if you could turn on ASCOM logging so I can look at the commands being passed back and forth.

-Ray

You can close the ticket. I decided to look into the registry and found errors with phantom com port assignments in PemPro and errors in PemPro so decided to blow the installation away and reinstall. After reinstalling, everything is working again as i t should.