Possible explanations:
1. Step delay was reset to 0.
2. Save driver configuration at setting the new board revision option.
3. Motor is wired incorrectly/to wrong driver.
4. Burned out motor or controller if the coils were left powered due to revision changes.

Can you move the motor with Waveshare sample code?

@ Kevin

I will try tomorrow.

I will check tomorrow.

I went back to a backup with a 1.0 version of the wmh driver. This works as used some weeks ago. So hardware is working without issues. I updated this version to the 1.4 driver.

However, using this 1.4 driver I noticed some unexpected behavior. I want to get a better understanding of what happens, so I will come back to you probably tomorrow with more detailed info.

Kurt

I played a bit with the driver today and I only noticed one issue: The "configuration" buttons did not work on my system. Accordingly I could not save a specific configuration. Is there any prerequisite for this?

Hi...That presumably will not have an effect taking everything into account. It will simply be utilizing some convention over a USB association. In any case, it makes me keep thinking about whether I've deciphered the OP effectively. It is safe to say that you are explicitly searching for an INDI driver that controls focuser equipment that is straightforwardly associated? Or then again do you simply require an illustration of a focuser driver to use as a source of perspective or format that you can drop your own engine regulator code into?

Kurt,

That is weird that yo can't save the configuration. I have not heard of anyone else having that problem. And in fact, my code doesn't do much, it mostly is the base INDI framework that does the saving and loading. Configuration is saved in the .indi folder in your home folder, along with all the other INDI driver config files. Maybe have a look there and see if there's anything strange going on there.

So, I guess I had an oopsie. Looks like the saved driver config did not load one time I had it powered on for other tests and the motor ran hot. Gonna have to reprint it's housing.
The default mode seems to be to set the pin Low. Which on the original board is the powered on state.

Try adding this to the /etc/rc.local file, before the exit 0 line:

That way, as soon as the Pi boots, it will turn off the motor.[/code]

I took care of the motor running hot on system start already with the pull-up resistor.
I believe the pull-up resistor is an overall better solution because it saves the motor even when the Pi is shutdown but still connected to power.
This time I believe it was when the focus driver started with the default configuration, which for me I noted was to engage to motor on the Revision 1 board. As seen here.
www.indilib.org/forum/focusers-filter-wh...html?start=264#72252

I didn't catch it this time because I assumed it was all saved and loaded correctly. But I do recall my preset positions were empty. So I'm quite certain that is what happened.

Ok. New information. It wasn't that the profile didn't load. I've noticed it will always engage the motor regardless the first time the indi driver is started after rebooting the system.
It didn't used to do that.

Restore these lines of code to prevent lockup of the motor on the first run after system boot