What is the problem?
After updating to 1.3.7 my hotend no longer shuts off after a print finishes
What did you already try to solve it?
I use S3D and the end codes to shut down the bed and hotend. I always have and it has always worked perfectly. I have done three prints since updating to 1.3.7 and now just the hotend won't shut off after printing. I have searched the forum and the facebook group. I made a post in the facebook group and here.
Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)
Octo 1.3.7
Wanhao Duplicator i3
Simplify3d
The two pictures show the end of the print code from Octo and my S3D settings.
That is octoprint.log, I asked for a serial.log (which you'll btw first need to enable, see here) I need to see what communication happens between OctoPrint and your printer.
I installed the gcode editor to be sure the code was in the file and it is. Here:
G1 X54.578 Y136.716 F2880
G92 E0
G1 E-2.3000 F2400
; layer end
G28 X0 ; home X-axis
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
M84 ; disable motors
So it looks as though the code was sent but the printer did not turn off the extruder. The bed shut off though.
2018-04-11 23:13:43,268 - Send: N4 M140 S7086
2018-04-11 23:13:43,281 - Recv: ok 4
2018-04-11 23:13:43,285 - Send: N5 M190 S7090
2018-04-11 23:13:43,286 - Recv: TargetBed:70
2018-04-11 23:13:43,297 - Recv: ok 5
2018-04-11 23:13:43,301 - Send: N6 M104 S250 T0*32
it actually doesn't look like a M104 S0 was sent. So the question is why. What I do see in there is a M400, M114 pair. Stock OctoPrint only sends those when cancelling a print, which was not the case here. Considering how many there are in there, I'm guessing you have Octolapse not only installed but also running here?
I know that this plugin does command replacements, and from the timing of that injected pair which is right where the M104 S0 should be, I'm wondering if what you are seeing here is maybe caused by the plugin. Please disable the plugin or better yet enable safe mode as I mentioned earlier and see if your heater then properly shuts off at the end of a print. If it does, this is an issue in the plugin that will need to be investigated.
@FormerLurker, pinging you since this might be related to Octolapse.
I will take a look at this ASAP since it could very well be an Octolapse issue. It looks like Octolapse tried to acquire a position after a home, which is where the M400+M114 comes from right after the G28, but maybe it didn't properly send the next gcode?
@mylomine, can you post your gcode file, or create an issue here? I'll definitely escalate this since we don't want hot ends staying hot after the print!!!!
So it looks like Octolapse is not properly sending any commands following a home (or any other command configured to reacquire the current position) if the command doesn't have an entry in the parser. This is not good. It looks like I left some remnents of the previous parser in the acquire_position function . Once I debug and test I'll push v0.3.2.
The new Octolapse did fix the issue. I reran a print with the new version and the hotend turned off as normal. I did uninstall the previous version just to be safe. I did not run in safemode as I wanted to try with the new version of Octolapse. Thank you both for your help. Sorry it took me so long to report back.
Thanks @mylomine! I am about ready to push this fix into production. I thought it would be last weekend, but I was experiencing issue armageddon. Let me know if you have any additional problems.