Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations JAE on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

N.X. 9.0 import .STP file error message

Status
Not open for further replies.

panelmethod

Aerospace
Joined
Apr 16, 2015
Messages
4
Location
US
Hello.

I'm having an odd issue; when I try to import a .stp file to N.X. 9.0, I am getting the error message 'Translation did not complete". Now, this would not be such a huge issue, but if I do a simple "open, .stp", all dimensions are by default in mm. In addition, using the simple "open, .stp" option yields some odd errors, such as models coming in as 10 times too large. How can I re-enable the import option? Any help would be greatly appreciated.
 
When you use the 'Open by Type' approach to importing data, NX uses a predefined template and by default it's Metric. If you want more control over this, first open a New 'empty' part file of the desired units and then go to...

Menu -> File -> Import ->

...and select the appropriate file format.

Now if you prefer to use the 'Open by Type' approach, you can go in and replace the default template with one using your standard units.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.
 
Thanks for your reply!

This is how I usually go about the units translation. It is also where I run into my main problem of the error message. I wasn't sure if it maybe had something to do with the settings file from the import menu (step203ug and ugstep203); there are two files, both of which result in the "translation did not complete" error. The only reason I mention those files is because I couldn't think of anything else that might affect the successful import... but its just as likely to be something else.
 
Import/export commands will generate a .log file which gives info on what happened during the import/export. If the translation got far enough to create the .log file, it should give some indication of what went wrong. For an import operation, I think the .log file will be generated in the same folder as the file to import. If/when you find the .log file, open it in your favorite text editor, it is just a text file.

www.nxjournaling.com
 
Unfortunately, the .log file ins't generated..
 
if you study the filenames of the step203ug and ugstep203 for a second you will realize when the respective file is used.
( yes, import and export)
In this case it should therefore only be the step203ug.def

Regards,
Tomas
 
I had that one selected (it was selected by default) and I was still getting the error message. I only attempted to use the other when N.X. gave me the error, for lack of a better idea as to how I should proceed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top