Home
Reply
Regular Contributor
sawarsi
Posts: 64

problem with importing a STEP file

a customer sent me a step file which contains two solids and when i read it in then get only a single body. even the Simple program in the samples directory shows one body. however, when i have a colleague read the file with Interop their output shows two bodies. i am using the same options for the converter but getting different results. please see the output from the two programs i don't see a difference in the options but i am getting different results.

i tried this with R21SP3 and R22SP1 with identical results.

 

see the attached files. any ideas what may be wrong?

 

Regular Contributor
sawarsi
Posts: 64

Re: problem with importing a STEP file

furthermore, when i run BRepInfo on the file it also shows 2 bodies, etc.

 

Regular Contributor
sawarsi
Posts: 64

Re: problem with importing a STEP file

ok, i got it work so that i now get 2 bodies however, please explain what the problem was.

 

here is the code that i had:

 

     SPAIAcisDocument imported_data;

     SPAIUnit unit;

     src.GetUnit(unit);

     imported_data.SetUnit(unit);

 

using this i got one body when i replaced it with:

 

     SPAIAcisDocument imported_data;

     SPAIUnit unit;

     SPAIUnit requestedUnit(SPAIUnitMeter );

     imported_data.SetUnit(requestedUnit);

 

WHY did this work??? the unit in the src was millimeters.

 

 

Spatial Employee
AmolK
Posts: 12

Re: problem with importing a STEP file

Hello Sawarsi,

 

I've gone through the two log files provided by you and except OS and Nb. of Solid Bodies there is no difference in the my_results.txt and correct_results.txt.

 

Now your analysis of the problem is that using the two methods to set the target-unit you are getting different results.

 

That is, when you set target unit as meter then you get two bodies and for target-unit mm you get one body.

 

Looking at the nature of the problem, we suspect that the problem may be occurring because the bounding box in the source STEP file.

 

That is "the source file bounding box may be larger than the ACIS supported bounding box" which is likely to be the root cause.

 

To confirm this, it is possible to share the file?

 

Thanks,

With best regards,

DS-SPATIAL Cilent Care

Regular Contributor
sawarsi
Posts: 64

Re: problem with importing a STEP file

sorry, the file is extremely confidential and i am not allowed to share it. is there someway i can verify this for you? i do intentionally ignore invalid bounding box messages.