thank you so much Sir. glad that somebody willing to helping me in order to gain new knowledge in design.
↧
RE: Error in member sections
↧
Error in member sections
Hope somebody can help reviewing my modelling. i dont know the problems. this is my first time modelling in staadpro
↧
↧
RE: staad pro foundation
thank you !
↧
staad pro foundation
hi,
I am doing a foundation analysis but when i launch the design analysis a error message come on the window :
ERROR : Could not calculate design shear force and bending moment , skipping design .
Thank you
↧
RE: staad pro
Warnings say that an average thickness of the flange is taken for the design procedure and the design results are restricted to TRACK 0 in the Output file (design summary only).
↧
↧
staad pro
what does these messages means :
**WARNING** AVERAGE FLANGE THICKNESS IS TAKEN FOR DESIGN
**WARNING** TAPERED BEAM DESIGN OUTPUT RESTRICTED TO TRACK 0
thank you
↧
RE: RAM Connection Beam Setback Assignment
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.
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.
↧
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.
↧
Load Combination in Response Spectrum as per Indian code
how Can we provide load combination in response spectrum analysis method as per IS 1893 (Part-1)? Shall we consider the equivalent static method along with response spectrum method in load combination?
↧
↧
RE: OpenSTAAD | Property.CreateMemberPartialReleaseSpec
Hi Surojit Ghosh ,
The command is working well and assigning the release to the members.
But I have notice that if I create two specifications in the same macro, OpenSTAAD creates and assigns only the first release specification (START MEMBER Partial Release).
The second specification (END MEMBER Partial Release) neglects it and does not create and assign to the member.
Should I create a separate VBA macro (Sub) for each release specification?
A portion of the macro is the following:
'************************************************************************
'
' START MEMBER Partial Release
'
'************************************************************************
Dim Spec1 As Integer
'Set the flags for releases
Dim DOFRelease1(0 To 2) As Integer
For i = 0 To 2
DOFRelease1(i) = 1
Next i
'Set moment release factors if any
Dim MPFactor1(0 To 2) As Double
For i = 0 To 2
MPFactor1(i) = 0.99
Next i
'Create specification 1
'objOpenSTAAD.Property.CreateMemberPartialReleaseSpec 0, DOFRelease1(i), MPFactor1(i)
Spec1 = objOpenSTAAD.Property.CreateMemberPartialReleaseSpec(0, DOFRelease1(0), MPFactor1(0))
'Assign partial release to webs
For i = 1 To RowsW
objOpenSTAAD.Property.AssignMemberSpecToBeam webs(i, 1), Spec1
Next i
'************************************************************************
'
' END MEMBER Partial Release
'
'************************************************************************
Dim Spec2 As Integer
'Set the flags for releases
Dim DOFRelease2(0 To 2) As Integer
For i = 0 To 2
DOFRelease2(i) = 1
Next i
'Set moment release factors if any
Dim MPFactor2(0 To 2) As Double
For i = 0 To 2
MPFactor2(i) = 0.99
Next i
'Create specification 2
'objOpenSTAAD.Property.CreateMemberPartialReleaseSpec 0, DOFRelease1(i), MPFactor1(i)
Spec2 = objOpenSTAAD.Property.CreateMemberPartialReleaseSpec(1, DOFRelease2(0), MPFactor2(0))
'Assign partial release to webs
For i = 1 To RowsW
objOpenSTAAD.Property.AssignMemberSpecToBeam webs(i, 1), Spec2
Next i
The command is working well and assigning the release to the members.
But I have notice that if I create two specifications in the same macro, OpenSTAAD creates and assigns only the first release specification (START MEMBER Partial Release).
The second specification (END MEMBER Partial Release) neglects it and does not create and assign to the member.
Should I create a separate VBA macro (Sub) for each release specification?
A portion of the macro is the following:
'************************************************************************
'
' START MEMBER Partial Release
'
'************************************************************************
Dim Spec1 As Integer
'Set the flags for releases
Dim DOFRelease1(0 To 2) As Integer
For i = 0 To 2
DOFRelease1(i) = 1
Next i
'Set moment release factors if any
Dim MPFactor1(0 To 2) As Double
For i = 0 To 2
MPFactor1(i) = 0.99
Next i
'Create specification 1
'objOpenSTAAD.Property.CreateMemberPartialReleaseSpec 0, DOFRelease1(i), MPFactor1(i)
Spec1 = objOpenSTAAD.Property.CreateMemberPartialReleaseSpec(0, DOFRelease1(0), MPFactor1(0))
'Assign partial release to webs
For i = 1 To RowsW
objOpenSTAAD.Property.AssignMemberSpecToBeam webs(i, 1), Spec1
Next i
'************************************************************************
'
' END MEMBER Partial Release
'
'************************************************************************
Dim Spec2 As Integer
'Set the flags for releases
Dim DOFRelease2(0 To 2) As Integer
For i = 0 To 2
DOFRelease2(i) = 1
Next i
'Set moment release factors if any
Dim MPFactor2(0 To 2) As Double
For i = 0 To 2
MPFactor2(i) = 0.99
Next i
'Create specification 2
'objOpenSTAAD.Property.CreateMemberPartialReleaseSpec 0, DOFRelease1(i), MPFactor1(i)
Spec2 = objOpenSTAAD.Property.CreateMemberPartialReleaseSpec(1, DOFRelease2(0), MPFactor2(0))
'Assign partial release to webs
For i = 1 To RowsW
objOpenSTAAD.Property.AssignMemberSpecToBeam webs(i, 1), Spec2
Next i
↧
OpenSTAAD | Property.CreateMemberPartialReleaseSpec
Greetings STAAD Users,
I am creating a Visual Basic Macro using the Properties Command CreateMemberPartialReleaseSpec.
After a couple of tries, I have being getting trouble with this command. See the following VBA.
A portion of the macro is the following:
'************************************************************************
'
' START MEMBER Partial Release
'
'************************************************************************
Dim Spec1 As Long
'Set the flags for releases
Dim DOFRelease1(0 To 2) As Integer
For i = 0 To 2
DOFRelease1(i) = 1
Next i
'Set moment release factors if any
Dim MPFactor1(0 To 2) As Double
For i = 0 To 2
MPFactor1(i) = 0.99
Next i
'Create specification
Spec1 = objOpenSTAAD.Property.CreateMemberPartialReleaseSpec(0, DOFRelease1(1), MPFactor1(1))
'Assign partial release to tTAShe members
For i = 1 To RowsW
objOpenSTAAD.Property.AssignBeamProperty webs(i, 1), Spec1
Next i
When I run the macro OpenSTAAD creates the partial release in the STAAD file, but it does not assign the specs to the members.
Any suggestions?
↧
RE: STAAD Foundation能计算基础抗拉吗？
Translation of your question : Is STAAD Foundation able to compute foundation under tension? It is to calculate and check the foundations’ capacity under tension, such as communication tower’s foundations.
Response : Yes. STAAD Foundation can design footings subjected to tension. If the tension results in partial loss of contact with the soil, the software can adjust the pressure based on the actual contact area and design the footing accordingly.
↧
RE: STAAD Foundation能计算基础抗拉吗？
Thanks for your answer，The situation what you said is not the my question meaning，the situation what I want to check is similar to regulation 7.2.4 in ANSI-TIA-EIA-222-F-1996.
↧
↧
STAAD Foundation能计算基础抗拉吗？
STAAD Foundation能计算基础抗拉吗？验算类似通信塔基础受拉。
↧
RE: RAM Connection in STAAD Editor
No, STAAD Editor is not modified when you use RAM Connection module.
Files .cut, .rcc and .rsd are created in the same folder there the .std file is located when you design connections in RAM Connection module.
Files .cut, .rcc and .rsd are created in the same folder there the .std file is located when you design connections in RAM Connection module.
↧
RE: RAM Connection in STAAD Editor
Hi Modestas!
Thank you for your reply.
This means that the STAAD editor and RAM connection are two separate "modules", we cannot combine them, right?
Im just thinking that if for example I have accidentally deleted the .rcc .rsd and .cut files, then I have to do my connections again.
Thank you for your reply.
This means that the STAAD editor and RAM connection are two separate "modules", we cannot combine them, right?
Im just thinking that if for example I have accidentally deleted the .rcc .rsd and .cut files, then I have to do my connections again.
↧
RE: RAM Connection in STAAD Editor
Both statements are correct.
↧
↧
RE: RAM Connection in STAAD Editor
Thank you so much for your help!
↧
RAM Connection in STAAD Editor
Hello everyone. Im currently studying the RAM connection in STAAD. I have some questions below.
I would appreciate if someone can help me on these.
Is there any modification to the STAAD editor when I assign a connection in RAM?
And what file does the STAAD creates when I assign ram connection?
Thanks for your help!
↧
RE: Beam splice connection AISC
Beam splices are available for the AISC code as well:
↧