I have little over four months of experience in Revit and I'm currently working on a dam project which requires me to use very specific types of wall profiles. These are thick concrete blocks which I created with generic models. Regular walls are used to support the blocks at few meters interval.
Here's the problem: If I want to export my model into Robot for structural analysis these components are missing (the walls appear fine).
Is it not possible to export Generic Models like these from Revit to Robot?
In that case any suggestions on how to get around that problem are well appreciated. Thank you in advance.
Solved! Go to Solution.
Solved by Rafal.Gaweda. Go to Solution.
Is it not possible to export Generic Models like these from Revit to Robot?
Generic Models can be imported (Open \ file type *.sat) as ACIS sat files only.
I'm having a problem when I want to assign properties to the panel that are imported to Robot like this. For example if I want to convert the panels to concrete walls with 400 mm thickness the program won't allow me.
Any ideas?
Thank you in advance.
All of the Structure objects in Robot are assigned as Panels.
I can assign the object as a wall and I can choose a reinforcement type, but that's all. It doesn´t assign material, thickness etc. which I would need to perform the analysis.
Thank you for your file it looks promising.
Can you please tell me how you created the volumetric objects from the solid objects that came with the sat file. I'm having trouble assigning material etc. to these solid objects.
This is what my model looks like:
In stead of having solid objects like in your case I only have panels and I'm not able to assign any materials or other properties to these panels. Is it possible to change the panels to solid objects after the file has been opened or is this something I can change in the Robot settings for opening .sat files.
Thanks in advance
Did you ever solve this issue?
I too am having problems in the exact same way.
How can i assign a material?
Kind regards
Andy
It may happen like this on ACIS objects. Try to replace such objects by the ones which does not have such problems.
It is registered in our database for correction.