Hi Chris,
Thanks. The 2nd version I sent yesterday was directly after calibration, and yes it was completed; after running calibration, utility flashed 'Calibration Completed'.

You say I should 'rebuild (driver) from sources'? Newbie issue: Is it obvious how to do this, or will I need some instructions? (sorry, not in front of hardware now, will need to try it later to night.)

You say "...new version of the sources released that will check the limits and only update them if ...": is this all the new source does thats new? Anyway, I can try.
Fyi, the stellarmateOS was updated just 2-3nights ago by running 'software updater' on Stellarmate 'desktop' (ie as seen in VNC).

thx
g

I'm sorry Glen but I don't know if this is available for someone who isn't a developer. Perhaps someone who is more familiar with the indi development system could help.

The driver log is reporting the limits as 0, 0 and I think the only place it reports the limits is when they are read from the hardware.

The new version is definitely worth trying, it has better logging, checks the limits and only uses them if they are sensible and has a calibrate routine built in.

@Chris celestron_gps now shows correct focuser values. Can you copy the missing elements also to _gps like calibation or presets?

Hi Chris,
Thanks. Ok, just so I understand the process, to install from source, is the following correct?

From the 'MATE Terminal' in Stellarmate, I need to run this:

sudo apt-get install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev

git clone github.com/indilib/indi.git
cd indi

## Build
mkdir -p build/libindi
cd build/libindi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../libindi
make
sudo make install

*************
Is that correct?
Or some how I can get only the focus drivers from indi/libindi/drivers/focuser/ . ?

Glen, if you update StellarMate now, you should get all the latest drivers. However, if you want to keep testing the development build, you should probably learn how to build it from source.

What you posted above is correct, but this is only for first time. Next time you go to ~/Projects/indi and just run git pull to pull all the updates. Then go to libindi (cd ~/Projects/build/libindi and run sudo make install and you're set.

I don't intend to add calibration or presets to the telescope driver. It's already complex enough.

Chris - what recommended way to copy and paste from mac to SM Mate terminal ( in order to do the build)? (I'm using VNC thru browser.)

Glen, If you aren't a developer I suggest not building from sources because when it goes wrong you will rapidy get out of your depth.

I would suggest switching to the beta builds, instructions for doing that are here
stellarmate.com/support.html?view=kb&kbartid=5

The message "The system should not be upgraded to the latest nightly beta packages." probably means "The system should now be upgraded...".

After that the normal GUI update process should work but using the beta builds.

They seems to be rebuilt every night (whenever that is) so by now the new vrsion should be in the beta.

Chris, Jasem,
Yeh - it seems to be working !! Great - thanks. For unrelated reasons, I had to do a factory reset on SM last night. So I ran the updater last night after the reset, and now focuser seems to be working. At least Min=0 and Max=60, and I can move focuser inward and outward. Great !!

Still there is some points of confusion, ie why Celestron Utility claims my Min~2000 and Max ~ 37000, and how they relates to SM values of 0 and 60000. Maybe Celestron original values are in some raw units, and the 0-60000 units SM reports are renormalized units ? Later I can test if stellarmate can really reach beyond 37000.

Other item I couldn't figure - how do you copy and paste to MATE terminal (from Mac)? I tried various command/control/shift C/V combos, and none worked. Do you run SSH?

Glen, can you please enable driver debugging, run this and post the log file. Your system should be reading the limits from the focuser and getting the same values as the Celestron Utility. I'd like to see what is really happening.
In fact there should be something in the info window, a message like "Focus range |high| to |low| invalid, range not updated". This gives the values read from the focuser, that would be a start.

Hi
I don't have a focuser attatched to my cgem dx mount aux port ( i have the starsense accessory attached)- I have a starizona focuser but that's attached via usb but the focuser tab still show up under the mount tab anyway, and the indi tries to talk to my mount about the celextron focuser and generates errors.. Maybe something more is required to understand what may be attached to the aux port so tha focuser tab does not show up when there is no focuser there... Or what could i be doing wrong

Hi, it me again, i did some check, switched on logging.. and it shows clearly in the loggs that what you think is a focuser is the starsense acessory...
I think its necessary to do a litte bit more checking to assure that whats connected in the aux port i actually a focuser
Also, the driver says my mont in not aligend an get wierd time and utc offset, but i confidently checked that time (gps-updated) and utc offset were correct and i made a quick align in the handset before connecting indi. Still there is some error som were..

Here is a log sample related to the focuser isse:
[2019-04-03T14:54:42.550 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] CMD <50 01 11 FE 00 00 00 02> "
[2019-04-03T14:54:42.551 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] RES <06 33 23> "
[2019-04-03T14:54:42.551 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] Getting focuser version... "
[2019-04-03T14:54:42.552 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] Does focuser exist... "
[2019-04-03T14:54:42.552 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] CMD <50 01 12 FE 00 00 00 04> "
[2019-04-03T14:54:44.917 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] RES <06 33 FE 00 21> "
[2019-04-03T14:54:44.920 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] Focuser Version 6.51.65024, exists true "
[2019-04-03T14:54:44.923 CEST DEBG ][ org.kde.kstars.indi] - Celestron NexStar : "[DEBUG] Firmware Info HC Ver 1.19 model CGEM DX StarSense GEM mount, HW Ver 6.51 "
[2019-04-03T14:54:44.925 CEST DEBG ][ org.kde.kstars.indi] - < Celestron NexStar >: < ON_COORD_SET >
[2019-04-03T14:54:44.974 CEST DEBG ][ org.kde.kstars.indi] - < Celestron NexStar >: < EQUATORIAL_EOD_COORD >

So I guess the code assumes any attached device that show a version number is a focuser. as you can se in the firmware info string, it says "Starsense", is it possible to get a similar firware info string related to the focuser and use that to do a string search for the work "focuser" (or?) to ensure is the focuser devise and not the "Starsense"...
I guess you sending commands for the focuser might result in other errors/strange behaviour in the hand controller since there is no focuser there...

What can i do?