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
Whether we are trying to dial-in optimal print settings or troubleshoot print failures, it could be helpful to have better data about the printer. Just a few starter ideas:
capture more stats, e.g. standard deviation of temp (to detect/quantify temp fluttering)
Use bluetooth to mirror printer log and/or enhanced messages to another device (phone, PC, etc).
Add a "set watch" feature/dialog window, including some basic "on break" actions. For example, if
set a "watche" on temp, position, and other computed stats. For example, "if TempStdDeviation > X then pause print + beepity-beep + email.... to catch sudden drop/leap in temp.
It looks like we can directly query Position, Temp from the Extruder Class, but if that is a performance hit, we can perhaps simply grab the data as it flows through the console logger.
The text was updated successfully, but these errors were encountered:
If an observing webcam is attached, it could be helpful to "mark" the video stream as an "on break" action, e.g. when "if TempStdDeviation > X", tag and/or timestamp video stream position" could then jump to that part of hours long video of a print to see what, if any print consequences were related to the event.
Whether we are trying to dial-in optimal print settings or troubleshoot print failures, it could be helpful to have better data about the printer. Just a few starter ideas:
set a "watche" on temp, position, and other computed stats. For example, "if TempStdDeviation > X then pause print + beepity-beep + email.... to catch sudden drop/leap in temp.
It looks like we can directly query Position, Temp from the Extruder Class, but if that is a performance hit, we can perhaps simply grab the data as it flows through the console logger.
The text was updated successfully, but these errors were encountered: