I have the configuration you require..

If you send me the library (and instructions about how to install it) I can try this evening...

Paco L.

Thank you for all the great work guys!! I just emailed PrimaLuca and asked them if they have an explanation for this. If we don't get any response, we can just comment it out.

Is the Windows software sending out any different/extra commands on startup if you snoop via WireShark?

They start with #MF!#GC!#GS!#QF!#QSN! then they repeat #QP!#QT!
During calibration they use #Sm;0! to set the min point and use #SM!#PS! to set the max point.

#SM! is sent without any position? so during calibration, the focuser is moved to some location and then #SM! is sent?

Sorry, forgot you do not have one.
Calibration is in 3 steps:
1) Set the focuser at 50% position manually
2) Move to zero using the motor, when you move to next step => #Sm;0!
3) Move to max using the motor, when you say done => #SM!#PS!

and no where is #SM;xxxxxxx! command used? Maybe that's the command causing the issue? we could implement calibration in the driver similar to what they have in Windows.

Exactly. We could or just leave the calibration in the Sesto App and just report on the max value. I like the idea of keeping the Indi drivers simple.

One thing I still need to look at is what is does with the Ascom driver.

Right, simple but functional. Why ask users to load windows and download an app just for this step.

The calibration could be made simple with two switches:
Calibration: [ Start / Stop ] [ Next ]

On Start, we ask user to manually move the focuser to the middle (or whatever message that is appropriate). Then we say click next after moving. Then we say move to minimum position, then when user click "NExt" we set sm;0 and then ask user to go to max position and send SM; and then save config.

That should work as it mimics their procedure.

They first release the motor with #MF! to allow you to set the focuser manually in the middle position in the first step.
They provide you with a "-" ,"+" and "Stop" control. These use #FI!, #FO! and #MA! to stop. This is for the second and third step when you use the controls to first set the zero point and then the max point.

Ok since you have everything set up now, do you want to give this a go?

OK. One thing I have not found yet is how the control panels are created. Are they defined in XML somewhere?

Go to the header files and you'll find the properties defined there. So for this you need something like this added:

ISwitchVectorProperty CalibrationSP;
ISwitch CalibrationS[2];
enum
{
CALIBRATION_START,
CALIBRATION_NEXT,
}

Then in initProperties, you fill in the switch vector property details. Next in updateProperties() is where you call defineSwitch(....) once connected and deleteProperty(....) once disconnected. Finally, in ISNewSwitch(....) is where you will process changes to this property. You might want to have perhaps another variable to keep the machine state of the calibration process.. something like:

typedef enum { Idle, GoToMiddle, GoMinimum, GoMaximum, Complete } CalibrationStage;

then define the variable:

CalibrationStage cStage { Idle };

and then in ISNewSwitch(...) once the user presses Next you know which stage you are in and how to proceed next.