jhardy1
Structural
- Jan 26, 2004
- 930
We are having trouble importing models into Staad.Pro (e.g. importing CIS/2 *.stp files) where the nominated section properties reside in multiple section property libraries in Staad.Pro. For example, we often design structures using hot-rolled sections (UB / UC etc) for the main beams and columns, but cold-formed members (CHS / RHS / SHS tubes etc) for bracing and secondary members, and these section properties are found in a different section property library to the hot-rolled members.
The problem arises even when the model is created in Staad.Pro, exported as a CIS/2 file, and then imported back into a new empty Staad.Pro model - no third-party application is required to generate the issue!
For example, see the attached zip file, containing two Staad.Pro models, and one CIS/2 file:
• “Built in Staad.Pro.std” is a simple frame of just three members, which was built using Australian sections (310UB40 for columns; 250x150x6 RHS for the beam) in Staad.Pro.
• CIS/2 file “Built in Staad.stp” was exported from Staad.Pro
• New Staad.Pro model was created, and “Built in Staad.stp” was imported. The 310UB40 columns were imported correctly, but the 250x150x6 RHS beam was not.
• This imported model was saved as “Imported from Staad.Pro-generated CIS2.std”
It would appear there is a fundamental problem that Staad.Pro cannot import CIS/2 files correctly if members have to be mapped to more than one Staad.Pro section property library; either that, or we need some assistance configuring Staad.Pro properly to enable such models to be imported correctly.
We have raised this with Bentley support, so far without success. Has anyone else observed this problem, and / or know of a fix?
The problem arises even when the model is created in Staad.Pro, exported as a CIS/2 file, and then imported back into a new empty Staad.Pro model - no third-party application is required to generate the issue!
For example, see the attached zip file, containing two Staad.Pro models, and one CIS/2 file:
• “Built in Staad.Pro.std” is a simple frame of just three members, which was built using Australian sections (310UB40 for columns; 250x150x6 RHS for the beam) in Staad.Pro.
• CIS/2 file “Built in Staad.stp” was exported from Staad.Pro
• New Staad.Pro model was created, and “Built in Staad.stp” was imported. The 310UB40 columns were imported correctly, but the 250x150x6 RHS beam was not.
• This imported model was saved as “Imported from Staad.Pro-generated CIS2.std”
It would appear there is a fundamental problem that Staad.Pro cannot import CIS/2 files correctly if members have to be mapped to more than one Staad.Pro section property library; either that, or we need some assistance configuring Staad.Pro properly to enable such models to be imported correctly.
We have raised this with Bentley support, so far without success. Has anyone else observed this problem, and / or know of a fix?
