Have you tried connecting the focuser to a windows PC, run the celestron calibration utility to retrain the focuser limits.

When you reconnect it to the Stellarmate, it will reread the settings from the focuser

What I've found is that if you abort a calibration before it's finished the limits are set to 0, 0.
I'm going to check and not update the limits if they aren't sensible.

Hi,
I'm about to order the Celestron Focuser for my SCT. Is an Usb port from a Raspi enough to power it up or do I need extra power ?
Thanks!

- Marc

Don't know, my testing was done connected to a RasbPi through a powered hub.

Chris. the in celestron_geps integrated focuser is reporting wrong max value (-23500) where the standalone does not.

Not interested without log files.

focuser of _gps

2019-03-07T19:04:47: [INFO] Focus Limits: Maximum (-23055) Minimum (1993) steps.
2019-03-07T19:04:47: [INFO] update focuser properties
2019-03-07T19:04:47: [INFO] Mount UTC offset is 1.00. UTC time is 2019-03-07T22:17:14
2019-03-07T19:04:47: [INFO] Mount is unparked.
2019-03-07T19:04:47: [INFO] InitPark: No Park data in file /home/hugo/.indi/ParkData.xml: No such file or directory
2019-03-07T19:04:46: [INFO] Mount model: AVX
2019-03-07T19:04:46: [INFO] Controller version: 5.30
2019-03-07T19:04:46: [INFO] Celestron GPS is online.

and standalone:
2019-03-07T19:04:47: [INFO] Device configuration applied.
2019-03-07T19:04:47: [INFO] Loading device configuration...
2019-03-07T19:04:46: [INFO] Celestron SCT focuser paramaters updated, focuser ready for use.
2019-03-07T19:04:46: [INFO] Focus Limits: Maximum (42737) Minimum (2249) steps.
2019-03-07T19:04:46: [INFO] Celestron SCT is online.
2019-03-07T19:04:46: [INFO] Celestron SCT Focuser is online. Getting focus parameters...
2019-03-07T19:04:46: [INFO] Firmware Version 7.15.8240

compare the max-limits

Please submit the verbose debug log files (check my signature for how to).

hope it helps

I run mine from the USB port on the PI without issue

Thanks, that's the sort of thing I need but the same log from the driver that's giving the incorrect values would help. I'm looking for the messages from the focuser.

What system are you using? I think it's happening because of the way different systems and compilers handle the conversion between char and int.

Jasem, the celestron-gps code is using a char buffer for all it's replies:
char response[MAX_RESP_SIZE];
would changing this to:
unsigned char response[MAX_RESP_SIZE];
or
uint8_t response[MAX_RESP_SIZE];
help and not interfere elsewhere? Most other places either use ascii characters or the incorrect conversion doesn't matter.

I'd like to get this right but I'm not seeing the problem and the incorrect conversion isn't picked up by the CI builds so it's going to be difficult to ensure that it's OK until the user sees it.
Getting late now so I'm going to leave it until the morning.