Parasolid Assemblies

[hudson888]

Is there any way that we can control the naming output of Parasolid Assemblies in NX. I was amazed to find having been given a file from another system with names I wanted to change that I simply could not do so. No matter how I tried too rename the files when output to Parasolid and imported back into NX they always retain the original names.

Add to that that when I output data from other NX files to Parasolid the assembly names are not the same as the original assembly whereas data from some other systems appears to be able to reproduce the correct structure.

Is there some setting I need to change?

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[hudson888]

I'm surprised and disappointed that there seems to be no way to address this question. Surely the intent when working with Parasolid data ought to be that the assembly you output is the same as the assembly that you read back in. Whether you're simply moving the data between versions of NX, dumbing it down for convenience sake or interoperating with other CAD systems. The fact that data I'm receiving from those other CAD systems seems to indicate that they DO support something like this really does make me wonder if I'm missing something.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[JonSelby]

I've not really done much with Parasolid Assemblies but when I have I've only ever wanted it to be a "dumb assembly". By that I mean that I'm not interested in changing the spacial relationship between any of the components.

Neither have I ever been bothered about identifying what the components are. If I wanted to do that I would export the individual parts as parasolids and build a new 'lite' assembly.

Possibly going off on a tangent but ... I've found with other software (notably MS Excel) that if you can't do something, then its often that its illogical to do so.
Now don't take this the wrong way, because I know your one of the respected gurus on this site and I've personally valued your input, but I always challenge my colleagues to take a step back and assess whether their workflow is sound.
That said ... NX is always evolving and by that very nature you may be on to something worthy of a user enhancement request?

Either way I hope you find what your looking for ...

Jon S

Medical Design Engineer - Glos. UK
NX 6.0.4.3 / TCE V10.0.3.8.6

 

[JonSelby]

I've not really done much with Parasolid Assemblies but when I have I've only ever wanted it to be a "dumb assembly". By that I mean that I'm not interested in changing the spatial relationship between any of the components.

Neither have I ever been bothered about identifying what the components are. If I wanted to do that I would export the individual parts as parasolids and build a new 'lite' assembly.

Possibly going off on a tangent but ... I've found with other software (notably MS Excel) that if you can't do something, then its often that its illogical to do so.
Now don't take this the wrong way, because I know your one of the respected gurus on this site and I've personally valued your input, but I always challenge my colleagues to take a step back and assess whether their workflow is sound.
That said ... NX is always evolving and by that very nature you may be on to something worthy of a user enhancement request?

Either way I hope you find what your looking for ...

Jon S

Medical Design Engineer - Glos. UK
NX 6.0.4.3 / TCE V10.0.3.8.6

 

[hudson888]

Thanks for bothering to reply Jon. It looks like we maybe the only way forward is to raise an ER. I'm somewhat surprised I must say because I would have thought that getting the Parasolid export/import process to recognise assembly structures should really be something that we wouldn't have to ask for. One wonders why the presumed understanding of what it means to have things work properly wouldn't include this.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum