surface load

[farukpolat3535]

Thank you for your answer dear Francesca.

I changed model with eleload. I gave up with generic loading. Cause I need to understand the mechanism of joint that is why I pass trough this command for a while. So my other question is that you were pointed the beams connections to beams. When I start solving this model I can see some stud beams are not constraint to the other beam. So I wonder that is there any possible way to create a beam-beam connection How can I model this existing building with some beam to beam connection in this pic? You can find my changed model in this link also.

https://dosya.co/2uho7bbhjitc/m161.scd.html

[marafini.f]

Dear faruk,

your question is not super clear to me.
What I understood by looking more closely at the physical properties of your model is that you are using different fiber sections for the center and the support of the beams to represent the change in the reinforcement arrangement.
What is the stud beam, beam-to-beam connection that you want to represent?
Is your question related to the interaction in terms of free DOFs between the beams, it's on plasticity modelling or on how to model the reinforcement?

Thank you in advance for the clarification.

Francesca

[farukpolat3535]

Dear Francesca

I am asking this beam's behaviour. When I say stud beam I mean a beam connected to another beam instead of column. I have 4 of this kind of beams and I think there is mistake at connection.

[marafini.f]

Dear faruk,

I tried to run the last model you uploaded, but I think it's not the same of the one with results you are showing.

Anyway, the detachment of those beams happens for two possible reasons:

• GEOMETRY: it could be that your beams in the T intersection are not connected. If you see the beams on the other side, only the at the first level present this problem, I suggest you check what difference is there in the modelling. You need to merge everything once you draw it and also in this case, make sure there are no overlapping nodes inside the merged geometry.
  You can check this, by allowing only node selection in the quick access toolbar, and try to select the node just by clicking on it, not with a dragging selection. If there are two, that's your problem there. You can also check inside the work tree geometry, but that's going to be a hard search cause you have a lot of elements.

• CONSTRAINTS: I don't know if you applied some specific constraints on that T intersection, maybe a release, or an equalDOF, you have to be careful with multi point constraints and the constraints handler you pick. When you have overlapping retaining/constraining couples and you use the transformation for example, in the analysis you could lose some of your imput.

Let me know if this helps, and if you found a solution.
If you can always upload the model you are showing results for, it is easier for us to find the problem.

Francesca