Hello guys, I have this problem where the pulg-in can’t be opened in SAP2000, I have done the method where I have to manually refer SAP2000 to the SpeckleConnector.dll and SpeckleConnectorCSI.dll. only the SpeckleConnector.dll has the OK in the add-in status as stated in this image below
Thanks for the question. I couldn’t reproduce on my end (the Connector is showing up). Would you mind:
Opening up SAP 2000, and removing the connector: Tools > Add/Show Plugins > Click on SpeckleConnector > Click Delete > Don’t forget to click Ok. Repeat for the manually loaded .dll. Close SAP 2000.
Uninstall SAP 2000 connector from manager
Reinstall lastest connector version for SAP 2000
Reopen SAP and try loading the plugin manually again (SpeckleConnector.dll)
The “Plugin completed successfully” pop-up seems to be appearing before the plugin shows, just click on Ok and wait for the connector to show.
if I select the geometry model, the sections are not imported and in SAP2000 it’s assigned as it’s default section, not my section in Revit
if I select the analytical model, the sections from Revit are imported perfectly
in both cases slabs (floor and walls) are not imported, also loads and joint restriction (i assigned fixed ends on the bottom of the columns and wall in Revit Analytical Model)
are there any solution to that?, is it a bug from my ends or right now or is it just not compatible yet to transfer slab/wall to SAP2000 from Revit
in my experience using this wonderful connector, it works perfectly in ETABS, and in SAP2000 those issues came
Sending and receiving physical (or “geometry”) model
This isn’t the supported workflow between Revit and CSi products. The behaviour you observed is expected. Bascially, the default section is just a safe fall-back such that you will at least receive some geometry in SAP 2000.
Sending and receiving analytical model
This is the supported workflow. Since CSi models are always anlaytical models, we should be sending the analytical model from Revit.
The analytical members have more information than the physical elements which can be used to transfer cross-section and material information effectively!
Floors and Walls
This is interesting! Would you mind sending me a screenshot of your logs after trying to receive the surfaces in SAP? As you mentioned, the surfaces from ETABS are working great, so SAP shouldn’t be any different.
This workflow from Revit to SAP is not supported as our understanding is that the loading patterns, cases and combos are best defined in the analysis hostApp itself. Could you share more as to the need to define loading in Revit?
Restraints
End releases are supported (on members). However, joint restraints aren’t supported from Revit. This is largely due to the fact that CSi products automatically assign restraints to nodes of new geometry coming in on the founding layer. Is this a blocker for your workflow(s)?
Thanks for your patience on this response. The nuance with SAP, is that it isn’t a buildings specific solver like ETABS. Therefore, the element-specific types like walls and floors aren’t distinguished in SAP. Rather, we just have area objects. For this reason, we can’t create the sections in the SAP model for you. This is the error you are seing in the logs (first two errors).
To fix this simply define an area in your SAP model and then you will be able to receive your geometry:
