Wishlist
This is specific to GalilMotor, but might apply to other device types as well:
- Change Position Factor to something more meaningful, e.g. microns per full step. The code must then take care of applying microstep factor.
- I am not sure, what Position Unit and Backlash distance Unit are for, but when I changed the latter from mm to um, suddenly the Backlash distance Value was interpreted as 10 mm rather than the 10 um as which it was give. Not sure if this is a bug, or I just don't get the use case. Neither of them is ideal.
- Velocities (regular as well as reference) would better be given in something like mm/sec. Again the code must then take care of the conversion to steps by using the factor mentioned above.
- The same goes for Reference steps back Value. Giving this in mm would be better than giving it in fullsteps.
As a compromise one could imagine two layers: One closer to the device and one closer to the user.