As these tend to vary between manufacturers...
Are these the turning rough/?/threading cycles?
I know NX (9?, maybe 8.5) supports the Siemens control's OD roughing cycle for turning.
At some point (when I get a few spare femtoseconds of free time) I was hoping to play with that to see if enough data exists to output Fanuc/Okuma roughing cycles. At this point I just don't know.
G76/G9[2/6] can be supported. but you have to suppress a LOT of output (normal G3x threading outputs 4 lines per pass). Search UGanswer for some example code, but you'll probably have to update it.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled
As my understanding We output G code before, We need use Nx and Nx post to make Nc file out. If we have no Nx post processor to support. Nx can not work G71,,etc,,,cycle out. So my issue is Where I can change in post processor?
The problem is that there are many cycles, so what kind of cycles are you talking about (drilling, turning, pocket, etc.)?
Each kind of these cycles have their own place in post builder where they are defined.
Production: NX12.0.2, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX (1876) | AWC 3.4 Preparing: -
Employees of the customers, together we are strong
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
In the past it has been a case of total customization of your post.
The way I've accomplished this is to create custom UDE's to switch on the cycles. The UDE's contain the parameters; rough feed rate, DOC, etc. The operation would use the finish turn template and an Approach Marker to trigger the G71 cycle. The post is written to handle the UDE. Typically, the sequence numbers are not output except on the P and Q blocks so the post can easily "predict" the Q value (P+1). The P and Q values are stored for the next G70 to use. So it's not pretty but it does the trick. Definitely not OOTB. I must say though that I haven't looked for this functionality in NX since long ago when machine memory was not so big. Maybe they have something now...