Issues I've run into

[SShadow1974]

I have run into a few issues. #1 it seems the WebUI doesn't install the latest version of the firmware. I manually updated it which solves the original problems I had. Not going to go into those, since they're old news now. I had commented on your YouTube video, but perhaps that's not the best place to get your attention though you have replied to other comments. shrug
So, on to my current issues. My settings are 30000 wait on start up and my timeout is at 6000. I'm powering the ESP via USB and not using the OEM runout sensor.
#1 no matter what I set the startup timeout to, it will always pause somewhere between layer 1 and 2 on every print I've done.
#2 Sometimes when the printer is told to pause, "pausing..." will appear on the display and not go away. I have to power cycle the whole machine, after which it will recover and start printing again.
#3 It will randomly pause for no reason. The filament is running fine and isn't tangled. Unfortunately I don't have a cap of the error from the logs.

Suggestions
Longer log scroll back or a separate tab that retains errors so you can go back and look the error up.
List the version somewhere of the firmware somewhere so you can reference which version is installed on the ESP32

[SShadow1974]

Well it just paused on me after I posted this. Here is a log:
9/6/2025, 2:29:30 PM: Sending Ping
9/6/2025, 2:29:30 PM: Received status update:
9/6/2025, 2:29:33 PM: Received status update:
9/6/2025, 2:29:35 PM: Checking WiFi connection
9/6/2025, 2:29:36 PM: Filament movement stopped, last movement detected 6000ms ago
9/6/2025, 2:29:36 PM: Pause condition: 1
9/6/2025, 2:29:36 PM: Filament runout: 0
9/6/2025, 2:29:36 PM: Filament runout pause enabled: 1
9/6/2025, 2:29:36 PM: Filament stopped: 1
9/6/2025, 2:29:36 PM: Time since print start 1616789
9/6/2025, 2:29:36 PM: Is Machine status printing?: 1
9/6/2025, 2:29:36 PM: Print status: 13
9/6/2025, 2:29:36 PM: Pausing print, detected filament runout or stopped
9/6/2025, 2:29:36 PM: Waiting for acknowledgment for command 129 with request ID d94911415e2848ef96eae30c3482233f
9/6/2025, 2:29:36 PM: Command 129 acknowledged (Ack: 0) for request d94911415e2848ef96eae30c3482233f
9/6/2025, 2:29:36 PM: Received expected acknowledgment for command 129
9/6/2025, 2:29:36 PM: Pause condition: 1
9/6/2025, 2:29:36 PM: Filament runout: 0
9/6/2025, 2:29:36 PM: Filament runout pause enabled: 1
9/6/2025, 2:29:36 PM: Filament stopped: 1
9/6/2025, 2:29:36 PM: Time since print start 1617116
9/6/2025, 2:29:36 PM: Is Machine status printing?: 1
9/6/2025, 2:29:36 PM: Print status: 13
9/6/2025, 2:29:36 PM: Pausing print, detected filament runout or stopped
9/6/2025, 2:29:36 PM: Waiting for acknowledgment for command 129 with request ID 5d61ecdcf9b64c4c9f12cbecf18bf307
9/6/2025, 2:29:36 PM: Received status update:
9/6/2025, 2:29:36 PM: Command 129 acknowledged (Ack: 1) for request 5d61ecdcf9b64c4c9f12cbecf18bf307
9/6/2025, 2:29:36 PM: Received expected acknowledgment for command 129
9/6/2025, 2:29:36 PM: Pause condition: 1
9/6/2025, 2:29:36 PM: Filament runout: 0
9/6/2025, 2:29:36 PM: Filament runout pause enabled: 1
9/6/2025, 2:29:36 PM: Filament stopped: 1
9/6/2025, 2:29:36 PM: Time since print start 1617425
9/6/2025, 2:29:36 PM: Is Machine status printing?: 1
9/6/2025, 2:29:36 PM: Print status: 13
9/6/2025, 2:29:36 PM: Pausing print, detected filament runout or stopped
9/6/2025, 2:29:36 PM: Waiting for acknowledgment for command 129 with request ID 30d005d828514955b384dd928d78191d
9/6/2025, 2:29:36 PM: Received status update:
9/6/2025, 2:29:36 PM: Command 129 acknowledged (Ack: 1) for request 30d005d828514955b384dd928d78191d
9/6/2025, 2:29:36 PM: Received expected acknowledgment for command 129
9/6/2025, 2:29:37 PM: Filament movement started
9/6/2025, 2:29:40 PM: Received status update:
9/6/2025, 2:29:43 PM: Received status update:
9/6/2025, 2:29:43 PM: Filament movement stopped, last movement detected 6000ms ago
9/6/2025, 2:29:44 PM: Received status update:
9/6/2025, 2:30:00 PM: Sending Ping
9/6/2025, 2:30:05 PM: Checking WiFi connection

I checked the filament, there is no issue with the filament. Moving freely. This time it did not leave the "pausing..." on the screen, so I can resume it. Maybe a "RESUME PRINT" button could be added to the Web interface? Or is that just a one way communication from the ESP to the webbrowser?

[SShadow1974]

Caught it when it paused again:
9/7/2025, 10:32:22 AM: Received expected acknowledgment for command 129
9/7/2025, 10:32:22 AM: Pause condition: 1
9/7/2025, 10:32:22 AM: Filament runout: 0
9/7/2025, 10:32:22 AM: Filament runout pause enabled: 1
9/7/2025, 10:32:22 AM: Filament stopped: 1
9/7/2025, 10:32:22 AM: Time since print start 446673
9/7/2025, 10:32:22 AM: Is Machine status printing?: 1
9/7/2025, 10:32:22 AM: Print status: 13
9/7/2025, 10:32:22 AM: Pausing print, detected filament runout or stopped
9/7/2025, 10:32:22 AM: Waiting for acknowledgment for command 129 with request ID 039b73bd2ce340c397bde9d2c46d9a50
9/7/2025, 10:32:23 AM: Command 129 acknowledged (Ack: 1) for request 039b73bd2ce340c397bde9d2c46d9a50
9/7/2025, 10:32:23 AM: Received expected acknowledgment for command 129
9/7/2025, 10:32:23 AM: Pause condition: 1
9/7/2025, 10:32:23 AM: Filament runout: 0
9/7/2025, 10:32:23 AM: Filament runout pause enabled: 1
9/7/2025, 10:32:23 AM: Filament stopped: 1
9/7/2025, 10:32:23 AM: Time since print start 446985
9/7/2025, 10:32:23 AM: Is Machine status printing?: 1
9/7/2025, 10:32:23 AM: Print status: 13
9/7/2025, 10:32:23 AM: Pausing print, detected filament runout or stopped
9/7/2025, 10:32:23 AM: Waiting for acknowledgment for command 129 with request ID 80cf6a37b5d241239a35ab2154764eef
9/7/2025, 10:32:23 AM: Received status update:
9/7/2025, 10:32:23 AM: Command 129 acknowledged (Ack: 1) for request 80cf6a37b5d241239a35ab2154764eef
9/7/2025, 10:32:23 AM: Received expected acknowledgment for command 129
9/7/2025, 10:32:23 AM: Pause condition: 1
9/7/2025, 10:32:23 AM: Filament runout: 0
9/7/2025, 10:32:23 AM: Filament runout pause enabled: 1
9/7/2025, 10:32:23 AM: Filament stopped: 1
9/7/2025, 10:32:23 AM: Time since print start 447289
9/7/2025, 10:32:23 AM: Is Machine status printing?: 1
9/7/2025, 10:32:23 AM: Print status: 13
9/7/2025, 10:32:23 AM: Pausing print, detected filament runout or stopped
9/7/2025, 10:32:23 AM: Waiting for acknowledgment for command 129 with request ID a8a30eedd7324aa08255d4b8ffc76f7a
9/7/2025, 10:32:23 AM: Received status update:
9/7/2025, 10:32:23 AM: Command 129 acknowledged (Ack: 1) for request a8a30eedd7324aa08255d4b8ffc76f7a
9/7/2025, 10:32:23 AM: Received expected acknowledgment for command 129
9/7/2025, 10:32:25 AM: Filament movement started
9/7/2025, 10:32:26 AM: Received status update:
9/7/2025, 10:32:29 AM: Received status update:
9/7/2025, 10:32:30 AM: Sending Ping
9/7/2025, 10:32:30 AM: Checking WiFi connection
9/7/2025, 10:32:31 AM: Filament movement stopped, last movement detected 6000ms ago
9/7/2025, 10:32:32 AM: Received status update:
9/7/2025, 10:32:36 AM: Filament movement started
9/7/2025, 10:32:37 AM: Received status update:
9/7/2025, 10:32:37 AM: Received status update:
9/7/2025, 10:32:37 AM: Received status update:
9/7/2025, 10:32:37 AM: Received status update:
9/7/2025, 10:32:37 AM: Received status update:
9/7/2025, 10:32:45 AM: Received status update:
9/7/2025, 10:32:57 AM: Received status update:
9/7/2025, 10:33:00 AM: Sending Ping
9/7/2025, 10:33:00 AM: Received status update:
9/7/2025, 10:33:00 AM: Checking WiFi connection
9/7/2025, 10:33:02 AM: Filament movement stopped, last movement detected 6000ms ago
Logs are automatically refreshed every 5 seconds.

[s3anami]

This is all happening to me too

[jrowny]

are you using orca slicer or elegoo slicer?

[jrowny]

are you able to build the firmware on your own? Would you be able to test this branch? #24

[s3anami]

Orca slicer

[SShadow1974]

v0.2.2 still pausing for no reason, even at 15000 timeout. At least at 30000 start up, it's not pausing at the very beginning of the print any longer. But will pause on the final layer, almost every print. LMAO I have to hit resume just for it to clean the nozzle, the extruder to do a little dance, and then go back to the purge bin and then I get the print finished dialog. It's hilarious the little issues that what something that seems so simple can cause.

[jrowny]

if it reliably reported the layers, I could fix it, but it doesn't, at least not with orca slicer.

[SShadow1974]

if it reliably reported the layers, I could fix it, but it doesn't, at least not with orca slicer.

Sorry, but I'm a dummy here... What does Orca have to do with this? Isn't the ESP32 just determining what the SFS is reporting? How does the ESP32 interact with Orca? I could install the Elegoo slicer and try that - but I'm just trying to understand the why behind it. Having never tried Elegoo Slicer, I don't really have a preference for a slicer, I've just always used Orca since I started 3D printing.

[jrowny]

Orca slicer is missing the gcode that reports layer progress so current layer doesn't work when slicing with orca. You can modify orca to work

[SShadow1974]

Orca slicer is missing the gcode that reports layer progress so current layer doesn't work when slicing with orca. You can modify orca to work

So what you mean is some gcode has to be included in the "start gcode" or one of the other sections in the printer settings? Did you list what changes should be added somewhere? I'll go take a look at your doc.

[SShadow1974]

I couldn't find reference to the gcode here in your GitHub, so I queried Gemini and this is what it returned... Does this look plausible?

G-Code
M118 E1 L

Explanation
M118: This is the Marlin gcode command for "Echo". It sends a message back to the host (in this case, your ESP32).

E1: This specifies the echo type. E1 is a special type that makes the message an "alert" or "notification", which some host software (like an ESP32 with a specific firmware) can be configured to listen for.

L: This is the placeholder for the current layer number. Orca Slicer automatically replaces this with the correct integer value during slicing.

You should place this command in Orca Slicer's custom G-code settings, specifically in the "After layer change G-code" section.

[jrowny]

Generally a good ol fashioned search will be better than Gemini, https://github.com/Chirimorin/CCOrcaLayerNumberFix

[SShadow1974]

Generally a good ol fashioned search will be better than Gemini, https://github.com/Chirimorin/CCOrcaLayerNumberFix

Yeah, never thought of searching GITHUB... I'm a new user to GitHub, didn't even know to search here. Surprised Google search didn't come up with a link to that page, though.

Anyways, so I went to that link, saw the two lines of code and when I went to input them into my printer settings... They're already there. And have been there since I installed Orca slicer and added this printer.

So what does that mean, since those lines were supposed to fix these issues? Have I still done something wrong with my installation (using the wrong firmware.bin file or something?)