Objective: I am trying to send an ETABS 21.2.0 model to Speckle using the Speckle Connector 3.9.0.
Issue:
When I try to send my model, I get the following error message:
The Unit System “0” is unsupported.
I expected the model to be sent successfully since my units are properly configured in ETABS.
I also tried switching to US Default and Metric Default units, but the error persists in all cases.
Example:
ETABS version: 21.2.0
Speckle Connector version: 3.9.0
Steps:
Open ETABS project.
Configure units (tested with US Default and Metric Default).
Try to send to Speckle.
Error appears.
Screenshot: [attached project units screenshot]
Logs: Speckle.Sdk.Common.Exceptions.UnitNotSupportedException: The Unit System “0” is unsupported.
à Speckle.Converters.CSiShared.CsiToSpeckleUnitConverter.ConvertOrThrow(eUnits hostUnit) dans //Converters/CSi/Speckle.Converters.CSiShared/CsiToSpeckleUnitConverter.cs:ligne 39
à Speckle.Converters.CSiShared.CsiConversionSettingsFactory.Create(cSapModel document, List1 selectedLoadCasesAndCombinations, List1 selectedResultTypes) dans //Converters/CSi/Speckle.Converters.CSiShared/CsiConversionSettingsFactory.cs:ligne 19
à Speckle.Connectors.CSiShared.Bindings.CsiSharedSendBinding.b__17_0(IServiceProvider sp, SenderModelCard card) dans //Connectors/CSi/Speckle.Connectors.CSiShared/Bindings/CsiSharedSendBinding.cs:ligne 63
à Speckle.Connectors.DUI.Bindings.SendOperationManager.d__11`1.MoveNext() dans //DUI3/Speckle.Connectors.DUI/Bindings/SendOperationManager.cs:ligne 71
From your screenshot, I can see a mismatch between US and metric units (length unit of ft but force unit of kN). This is why you get the The Unit System “0” is unsupported. error. The “0” here indicates that your model settings aren’t one of the 16 predefined ETABS settings.
Switching to the US Default and Metric Default should have resolved the issue, however, the settings may be in a stale state. Did you try removing the model card and sending again? Or closing ETABS down / sending a different model? Model display units and model definition units may differ which could explain the persistence of this issue.
Nonetheless, custom units is something we should support. So, I have logged this and will add some functionality for parsing this correctly. I will keep you posted once this has been resolved. Would you mind sending me the original problematic model? When I switch units around, it forces me back to a consistent settings, so I can’t reproduce. Your model will help us cover some edge case(s).
Hi @Bjoern,
Thanks a lot for the explanation. Sorry about that—you made me realize that the screenshot I shared with the unit list was misleading. I had been playing around with the units, trying a trial-and-error approach to send data to Speckle.
In reality, the project was originally 100% imperial. I was the one who created the mix. I still get same error with initial unit config.
Even if I export the project as a .e2k file and then import it into a new project with a different (default) model definition unit in ETABS, I still get the same error.
I’ve successfully sent other ETABS models to Speckle, but only when the projects were metric. It looks like the issue only happens with projects that use imperial units. I’ll send you an example file in a private message.
Thanks for sending that test file over. Seemed to be an issue with the API for ETABS v21. We have found a workaround and these changes should be reflected with the next release. I’ll let you know when this is available!
Thanks a lot Björn, appreciate the quick workaround! Looking forward to the next release.
