khapple
commented
9 years ago I just ran into this bug trying to visualize some g-code produced by a cam software I was trying. chilipeppr displayed my interpolated hole just like the bottom right example which made it appear like a peck drilling operation. This had me concerned that the cam software I was trying wasn't working very well. I found this issue report and I went in and added a line break after every single G17 command and chilipeppr displayed perfectly. Would love to see this corrected automatically.
chilipeppr
Hi, I was wondering why chilipeppr did not display some of my gcode correctly. I could finally reproduce it with a simple test case: The attached gcode contains 4 shapes like the digit 8 (see output of OpenSCAM, this is also how tinyg interprets it). First shape, lower left: Done with G2 and G3 with paramters I and J (circle center). All OK here. Second shape, upper left: Done with G2 and G3 with parameter R (radius); 270 degree arcs cannot be specified uniquely by radius, gcode interpreters take it as a 90 degree arc. Note how chilipeppr does it right for the G3, but not for the G2. Third shape, upper right: Same, but 270 degree arcs are broken up as 180 + separate 90 degree arcs. Fourth shape: Like the first one, but the G2 and G3 are written on the same line as a G17 (in my understanding perfectly legal). Chilipeppr ignores the complete line.
Not a very big or urgent problem as it only affects the preview with some types of gcode, but probably also not hard to fix.