Run time hour meter
-
It would be great to have an hour meter to keep track of total life Duet power on time and maybe printing times. Something to help with maintenance schedules for lubing, cleaning and replacing components.
-
Agreed
-
Yup,
Something that I requested a long, long time ago. But in the great scheme of things, I understand that it's low priority and possibly better to implement via DWC rather than the main firmware? Dunno - just a guess.
-
Yep I'm sure its low priority. It would just be a nice feature.
-
Yep I'm sure its low priority. It would just be a nice feature.
Yes I agree - and for exactly the same reasons as you (maintenance schedules etc).
-
I would love this as well
-
What information should be recorded? How often should it be updated? Bear in mind that the flash memory has a limited number of writes, so updating this information continuously or very frequently is not desirable. Also, some users provide 5V standby power; for those users, should the total power on time only include time when VIN power is provided?
-
I'd love to be able to have the data similar to the OctoPrint History Plugin: https://plugins.octoprint.org/plugins/printhistory/
Primarily, it tracks print time and filament used on a per-job basic. This is summed together for totals.
To your specific question, David, I'd track total power-on time when VIN power is provided.John
-
couldn’t you stor it on the SD card instead? Solves the problem of limited write cycles…
-
Would it be possible to have last print time next to a file in G-Gode files section. It would be good for tuning speed and for people printing same parts over and over. Also stored somewhere on SD rather than eeprom
-
SD card is flash memory.. Dc42 wasn't talking about eeprom
-
Would it be possible to have last print time next to a file in G-Gode files section. It would be good for tuning speed and for people printing same parts over and over. Also stored somewhere on SD rather than eeprom
One thing I have been considering is that when a file is printed of simulated, a comment giving the print time could be appended to that file. RRF and DWC would be able to extract that information. I'd probably make this optional, because some users might not want the Duet to modify their GCode files.
