Initialisation Invalid Data

[ozonejunkieau]

Thanks for the test unit @AlistairSymonds, I've spent the last couple of nights putting together some Python code that enables me to test out the device without needing a full INDI or ASCOM stack running, and should also allow me to use it for things like macro focus stacking.

Throughout the testing I've noticed a few things in the initialisation of the device:

• Powering the device up with the stepper driver power disconnected results in the "is moving" flag being set, which seems optimistic.
• Neither the "home positive" or "home negative" bits seem to be set on power up, which doesn't seem to be a valid state? What is the default direction for homing?
• On initial power up, the driver status values seem to indicate all the following bits are set MOTOR_STOPPED|S2VSB|S2VSA|S2GB|S2GA|OVERTEMP_ERROR|OVERTEMP_WARNING.

I'm hoping to actually get a motor connected to the board in the next few days to test further.

[AlistairSymonds]

• That first one doesn't sound right! You could AND it with the DRIVER_ENABLED bit and it should be correct then, its likely something to do with the code added to not report a move as done until CS_ACTUAL == IHOLD, so any mechanical shifting from reducing current from run to hold levels is accounted for. Will fix though.

• In this case trigger homing would just do nothing. It probably doesn't make sense to just home towards max in isolation or past one time to set limits, (as any error in detecting the stall at max would shift the zero position limit) but the driver is very much "expose as much as possible" and not "What makes sense" right now.

• And yes, my dirty laundry, the usb_protocol is a spec for what should be supported in the future, not reality as it is right now. Got lazy and forgot about those bits and neither does the read request from host->device work either.

So a few things to fix up still, glad you're interested still and haven't been turned by the state of the project beneath the surface :)