Newer Post Older Post Home. The third and final attempt was to create every single element type that was contained in the ETabs model, the trick for automatic mapping of elements is to create the element within Revit and make sure the name is exactly the same as the name within ETabs, or so i thought……. Unfortunately, this post is more of the same. Will be loaded if not already loaded.
|Date Added:||24 July 2009|
|File Size:||15.3 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
A total of 21, errors 17, Element join errors Line too short errors 32 Point Load errors 40 Wall Errors and a huge database log file csixrevt a lot of error messages. To save myself another hours for the second trial I set up a beam family within the Revit template named in accordance with the CSiXRevit documentation and purged out all other families from the project file.
If CSiXRevit cannot easily map the names, then you can set the mapping at time of import. There is a table in the CSi guide that shows the naming of the families that have to be loaded into the Revit template prior to import, these are essentially the out of the box families. There was a desire to get the model into Revit so the people involved in the project could take a closer looks at the facade framing which was fairly complex in nature.
Will be mapped to equivalent Revit Structure sections. I still maintain a view that the bi-directional link between analysis packages and Revit will not work fluently, this was exposed when I trialled Revit and Robot interoperability, it can be read about in the post above, and there are extensive discussions from myself on AUGI.
This means you could easily have 3 concrete beams csicrevit are exactly the same size, but all have different names because the material is different. In this post I am going to take you through my findings when going from ETabs to Revit. To facilitate the mapping of concrete sections, it may help if you have the various Revit Structure sections already loaded before you import your ETabs model into Revit. Equivalent Revit Structure sections will be automatically created and mapped See note 1 Note 1.
CSiXRevit - Civil Engineering Community
Newer 20013 Older Post Home. However, I do see real added value in going in the other direction depending on the complexity of the building in question. This came about with a project that had been modelled in ETabs but documented in AutoCAD, I cannot name the project or show any images of the project but it involved 2 36 story approx xsixrevit coming down onto a podium level with 4 or 5 stories below the podium. Steel Sections Will be mapped to equivalent Revit Structure sections.
The few concrete members that mapped automatically were all the same size and all other framing members were steel. In the past I have written posts about the links between Revit and CSC Fastrak and the links between Revit and Robot these posts have generally pointed out more problems than solutions. cdixrevit
If a time saving can be made by building a Revit model first then exporting into an analysis package I strongly believe we should be taking advantage of that efficiency. If you would like CSiXRevit to be able to automatically create equivalent Revit members of families you must load at least one member of the family for CSiXRevit prior to import.
Unfortunately, this post is more of the same. This would allow me to see whether or not the CSiRevit tool could automatically create csidrevit members as suggested above.
Revit Add-Ons: CSiXRevit - ETABS and Revit Structure Link
The next step was to let the CSi Exchange tool do all the work, after all the CSi documentation does say that:. My initial idea was to simply import the ETabs model into Revit using our default template file and see what the results are.
Having said that, I was left with a Revit model, the geometry was there despite the members being incorrect. The next step was cslxrevit let the CSi Exchange tool do all the work, after all the CSi documentation does say that: The third and final attempt was to create every single element type that was contained in the ETabs model, the trick for automatic mapping of csisrevit is to create the element within Revit and make sure the name is exactly the same as the name within ETabs, or so i thought…….
Despite my thoughts on bi-directional interoperability, I do still see a benefit in linking analysis software to Revit.
Will be loaded if not already loaded. The ETabs model contained 18, individual members.
The third csixdevit was complete with 13, element join warnings, and a total of warnings from CSiXRevit itself. This process was quite cumbersome but once complete I felt confident the import process would be a success.