Is there a reason why you're creating STEP files from NX and importing them back into NX? Other than checking the translation results (which as you have already seen isn't 100% accurate for checking how it will behave in other CAD softwares), that seems like a long way around opening an NX file directly or using a Parasolid export. Based on what you're describing, that's the way I'd test it out & see what happens. Your surface bodies aren't going to automatically be added to the PART reference set (I think that's what you mean by "final part reference set") and in order for the translation to show those bodies (in NX at least) you're probably going to have to either add them in the source NX file OR after opening or importing the STEP change your reference set to Entire Part. So the issue becomes clearer now that all details are given. NX 10.0.2.6 RE: NX 10 - Hidden bodies after STP conversion Xwheelguy (Automotive) 11 Nov 16 17:53 The reference set was my first try, while I've pressed all parts into the final part reference set, then the STEP file did not contain hidden bodies by default. RE: Parts are not appearing in assembly markvdh (Industrial) (OP) 20 Apr 16 22:05. I see no difference between opening file by importing and opening (issue is still). UG/NX Museum: The secret of life is not finding someone to live with Its finding someone you cant live without. Sometimes, when the model is easy, the representation could be 'Entire Part'. Your 3D file will be automatically rendered for you to view instantly. Click inside the file drop area to upload a file or drag & drop a file. The models are done by surface design and for the representation on the assemblies, I use reference set that contains only the last detailed solid body. How to view a 3D file using Aspose.3D viewer app. Then in the Part Navigator there are some bodies hidden by default. When I'm done with STEP transition, I open the STEP file once more in NX. The objects on layers 5, 41, 44, and 63 all come from imported part files. You can import the stp files by using step/stp import function. Indeed, sorry my mistake - the parts are not hidden in Assembly navigator (instead of Part Navigator). Our company produces one-off products that are exported to a step file with objects on specific layers broken down like this: Layer 1 - Solids. That's how it works with floating licenses, but a bundle is a bundle is a bundle.To make it completely clean: I export selected objects (by clicking on them) to the STEP file, they are not hidden while I'm selecting them. But if I opened 2 sessions and was doing modeling in both I would have checked-out ONE Gateway and ONE Modeling license. So getting back to what happens with floating licenses, if I opened 2 sessions and in one I created a model while in the other I create a drawing, it have checked-out ONE Gateway as well as ONE Modeling and ONE Drafting license. So there are no individual licenses to check-out and then check back-in. They can't be separated and thus don't start in the same manner as does a seat of Gateway which simply waits to check-out application licenses whereas the bundle has already 'checked out' everything which it contains, all in one hit. However bundles don't behave that way, hence the term 'bundle'. When we refer to 'not taking an extra license' that was relative to floating licenses, meaning that it would not take an additional Gateway license to start the second seat. RE: Display multiple parts at once? man2007 (Aerospace) 13 Jan 10 00:51 To an Engineer, the glass is twice as big as it needs to be. And if you tried to start two separate TeamCenter sessions on the same workstations, this could be even more difficult to get the desired behavior. If however you're working from within TeamCenter itself and launch NX by 'opening' a part file associated with a TeamCenter record master, if you tried to do that with a second file, it would just assume that you were opening a second part in the NX session that was already running (although there are ways to change that, this would be the default behavior). If you've configured NX to start in the so-called 'managed-mode', where NX automatically connects to TeamCenter when you ask to open a file or create a new one, then there should be no problem at all. To answer Hudson question, Yes, you can run two separate sessions on the same workstation even if you're running with TeamCenter, but it does depend on how you access TeamCenter whether this would be easy or not.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |