[Issue]: Very reliable "MCU 'eboard' shutdown: Timer too close" error on simple print

[canadaohcanada]

Printer Model

Adventurer 5M

Firmware Version

3.1.5

Mod Version

1.3.4-40-gd05d6eda

Other Mods Installed

• I have installed Klipper Mod earlier.
• I have installed ZMod earlier.
• I have installed ForgeX earlier.

Screen Type

• I use Stock screen.
• I use Feather screen.

What did you do?

I have a complicated print that always fails at the same spot with the "Timer too close" error. This seems to be related to a specific model I'm attempting to print which fails reliably in two different places.

What didn't work?

To resolve this I have resized, moved, changed infill settings, etc. to try to shake it loose. When that didn't work I started turning off stuff in the Forge-X system including all of the content of this FAQ page including the "Headless mode" camera and Finally, I shaved the model really close to where it was having the issue and have provided it for your enjoyment in the attached .zip file.

I'd love it if someone else could try to print this lil' fella and see if the same thing is happening with them.

Debugging Information

debug_20250629_055046.tar.gz

Installation/Uninstallation Logs (if applicable)

I don't believe this is relevant to my issue, but the files are located in the attached .zip all the same.

Checklist

• I have read the documentation and did not find an answer.
• I have read the F.A.Q.
• I have tried rebooting the printer, and the problem persists.

Additional Information

gcode_and_3mf.zip
config_and_logs.zip

[DrA1ex]

I tested your G-code and it also caused a 'Timer too close' error on my printer. I replicated the test with Stock firmware, and it failed there too.

This appears to be a Klipper/MCU-level issue. A fix would require modified MCU firmware, which isn't currently available. The community is actively working to adapt the latest Klipper for the AD5M - if successful, we can retest to see if the issue persists.

For now, unfortunately, there's no viable solution.

[canadaohcanada]

Thanks for the reply and the confirmation that I haven't lost my mind. We can close this issue if you like or keep it open as a reminder once the new firmware is figured out.

[DrA1ex]

Let's keep this issue open for now, so others who encounter similar problems can find it

[phillipmoak]

i also have this mcu eboard shutdown. can someone lead me in the right direction of how to uninstall this firmware and go back to stock system?

[canadaohcanada]

@phillipmoak https://github.com/DrA1ex/ff5m/blob/main/docs/UNINSTALL.md . With that said, just as @DrA1ex found, my issue is related to the underlying Klipper software and not related to the mod. I suspect you have the same situation and will likely benefit from keeping the mod in place. With that said, go with your gut.

[phillipmoak]

Thanks! Sent from Yahoo Mail for iPhone On Thursday, July 10, 2025, 11:10 AM, canadaohcanada ***@***.***> wrote: canadaohcanada left a comment (DrA1ex/ff5m#40) @phillipmoak https://github.com/DrA1ex/ff5m/blob/main/docs/UNINSTALL.md — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[stevenwalton]

Is there more information about what in the firmware causes this issue? I got this error on a recent print and wondering what I can do to debug.

[github-actions]

This issue is stale because it has been open for 28 days with no activity.

[github-actions]

This issue is stale because it has been open for 28 days with no activity.