@CHRISROWLAND, thanks for that. Indeed for that I ran both but the error also came as iit ran alone. Happy to test the next version tonight (UTC 15h)

as you were talking about signed/unsigned stuff. maybe OT but. If I use the EKOS handcontroler and press the left, the scope turns right and other way round (celestron_gps) strange behaviour where I don't know the reason for (may be because the AVX only went through quick align and then solving?)

@Glen, thanks for the log.
There seems to be an issue with debug where it isn't enabled until after the initial startup so I can't see the messages to the hardware but the limits are reported as the maximum and minimum both zero. I think that's coming from the hardware.

Are you sure that this run had the full calibrate process done? I found when I was testing that if the calibrate process is interrupted at any point the limits are set to zero. It has to wait until the focuser has moved to the low stop, the high stop, returned to the start position and stopped.

The errors and lack of motion seem to be partly because the code you are using to control the focuser is checking and refusing to move if the position is out of range. I don't think the driver is actually getting any move commands.

I've a new version of the sources released that will check the limits and only update them if they are sensible, that the maximum is significantly greater than the minimum. This should help. It also improves the log output.

You seem to be running the released compiled version and I'm not sure how a new version will be generated, if it isn't then you would need to build indilib from the sources.

@Chris: What I forgot to mention. the standalone as 3 fields for preset, which are missing in the celestron_gps version

There's a new version escaped as sources which I hope fixes the incorrect values for the Celestron GPS telescope driver. I can't test because the problem doesn't exist for the RaspPi compiler. I'd appreciate it if you can get the sources, build and test. The limits should be the same as the stand alone version.

The presets seems to be a function of the base focuser driver implementation, that's why they aren't in the telescope driver. The telescope driver is so complex and the UI is so busy that I don't think it would be a good idea adding any more to it.

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.