Open turt2live opened 7 years ago
Those are both great ideas - here are a couple of other things we could think about querying (if the data can be extracted from Octoprint or whichever solution):
!printer file mendel90 - spits out the name of the gcode file currently running on the printer
!printer timeleft mendel90 - spits out the ETA being reported by Octoprint, though caution that this is the software's best guesstimate
I'm not tied to these commands, just interested in the idea of them and I think a time estimator is more useful of the two.
If we were to build a kill command, maybe the user would need to be opped to use it? Remote login to Octoprint may still be a better solution, but it could look like this:
!printer estop mendel90 - stops all motors, turns off nozzle and bed heaters
We might be able to use some kind of shared authentication (link matrix accounts to ocotoprint accounts, read permissions from octoprint). Could have overrides for directors/admins of rsheep.
Great suggestions in any case, I'm sure they're all possible. We'll have to tune the settings of Octoprint to make the estimated time more accurate (although I'm sure it'll still be way off).
!printer snapshot mendel90
!printer status mendel90