Open gege2b opened 4 years ago
Octolapse Version: 0.4.0RC3 (but seems to be there for long)
OctoPrint Version: 1.4.0
Diagnostic Logging was Enabled: Nope
Restart of the print, and Octolapse gently handle this case (by, i.e. deleting already captured frame, and start over)
Restart of print (good point) but octolapse fired an error popup
OS Name: Raspbian Os Version: 9.11
not needed
2020-06-03 21:46:26,244 - octolapse.timelapse - DEBUG - Sent: G1 X123.676 Y111.603 E8.49046 2020-06-03 21:46:26,261 - octolapse.timelapse - DEBUG - Sent: G1 X115.749 Y119.524 E8.67022 2020-06-03 21:46:26,277 - octolapse.timelapse - DEBUG - Sent: G1 X115.588 Y119.594 E8.67303 2020-06-03 21:46:26,292 - octolapse.timelapse - DEBUG - Sent: G1 X115.424 Y119.568 E8.67569 2020-06-03 21:46:26,312 - octolapse.timelapse - DEBUG - Sent: G1 X115.339 Y119.513 E8.67731 2020-06-03 21:46:26,340 - octolapse.timelapse - DEBUG - Sent: G1 X115.046 Y119.218 E8.68399 2020-06-03 21:46:26,357 - octolapse.timelapse - DEBUG - Sent: G1 X114.962 Y119.103 E8.68627 2020-06-03 21:46:30,622 - octolapse.timelapse - DEBUG - Sent: M105 2020-06-03 21:46:30,646 - octolapse.timelapse - DEBUG - Sent: M400 2020-06-03 21:46:31,134 - octolapse.timelapse - DEBUG - Sent: M114 2020-06-03 21:46:31,246 - octolapse.timelapse - DEBUG - Sent: M85 S240 2020-06-03 21:46:31,383 - octolapse.timelapse - DEBUG - Sent: M105 2020-06-03 21:46:31,392 - octolapse.timelapse - INFO - Print Paused. 2020-06-03 21:46:34,238 - octolapse.timelapse - DEBUG - Sent: M110 N0 <=== Here I clicked Restart 2020-06-03 21:46:34,328 - octolapse.timelapse - ERROR - File line number 944 was expected, but 1 was received! 2020-06-03 21:46:34,603 - octolapse.timelapse - DEBUG - Sent: M107 <== print restarted 2020-06-03 21:46:34,624 - octolapse.timelapse - DEBUG - Sent: G92 E0 2020-06-03 21:46:34,712 - octolapse.timelapse - DEBUG - Sent: M92 X80.402 2020-06-03 21:46:34,729 - octolapse.timelapse - DEBUG - Sent: M92 Y78.798 2020-06-03 21:46:34,744 - octolapse.timelapse - DEBUG - Sent: M92 Z2622.950 2020-06-03 21:46:34,760 - octolapse.timelapse - DEBUG - Sent: M92 E599 2020-06-03 21:46:34,776 - octolapse.timelapse - DEBUG - Sent: G21 2020-06-03 21:46:34,791 - octolapse.timelapse - DEBUG - Sent: G90 2020-06-03 21:46:34,807 - octolapse.timelapse - DEBUG - Sent: M82
Screenshot/Video Links: see below
Thanks for the report! I'm still working on dealing with my backlog, but this will get some attention soon.
Version of Octolapse
Octolapse Version: 0.4.0RC3 (but seems to be there for long)
Version of OctoPrint
OctoPrint Version: 1.4.0
When you ran into the problem, did you have diagnostic logging enabled?
Diagnostic Logging was Enabled: Nope
What were you doing when the problem occurred
What should have happened?
Restart of the print, and Octolapse gently handle this case (by, i.e. deleting already captured frame, and start over)
What happened instead?
Restart of print (good point) but octolapse fired an error popup
Operating System running OctoPrint and Octolapse
OS Name: Raspbian Os Version: 9.11
Printer model & used firmware incl. version
not needed
Browser and version of browser, operating system running browser
not needed
Link to the gcode file you were printing when the problem occurred
not needed
Link to settings.json
not needed
Link to plugin_octolapse.log
Link to octoprint.log
not needed
Link to contents of Javascript console in the browser
not needed
Screenshots and/or videos of the problem:
Screenshot/Video Links: see below