I have used the focuser for basic setting presets and move in and out. Seems to be working fine
No chance to test it in a real situation, the weather has not behaved, but from initial playing it seems to work fine.

One Cosmetic item, In the Indi Control panel for the focuser, under the Main Control tab, the text on the left specifically the Relative Position and absolute position need to be fully visible. Presently they are only partly seen even if you resize the window.

It would be nice if the min and max positions could be populated on the screen which the focuser learns when the calibration tool from Celestron is run and then saved to the focuser by the tool

no difference. did reboot

Good to hear to works for more than one person!

Do you mean the text messages? I've no idea how to change that, it's part of the display stuff.

My max and min positions are shown, at least once connected and before that they aren't shown. I'll have a look though.

@ChrisRowland, please let me know your connection details. What is connected where and how. Maybe the driver is looking for all USB devices?

I've no idea, all I can suggest is enabling as much debugging as possible, trying it and posting the log files. I put a lot of debug logging in the driver.

The reason I suggested removing the Aux cable was because there may have been telescope control messages on the bus which were confusing things.

All I did to connect was to plug a USB cable into a hub connected to a RPi and plug the other end into the focuser. No other connections, not even power.

how is your focuser powered? mine is not connected to additional power but only usb (and aux)

nope - power did not help

update - connected to my linux client (xps13) - there it works fine. So it is a problem with my NUC. need to check if both computers use the same nightly stuff

update2 - both are using the nightly, strange
- the failed is using kernel 4.18, t (kstars he working one 4.16 (kstars Build: 2019-03-04T12:52:04Z)
- kstars on my NUC is running solely the focuser after throwing some errors: failed after some "read package fail read hdr" and erors to connect to ttyUSB but success on ttyACM.
Sooo. is the pure indi_celestron_sct_focuser not performing the autosearch as kstars does?

St

whowow.

are celestron_gps and the indi_focuser using the same ttyACM0? Now I got on the client (with all drivers enabled on the indi-server) the focuser but not the mount connected (failes with "2019-03-05T20:50:45: [WARNING] Port /dev/ttyACM0 is already used by another driver or process. ")

another update. raising all drivers by using indistarter as user is working but as a service not (only focuser failes)

AFAIK the celestron sct driver will search through the serial ports to see if it can find a focuser. It did when there were problems. On my system it uses ttyACM0 but that isn't fixed.
I don't know what happens if a Celestron HC with a USB connection and a Celestron focuser are connected at the same time. I would expect that the system would differentiate between them.

day is gone and night has come - my summary so far:
1. I got it working as normal user with indistarter
2. focuser driver failes (alone among all the other drivers) when called up as root (especially celestron_gps is working)

do you apply different access rights than to celestron_gps?

for now I can use (1) until (2) is working

off for now
St

I've added the focuser control to the celestron gps telescope driver. It only happened this afternoon so may only be available from sources.

This is designed to work with the focuser connected to the mount using the Aux cable, NOT the USB cable. The focuser control appears in EKOS in a Focuser tab.

If you don't have a focuser connected you shouln't see anything.

Jasen - Nevermind - Ignore my previous reply - probably not posted yet.
I see - I just need to install all updates that "SOFTWARE UPDATER " gives me (on SM 'desktop' as seen through VNC).
thx
glen