I believe the Indi driver for the Celestron CGEM mount is reporting an incorrect 'Guide Rate." I have an updated hand controller for the CGEM mount. I recorded a verbose debug log during start up. A section of that log is attached

and I have copied the lines of interest here:

"2023-04-01T21:03:27.179 EDT DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[DEBUG] RES <80 23> "
[2023-04-01T21:03:27.179 EDT DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[DEBUG] Get Guide Rates: Ra 50.588235, Dec 50.196078 "
[2023-04-01T21:03:27.180 EDT DEBG ][ org.kde.kstars.indi] - < Celestron CGEM >: < TELESCOPE_TIMED_GUIDE_NS >"

I have the guide rate (both RA and DEC) at .5 Sidereal in the hand controller. The result above seems to indicate that the driver is interpreting that number as percent and not the actual value. Phd2 is computing a guide rate based on this value and reports (Phd2 debug log) a guide speed which is two (2) orders of magnitude too large, see below:

Calibration Begins at 2023-03-20 21:29:48
Equipment Profile = Feb11_23_f63_OAG_SX
Pixel scale = 1.20 arc-sec/px, Binning = 1, Focal length = 1480 mm
Search region = 15 px, Star mass tolerance = 50.0%, Multi-star mode, list size = 1
Camera = INDI Camera [SX CCD LodeStar], full size = 752 x 580, have dark, dark dur = 3000, no defect map, pixel size = 8.6 um
Exposure = 3000 ms
Mount = INDI Mount [Celestron CGEM], Calibration Step = 300 ms, Calibration Distance = 25 px, Assume orthogonal axes = no
RA Guide Speed = 756.8 a-s/s, Dec Guide Speed = 750.9 a-s/s

In actual guiding it is using this rate:

Norm rates RA = 9.0"/s @ dec 0, Dec = 8.2"/s; ortho.err. = 7.9 deg

I have not had any issue using Phd2 for guiding (other than what you might expect from an aging CGEM mount) but I would feel better if the info from the mount (as reported by the Indi driver) was in better agreement with the actual guide speed. I don't know if this could cause issues with the internal guiding of Kstars/EKOS (I have used the internal guider succesfully also) or any other aspect of the program. It would just be NICE to get this corrected, if in fact it is an error in the driver.

thanks,