Print history
-
Would sure be nice to have a log of canceled and finished prints, for records, but also performance differences. Can’t really count on web interface to be up the whole time to snag it manually. As it is post printing, shouldn’t be a performance drag to write a lot of the print status items to a log.
-
If you enable logging in the 1.20beta firmware, than all prints are logged.
-
Would it be possible to add the total amount of consumed filament to this log message?
https://github.com/dc42/RepRapFirmware/blob/8158ac9f5f9f00c7d8fe55893540549e5ca7e90d/src/GCodes/GCodes.cpp#L3949This would be very useful to keep track of filament/spool usage. I can do some basic log-file analytics and math to check if my next print has enough filament available.
-
Id like that it would be nice to see stats based on the log, maybe if the information is in there some way of parsing it into global stats for the printer would be very interesting data.
-
Id like that it would be nice to see stats based on the log, maybe if the information is in there some way of parsing it into global stats for the printer would be very interesting data.
I think that would be best done in Duet Web Control. It could download the log file and then give you options for reporting on it. I could change the format of log file entries to JSON if that became the standard way of looking at log files.
-
Cool on loggging, have 1.20 installed, how do you enable logging tho.
-
greecher: Take a look here: https://duet3d.com/wiki/G-code#M929:_Start.2Fstop_event_logging_to_SD_card
-
DC42,
man you do a bang up job, thanks for the info, put it in will try it out.dave
