3.8.1: Export Model to DStV π·
Communication between Karamba3D and RStab or Robot works via βDStVβ-file which is a βSTEPβ- derivative.
In order to create an exchange file place a βExport Model to DStVβ-component on you definition and feed it with a model via the βModelβ-plug. The βPathβ-plug lets you chose a name for the exchange-file. RStab names cross sections and materials depending on the selected language. Therefore set RStab to βEnglishβ before importing Karamba3D DStV-files. The output-plug βDStVβ returns the export-file as a list of strings which can be viewed with a βPanelβ- component. Check the output of the βInfoβ-plug to see whether Karamba3D encountered problems during export.
The different versions of RStab and Robot interpret some aspects of DStV data differently. For example distributed, projected loads will not be imported correctly in all versions of RStab. Therefore you should always compare the structural response calculated with the exported model in RStab or Robot to that obtained with Karamba3D. In DStV-files the export of standard cross sections works via their name. RStab and Robot show slight differences in naming them: for example a βHEAA100β in Karamba3D is the same as a βHE100AAβ in Robot and a βHE100Aβ in RStab. In order to get the standard cross sections right one needs to convert their names in the exported file. Karamba3D applies the conversion tables βCrossSection NameAliases_Robot.csvβ and βCrossSectionNameAliases_RStab.csvβ for Robot and RStab respectively.
One can open them with either a text editor or a spreadsheet program. In case the first row contains a β#β the rest is a remark. The second row contains the cross section name as used in Karamba3D, the third the alias, the fourth a user defined name or nothing. Currently the name conversion tables which come with Karamba3D do cover many but not all cross section names. In case there is no alias for a cross section name it gets exported as a non-standard cross section.
Last updated
Was this helpful?