.STP File Import Error Message...

[4mranch6]

I have received a large .stp file (34MB) from a supplier and the translation fails. Here is the text I am receiving in the translation window:
"Unhandled UG exception caught.
With the following message <Internal error: memory access violation>.
Please refer to syslog for more info."

I downloaded the .stp file from a supplier FTP site.

We are using NX7.5.

Does anyone have any advice on what I might do to get this file translated?

Thanks in advance.

 

[JohnRBaker]

My advice is to contact GTAC and have them look at your STEP file.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[Toost]

The Step translator will / should write a logfile on whats goes and what don't. "initiate" a new translation and check in the "black window" where it will write the logfile. If the translation stops , the black window should state "about what" went wrong.
( The name of the log file seems to be missing in the NX75 dialogue, it used to be visible in older versions if i remember things correct.)

 

[JohnRBaker]

That is correct, except that memory access violations indicates that the problem is in the code itself and that you will learn very little of value by looking at the translator log file. However, GTAC should be provided a copy of the NX syslog file as the error will be highlighted there, but in a format which only the GTAC and development people will be able to glean anything useful from.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[braddles90]

Are you importing it using File/Import, or are you opening it using File/Open, then dropping down the 'Files of type' menu and selecting STEP? I've found (using NX6) that I can open larger files without memory errors easier than I can importing them into an existing part. I haven't touched NX7.5, but I guess it should still work the same.

Just note that if you do this, and its a large assembly, NX creates a part file for each component of the STEP assembly in the same directory the original STEP file was in, so if you have a thousand parts in that STEP file you might want to just put it in its own folder so you can keep track of them all.

 

[4mranch6]

braddles90,
I tried your idea and received the following Open error message:

"Could not open D:\Documents and Settings\aaekaga\My Documents\iM2700.stp.
The following files could not be loaded causing this open to fail:

D:\Documents and Settings\aaekaga\My Documents\iM2700.stp - Error number: 1

OK"
-----------------------------------------------------------------
John Baker,

I cannot send this file to GTAC because it contains proprietary information that cannot be disclosed.

 

[looslib]

Are you on a 32 or 64-bit system? While that may not be the reason, the different code compile may solve the issue.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[4mranch6]

looslib,
How would I determine that bit of information?

 

[looslib]

My Computer, RMB-Properties will give you the OS version.

The NX log file will tell you if you have a 32-bit version of 64-bit version. John posted this information a few days ago.

If you have3 a 64-bit system, do you have more than 4GB of memory?


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[JohnRBaker]

As for sharing proprietary information (your part files/syslogs/etc.) with our GTAC group, customers do this all of the time and we have an extensive system in place to protect your data. In fact, we assume that ALL information provided to us from any customer IS proprietary UNLESS you tell us otherwise (and sign an agreement to that effect). And once that data is in our possession it can only be shared on a strict 'need-to-know' basis (even I'm NOT allowed to see customer data that has not been released to the general population since my position has NOT been designated as being part of the 'need-to-know' community).

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[4mranch6]

Thanks for the clarification John. I have requested the supplier try and provide a .x_t Parasolid file in lieu of the .stp. If that does not work then I will submit the .stp file in question to GTAC.

As for what sytem I am running, 32 or 64-bit, I still cannot find that information. My workstation does only have 3G of memory though.

 

[JohnRBaker]

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...

Help -> NX Log File

...and when the listing window opens near the top of the listing you will find a section which reads something similar to this:

[tt]Node Name :- XXXXXXX
Machine type :- GenuineIntel Family 6 Model 5 Stepping 5, Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz
OS :- Windows NT 6.1 (Workstation) (Build 7600)
:- 32 bit software version
# Processors :- 4
:- 1 packages, 2 cores, 4 logical processors
:- cache L1 128Kb / L2 512Kb / L3 4096Kb
Memory :- 4017Mb[/tt]

The entry just below the line designated '[tt]OS[/tt]' (underlined above) will tell you what version of NX that you're running, irrespective of the what the system OS is. 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).

Anyway, I hope this helps.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[4mranch6]

Node Name :- ae413298
And there it is, thanks again John:

Machine type :- GenuineIntel Family 6 Model 15 Stepping 11, Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
OS :- Windows NT 5.1 (Workstation) (Build 2600: Service Pack 3)
:- 32 bit software version
# Processors :- 2
:- 1 packages, 2 cores, 2 logical processors
:- cache L1 128Kb / L2 4096Kb / L3 0Kb
Memory :- 3069Mb
Total Swap :- 3910Mb
Free Swap :- 2510Mb
Machine supports 3G address space
Running customer environment
Session is running in codeset 1252 17

 

[JohnRBaker]

I would say that the line which reads...

[tt]Machine supports 3G address space[/tt]

...is a give away that you're only running a 32-bit OS.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[looslib]

This line, also indicates 32-bit:
OS :- Windows NT 5.1 (Workstation) (Build 2600: Service Pack 3)

XP-64 only has 2 SPs!


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[BISPP]

I suggest that you create a "working directory" on c:.
E.g. C:\NX_work". I found that NX does NOT like "spaces" in the file search path....... Nor does it like "å, ä, ö" or the likes.... if you are in the nordic countries.