Hi! As far as I understand from the other replies, EMC should not be the software that solves these problems. However, as I develop on a gcode manipulating software, maybe this would be better suited. http://code.google.com/p/grecode/ All the gcodes are read to memory, and it would be relatively little work to find these concave corners, and do automatic joining of line segments, especially near the corners. However, I am a bit short on time currently to implement this. If you know/want to learn C++, and like hacking a bit, maybe my code could be a nice starting point.
Btw, I had similar problems with radius compensation, while hacking the gears-gcode-creator at http://www.thingiverse.com/thing:1963 very nice greetings, bernhard On 8/19/2010 2:54 PM, Viesturs Lācis wrote: > Hello, guys! > > I have been running my waterjet cutting machine with EMC for a while > now (currently that is version 2.4.3.1) and I have gathered few > questions about the way, how EMC interprets the g-code. > > The main issue is that sometimes I receive this error message: > "Arc move in concave corner cannot be reached by the tool without gouging" > > It also indicates the number of the line in the g-code, which is near > the one, causing error. So I found that in the following piece of code > the G3 move was the problem: > G1 X+115.175 Y+245.013 > G3 X+118.786 Y+245.339 I+1.484 J+3.720 > G1 X+120.236 Y+246.394 > > I have G41/G42 tool diameter compensation commands included as well as > there is M6 T1 command in the beginning of the file and in the tool > table I have saved the size of the water jet as a tool number one, so > that EMC compensates the kerf size. The confusion is caused by the > fact that saved diameter is 1.1 mm and in the code above we can see > that radius of the G3 move is larger than half of the tool's diameter, > which has to be offsetted. > > > I just received also this error message: > "Straight feed in concave corner cannot be reached by the tool without > gouging" > It indicated that the error is around line 24, so here is the part of the > code: > G1 X+167.031 Y+46.741 > G1 X+167.643 Y+46.983 > G1 X+168.223 Y+47.330 > G1 X+168.364 Y+47.433 > G1 X+168.364 Y+23.726<--line24 > G1 X+147.289 Y+23.726 > G1 X+147.289 Y+54.982 > > The code consists of very small G1 moves. Unfortunately the CAD > drawing consisted almost only of splines, which are not very welcome > by my CAM application, so it converted the splines in very small > straight segments. That is why that file consists of 16344 lines, so I > do not see an option of manual correction of the code. > > Can anyone explain, what is that EMC does not like about the g-code > and what can I do to correct it? > > Thank You in advance! > > Viesturs > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
