As seen in the screenshot, the report back from the Marlin-based firmware indicates the shown numbers. Unfortunately, only part of the information is available: "300 mm" steps per unit without revealing that this is actually 300 mm/sec as reported by an M501 command:
The complication then is how OctoPrint's own printer profile screen works.
As seen here, all the settings are in mm/min rather than the Marlin default of mm/sec. So presumably that 80mm/sec figure translates into 4800mm/min rather than the default 6000mm/min, as seen.
I would suggest that the EEPROM Marlin plugin (since it is specific for Marlin) go ahead and indicate that the units are in mm/sec for the set of input fields and have an onMouseOver() event or a title attribute of some kind in the interface which would indicate this again in the mm/min units, as converted. Hovering over the entered "80" would then do the "times 60" math and display the result.
As seen in the screenshot, the report back from the Marlin-based firmware indicates the shown numbers. Unfortunately, only part of the information is available:
"300 mm" steps per unit
without revealing that this is actually300 mm/sec
as reported by anM501
command:The complication then is how OctoPrint's own printer profile screen works.
As seen here, all the settings are in
mm/min
rather than the Marlin default ofmm/sec
. So presumably that 80mm/sec figure translates into4800mm/min
rather than the default6000mm/min
, as seen.I would suggest that the EEPROM Marlin plugin (since it is specific for Marlin) go ahead and indicate that the units are in
mm/sec
for the set of input fields and have anonMouseOver()
event or atitle
attribute of some kind in the interface which would indicate this again in themm/min
units, as converted. Hovering over the entered "80" would then do the "times 60" math and display the result.