When reviewing the Report, the following failed message was noted: Unable to retrieve valid length units from the ETABS document, giving an indication of the error source.
Changes:
Re-introducing the old method for obtaining model units, this change happened in #3410. The 'old method' is needed for SAP 2000 and CSIBridge (GetPresentUnits()).
The change from the aforementioned PR remains relevant for ETABS and SAFE (GetPresentUnits_2())
A function for each respective method was created:
GetModelUnitsFromETABS()
GetModelUnitsFromSAP()
Links to the appropriate call depending on the calling application with preprocessor directives.
Screenshots:
From the community forum, model received and noted as "successfully completed", however, SAP model is empty:
After above mentioned fixes, model is well received in SAP 2000:
Validation of changes:
Fixes to SAP 2000 can have adverse effects on the other CSI products as such, sending and receiving in SAP 2000 and ETABS respectively was tested.
Description & motivation
Two community issues related to the SAP 2000 Connector doing nothing (both Send and Receive). For more context, the community issues are linked here:
When reviewing the Report, the following failed message was noted:
Unable to retrieve valid length units from the ETABS document, giving an indication of the error source.Changes:
GetPresentUnits()).GetPresentUnits_2())GetModelUnitsFromETABS()GetModelUnitsFromSAP()Screenshots:
Validation of changes:
Checklist: