Home
Reply
Contributor
stress97
Posts: 8

problem when converting iges file to sat file

[ Edited ]

Hello.

 

I have a probelm when converting iges file to sat file.

 

our application tried to to import the attached IGES file, but no geometry was imported into our application.

As a workaround, I used NX6 to import the IGES file and the geometry appeared with no problems. I then exported the NX6 model to a new IGES file. Then I imported this new NX6-generated IGES file into our application , and the geometry was successfully imported.

so, I used InterOp sample
I attach iges file,log file and sat file.

I want to know what is the problem.


Thanks and Regards
kihoon

Contributor
Sarvnaz
Posts: 25

Re: problem when converting iges file to sat file

I tried this with R20 as well and I can't get anything to get translated. This could be a bug. I tried many options, but nothing gets translated. I recommend you submit an incident for this. That way, we can confirm if it is a bug and log a bug for it.

Thanks

Sarvnaz

Contributor
stress97
Posts: 8

Re: problem when converting iges file to sat file

Sarvnaz

 

Thank you for prompt reply.

but, how do i submit an incident for this ? 

 

kihoon.

 

Spatial Employee
RTadlock
Posts: 40

Re: problem when converting iges file to sat file

Hi Kihoon,

 

I've taken a look at this case, and I've got a question.  How did you create the original reg.igs file?  Based on the header information, it appears that it was generated by exporting a 2D sketch from SolidWorks 2008.  I tried to reproduce this problem, by exporting the reg.igs file from SolidWorks 2008 and 2009 and I get a file that converts correctly, but more importantly has different entity types saved in it.  Based on what I've seen, you shouldn't be able to create a file like you did from Solidworks 2008.  The file you gave us has no 3D geometry, and that is why nothing gets translated.  So in order for me to go any further with this problem, I'd like a little more information regarding how you generated this file.

 

Thanks,

 

Robert Tadlock

Technical Account Manager