Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /error3.JPG Uploaded by : tonybenjamin@...

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /error2.JPG Uploaded by : tonybenjamin@...

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /error.JPG Uploaded by : tonybenjamin@...

So I have a bit more wrt this error message. Initially the "Cannot Set Allocation" error message comes up in a little box followed by the following (see pics) if I try to connect the AP V2 Driver

This particular message has been seen for years in various applications, including Chrome, so I don’t think it is something specific to apcc and the driver. The only possible solution I saw was a

Ray, I cannot say for sure - but possibly. I have had problems with virtual ports quite a few times and I have seen this message in the past. Cannot be certain about the correlation though. I will try

Hi Hemant, When you have seen this, did you notice if the virtual ports did not get allocated? -Ray Gralak Author of APCC (Astro-Physics Command Center):

I have seen that message before. I am wondering if it is related to virtual com ports. Regards Hemant

If you configure APCC to not connect to the ASCOM driver, do you still see this error message? -Ray Gralak Author of APCC (Astro-Physics Command Center):

Tony, I loaded up your PHD2 log in the (free) PEMPro Log Viewer app, which parses and color codes the PHD2 logs. In between the dithers there are these odd "settling" state changes. It's not clear

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /TonysPHD2LogViaPEMProLogViewer.jpg Uploaded by :

Thanks for checking. I’ll see what I can do.

Benoit, A few other questions: 1) Which version of the mount firmware were you using? 2) Was the mount left on and parked (or tracking stopped) for several days previously? 3) Was this the first

One possibility... the mount would continue to slew if the software sent a "move" (not the same as a "slew") command but didn't send a "stop move" command. Or, the "stop move" command was malformed

No ASCOM driver. Linux with direct serial commands. -- benoit

Hi Benoit, Where you using the ascom driver? -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of

I could not find that message either, so it's not clear where it is coming from. Maybe try renaming your settings files, in case one of them is corrupted. -Ray Gralak Author of APCC (Astro-Physics

using an ap-1600 + the sky I did a goto and the mount went into a never ending RA move(well, I stopped it after 3 full rotations) (broke two cables) ? I checked the command log from the sky and

My apologies. It just did it again. “Cannot set allocations” is the exact error message.

I have been having some guiding problems in Dec with my AP900. I used Pempo's backlash exerciser and the backlash compensation via the keypad and managed to get the Pempro graph looking good after