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"
Date: Fri, September 12, 2014 2
Norbert,
best to ask on dev irc or dev email list.
the error is beyond my inderstanding
AND
thanks for all the great work!
tomp tjtr33
On 09/12/2014 01:38 PM, Niemand Sonst wrote:
> Thanks for the hint, I just checked from a terminal, but giving
>
> rs274 ./gmoccapy_with_cutter_radius_compensation
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
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 tklinuxc
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 i
