[[RAM Frame Elevation DXF Export crashes]]
[[Steel column design crashes with assigned sizes]]
Exporting Reactions from RAM Structural System with ISM
[[RAM Frame Elevation DXF Export crashes]]
[[Steel column design crashes with assigned sizes]]
Exporting Reactions from RAM Structural System with ISM
Applies To | |||
Product(s): | RAM Steel | ||
First Affected Version: | 14.06.01.00 | ||
Found in Version: | 14.06.01.00 | ||
Fixed in Version: | 15.00.00.00 | ||
Area: | Import/Export | ||
Issue #: | 119960 |
Beam End Reactions are not being exported to the ISM repository when typical floor types are used for multiple stories in RAM Modeler.
This problem was fixed in Ram Structural System CONNECT Edition (version 15.0). The solution below applies to version 14.6 and 14.7.
After creating the repository re-run the RAM SS model through the various design module and then use the Update Repository command in RAM Manager to update the newly created repository. The beams created from typical floor types will be update with the reaction data.
Alternatively, create unique level types for each story initially.
(Please visit the site to view this file)
Product(s): | RAM Concept | ||
Version(s): | Various | ||
Environment: | N/A | ||
Area: | Design | ||
Original Author: | Bentley Technical Support Group |
The location in the error message is the location of a column and punching shear check in the model. The error usually occurs where multiple beams of varying thickness intersect the column creating an overly complex punching shear failure plane.
Often in those cases no punching shear check is even required (provided the beams have sufficient one way shear capacity in both directions). If that's the case simply delete the offending punching shear check to proceed. In cases where a punching shear check really is required, try simplifying the geometry to limit the number of changes in thickness at the column. For edge columns, the concrete beams or slabs should typically cover the full column area.
Modifying the punching check by reducing the Search Radius or changing the Edge Treatment could potentially help as well.
The warning message "No column critical sections were found at a punch check" or "No cutoff critical sections found" can also occur under the same conditions.
This warning is more likely when the search radius is so small that the critical section a distance "d" from the face of the support is bound to be beyond the search radius.
This error occurs when there is a potential failure plane that is a single line (in plan). As such it's not a valid punching check, though one-way shear should certainly be checked using a design strip or design section.
In some cases, reducing the punching check radius so that the circle does not cross 2 opposite slab edges is a solution.
Stud rails are extended to the extents of the search radius of the punching shear check. If the rails are extended to this point and the design is not satisfied, then no stud rails will be designed by the program.
The ACI code limits the shear strength, Vn, of the slab. See ACI 318-08 11.11.3.2, for example. If the shear demand exceeds this maximum strength, then no stud rails will be designed.
No, in Ram Concept each column reaction is used in an independent punching check, No group punching for close columns is considered.
Punching around walls is also not considered. For this reason we do not recommend checking punching for column pilasters at wall locations.
Refer to the program manual, section 66.2 "How does RAM Concept handle punching shear?" and 66.2.1"Step 1: Determine the force envelopes to be checked" for details. In brief, the program uses the column reactions, less any point loads or column above reactions inside the column shape. Surface loads around the column within the punching failure plane are not discounted from the demand.
The critical section for circular columns is approximated as an equivalent polygon with 16 sides and the properties are calculated using the resulting linear segments. This approximation is used so that the program can handle critical sections with irregular shapes.
Yes, for example, the ACI equation 11-34 indicates:
Vc = (as * d / bo + 2 ) (root f'c) bo d
but phi = 0.75
So Concept reports ( phi Vc / bo d ) as the allowable stress.
No, Ram Concept designs stud rails (including the Ancon Shear fix) but not a traditional shear cage.
No, the punching check, and potential stud rail design, is performed independently from the one way shear reinforcement in the design strip design. The one-way shear reinforcing is not considered in the punching check, and the stud rails are not considered in the one way shear check.
RAM Concept Design Strips [TN]
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Technotes | ||
Subarea: | STAAD.Pro EN 1993-1-1:2005 Implementation: Example 2 verification as per SCI P364 | ||
Original Author: | Modestas Turulis | ||
A validation PDF document and STAAD.Pro model can be downloaded from here:
(Please visit the site to view this file)
(Please visit the site to view this file)
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Technotes | ||
Subarea: | STAAD.Pro EN 1993-1-1:2005 Implementation: Example 3 verification as per SCI P364 | ||
Original Author: | Modestas Turulis | ||
A validation PDF document and STAAD.Pro model can be downloaded from here:
(Please visit the site to view this file)
(Please visit the site to view this file)
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Technotes | ||
Subarea: | STAAD.Pro EN 1993-1-1:2005 Implementation: Example 4 verification as per SCI P364 | ||
Original Author: | Modestas Turulis | ||
A validation PDF document and STAAD.Pro model can be downloaded from here:
(Please visit the site to view this file)
(Please visit the site to view this file)
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Technotes | ||
Subarea: | STAAD.Pro EN 1993-1-1:2005 Implementation: Example 9 verification as per SCI P364 | ||
Original Author: | Modestas Turulis | ||
A validation PDF document and STAAD.Pro model can be downloaded from here:
(Please visit the site to view this file)
(Please visit the site to view this file)
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | STAAD.Pro Tech Notes | ||
Subarea: | N/A | ||
Original Author: | Bentley Technical Support Group | ||
This page contains a list of TechNotes related to STAAD.Pro
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Technotes | ||
Subarea: | STAAD.Pro EN 1993-1-1:2005 Implementation: Example 10 verification as per SCI P364 | ||
Original Author: | Modestas Turulis | ||
A validation PDF document and STAAD.Pro model can be downloaded from here:
(Please visit the site to view this file)
(Please visit the site to view this file)
Product(s): | RAM Structural System | ||
Version(s): | Any | ||
Environment: | N/A | ||
Area: | Modeling | ||
Original Author: | Bentley Technical Support Group |
Whatever story height you enter into RAM Modeler, that is where the centerline of the frame beams will fall in the finite element model and vertical braces always connect to a work point at the beam and column centerlines. This is done for simplicity in the finite element analysis.
For drift sensitive structures, using a first story height that is equal to the distance from the ground level (or foundation level) up to the top of steel - average frame beam depth / 2 is probably the most accurate modeling (see "Alternate Story El." below). But using a distance from ground level to beam top of steel (a.k.a. deck bearing) is more common practice and is conservative in most aspects (see "Common Story El." below).
The common story approach is also used when the RAM SS 3D model is exported to ISM. In the ISM model the beam locations are established relative to the story datum based on the following rules:
Keep in mind, story height can also affect the following calculations:
Regretfully, in RAM Modeler, typical layout types can only be used on consecutive floor types. Furthermore, any layout that includes a transfer beam can only be used once in the story data. Consequently, a building with alternating floor types requires a unique layout type for every story.
An enhancement request has been logged to allow alternating floor types, or other sequences, where a typical layout type could be used on non-consecutive stories, but this requires many changes to the architecture of the program and implementation of the "framing tables" so it won't be possible in the short term.
Models that are synchronized with ISM also must have a unique layout type for every story.
In Ram Structural System, the framing must all be determinate, so multi-span indeterminate framing is not directly possible. There are two approaches to modeling and designing continuous beams.
The first is to model each span as a lateral beam. use the same size for each span and be sure to assign the ends to be fixed. The supporting columns also need to be lateral, but they may be pinned (in the plane of the framing). To see the accurate member forces or steel design of the beams, use Ram Frame analysis and the Steel Standard Provisions respectively.
Alternatively, for those that do not have Ram Frame, the system can be approximated using a cantilever and suspended span approach. In other words, model one span normally and add a cantilever extension into the second bay. Then add a suspended span from the end of the cantilever to the third support (or add a cantilever beam in every other bay for continuous beams more then 2 spans long). The length of the cantilever is important here since it dictates the inflection point or point of zero moment.
When using the cantilever approach one side effect is that the supporting columns will assume zero eccentricity in the design.
Yes, the option to create a stub cantilever or beam with a single support was added in version 14.02. Prior to that version a dummy column of near zero stiffness and a lateral beam with one end fixed was required.
There are some basic limitations to what you can model with RAM Structural System, so it may not be possible to model some structures perfectly, but you can usually get close. The following guidelines should help
Other things to note:
If the sloped framing causes anything to look incorrect in 3D, see [[RAM SS 3D viewer FAQ]].
When a brace needs to skip a level use Layout - brace - Add Special and follow the prompts at the bottom left.
For details on how these braces effect frame story shear reporting, please reference [[RAM Frame - Building and Frame Story Shear]].
On the upper story level model the column as a standard column (not a hanger).
On the lower level model the beam passing through the location of the column above. This could also be a beam cantilever.
Use Reference layout types (under the options menu) or construction grids to aid in the alignment of the column and beam below.
The Copy and Import from DXF features (RAM Modeler - Layout - Type menu) are only active for layout types that contain no information. These commands are deactivated in RAM Modeler even if the layout contains only grids and no other objects. To use either command, create a new layout and then use the copy or import features before any other information is defined on the layout.
In the RAM Modeler first change the material to “Concrete”. Then go to Layout>Beam>Change Material. This process also applies to columns and braces. The trick here is to set the material to what you want the member to become, not what material it initially is. This is backwards of other commands that only work on members that match the material setting.
RAM SS - Using DXF as a Reference Layout
[[Deleting a Brace that does not appear in Elevation]]
[[Multi-story sloped columns]]
[[Modeling 2D Frames in Ram Structural System]]
[[Modeling Grade Beams]]
Structural Product TechNotes And FAQs
Applies To | |||
Product(s): | STAAD.Foundation Advanced | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | General Design Solutions | ||
Subarea: | STAAD.Pro Codes | ||
Original Author: | Bentley Technical Support Group | ||
Following are the design codes supported by STAAD.Pro SS5. Users need to have suitable licenses as stated below in order to use these design codes.
STAAD US Standard Design Code License pack comprises the licenses of following design codes:
American Steel Design per AISC 360
Unified Specification - Steel member design per ANSI/AISC 360-05 and 360-10,
Since the ASD and the LRFD method are both addressed in those specifications,
they are referred to as UNIFIED
.
Steel Design per AISC
9th Edition ASD and 3rd edition LRFD
Design per American Cold Formed Steel Code – AISI 1996
American Concrete Design ACI 318 - Four versions of the
code are currently implemented: the 1999, 2002, 2005, and 2008 editions
American Timber Design- AITC 1984 and AITC 1994.
STAAD US Special Design code pack license pack comprises the licenses of following design codes.
Steel Design per AASHTO Specifications ASD and LRFD
American Aluminum Code based on ASD 1994 Sixth Edition (October, 1994).
American Transmission Tower Design Code Steel Design per ASCE 10 -97
Steel Design per American Petroleum Institute Code - based on the API 2A-WSD
standard, 21st Edition.
ANSI/AISC N690-1994 Code – needs the STAAD Nuclear Design Codes
SELECT Code Pack.
ANSI/AISC N690-1984 Code
ASME NF 3000 - 1974 & 1977 Codes
ASME NF 3000 - 1989 Code
ASME NF 3000 - 1998 Code
ASME NF 3000 - 2001 & 2004 Codes requires Nuclear Design Codes
SELECT Code Pack
STAAD Asia Design SELECT Code Pack comprises the licenses of following design codes:
Chinese Steel Design – GB 50017
Chinese Concrete
Singapore Concrete – CP65
STAAD UK Super Code license pack supports the UK codes (typically BS5950, BS8110, BS5400) and Euro codes as below with all National Annexes.
British:
BS 5950-1:2000 (steel)
BS 5950– 5:1998 (cold formed steel)
BS 8110-1:1997 (concrete)
BS 5400- 3:1982 (steel, concrete and composite bridges with amendment # 4051
and 6488)
BS 8700- 1997 (concrete structures for retaining aqueous liquids)
Euro:
EC2 ENV 1992-1-1:1991 (concrete)
EC3 DD ENV 1993-11:1992 (steel)
EC3 DD ENV 1993-11:2005 (steel)
EC5 Timber Design Per EC 5: Part 1-1
EC8 Seismic Design of Buildings
EC3 Composite
The STAAD ECC Super Code license pack supports all European codes that were previously covered by the STAAD packs Eurozone (typically French, Spanish and
German codes), North Eurozone (typically Norwegian and Finnish codes), and East Eurozone (typically Russian codes) as stated below with all National Annexes.
Euro:
EC2 ENV 1992-1-1:1991 (concrete)
EC3 DD ENV 1993-11:1992 (steel)
EC3 DD ENV 1993-11:2005 (steel)
EC5 Timber Design Per EC 5: Part 1-1
EC8 Seismic Design of Buildings
EC3 Composite
Russian:
SNiP 2.03.01-84 (concrete)
SP 52-101-2003 (concrete)
SNiP 2.23-81 (1999) (steel)
SP 16.13330.2011 (steel)
German:
DIN 1045-1:2001 (concrete)
DIN 18800: 1 & 2 (steel)
France:
B.A.E.L- 1991 (concrete)
CM66 1977 (steel)
Norway:
NS 3472/NDP (steel)
NORSK N-004 (steel)
NS3473 (concrete)
Finnish:
B4 (concrete)
B7 (steel)
Spanish:
NBE –MV103-1992 (steel)
EHE (concrete)
Swedish:
BSK 99 (steel)
BBK 94 (concrete)
Dutch:
NEN 6770 (steel)
Danish:
DS412 (steel).
Cyprus:
Cypriot Codes - Concrete Design in Cyprus
STAAD CAN/AUS/SA design code pack includes the Licenses of following design code:
Canadian Codes - Concrete Design per CSA Standard A23.3-94
Steel Design per CSA Standard CAN/CSA-S16-01
Design Per Canadian Cold Formed Steel Code S136-94
Wood Design Per CSA Standard CAN/CSA-086-01
Steel Design per CSA Standard CAN/CSA-S16-09
Australian Codes - Concrete Design per AS 3600 – 2001
Steel Design per AS 4100 – 1998
South African Codes - Concrete Design per SABS-0100-1
STAAD Indian Design Code pack includes the licenses of Following design codes:
Indian Codes - Concrete Design per IS 456
Concrete Design per IS 13920
Steel Design per IS 800 – 1984
Steel Design per IS 800 – 2007
Steel Design per IS 802 – 1995
Design per Indian Cold Formed Steel Code 801 – 1975
STAAD Japanese Design Code pack includes the licenses of Following design codes:
Japanese Codes - Concrete Design Per 1991 AIJ
Steel Design Per 2005 AIJ
Steel Design Per 2002 AIJ
STAAD Middle east Design Code pack includes the licenses of following design codes:
Egyptian 205 – Code of Practice for Steel Construction
TS 500 – Turkish Concrete Design Code
STAAD Latin American Design Code Pack comprises the licenses of following Design Codes:
Mexican Codes - Concrete Design Per MEX NTC 1987
Steel Design Per NTC 1987
Applies To | |||
Product: | RAM Foundation | ||
First Affected Version: | 15.03.00.00 | ||
Found in Version: | 15.03.00.00 | ||
Fixed in Version: | 15.04.00.00 | ||
Area: | Design | ||
Issue #: | 541339 |
When a foundation supports a braced frame and the brace is one that spans across intermediate stories (modeled using Layout - Brace - Add Special) then the resultant reaction from the brace is absent in the foundation loads giving an unconservative design.
The program is not seeing the brace when determining the foundation loads.
The issue will be resolved in the release after v15.03.00. In the meantime, either revert to the prior version 15.02.00.00, or modify the braces so that they intersect a few inches above the base. This cam be accomplished by re-modeling the braces using the "knee brace" standard configuration or by adding an extra short story at the base with only columns (and foundations) modeled.
Applies To | |||
Product(s): | RAM Structural System | ||
Version(s): | 10.0 and later | ||
Area: | Modeling; Design | ||
Original Author: | Bentley Technical Support Group | ||
Mat foundations cannot be designed in RAM Foundation. Mat foundations modeled in RAM Structural System can be exported into RAM Concept for analysis and design using the Ram Manager - Design - Ram Concept option or from within Ram Concept using File - Sync Ram Structural System - New from RAM SS.
The estimated perimeter of the mat must be modeled to encompass all of the supported columns and walls, and some concrete deck also needs to be assigned to the mat in Ram Modeler.
See the following web page for more on importing RAM Structural System models into RAM Concept:
RAM Concept-RAM Structural System Integration
Though foundations are designed in the Foundation module, they must be initially modeled like everything else in the Modeler. Rather than having a whole extra level type for foundations, we expect users to model foundations (using Layout - Foundations...) on the lowest framed level (e.g the second floor framing plan).
The allowable soil stress assigned to the footing is constant for all combinations. So, there is no good way to accommodate 1/3 allowable overstress in the design if it pertains to some, but not all of the load combinations.
We suggest incorporating the equivalent allowable overstress into the soil combos, by using reduced load factors on the combos with short duration loads.
Alternatively, the model could be designed twice; once with only gravity combos and a lowered allowable soil stress, once using gravity and lateral combos with the higher allowable.
See this blog post for details: Spread Footing Overturning and Uplift Checks in RAM Foundation
In small foundations, the longitudinal bars are only partially developed at the critical moment location. When the program reports the area of steel required it is increasing the value reported by dividing by the percentage of full development. With smaller bars the development length is shorter so less net area of steel is commonly required.
This check can be circumvented by assigning the bars to be hooked (Assign - Geometry command)
The same rule also affects continuous footings in the transverse direction.
Yes, the Foundation module uses the same live load reduction values for columns.
For lateral columns, the foundation loads should match Ram Frame analysis results.
For gravity columns, the loads can be taken from either the Ram Steel analysis results or the Ram Concrete analysis results, both of which are subject to Live Load reduction. See RAM SS Analysis Types for reasons why those two results can differ. See RAMSS Two Way Decks for limits on LL reduction for two-way decks.
In RAM Foundation, all of the force of a wall segment is applied to the continuous foundation at the center point of the wall. When a wall intersects a footing (i.e. a perpendicular wall), the forces on the walls are resolved into two end reactions considering the wall segments as a simple beam. Having a large reactions from a perpendicular wall near the end of the footing often results in a long continuous footing extension.
To minimize these effects, walls can be further segmented in RAM Modeler. So instead of drawing one 100 foot wall, four 25 foot walls can be drawn in its place. Naturally the smaller the segments, the better distribution of load you will get.
For shorter walls in groups, like an elevator core, we recommend modeling a single mat foundation under the group of walls and designing that with Ram Concept.
In v15.03.00, a change was made so that the load from the intersecting wall are no longer considered in the design of the continuous foundation in the other direction.
The size of the spread footings are first optimized for uplift and then their thickness is increased to meet any punching shear requirements. If you assign the footing the thickness needed to meet the punching shear requirement, the optimized size of the footing will be smaller.
Refer to Modeling Grade Beams
Modeling Continuous Foundations
Structural Product TechNotes And FAQs
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Concrete Design | ||
Subarea: | Design for Shear & Torsion | ||
Original Author: | Bentley Technical Support Group | ||
I am performing concrete design for a beam per the ACI code and I encounter an error message : "LOCATION FOR DESIGN FOR SHEAR AT START OF MEMBER 2 IS BEYOND THE MIDPOINT OF MEMBER. DESIGN FOR SHEAR AND TORSION NOT PERFORMED." How can I get around this situation?
STAAD performs concrete design for shear and torsion at locations defined by
(d + SFACE) from the start of the member
and
(d+EFACE) from the end of the member
respectively. The basis for this assumption can be found in Section 11.1.3.1 of ACI 318-99.
If these locations are beyond the mid-point of the member, that triggers the error message you encountered. In case you are not familiar with the parameters SFACE and EFACE, you will see in Chapter 3 of the Technical Reference Manual in Table 3.1 that these are values which the user may specify to convey to STAAD how far the face of the member is from the nodal point of the member. The default value for SFACE and EFACE is 0.0. "d" is the effective depth of the member.
So, this is what you can do. You can set the values for SFACE and EFACE to be negative quantities equal in magnitude to "d". That will result in (d+SFACE) and (d+EFACE) becoming zero, which means that the design will be performed at the nodal points of the member, thereby avoiding the situation of the design point being beyond the mid-point of the member.
So, in your input file, under the START CONCRETE DESIGN command, specify these parameters along the following lines:
START CONCRETE DESIGN
CODE ACI
SFACE -d MEMB 110
EFACE -d MEMB 110
DESIGN BEAM 110
END CONCRETE DESIGN
where "d" is the effective depth of the member.
Applies To | |||
Product(s): | STAAD Foundation Advanced | ||
Version(s): | 8.0 and later | ||
Environment: | N/A | ||
Area: | General Topics | ||
Subarea: | Modeling | ||
Original Author: | Payel Sasmal, Bentley Technical Support Group | ||
How do I stop the Auto Save dialog box popping up while I'm working on a model?
In the Home page, there is an option to turn the Auto save off as shown here. By default, this is on; clicking on it turns it off.
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | ALL | ||
Environment: | ALL | ||
Area: | Known Issues | ||
Subarea: | Known issues in STAAD.Pro SS6 | ||
Original Author: | Sye Chakraborty, Bentley Technical Support Group | ||
This page lists issues that has been observed in SS6 since it's release
Issue # | Issue Description | Workaround | Comments |
- | New STAAD.Pro Editor freezing up/crashing | Addressed in 20.07.11.45 | |
257533 | Section properties for std pipes and extra strong pipes are interchanged for AISC section database | Addressed in 20.07.11.45 | |
257492 | Some newly added wide flange section names in the AISC database had spaces in them which caused the engine to crash | Addressed in 20.07.11.45 | |
264569 | Inclined members are not being split through Geometry > Intersect Selected Members > Intersect | 1. Open the program and go to configuration 2. Set the base unit as English. 3. Open the model and go to the top menu option View > Options > Tolerance 4. Set it to 0.1 inch and click on Apply > Ok 5. Select the members and try to intersect them by going to Geometry > Intersect Selected Members > Intersect. Enter a tolerance of 0.1 inch. | |
257167 | The plots of Mz, My, Fy, Fx etc.in the Post Processing Mode > Beams -> Graph page are not displayed for the load cases or load combinations which include wind load generation | The diagrams can be seen in the graphics window by turning on the display icons for these items from the toolbar or one can double click on the individual members and go to the Shear Bending Tab inside the Member Query dialog box to see the diagrams. | Addressed in 20.07.11.45 |
257528 | When multiple tapered members are designed in group with CHECK CODE ALL command vs. designed individually, the design results do not match. Noted for multiple codes like AISC /IS 800/ S16. | The only option for now is to design these tapered members individually using CHECK CODE MEMB ... command. | |
290989 | For design as per AISC 360-05 or 10 codes, the MNZ and MNY are reported as 0 in the Steel Design tab within Member Query dialog box. This is a reporting error. | Add the design parameter called TRACK and set it to 1 or 2. Rerun the analysis and the MNZ and MNY should now be non-zero in the Member Query dialog box. | |
314845 | Design of angles and Tees fail as per the AISC code when seismic provisions of AISC 341 are checked | There is currently no workaround other than commenting out the seismic checks for these sections. | |
323889 | STAAD.Pro is not able to read the external user table files and is generating errors like
*** ERROR : FILE NOT FOUND C:\...\... | Provide the full path name to the file. For example instead of specifying
START USER TABLE TABLE 1 wf1.txt END
specify the input as shown next
START USER TABLE TABLE 1 C:\Model_folder\Model_name\wf1.txt END
| Addressed in 20.07.11.50 |
324630 | STAAD.Pro is crashing during analysis when SELFWEIGHT is applied to a list as shown next LOAD 1 LOADTYPE Dead | Please avoid using the word LIST for now and use only SELFWEIGHT Y -1. | Addressed in STAAD.Pro 20.07.11.50 |
319346 | There is an error in plotting of the axial force diagram (FX) for TRUSS members. Wedges are formed at the ends instead of a uniform plot. The values are correctly computed in the analysis. | None | Addressed in 20.07.11.50 |
329816 | For tapered member design as per AISC 360-05 code, design results are coming out different when members are designed in groups vs individually | Design the tapered members individually each with its own CHECK CODE command | Addressed in 20.07.11.50 |
290996 | When the report option Output > Steel Design Detail is used to get detailed design report, the generated report is incomplete for some codes like AISC 360-05 or AISC 360-10 | One can get the detailed design report ( TRACK 2 output ) printed in the analysis output file. A concise version of design report can be obtained by including the option Output > Utilization Ratio Table | |
357132 | Some users were not able to access the STAAD News from within the startup page and also not able to connect to the Personal Portal using the Connection Client Widget. | For those users experiencing the problem the following workaround is suggested.
| |
327465 | Design for Tee Sections as per AISC 360-10 for which critical condition is H2-1 may not be correct as software is not considering the correct section modulus for all cases. | Note : This issue is Addressed in 20.07.11.70
Workaround if using older version | |
371896 | In a Pdelta analysis with tension/compression, the pdelta effect is not considered in section force calculations unless each load case is followed by the PDELTA ANALYSIS and CHANGE. | Provide PDELTA ANALYSIS and CHANGE command after each load case for which analysis/design is to be carried out | |
358709 | The design of double angles as per IS800:LSD code is incorrect. The cross sectional properties for Y and Z axes got reversed due to which the design is being done incorrectly. | None. The fix would be available in STAAD.Pro SS6 SP2 expected to be released in March 2016. | |
376915 | Slenderness calculation and hence compression capacity caclulation for double angle sections as per IS800:2007 is incorrect. | None. The fix would be available in STAAD.Pro SS6 SP2 expected to be released in March 2016. | |
392114 | If any primary load case containing self weight is included in a Repeat Load case, the effect of self weight on member section axial forces gets ignored, thereby producing incorrect axial forces at intermediate section locations for the Repeat Load case. The values at the start and end of the member are correct. | Found to be present in versions 20.07.11.50 and 20.07.11.70. The fix would be available in STAAD.Pro SS6 SP3 | |
438681 | Deflection check as per AISC 360, IS 800, S16-14 codes are always reporting last load case in the serviceability envelope as critical load case for deflection. The design is correct and reports the correct critical ratio. It is just the reporting of the critical load case which is incorrect and that too when deflection governs. So for any design where deflection is not the governing criteria, this reporting error does not have any effect. | This error is first noted in 20.07.11.70 and will affect versions 20.07.11.50 and 20.07.11.33 too. It will be addressed in STAAD.Pro SS6 SP3 version scheduled for release in Q2 of 2016. | |
447990 | Double Channel Front to Front cannot be designed as per AISC Unified 360-05 and 360-10 codes. An ERROR: MEMBER DESIGN FAILED FOR MEMBER xx is reported |
The error in noted in version 20.07.11.70. The sections can be designed in earlier versions like 20.07.11.33, 20.07.10.65 etc. This will be addressed in SS6 SP3 release planned for Q2 of 2016. | |
460624 | Deflection check as per AISC 360-10 and AISC 360-05 is incorrect and reporting incorrect ratio and incorrect location of critical section. | The error in noted in version 20.07.11.70. As a temporary workaround, for the serviceability check, one may use the CODE AISC instead of the CODE AISC UNIFIED which would invoke the AISC 9th edition code for checking the deflection. This error would be addressed in SS6 SP3 release planned for Q2 of 2016. | |
468342 | Incorrect section properties considered for design of Pipe sections ( PIP ) when design is carried out as per IS800:2007 code and multiple members are part of the same design command ( like CHECK CODE ALL, SELECT ALL ) | This error is detected in version 20.07.11.70 and will be addressed in the build of SS6 expected to be released in Q2 of 2016. The properties are considered correctly for design when the members are designed individually (like CHECK CODE MEMB xx ). So a temporary workaround is to have separate design commands for each individual member having a pipe cross section. | |
472595 | For IS 800 2007 design, STAAD.Pro does not do bending check for I sections with slender flanges. The members may be shown as PASSed based on axial and shear checks without bending being actually checked. This is not evident unless one asks for a TRACK 2 output and hence could be misleading. |
| |
472684 | In some cases, when connections are designed using the RAM Connection module launched from within STAAD.Pro, the connection status is shown as Pass in the Design Report sheet, but shown as "No Good" in the table. | The error has been observed in version 20.07.11.70 and will be addressed in the SS6 SP3 release of STAAD.Pro expected to be released in Q2 of 2016. | |
531839 | When trying to add any design parameter as per EN 1993-1-1:2005 code, a warning message shows up saying 'Warning, Design code license is not activated. Please activate the license in order to use the code'. The software does not allow to add any design parameter or even check code command to be added for EN 1993-1-1:2005 code. The same issue has been observed for some other country codes as well like the ACI, CSA086-01 etc. | This error has been found in build 20.07.11.82. A simple workaround is presented below While adding the first design parameter, one needs to check the box 'After Current' before clicking on the Add button. The design parameter can then be added. Subsequently all other design parameters and CHECK CODE command can be added as usual without any errors. |
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | All | ||
Environment: | N/A | ||
Area: | Import Export FAQ's | ||
Subarea: | Import/Export | ||
Original Author: | Bentley Technical Support Group | ||
I do not see the option import/export using StrucLink under User Tools section.
There could be few reasons behind this.
1) You must not have installed the StrucLink while installing STAAD.Pro.
2) You may have installed StrucLink sperately, but there is a version mismatch.
To fix it, uninstall STAAD.Pro & any version of StrucLink you may have from Control Panel (Add/Remove Program or Programs and Feathures)
Reinstall STAAD.Pro, for Windows Vista/7/8 operating system, right-click on the .msi./.exe file and select the option "Run as administrator" (though you are logged in as administrator). If you run the file as the local administrator only, the program will not be installed properly. "Run as administrator" option is a must; you may need help from your IT personnel. Ensure that the check box next to the "Install companion product" is checked.
Once installation is done successfully, you should see the following options under "User Tools" section.
Note : The Export Using StrucLink and Import Using StrucLink options are now taken out from STAAD.Pro as these are not required anymore. STAAD.Pro now supports data exchange through ISM ( accessed through File > ISM ) which can be used to exchange data between STAAD.Pro and other Bentley products or third party software like Revit, Tekla Structures.
Applies To | |||
Product(s): | STAAD.Pro | ||
Version(s): | 20.07.11.33 and later | ||
Environment: | ALL | ||
Area: | Gereral | ||
Subarea: | N/A | ||
Original Author: | Payel Sasmal, Bentley Technical Support Group | ||
Description
When I am trying to create repository via ISM, I'm getting the following error message.
Explanation:
The Structural Synchronizer is not installed in the machine.
Solution
Please note that Structural Synchronizer is the engine that makes ISM work.
Install Structural Synchronizer by following the steps stated in the link below.
Software Download Instructions
Since this is a software with no charge, you can download it from the Bentley Free App page too.
Applies To | |||
Product: | RAM Frame Analysis | ||
First Affected Version: | 15.03.00.00 | ||
Found in Version: | 15.03.00.00 | ||
Fixed in Version: | 15.04.00.00 | ||
Area: | Analysis | ||
Issue #: | 537872 |
Incorrect Building Story Shear and Frame Story Shears are reported when dynamic load cases are analyzed with gravity load cases only. Correct results are obtained when only dynamic load cases are analyzed or when the dynamic loads are analyzed with both gravity and static seismic load cases. The issue affects models with semirigid diaphragms and two-way decks.
The program is not processing results for gravity columns and walls correctly.
The issue will be resolved in the release after v15.03.00. In the meantime, analyze dynamic load cases with gravity load cases and static seismic load cases.