I got a face plate and a new bit for plywood, made some mods to the design to “optomiz” the CAM. I also changed to a larger and better bit (1/4") and best I can tell that is when this problem started. Then I proceeded to cut the final material.
The problem:
On the second arc it cuts the clockwise (G2) arc fine and then on the return (G3) it cuts a straight line vs returning on the same arcs path.
It cuts the center area (for face-plate) and the first arc fine. While cutting the second arc, on the first CCW arc it does not follow the arc, but rather a straight line back to its starting position. Subsequent arcs have similar albeit more complex forms of the same problem.
Its as if when cutting the second arc instead of a G3 move it just makes a linear move back to the start.
Consider:
It used to work…
It makes the center clearing cuts (which are arcs) and the first large arc ok, these are G2-3 cuts.
I haven’t changed the machine or the driving software
I did change some CAM parameters and the bit size
I glanced at the Gcode and I don’t see anything obvious yet, however its complex.
All of the simulations that I have run with 3 different software’s do not show this error. Everything looks fine.
This issues makes me think it’s the TinyG firmware. There were historical arc translation problems on TinyG. I thought those were all solved, but might you have an older firmware?
Hmm. The arc issue I believe is the direction that it entered into or out of the arc. Was it the exact same Gcode? I, too, have found that even on my current firmware, there is very rarely some straight line move that ruins my work piece. I think it happens if I’ve paused the job via ~ and then resumed, but it is frustrating. Although, I may be on old firmware at this point because I haven’t upgraded it in a while.
I’ve run into this. Changed post processors fanuc, fadel, haas, no success. Down revved dxf autocad files to r12 before running cam software to break arcs into lines, no success. What finally works is shutting down your computer and doing a nice clean restart of the JSON server.
Not necessarily, seems like when it happens ive been running my computer without reset for awhile, or starting and stopping json server. I run ubuntu, sometimes even though i force stopped the server and close all the terminal windows json will tell me there’s already an instance of json running. Did restarting solve your issue?
I ran into a cutting error that is baffling me.
