trueprecisioncnc
Aerospace
- Feb 10, 2006
- 2
Just curious as to how other NC programmers are creating their code. At my shop, we use Catia to post aptsource files and then we run that through P-works to create the NC program in G-code format. This is very innefficient and there are numerous problems associated with it.
For instance, Catia sometimes posts a code "INTOF" in its aptsource files which causes bad NC code in arcs using circular interpolation over 180 degrees. Our programs are a mile long, partly due to Feedrate commands being repeated unnecesarily with each retract, approach, and machining moves and due to having to post entire programs point-to-point since I cannot trust p-works' circular interpolation. (Though I post all 5-axis programs point-to-point anyways, I would use g02,g03 in 3 axis machining)
My question is how are most Catia NC programmers creating their NC codes and does Catia's post work cleanly. I program 5-axis SNK's and various 3 axis machines all using Fanuc controls or aptsource files. Thanks for all opinions.
-Bryan
For instance, Catia sometimes posts a code "INTOF" in its aptsource files which causes bad NC code in arcs using circular interpolation over 180 degrees. Our programs are a mile long, partly due to Feedrate commands being repeated unnecesarily with each retract, approach, and machining moves and due to having to post entire programs point-to-point since I cannot trust p-works' circular interpolation. (Though I post all 5-axis programs point-to-point anyways, I would use g02,g03 in 3 axis machining)
My question is how are most Catia NC programmers creating their NC codes and does Catia's post work cleanly. I program 5-axis SNK's and various 3 axis machines all using Fanuc controls or aptsource files. Thanks for all opinions.
-Bryan