cancel
Showing results for 
Search instead for 
Did you mean: 

Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

Creator
Creator

Hi Anybody having similar issue when the clsf output is different for legacy lathe in version dif?

Expecially those operation path was created is older version,

any method to deal with the different for operation path.

 

there 2 things was found currently with legacy lathe

1). Feed and speed wasn't output into clsf and shown rapid.

2). TLANGL and RADIUS could not output.

3). Any idea to unlock the access to change the parameter for a tools ( show in attachment)

 

 

CharlesOw

 

6 REPLIES

Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

Esteemed Contributor
Esteemed Contributor

Note there are several options when exporting the CLSF - did you try some of the other ones?

 

TLANGL and RADIUS -  For some reason, Siemens keeps "disappearing" them every couple versions.  Then enough users complain and they put them back. (deep sigh)

 

Note the CLS export is very similar to the UGpost architecture, so you can create your own (or copy from a previous version that worked) - edit the tcl/etc.  I believe the same variables are used (although I'm not 100% sure) so if you know how to do it in a post, you can do it in the CLS

Folder is ...\MACH\resource\tool_path\

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

Creator
Creator

Hi Ken,

 

I did 2 test,

1). change directory of tool_path to nx7.5 tool_path but show error.

2)  change directory of mach to nx7.5 mach folders and nx 10 working, but still the same issue with tlangl ,rad & feed rate issue.

 

Need your guidiance as i not really familiar with ugpost and clsf.

 

Charlesow

Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

What CLSF template are you selecting when you output?

 

Do you have sample CLSFs of the same operation output in 7.5, 10.0.3, and 10.0.3 after generating? 

 

Mark Rief
Retired Siemens

Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

Creator
Creator

Hi Mark

 

I was using CLSF output standard.

 

Here you go OD facing program sample.

 

Charlesow

Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

Creator
Creator
While this will not solve your problem, have you ever used "WinMerge" to compare txt files like your CLSF? It just makes life easier trying to spot the differences.
 
Andy.

Re: Dealing with CLSF Differences for legacy lathe to upgrade to NX 10

I agree that does not look right.

Please log a call with GTAC so that development can investigate it.

Mark Rief
Retired Siemens

Learn online





Solution Information