You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The origial idea was to replace all instances of RPM values with re-calculated values. But I think a better approach is to keep current RAW RPM values as they are and add real calculated RPM values to all of the screens.
That way backwards compatibility is not broken. We will need to add a microstepping field to the calibration files, to ensure proper settings have been used when calculating real RPM.
In case current microstepping setting is different from the one in the file a clear warning should be displayed.
The text was updated successfully, but these errors were encountered:
The origial idea was to replace all instances of RPM values with re-calculated values. But I think a better approach is to keep current RAW RPM values as they are and add real calculated RPM values to all of the screens.
That way backwards compatibility is not broken. We will need to add a microstepping field to the calibration files, to ensure proper settings have been used when calculating real RPM.
In case current microstepping setting is different from the one in the file a clear warning should be displayed.
The text was updated successfully, but these errors were encountered: