If MaximDL is being run "as administrator" in your first case, it can use a different COM port than when run as a regular user. That's because there can be two separate ASCOM driver instances running

Thanks Ray, will do on next clear evening. Just remember I live in Vermont ;-) Terri

SkyX connects to the mount via the ASCOM driver. You need to set SkyX up to connect to ASCOM mount. Make sure that the ASCOM driver is connected to an appropriate COM port. Use the computer's Device

You can slew from a planetarium program and Maxim is NOT stuck. It's only if you slew with Maxim. It has nothing to do with matching coordinate targets. A simple button push slew in Maxim causes the

It is NOT a problem with APCC! It does the same with APCC out of the loop. Maxim is not picking up the ASCOM driver status after a slew. It's as simple as that. Why it doesn't is a mystery. Roland

>>>It is caused by a high inertial load on the mount (large heavy scopes with lots of counterweights) that needs a higher damping factor in the control loop. Simple adjustment in software really. I

I am not sure to help here... Regarding the second point, as I see skyx, you may want to check this thread #71772 There was no maxim involved in my case but there was a problem stopping a slew

No, it is not SDE that is causing this. The Mach2 and our other encoder mounts do not have SDE. It is caused by a high inertial load on the mount (large heavy scopes with lots of counterweights) that

Configure TSX to use an ASCOM driver to connect to a mount, and select the Astro Physics V2 ASCOM driver as the driver for it to use.

I’m new to APCC and have been working my way around the program. I did browse the manual. I see the section where I can enter coordinates to slew to a target in APCC and I am able to grossly find

Ray, If I connect Maxim DL directly without APCC, it brings up the ASCOM driver but will show an error message saying that the mount cannot be found. If I connect SkyX first, without APCC, and let it

I use a USB cable directly from my laptop to the CP5. Roland

Ø 10. Note that the Mount status in APCC and the AP-V2 Telescope Driver looked OK If the driver and APCC indicated the mount status as normal, this points to a possible MaximDL issue. It might

Hi Ray Thanks for weighing in on this issue. I guess my question to you is whether you know of any reason why the mount status would stop being sent to MaxIm DL. The folks at Diffraction Limited say

Roland, I don't have an AP mount (on the waiting list for a Mach2), but this sounds very similar to the SDE generated oscillation that has plagued Ioptron's attempt at encoder equipped mounts. The

Hi Terri, I made a possible fix for the invisible error log window issue in the latest APCC Pro beta (v1.9.1.5) that I built yesterday. It also has the fix that Howard mentioned for the Dec/RA

If you meant me, it's a Mach2, just like Terri's. It only happened once. I cleared the error and continued with no problem. I'm not even sure how much time passed before I noticed it. I'll need to

Hi Mike, I have MaximDL 6.29 installed, but I cannot reproduce the behavior that you mentioned. I could not find anything obviously wrong in the APCC logs that you provided yesterday. Can you

I will try this.. and this is on the Mach2 for me. For the most part my mount stays in a garage unless imaging. Has never been in the rain, although we get significant dew at times. For me,

Hi Roland I would be interested to know what they tell you. They are pretty much taking the stance with me that it is not a MaxIm DL problem and must be something with APCC or the AP ASCOM V2 Driver.