Quantcast
Channel: RAM | STAAD | ADINA Wiki
Viewing all articles
Browse latest Browse all 8748

STAAD.Pro is considering incorrect Cw values in some situations leading to incorrect LTB capacity calculations when designing per AISC 360-16

$
0
0
Revision 1 posted to RAM | STAAD | OpenTower Wiki by Sye on 7/8/2020 10:45:12 PM
 Product:STAAD.Pro
First Affected Version:
 Found in Version:22.04.00.40
Fixed and Released in Version: 
 Area: Steel Design as per AISC 360-16
 Issue #:1101622

Problem Description

The AISC 360-16 code check is considering incorrect value of Cw for non-General UPT sections and non-Isections (WF, S, M, HP types) like Channels when the following conditions co-exist

The model contains General UPT sections or I-section (WF, S, M, HP types).

The sections mentioned in (a) are designed in the same CHECK CODE command along with non-General UPT sections and non-Isections (WF, S, M, HP types) and the former sections are checked ahead of later

For the above situations the software is incorrectly considering the Cw value used to check the last General UPT sections or I-section (WF, S, M, HP types) and using that for the other section types. This is causing the LTB checks to be incorrect for the other section types.

.

Workaround

There are a couple of workarounds which may be used

  1. If all the general UPT section or  I-section (WF, S, M, HP types) are put in the same CHECK CODE command along with other members, the other section types should be specified ahead in the member list.
  2. The general UPT section or  I-section (WF, S, M, HP types) and non- general UPT section or non- I-section (WF, S, M, HP types) may be used in separate CHECK CODE commands.

Solution

The defect is being addressed and a fix will be available in the upcoming STAAD.Pro CONNECT Edition V22 Update 5, scheduled to be released in September of 2020.

Tags: AISC 360-16, Known Issues

Viewing all articles
Browse latest Browse all 8748

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>