<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>E P's Communities Activities</title><link>https://communities.bentley.com/members/2e06a4d2_2d00_b39c_2d00_4882_2d00_8aa4_2d00_e1e09acdb4d6</link><description>Recent activity for people in E P's community</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Code Checks for Dutch Flats</title><link>https://communities.bentley.com/products/ram-staad/f/ram-staad-forum/129531/code-checks-for-dutch-flats</link><pubDate>Tue, 13 Dec 2016 00:59:41 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:af8f902a-147f-4078-a58f-ad15efef8774</guid><dc:creator>E P</dc:creator><description>&lt;p&gt;I am aware that code checks are not carried out for user defined plates.&lt;/p&gt;
&lt;p&gt;For this reason I tried to use the pre-loaded Dutch plate/strip profiles, thinking that the program would know it is a flat and use the appropriate section of the code to calculate the code capacity.&lt;/p&gt;
&lt;p&gt;However, I ran into problems. One model (it was a complex model) simply crashed if I changed one of the members to a Dutch flat returning &amp;quot;Exception [Unkonown (-529697949)] Raised! Aborting Analysis.....&amp;quot;&lt;/p&gt;
&lt;p&gt;So I tried a simple model consisting of 3 nodes, 2 supports and a node load applied at midspan. &amp;nbsp;This time the model didn&amp;#39;t crash but the figures for the code check seem to be incorrect.&lt;/p&gt;
&lt;p&gt;STAAD says the member fails with a utilisation ratio of infinity. This is due to it having a shear capacity of zero (AISC 360-10 ASD):&lt;/p&gt;
&lt;p&gt;SHEAR: FORCE: CAPACITY: RATIO: CRITERIA: LOAD CASE: LOCATION(ft):&lt;br /&gt;MAJOR(VZ): 0.001 0.000 Infinity Eq. G2-1 1 0.000&lt;br /&gt;MINOR(VY): 0.001 0.000 Infinity Eq. G2-1 1 0.000&lt;br /&gt;INTERMEDIATE: Aw: Cv: Kv: h/tw: Vn:&lt;br /&gt;MAJOR(VZ): 0.000 0.000 5.000 Infinity 0.000&lt;br /&gt;MINOR(VY): 0.000 0.000 5.000 Infinity 0.000&lt;br /&gt;&lt;br /&gt;TORSION: FORCE: CAPACITY: RATIO: CRITERIA: LOAD CASE: LOCATION(ft):&lt;br /&gt;0.000 0.000 Infinity Eq. H3-1 1 0.000&lt;br /&gt;INTERMEDIATE: Fcr: Tn:&lt;br /&gt;0.000 0.000&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is this a hopeless case and I should give up trying to force STAAD to do a code check for plates? Or am I making a silly error somewhere?&lt;/p&gt;
&lt;p&gt;Version: 20.07.10.41&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Grid Data not Available</title><link>https://communities.bentley.com/products/ram-staad/f/ram-staad-forum/124934/grid-data-not-available</link><pubDate>Wed, 17 Aug 2016 04:01:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:0c50c0eb-acf0-4402-b2fa-7bace40c37d5</guid><dc:creator>E P</dc:creator><description>&lt;p&gt;I have a pile-support mat foundation which I imported from STAAD into STAAD.foundation.&lt;/p&gt;
&lt;p&gt;I specified the mesh and added piles. &amp;nbsp;I ran the analysis.&lt;/p&gt;
&lt;p&gt;But when I go to do the design the program returns: &amp;quot;Grid data not available. Design aborted&amp;quot;&lt;/p&gt;
&lt;p&gt;Can someone advise why this is and what I need to do to avoid this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>STAAD shear calculation error for AISC 360-10</title><link>https://communities.bentley.com/products/ram-staad/f/ram-staad-forum/105551/staad-shear-calculation-error-for-aisc-360-10</link><pubDate>Fri, 20 Mar 2015 01:22:50 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:81b38edf-2eac-44bd-a341-d5e5442f7a40</guid><dc:creator>E P</dc:creator><description>&lt;p&gt;Hi All,&lt;/p&gt;
&lt;p&gt;I have noticed that STAAD incorrectly calculates the shear capacity for a member.&lt;br /&gt;&lt;br /&gt;Specifically, it uses a VERY large shear area (overstated by a factor of 2!).&lt;br /&gt;&lt;br /&gt;Here is the output for an Australian 250UC72.9:&lt;br /&gt;&lt;br /&gt;INTERMEDIATE:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Aw:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cv:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Kv:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; h/tw:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Vn:&lt;br /&gt;MAJOR(VZ):&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7.454&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.000&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.200&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 8.944&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 194.597&lt;br /&gt;&lt;br /&gt;The depth of a 250UC72.9 is 254 mm and the web thickness is 8.6 mm which yields an area of 2184 mm^2 (3.385 inch^2). STAAD uses 7.454 inch^2 which is 2.2 times larger, causing the final capacity to be similarly overstated.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Is this intended?&amp;nbsp; Has anyone else experienced this problem?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>