We have some users utilizing Rhino to build from the industrial design team defining Boat models and when it’s transferred to our Engineering and CAD team which uses a different CAD solution. It’s coming over as 1 CAD file with numerous sub-elements being defined through a series of layers. The receiving team needs to be able to have the CAD file broken down into sub-elements like Assemblies, Parts, etc. which will enable us to reduce the effort of conversion as opposed to having one file.
We would like to do a training session with the Rhino team on how to achieve this process. Is this something we can request for next week?
would this group of 1230 surfaces be considered one part? or is the rod a part, each bracket a part and then one set would be an assembly (with 2 instances), which are part of the overall assembly?
Correct an assembly of two standard instances of the same components. The rod is a part, each bracket a part and then one set would be an assembly (with 2 instances), which are part of the overall assembly.
There isn’t enough information in the file to create that structure. You can create layer structure that will do that for you, or add user text (key / pair values) that help organize.
Here is a python script that asks you for the folder to export to then exports each layer with the original filename + layer name as the file.
Run the ScriptEditor command and open the attached file. Users can make a button referencing this script once refined.
Thanks for the script can we have a team’s call with you on the deployment for one of our users. My IT would like to have that if possible to sort out what we are missing to deploy.
To be able to export this into a solid modeler with a part assembly organization the model must be organized correctly.
Surfaces cannot be grouped, but must be joined together into closed polysurfaces.
Then each “part” must be made into a block. For instance the brackets that hold the pipe would be one block, then copied and oriented to match the orientation of the 8 instances it exists in the model. This of course will be one part instanced 8 times. Other parts are the table top, pipe and pipe endcap.
Once all blocked and instanced, then use STEP to export the model and that should get across to catia as parts. Then will need to externalize the parts if they want them to be stored outside the model. Which STEP flavor will need to be experimented with.
This will be helpful for my Rhino users. When they build that data moving forwards. We do have a Rhino Convert to CATIA license which have been using currently and it’s tremendously helpful.
But the users have to first manage their data as you have proposed with Polysurfaces and Blocks.
