Although the location of the calculation axis is important, the program tries to find the most appropriate spacing by looking at the distances between the columns. However, the algorithm will be valid with a truly beamless definition of a beamless slab. However, there are also beams in your system. In this case, a mixed evaluation will be made., I think the program ts500 makes the thickness control according to the distance that the reinforced concrete calculation axis passes. I changed the location of the calculation axles, and ide 6 with less thickness did not warn of lack of section.
This is the point I wanted to draw your attention to. There will be no beam definition in the beamless slab model, but a second model is required for earthquake transmission.and how does ts500 accept such slabs in thickness control. There are beams in this system, but if the ts500 accepts this floor as a double-sided system with beams, this thickness control would not be correct
It is necessary to accept the floor thickness controls for the system without beams. Thickness>=ln/30 for beamless slab without table, Thickness>=ln/35 for plated floor.if it accepts beamless, this time there are cantilever zones in the project. so I think we have to do the thickness control of the project ourselves in such systems.
We enter the beams we entered for the relative floor hoteling and earthquake regulation controls and so on. However, at 6, it is possible to print out the hidden beams without having the regulation checks, if necessary. As long as we are aware of the results of the model we make as an engineer. In the 2nd model, you can not have a conformity check while receiving a report. .but I also think that we need to pass the axes of calculation through large areas for the reinforcement solution. In this case, if I solve this project with ide 6, I will not get an error-free report that will give an insufficient thickness warning. If we throw hidden beams for earthquake load transfer in the horizontal direction, these beams will be beams that do not comply with the beam specifications. Also, when we model these beams in ide, they will make these checks and will not provide a cross section, I think. ]
In link elements, I meant rigid connectors in the program, but I saw that it does not need to be defined because rigid diaphragms are already accepted at the top of the column. As I wrote, the aim is to be able to control the relative floor drift etc. section 2. The most suitable modeling for this will be by defining the hidden beams.How do we know if the slab rigid diaphragm is sufficient for the column endpoints to move together in seismic load transfer? Even if we make hidden beams, the cross-sections of these beams will not change, only the reinforcement will be thrown more often in that area. we are already doing this in practice and drawings. You mentioned link elements, I don't fully understand it. How will we do this in practice and calculation?
Panels split by beam rather than panels have an issue with printing zeros in the alphas report Values will appear in the first updated version.For now, if you want those values to appear in the AAlfas report, you can delete the beams connected to those panels before receiving the report, and undo them after you receive the report.In addition, since there are no basement perimeter curtains in your project, you need to enter the rigid basement floor number -2 in your project. I think the -1 value was left incorrectly."tavekkul":kodio47w" said:in addition, the program takes the shear force capacity of the curtains I have defined with the panel object as 0 in curtain shear force control...You do not have permission to view link Log in or register now.