-
Notifications
You must be signed in to change notification settings - Fork 19
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
Preheat using wildly high temperatures for the heated tool #55
Comments
Versions used: Preheat Button (0.7.2) Printer: |
This does look concerning! If it does work sometimes and doesn't work sometimes it's really difficult to diagnose. Did it happen again since you posted this report? Does it happen with all files or only with certain files? |
I haven't been printing much lately, I'm waiting for parts and I have the printer half disassembled, but tomorrow I'll run some tests if I can find a pattern. As a fellow programmer I understand how frustrating intermittent errors are. I really want to help you identify the issue, if there's really one! Does this plugin outputs any log? I can't check myself right now. |
I received the parts today, I've rebuild the machine and so far I haven't seen any issues so far. I've updated the plugin to version 0.8.0, too. I also saw that the octoprint.log show the preheat logs... Unfortunately I no longer have the logs from 16 days ago. :( I'll let you know when I see this behavior again! I'll try to record it then. |
I have the same problem, I'm also on version 0.8.0 and it keeps happening. |
I'm "glad" you also had this issue, since that indicates that's not only a thing that happens to me alone. I haven't printed in more than a month so that's why I haven't posted any follow up to this issue, but I hope I can provide feedback when I get back into printing. |
Looks like that when it cannot parse a heat command it goes crazy. 395 ºC holy sheet. This is the gcode I'm trying to print: 04_USB_enclosure_lid.aw.gcode.zip Things I tried: |
I want to report an issue that I've seen every so often that could be potentially dangerous. At the very least it could cause damaged bowden tubes or clogs or in a worst case scenario it could start a fire.
Sometimes the plugin sets the target temp to 395ºC and shortly after to 260ºC and it stays there unless the user chooses to press "Cool". You can see the spikes in the attached graph.
I was recording a video to show you proof but after disconnecting and reconnecting to the printer to clear the loaded gcode, the plugin started working fine again setting the correct temperature (200ºC).
I've seen this behavior several times now and the gcodes are correctly set to 200ºC...
If it happens again I'll post a follow up video.
The text was updated successfully, but these errors were encountered: