No they can not be edited in that way. It must be recompiled from source.
I do not have the resources to make a version compatible with your system.
Either request and wait for an update to the driver, or look into compiling it yourself.
It's not too difficult to do yourself and can be handy to know how I'm the future.
Give these a go, Built for Raspberry Pi 64bit.
*Backup original drivers first.
Oh, I can make a 64 bit version too. Give me a little time.
Check your PHD2 Calibration steps in the Brain. They are calculated based on guide scope focal length, you must set that yourself, and the sensor specs.
If PHD2 does not have the correct focal length, it likely will not use effective pulses for calibration.
In my earlier post, that I mostly retracted with a strike through, I did exactly that. Added a zero to make it 2,000,000 and compiled a version that should work on a raspberry pi 4, 32 bit system and attached it for him.
I'm not sure if it is compatible though, so he should backup the original driver first..
I switched to the Waveshare motor hat.
The biggest issue with driving a motor over i2c is getting high speeds because of frequency limitations.
Something to consider, but there are a few other good options to look at too.
I don't know the details about your system. But I compiled a custom version of the SestoSenso drivers on a Raspberry Pi 4 (32bit). It might work for you if you have a similar system.
Copy them into /usr/bin/
To copy it you will have to use sudo cp command in the the terminal.
I'm no expert. It's just how I interpreted the code.
Now, it's not just a matter of editing the file. You will have to install the tools for compiling INDI drivers. Download the source code, make the edit, build the driver and have the compiled driver installed in the right place.
Hope it helps.
In my experience, just consider the zero point to be the default software starting position when you run EKOS. I'm not sure about this but this may not be true if the motor has encoders.
Starting from zero can be a bit annoying at times, Say your focuser is already near the focus point. If it starts at 0, it will have no valid inward travel steps available.
In that situation, I use the Sync box under the focus driver's Main Control Tab to give it some arbitrary higher value.
I would recommend you rack he focuser all the way in. Sync it to zero. Focus the telescope on the sky and note the position.
Save that position as a preset in the INDI driver. Now the next time you start from zero and fully racked in, you can call upon the preset to get a roughly accurate focus to begin with.
The 3677 value on the left is the current position. The 0 on the right is where you manually enter where you want to move when you hit the play button next to it. Doing so will drive the motor in, then it will read 0 on the left.
Elsewhere under mechanics, you can set the initial step size. This is used my the autofocus algorithm. But it is also how far it will focus in/out with the arrow buttons above.
Lastly if you want to set the current position to a custom value without moving the focuser. Use the Sync box in the INDI diver itself.