RAM Connection Beam Setback Assignment

I am using RAM Connection integrated with STAAD.Pro V8i and am running into an inconvenient issue with setbacks in my connections.

1. I have created several custom templates where I have clearly defined the beam setback "sb" and checked it in both the GUI and the .con text file, however once assigned the setbacks automatically default to 0".

2. Once I manually enter the setbacks, if I alter the beam/girder configuration on any connection, every setback I have manually defined throughout the model defaults back to 0".

Are either of these known issues? I am trying to make these standard connections for my colleagues to use and it would be less than desirable to have them do any alteration to the connections once they're assigned.

Parents
  • Beam setbacks are defined in the joint within Ram Conenction stand-alone. Just like the member sizes or brace angles, the beam setback can only be set by the host applciation, not saved within the individual conenction designs (aka the Connection Pad).
    We need to enhance this so that changes in the beam setback can be made and saved in the connections themselves, or in the template for new connection types as you noted. This has been previously logged as Enhancement 567021: Beam Setback and Is Column End Settings Changes are Not Saved in Connection Pad.



Reply
  • Beam setbacks are defined in the joint within Ram Conenction stand-alone. Just like the member sizes or brace angles, the beam setback can only be set by the host applciation, not saved within the individual conenction designs (aka the Connection Pad).
    We need to enhance this so that changes in the beam setback can be made and saved in the connections themselves, or in the template for new connection types as you noted. This has been previously logged as Enhancement 567021: Beam Setback and Is Column End Settings Changes are Not Saved in Connection Pad.



Children
No Data