Basic Information: Printer Model: Voron trident (Rpi Zero 2 w) MCU / Printerboard: Octopus + BTT EBB36 klippy.log klippy.log (1.9 MB) Describe your issue: I turned on Arc fitting in PrusaSlicer (G2/3 I J), to reduce the size of my gcode files a bit, and this seemed to work fine on a bunch of …

As mentioned by @LifeOfBrian the initial error is a “Timer too close”. The rest of the errors are IMHO purely consequential to this and should be disregarded. Hard to tell if this is related to using arcs or not. Generally, I do not see any valid reason to use arcs with Klipper: A 3D printer is …

Either in addition or related to the above error your have the following as well: MCU 'toolboard' shutdown: Timer too close See here: [image] Timer too close Knowledge Base Timer too close Background A “Timer too close” error occurs when the MCU is asked to s…

Would be interesting to see the parameters of the G2 command. Do you have some code lines?

If I’m reading the log right this should be the recent code: Y115.309 E.14327 G1 X73.011 Y115.323 E.00269 ;WIDTH:0.41646 G1 X72.928 Y115.337 E.0025 ;WIDTH:0.38292 G1 X73.098 Y114.687 E.01814 M204 S3000 M204 S5000 G1 X72.902 Y116.075 F24000 M204 S4000 ;WIDTH:0.449999 G1 F12000 G1 X75.948 Y113.029 E.…

According to this: [image] Internal error in MCU 'mcu' stepcompress Knowledge Base Internal error in MCU ‘mcu’ stepcompress Background An unforeseen issue in the stepcompress logic has happened. Reasons This is an error that should not happen under normal …

Connected to the Rpi I have the Octopus board, a BTT EBB36, and also a “Microsoft Modern webcam”, but I have it capped at 1 fps, and 640*360, so very low. Everything runs over USB. I can try to run the file again with the webcam disabled if that rules out any MCU timeout issues. I had been runnin…

If G2 X75.89 Y113.605 I.04 J.02 E.00301 is the culprit here this is maybe just too tiny for the (step) calculation. In your printer.cfg you have set: [gcode_arcs] resolution: 0.05 The default is 1.0 Maybe you can just for testing purpose set it again to 1.0 and retry your failing gcode after a…

Did a test with the resolution set to 1.00 and did not see issues. I had the arc value at 0.05 because I think this is what is used by Octoprint arc welder, although I don’t know if that value translates directly to Klipper. 1.00 seems very high, considering I often have arcs with radius 0.5 in my …

“Timer too close” is an error that is created on the host side. You are using a pretty weak host (Rpi Zero 2 w) and in combination with quite an extreme resolution, I could imagine that this is causing the issue. Graphing your log’s content yields: [image] Which shows a pretty high peak in the h…

I was under the assumption that there were no downsides to the arc welding (wrongly so apparently), so for me smaller files without any downsides made sense. Based on what you’re saying it seems like I should go for something like a RPI 4b for my next printer then, since rpi zero 2w has the rpi 3B …

Internal error on command:"G2"

General Discussion

EddyMI3D December 12, 2023, 8:41am 5

According to this:

@koconnor may have a look on this.

Topic		Replies	Views
Internal error on G1" stepcompress error General Discussion	24	2278	January 5, 2024
Klipper Internal error on command:"G1" General Discussion	33	696	May 4, 2025
Unknown command G2 and G3 General Discussion	4	17145	June 13, 2021
Internal error in stepcompress after upgrading to v0.11.0-303 on CR-10S with Raspberry Pi 4 and Ubuntu ARM General Discussion	3	597	October 21, 2023
Possible bug in G3 (arc) command General Discussion	7	1271	April 3, 2023

Internal error on command:"G2"

Related topics