knro wrote: I see your point. So if the values were really stored in the EEPROM, they were not then read correctly by the driver?
The driver never read the motor settings values before my changes - it just simply applied the default "slow" motor settings preset stored in the EEPROM via a serial command on connect: