cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Rhino to Pro/E imports

Highlighted
Newbie

Rhino to Pro/E imports

Hi everyone,



We use Rhino for conceptual ID work and then Pro/E for detailed design.
At this point in time we use the imported Rhino file as a template to
then create unreferenced Pro/E geometry however this is time consuming
and has issues depending on the user when it comes to maintaining the
detail of the ID intent. We have played with the new native Rhino
import functionality and also with step and iges but find that we get
lots of geometry issues when it arrives in Pro/E (mismatched
intersections, distorted boundaries etc). The issue with the new import
functionality is also that the accuracy and units are locked so using
master model techniques is a big problem.



I would be very interested in getting feedback from other users that
also use Rhino and Pro/E on how they handle the work flow. Have you
found a good import method that does not have the geometry issues? Are
there things that the Rhino users have to pay particular attention to or
do so that the geometry come out is good?



In an ideal world I would like to be able to import the Rhino model into
a master surfaces file and then use copy geom functionality to then
build my master models. I know the principle will work but it requires
good geometry to start off with!



Look forward to your comments.



Kind regards



Jason Anderson

Product Development Manager



Marinco Electrical Group

Product Design Centre

Auckland

New Zealand


1 REPLY 1

RE: Rhino to Pro/E imports



In Reply to Jason Anderson:


Hi everyone,



We use Rhino for conceptual ID work and then Pro/E for detailed design.
At this point in time we use the imported Rhino file as a template to
then create unreferenced Pro/E geometry however this is time consuming
and has issues depending on the user when it comes to maintaining the
detail of the ID intent. We have played with the new native Rhino
import functionality and also with step and iges but find that we get
lots of geometry issues when it arrives in Pro/E (mismatched
intersections, distorted boundaries etc). The issue with the new import
functionality is also that the accuracy and units are locked so using
master model techniques is a big problem.



I would be very interested in getting feedback from other users that
also use Rhino and Pro/E on how they handle the work flow. Have you
found a good import method that does not have the geometry issues? Are
there things that the Rhino users have to pay particular attention to or
do so that the geometry come out is good?



In an ideal world I would like to be able to import the Rhino model into
a master surfaces file and then use copy geom functionality to then
build my master models. I know the principle will work but it requires
good geometry to start off with!



Look forward to your comments.



Kind regards



Jason Anderson

Product Development Manager



Marinco Electrical Group

Product Design Centre

Auckland

New Zealand