New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after fil sensor response is poor message, disabled sensor and then the printer reset! (trans petg) #1043
Comments
The same with the M600 command. Filament unload, load and firmware reset. |
Does it also happen if you copy the gcode file to the SD card and run it from there? Just to rule out Octoprint seeing it as the printer hanging, and then trying to reconnect, and by doing that resetting it. |
I did not check the print from the SD card, but the same version of Octoprint plus FW 3.3.1 works properly. |
I ran a test print on FW3.3.1 from Octoprint and SD card without incident. I updated to 3.4.0-RC1 and printing from the SD card worked alright but it reset on filament loading when printing from Octoprint. |
Sounds like Octoprint thinks the printer is timing out, and resets it. |
I had an issue that I think (?) was related to this recently on 3.4.1 RC2. My printer was left beeping for about 5 hours when it hit an M600 command in the gcode. The hotend hit the time limit and cooled down, then I came back and preheated the nozzle to unload and then load the next filament color. After doing that, the printer spazzed out and started moving diagonally across the bed while lowering the head (moving Z down) straight into my partially printed model. I turned it off immediately and had to restart the print. |
Check out this workaround: OctoPrint/OctoPrint#2026 . GurliGebis, you're headed in the right direction. |
This issue has been closed due to lack of recent activity. |
this was my first print after updating to this firmware. i was using octoprint and had a transparent petg print at about 80%. came up to the printer with it beeping. after unloading, and when it came up, i clicked disable sensor, then i noticed it showed"fillament loaded correctly" screen was barely legable(very dim) and right after that, the printer just reset.
The text was updated successfully, but these errors were encountered: