07-30-2019, 01:03 PM
Hello community,
we have a Closs Romat 310. Together with Albert we created a first version of a postprocessor last year. The postprocessor creates two different files (.txt with the commands and .pkt with the coordinates in pulses per degree). Now we just need one file (.txt). In this file there are the cartesian coordinates of the points and the commands.
I have created a new postprocessor with combinating the former cloos post with the kuka cnc.
In the attachment I will Show you how the program should look like (created by online programming) and how my postprocessor looks like so far.
The "List" still Needs two variables for Speed and feed (filled with the Parameters out of gcode?). The rest can be a string. The Points doesn't transfer to pulses per degree. Every Point will "saved" as in Picture 3
(STORPOSR) with his x,y,z,a,b,c coordinates.
The "GP" command has to be in cartesian coordiantes as well like the GC commands. Furthermore the coordinates and the commands has to be splitted (see attachment)
we have a Closs Romat 310. Together with Albert we created a first version of a postprocessor last year. The postprocessor creates two different files (.txt with the commands and .pkt with the coordinates in pulses per degree). Now we just need one file (.txt). In this file there are the cartesian coordinates of the points and the commands.
I have created a new postprocessor with combinating the former cloos post with the kuka cnc.
In the attachment I will Show you how the program should look like (created by online programming) and how my postprocessor looks like so far.
The "List" still Needs two variables for Speed and feed (filled with the Parameters out of gcode?). The rest can be a string. The Points doesn't transfer to pulses per degree. Every Point will "saved" as in Picture 3
(STORPOSR) with his x,y,z,a,b,c coordinates.
The "GP" command has to be in cartesian coordiantes as well like the GC commands. Furthermore the coordinates and the commands has to be splitted (see attachment)
