Hi Karsten, Thanks for pointing the error message. We will look into it. There is no need to take any more actions, your update is successful and complete. The Wi-Fi firmware for your hardware has not

Marcelo, Since it works when the ASCOM client launches the driver, but not when APCC launches it, that implies the COM port settings in the driver "Setup Telescope" might not match the driver settings

#APCC #Mach2GTO

To all, Some of you who use a keypad with their Mach 2, and who recently upgraded the keypad to V5.010, have noticed that the "Modeling" tool disappeared from the "Tools" screen. We determined that th

Konstantin, We decided the most expedient way to resolve is with a change to the CP5 firmware. You can find P02-14 on the AP web-site. Alternatively, you may use USB/Serial Utilities, which will "sens

Hi Dale, Thanks for noticing. FWIW, APCC can "find" CP4s and CP5's. See below. If UDP or TCP is checked, you can click the magnifying glass, which will perform auto-discovery. A List of reachable AP h

Hi Tom, 4-5 arc sec is a HUGE amount. Could you please provide an APCC log file. The APCC log file will have more information in it than an APPM log file. Thanks, Mike Hanson

Hi John, Copy the program to your desktop and run it from there. The issue is file and directory permissions in the Downloads directory. Next version of the program will use a different area for cachi

Yves, There are multiple configurations of Wi-Fi radio hardware due to obsolescence. They use different and incompatible firmware. VNET-P01-02.net is for one configuration, but not for yours. Other cu

Wade, Sync and re-cal are not the same, they still mean the same thing as they always have. Presumably, they are using plate solve to "fine tune" the calibration. If so, you are correct, and they shou

Darth, I am confident that the Wi-Fi module in your CP5 is having difficulty with the apostrophe in the SSID, although there's nothing inherently wrong with the SSID. The issue is deep in the bowels o

Hi Brent, The firmware change you refer to addresses a couple of items, including reducing two of the contributors to the slew warning. However, the primarily beneficiary is the DEC axis. If you provi

Steven, I have contacted you privately for troubleshoot. Regards, Mike Hanson

#Absolute_Encoders

Hi Jim, You description of the LED color indicates the DEC encoder read head ("housing") might be slightly out of alignment. The read head is attached to the mount with a pair of 3/32" hex screws. Wit

Hi Konstantin, The symptoms have nothing to do with P02-08. They are related to differences in silicon. We received a different version of silicon than we specified a while back. Unfortunately, by the

Hi Alex, We'll contact you privately. Anyone else with symptoms identical to Alex's, please contact us directly. It requires a little TLC to get past P02-08 in a very small subset of control boxes. Re

Hi Brent, Please uncheck the "Require High Accuracy slews". The threshold is too small for the small aperture of the DEC axis encoder. Regards, Mike Hanson

Hi Linwood, We are looking into this. There are no open "sockets", so the mount is not controllable via WiFi in this state. However, you are correct, no access point should be advertised if the Wi-Fi

The IP address isn't your only change, you've also placed a router between the PC and mount. Since APCC can "Find" the mount, we know that the electrical connections are good, and that APCC can commun

Shane, It was my response that Roland was asking you to wait for. Ray can also provide good insight into the inner workings of the V2 driver. One way to accommodate the side effects of the MoveAxis()

Hi Shane, The API you are using is modulating the tracking rate, not really "slewing". When a custom track rate is commanded it takes effect immediately. Yet, the mount cannot support infinite acceler