Date
1 - 3 of 3
Comm Error APCC Pro
|
Hi everyone,
All of a sudden I am getting COMM ERRORS when I start up APCC Pro. The mount won’t move. I can park and I park however. I was running ASCOM 6.4 and then updated to 6.5 SP1. Getting errors on both versions. GTOCP4 I have VCP4-P01-13 Firmware Encoder A01-13 V1.8.7.1 ASCOM 6.5 SP1 6.5.1.3174 but same issue with 6.4 Log files. Issue two is a common one that I hear about on this forum. My default slew speed in APCC Pro is 1200x I can’t seem to set it to 600x. Any support would be appreciated. Matt Hughes |
|
|
|
Ray Gralak
Hi Matt,
All of a sudden I am getting COMM ERRORS when I start up APCC Pro.The logs you attached only contain ASCOM logs, not any APCC logs. However, I can tell from your screenshot what is happening. APCC 1.8.7.x is mistakenly sending a ":m#" command that is meant for a later firmware version. You can ignore that error as it does not hurt anything. I will post an update this evening that fixes this. Issue two is a common one that I hear about on this forum.You must set the slew rate in the Initialize dialog so that when APCC initializes the mount it will set the mount rate. Otherwise, if the mount has already been initialized, APCC will not automatically change the rate when you connect to the mount. So, to change the default slew rate, go to the menu Settings-> Edit Initialize Mount Settings... This will open the "Initialize Astro-Physics Mount" window. In this window, make sure "Set Slew Rate" is enabled, and set the rate to 600x in the dropdown list box. -Ray Gralak Author of PEMPro Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver -----Original Message----- |
|
|
|
Hi Ray,
yep new version fixed the comm error. Thank you, I like having things neat and with the errors. the 1200x / 600x problem I was having has been fixed too. I was doing as you suggested before but this time it worked. I had the GTOCP4 connected when I made the change, however It was most likely operator error 😏 |
|
|
