![]() To an Engineer, the glass is twice as big as it needs to be. Of course, you can't run 64-bit NX on a 32-bit OS, but you can run 32-bit NX on a 64-bit system (which is what the log file excerpt above is indicating). The entry just below the line designated ' OS' (underlined above) will tell you what version of NX that you're running, irrespective of the what the system OS is. :- 1 packages, 2 cores, 4 logical processors OS :- Windows NT 6.1 (Workstation) (Build 7600) NX can just work with PART files so I need support. Machine type :- GenuineIntel Family 6 Model 5 Stepping 5, Intel(R) Core(TM) i7 CPU M 620 2.67GHz Hallo everybody, I want to open a STEP file with NX12 but it doesnt work. ![]() and when the listing window opens near the top of the listing you will find a section which reads something similar to this: When NX transitions to a no part environment, all dialogs are automatically closed in order to secure a safe, clean environment with no retained part dependencies such as selected objects or assumptions that parts are still open. 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.It can be a bit trying to find that information for the Windows environment, however to see which version, 32-bit or 64-bit version of NX which you're running, while you have a session of NX running, simply go to. If you open either a read-only file or a file that is already open in your CAD application or another eDrawings Viewer, a message box advises you of this. The closure of all parts in NX results in a return to the NX No Part environment. 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. ( The name of the log file seems to be missing in the NX75 dialogue, it used to be visible. If the translation stops, the black window should state 'about what' went wrong. 'initiate' a new translation and check in the 'black window' where it will write the logfile. And the receiving software has to have the ability to read/open a Parasolid file. The Step translator will / should write a logfile on whats goes and what don't. NX 10.0.2.6 RE: NX 10 - Hidden bodies after STP conversion Xwheelguy (Automotive) 11 Nov 16 17:53 Using the Parasolid export function you can only export Solid and Sheet bodies. The translation is executed first and then the resulting. Headquarters & Technical Agency 90, avenue Flix Faure F-69003 Lyon Tel +33 478 396 369 Access map. ![]() Get the latest when you sign up for our newsletter. 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. STEP files can be opened directly in NX12 just using the FileOpen command and changing the Files of type filter: Select FileImportSTEP203, STEP214, or STEP242. lbp6030w Open -stpz in ug nx Free adobe flash player download. I see no difference between opening file by importing and opening (issue is still). Sometimes, when the model is easy, the representation could be 'Entire Part'. 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. 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. Choose FileImportSTEP203, STEP214, or STEP242. It may be necessary to rename the file before NX will recognize it as a STEP file. Indeed, sorry my mistake - the parts are not hidden in Assembly navigator (instead of Part Navigator). Regardless of which STEP protocol was used to create the STEP file, NX expects a file extension of. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |