composite beam

i analise a composite beam using staad.pro  select series 1 20.07.06.23, i did de entrance of the beam in the same staad.

afer i analyse i receive the next warning "  ***WARNING: MEMBER 1 HAS COMPOSITE PROPERTY ASSIGNED TO IT AND HENCE THE MATERIAL CONSTANTS ARE SET AS THOSE OF STEEL. CURRENT SPECIFICATION IS IGNORED EXCEPT DAMPING RATIO.

then i did the entrance in staad.pro release 20.07.05.15 and ran it in the same release and i dont get that warning. if i use this file in the release 20.07.06.23 i dont receive the warning  why ??

 

thanks in advance

  • It looks like that warning is displayed any time a composite section is defined, even if the Material is already set to Steel.

    If you evaluate the results by comparing the deflections of members with and without the composite specification, you can see that the composite beams are more stiff, all else being equal.  So it looks like the composite section properties are being taken into consideration in the design, and the warning is just making us aware of the fact that STAAD.Pro is automatically using the Steel material for any beam with a composite section.

    I don't know why the new version would not throw the warning for the model created in the previous version.  Are you sure that the model created in v. 20.07.05.15 definitely contains composite member properties?

    Cheers,

    Chris



  • THANKS FOR YOUR QUICK ANSWER.  YES I'M SURE THAT THAT THE MODEL CREATED IN V 20.07.05.15 IS A COMPOSITE SECTION. ITS VERY STRANGE IF I CREATE A COMPOSITE BEAM MODEL IN THE V.20.07.06.23 I RECEIVE THE WARNING AND IF IT IS CREATED AT THE PREVIOS VERSION 20.07.05.15 NOT. THE RESULTS OF THE ANALYSIS ARE ALMOST THE SAME. FOR EXAMPLE A DIFERENCE OF 1 .5 KG/CM2 AT THE STRESSES BETWEEN THE ANALYSIS IN THE TWO VERSIONS.

     

    ALSO I NOTICE A DIFERENTE ALPHA IS USED FOR STEEL AS THE DEFAULT VALUE ON BOTH VERSIONS

    ALPHA 6E-006   VS   ALPHA 1.2e-005

     

    THANKS

  • If you would like to post the two versions of your model, I would be happy to take a look at them and try them on my machine to see if I can spot anything that may be causing the difference in behavior.

    Chris