Google Search
Different USB cables
Re-checked F/W
Found GitHub Bug Report #4862 - No help, but waiting on reply (original report started over one-year ago)
Have you tried running in safe mode?
Yes, the same results.
Tested in Safe Mode before saving this latest bundle.
Currently nothing in that script section. But I did find some sample scripts last night that I am going to try. It will have to wait till Monday tho.
{% if pause_position.x is not none %}
; relative XYZE
G91
M83
; retract filament, move Z slightly upwards
G1 Z+5 E-5 F4500
; absolute XYZE
M82
G90
; move to a safe rest position, adjust as necessary
G1 X0 Y0
; relative XYZE here so that you can adjust your filament via octoprint while paused
G91
M83
{% endif %}
There is still an issue with printing from SD with runout and pausing.
But now I am able to trigger a runout from UI printing. But the notification that the Filament T0 runout is always present. Have to do some more digging.
Before print job starts
G90 ; use absolute coordinates
M83 ; extruder relative mode
M140 S80 ; set final bed temp
M104 S200 ; set temporary nozzle temp to prevent oozing during homing
G4 S10 ; allow partial nozzle warmup
M412 R S1 ;runout sensor
M412 D15 ;15mm post-sensor filament use, change if reverse bowden is replaced
M412 H1 ;enable host mode, so octoprint can respond
M413 S1 ;enable Power Loss Recovery
G28 ; home all axis
M75 ;Start Timer
After print job completes
M77 ;End Timer
After print job is paused
{% if pause_position.x is not none %}
G91
M83
G1 Z+5 E-5 F4500 ; retract filament, move Z slightly upwards
M82
G90
G1 X10 Y10 ; move to a safe rest position, adjust as necessary
G91
M83
{% endif %}
Before print job is resumed
{% if pause_position.x is not none %}
M82
G90
G92 E{{ pause_position.e }}
G1 X{{ pause_position.x }} Y{{ pause_position.y }} F4500
G1 Z{{ pause_position.z }} F4500
{% if pause_position.f is not none %}G1 F{{ pause_position.f }}{% endif %}
M412 R S1 ;Reset and re-enable filament runout detection
{% endif %}
Still having this canceling issue with SD printing.
Question: When starting a print from the SD, from the UI, should the LCD display printing information? Mine is just the home screen on the LCD.
But here is another problem. The place with the printer has no internet. So I am using a Moto One 5g with Octo4A and Octoeverywhere. This way I can monitor (also with AI) my prints, which are all over 24hr ea. So I cannot use a Pi like a normal setup. I need to print from the SD because if I print from the UI octoprint "stutters" and the print gets jacked up. So printing from UI is a NOGO.
Since this topic is getting no where, I did tons of testing and I am now able to print from the UI with "virtually" no issues. So now the need for SD printing is a moot point. But there is still a bug issue with the printing from SD canceling status on runout and pause....
I have created a post outlining my working firmware and GCODE mods here:
