Hi Andy, I think there is an issue setting the proper move rate with 5.30.10 with CP3's. Almost all of the changes in the 5.30.x versions were for the Mach 2 and GTOCP4. If it’s a problem you can

Yeah the impressive thing for me isn't just the scope, as the Mach 2 can easily handle that within specification. It was how loaded down the total system was, it's size, AND the total length of the

Back many years ago while waiting for my AP1100 mount, I had no issues imaging with my Mach 1 with my C14 black tube, so Im not really surprised that the Mach 2 can handle a 12.5” AGO and

Since I updated the Ascom driver to the version 5.30.10 I am unable to move the Mach1 GTOCP3 with V chip at 1200x using the buttons in the driver window. The mount just won't move if I have 1200x

@JoePetrick9 write: I disabled a virtual port in device manager on win 10 PC and now when i create ports in APCC it does create the ports in APCC but not in my device manager so I cannot connect

I disabled a virtual port in device manager on win 10 PC and now when i create ports in APCC it does create the ports in APCC but not in my device manager so I cannot connect to V2 . Does anyone know

It's nice to know that even a bigger scope is possible on the Mach 2.

For the sake of testing it. 🙂

Bill, why go from original 5 sec guide exposures to 1 sec, I have gone through the screen shot and can’t figure out the collective differences TJF Mobile

Really amazing results Bill! Makes me hope and worry that my name will come up for one sometime in the near future. I dont see myself ever getting a bigger scope than what you are using on here. In

Results tonight... Note the 1 second guide exposures. The Mach 2 is the best mount ever made. Period. This is with the same massive overloaded system I talked about before. If the Mach 2 could not

Powered up my mount last night and the keypad displayed this error message. I switched off ,removed motor cables, reattached cables and powered up. Mount ran fine for the evening. Am I correct in

Linda, Additionally, at the top left of APCC, click the “Advanced Settings” button and change the “Auto Initialize (secs)” to “0”. Regards, George George

Tried a couple more times and it seems to behave. In my earlier, “it’s still happening” comments I was referring to the dialog popping up. I was expecting that to go away with the change George

Well…I let the “I’m going to set the park to last parked” dialog time out and it stayed parked which is exactly what we wanted so maybe there isn’t an issue. Or the setting change that

Linda, Unparking is not the same as tracking. Look at the very bottom of APCC (the white horizontal band at the base. Does it say that it is unparked and tracking or unparked and zero

Ray, If I don’t hit cancel on the operation that says it’s going to unpark on me, then it does unpark and doesn’t repark. At least that is what i think is happening but I will verify that as

Hi Linda, As Howard said, unparking is part of the mount initialization operations. APCC will initialize the mount, including the unpark operation, but then immediately repark the mount. Is it not

Hi Brian If power to mount is not recycled, and last command was to Park, Everything would work as expected. In my case because I have to power down everything in my observatory between visits, it

Here is the mount related portion of the startup: 1. power on the mount from the remote power switch 2. start apcc 3. click initialize (it’s set to don’t unpark and currently track to zero). 4.