Post-process imported clsf containing UDE events. NX standard UDE will output, custom UDE won't.

[joachimsarkimaki]

Hi,

I have exported the clsf from my operations, modified it (with feedrate optimazations) and then imported it back into NX again. After that, when post-processing, my added custom UDE:S won't be outputted (only the standard ones that's installed with NX). The pp just complaints on "unidentified text".

I have added events and templates for my custom UDE:s inside clsf.tcl and /.def to output the correct syntax inside cls when exporting. Somehow I need NX to interpret that syntax and give my UDE-variable this value when post-processing. How can I do it?

I mean, it must be possible since nx does it with its "pre-installed" UDE:s. Hopefully someone of you guys have faced this problem before.

Regards

Joachim Särkimäki

 

[joycejo]

My first question is why are you outputting the .cls? I'm sure you must have a good reason.

Does the imported .cls contain the UDF text?

If that is the case then you will need to interpet the text that is now being output. Look at the MOM_text proc in the ug_post_base.tcl

You may want to copy this to your post and modify it to include the text that is now being output.



John Joyce
N.C. Programming Supervisor
Barnes Aerospace, Windsor CT
NX6.0.5.3

 

[markrief]

I also wonder why you are using a CLS?

If you post an operation with an imported path, you are no longer using the internal tool path and UDEs.

Mark Rief
Product Manager
Siemens PLM

 

[joachimsarkimaki]

Thanks for your replies!

The reason why I have to use the cls is because I'm using a advanced third party optimization software which only handles cls anp apt-files!

Yes, I know that the internal data is not used after importing. But it's possible to modify the clsf.tcl and clsf.def to output all necessary data to the cls (which works as a post for the internal data to output a cls).

My problem now is that I can't find the program piece that does the opposite (that is to interpret the imported .cls and send the right events to my g-code post-pro).

Regards

Joachim

 

[joycejo]

Why not use Machine control operation outside of the imported tool path to place the UDE's

Keep the imported data to just the tool motion.

John Joyce
N.C. Programming Supervisor
Barnes Aerospace, Windsor CT
NX6.0.5.3

 

[joachimsarkimaki]

If it's mill_control you mean, that doesn't work. That was the first work around I've tried..