Help with thread G Code

[Buckshott00]

Hello,

I'm using NX CAM 7.5.1.5 and no matter what I try I can't get the thread cycle to run correctly.

I know I need to output a G99 code to cut thread on the lathe, but no matter what I've tried it keeps posting a G98.

I've tried changing the insert type, the cutting type, the thread type, the feedrates, just about everything I could think of on the UG pallet side of things.

On the post-processor side I've changed blocks of code, the best I could get it to do was to Output a G99 but in the wrong spot and the G98 was still present further in the post so it cancelled it out.

Any advice would be much appreciated. Thanks.

Has anyone else had this problem?

 

[Buckshott00]

Thanks John,

It's not so much that I can't make the output I want with UDE it's that I want the CAM or the Postprocessor to do it correctly with a lot of input.

Plus it has to simulate correctly. When turning thread I have to show it turning correctly.

Thanks,

 

[markrief]

As noted by others, we do not provide turning canned cycle output out of the box. Canned cycles are intended to reduce file size and provide easier manual programming. In a CAM system, these are not usually issues. We provide more options and parameters than standard canned cycles, and offer more flexible tool paths.

We also have to accuratey simulate all tool motion in the CAM system, and we cannot guarantee this if we are dependent on a external CNC controller. We have seen that so called standard cycles can have many variations even among the same controller model.

We are in fact working on the output of turning cycles, and will soon be able to output Siemens CYCLE95 for example. One of the most challenging requirements was accurate simulation. Our simulation has to have access to the routines that the controller uses to move the machine axes.

So although turning cycles may seem simple for a machinist to enter at the control, generating them from a CAM system is more complicated.

As the others have shown you, if you must have turning cycles, there are workarounds available today.

Mark Rief
Product Manager
Siemens PLM

 

[Buckshott00]

Thanks Mark,

Just about everything we do here is turning. Plus, all of it has threads. So we have to have thread turning cycles, and we have old machines too, so if we Single Line these programs they would swamp the memory of those older controllers.

I'm still looking for the best way to do a lot of thread turning in CAM with the simulation that won't swamp the Controller Memory.

Thanks again.