Possible bug in G3 (arc) command

General Discussion
1

Dear devs,

I have uncovered what appears to be a repeatable bug in the G3 (arc) command. I have a print that stops every time, with log entry “Internal error in command: G3”. The gcode file has been post-processed by Arc Welder but some slicers are now incorporating arc generation directly so this might be a latent bug that is just now getting uncovered. I have a log file and gcode file but nowhere to upload them… it doesn’t seem to be possible to create issues on GitHub against Klipper. How would you suggest we proceed?

Best regards,
Tim Long

2

Hello @NameOfTheDragon !

Would be interesting to know what G3 command was sent that caused the error.

3

It’s a little different opening an issue concerning Klipper than usual on Github Contact - Klipper documentation

Good luck, hcet14

1 Like
4

This looks to be the offending line…

Upcoming (2524913): u'G3 X210.727 Y214.978 I-6.478 J18.383 E2.91982; perimeter\nG1 X210.326 Y214.953 F30000 ; move to first perimeter point (minimum ac'
5

Too many instructions, TL;DR - I slipped into a coma reading them. I think I’ll just let someone else report it. Thanks for the heads-up.

6

Upload a klippy.log and a sliced gcode file here. Zip them if too big

7

G3-issue-klippy.zip (5.7 MB)
Ah, I had missed the upload button, I’m used to seeing a paperclip icon and didn’t register the upload icon. OK, here they are…
Cheers,
Tim Long

8

Your issue is not related to G3. In fact the error message is Timer too close. The other errors are consequential errors.
When checking a klippy.log always start at the bottom and work your way up until you find the first error

1 Like