da file st5 a nx

[doriano]

Good evening.
having solids created with st5 I should bring them to the table with nx but I have problems.
being the 2 siemens software I thought they were compatible but I'm afraid I have to turn them into stp.
if there are other solutions
thanks to all

 

[alex64]

Hi.
Unfortunately that I know even if they belong to the same "ditta" are not compatible with each other, or rather, nx sees the files of st5 and recognizes them as such but in practice when you load them you lose all the features, if then you have to put them into the table in practice it is as if you have a parasolid or similar. from here on you have to manage any changes with the synchron or adding features.
no know if there is a " feature recognizer" or similar tool in nx.

Hi.

 

[cacciatorino]

Good evening.
having solids created with st5 I should bring them to the table with nx but I have problems.
being the 2 siemens software I thought they were compatible but I'm afraid I have to turn them into stp.
if there are other solutions
thanks to all

Actually, I think the interoperability should be there, with the limits already expressed on the lack of recognition of features, but both cads should still upload the files of the other. Maybe your problem is that your nx is too old to recognize solid edge st5 files.

 

[The_Matrix]

from nx you make a simple "file/open" and you choose the solidedge file type.
Obviously with the limits expressed by hunting and alex.
I, personally, never step by these direct interfaces, but through the jt that is a much more reliable format regarding:
- attributes
- colors
... but if the problem is just to put on the table, the direct opening is good. (i.e. if you have an attribute in yourself and you want to put it on the table, in a note or in the cartilage, better the jt)

 

[supertramp]

if from nx (from 8.0 onwards I'm sure) do open files find both the .asm axiemi and the .par of the individual components if. once open proceed with the drafting environment. The only interoperability I used is this: each .par opened in nx in the feature tree makes a feature appear that at the time you do the update goes to update the model according to the changes that were made in .par.
So (I don't know if that's what you need) but you can open the .par with nx to make the table. then if you change in if the initial .par returns in nx in model environment update the only feature, go in drafting and update the table.

 

[doriano]

if from nx (from 8.0 onwards I'm sure) do open files find both the .asm axiemi and the .par of the individual components if. once open proceed with the drafting environment. The only interoperability I used is this: each .par opened in nx in the feature tree makes a feature appear that at the time you do the update goes to update the model according to the changes that were made in .par.
So (I don't know if that's what you need) but you can open the .par with nx to make the table. then if you change in if the initial .par returns in nx in model environment update the only feature, go in drafting and update the table.

thanks to all (supertramp,cacciatorino,alex64,the_matrix )
Unfortunately while having the latest version of nx the st5 files are recognized as step, or parasolid in poor words lose all history.
my problem is not so much to put in the step table, but are any modifications of the original st5 files, and the most serious are the threaded holes that being only virtual do not exist in the steps or similar.
go to recreate threads is not only expensive but annoying.
I can understand from different companies but from the usual one expects compatibility.
a greeting to all

 

[The_Matrix]

thanks to all (supertramp,cacciatorino,alex64,the_matrix )
Unfortunately while having the latest version of nx the st5 files are recognized as step, or parasolid in poor words lose all history.
my problem is not so much to put in the step table, but are any modifications of the original st5 files, and the most serious are the threaded holes that being only virtual do not exist in the steps or similar.
go to recreate threads is not only expensive but annoying.
I can understand from different companies but from the usual one expects compatibility.
a greeting to all

nx and if they are compatible slightly more than nx with any other competition cad.
the procedure described:
- I make models on if
- I read models in nx
- I make nx boards
... preserves the association. then if you change the files if the nx tables are updated (to see what happens at odds)
with regard to threads, unfortunately there is little to do, each cad treats the "cosmetic" features in a particular way and the combatability is practically never there.
if you want, put a file if simple (cube with threaded hole) in these formats:
- native if
- step.
- jt
and I'll give you some evidence with a recent version of nx and tell you if something is preserved.
(apart from rereading in itself the step or the jt immediately understands what keeps you or not)