This must be why the last couple of programs the guys have ran, gremlin won't display the back plot on Gmoccapy, or give a fault description, but it will run the program and make good parts. I ran the program with Axis on my test PC, and immediately got a fault when loading the program about radius end points being different on some G03 moves that were making chamfers on some shoulders.
Rick -------- Original Message -------- Subject: Re: [Emc-developers] How to check G-Code before executing with python From: "Niemand Sonst" <nie...@web.de> Date: Fri, September 12, 2014 2:38 pm To: "EMC developers" <emc-developers@lists.sourceforge.net> Thanks for the hint, I just checked from a terminal, but giving rs274 ./gmoccapy_with_cutter_radius_compensation.ngc and selecting the corresponding tool table, I get an error, that cutter radius compensation is not OK, but it is definitely correct. Or I do a mistake in using it, or it is buggy Norbert Am 12.09.2014 20:06, schrieb TJoseph Powderly: > Hello > maybe you could use the SAI ( Stand Alone Interpreter found in > ...src/emc/sai ) > and have a python wrapper to call it , > then python examine the output ? > regards > TomP tjtr33 > > On 09/12/2014 12:51 PM, Niemand Sonst wrote: >> I found the following problem with gmoccapy and gscreen and also tklinuxcnc. >> >> If you do load a file with an error in the gcode, you will not be >> informed about the error until the interpreter gets there. >> In difference, axis will take notice of the error and will not even >> start the program. >> >> Just include something like G4A6 in a file of your choise and use a 3 >> axis machine, and you will see what the problem is. >> >> I tried to understand how axis does this, but I am lost in MyGlCanon, >> canondraw axis.py and so on. I do not understand that. >> >> So now I am looking for a solution to check the code using python. >> >> Anyone an idea? Or does someone know how axis does handle that? >> >> Thanks for any help. >> >> Norbert (gmoccapy) >> >> ------------------------------------------------------------------------------ >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
