What prevents jobs from ending?
It occurred to me just now I haven't tested this without octoprint connected, even though jobs run from the SD card exhibit the same behavior. When this job is done, I'll check that.
What's happening is that when a job completes, I am unable to start a new one, and I don't know what it's doing. The piece is done. The extruder is parked. but the control screen will say "heating" even though the job is done.
I don't have any custom g-code to retract filament at the end of the job as I do on my Ender 3. I just checked and this is the end of job gcode:
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+1, max_print_height)} F720 ; Move print head up{endif}
G1 X0 Y200 F3600 ; park
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+49, max_print_height)} F720 ; Move print head further up{endif}
G4 ; wait
M221 S100 ; reset flow
M900 K0 ; reset LA
{if print_settings_id=~/.*(DETAIL @MK3|QUALITY @MK3|@0.25 nozzle MK3).*/}M907 E538 ; reset extruder motor current{endif}
M104 S0 ; turn off temperature
M140 S0 ; turn off heatbed
M107 ; turn off fan
M84 ; disable motors
; max_layer_z = [max_layer_z]
I don't see anything in there that would cause some kind of "wait state."
I find I have to quit a job twice on the control panel (the first one just pauses?) and there is no way to do it through octoprint except to disconnect and reconnect.
Latest firmware, MK3S, used but only 12 days of time on it (I got it with 9 days).
RE:
G4 ; wait
as someone on the octoprint forum pointed out, this line will wait forever. So I commented it out. No difference. What's puzzling me is how no one else has seen this.
The next thing to try is running without Octoprint.