Updated October 2014
The local axis position for braces was rotated when opening a RAM Structural System model. This has now been corrected.
In some instances, the Welcome Screen library (DLL) caused the Examples.cnx model to make RAM Connection Standalone crash when it was active. The library has now been fixed and no longer affects the connection design.
The signs for the brace-to-gusset interface (left brace only) forces in the UFM were miscalculated. This has now been fixed.
The geometric check for holes in both legs of the connecting angle on page 10-133 of the AISC 14th Edition Manual was being applied to double angle connections, when it is only applicable to single angle connections. This has now been corrected.
In connections welded to the web of the column, the rupture strength check was not considering the “Has opposite connection” option to increase the demand as explained in page 9-5 of the AISC 13th Edition Manual.
Only one of the minimum thickness checks (beam web or single plate) has to be performed, not both. This has been fixed for single plate connections.
The slip critical capacity calculation was considering erroneous factors for standard and short slotted holes when the force is parallel to the same.
The horizontal edge distance check was not being accurately calculated for bent plate connections.
The lever arm for the moment demand in the tension interface of pinned base plates was not considering the option to have the anchors inside the flanges. This has now been adjusted.
The weld length for cap plate connections was mistakenly using the width instead of the length of the plate.
The demand for the capacity of the weld in double cleat angles, was only considering the shear force and it now correctly considers the resultant force of the shear and tension forces.
Brazilian sections from the RAM Structural System database were not being recognized correctly by RAM Connection.
Models created in versions prior to v9.0.0 using AISC ASD design, were inadvertently changed to LRFD when opening them in v9.0.0 or v9.1.0. This has now been corrected.
Several other minor fixes.