Forum Replies Created

Viewing 15 posts - 46 through 60 (of 261 total)
  • Author
    Posts
  • in reply to: p-delta analysis strange behaviour #5212
    NextFEM Admin
    Keymaster

    The important thing to do is to have a model with at least an internal node, otherwise the solver tries, as said, to compensate the residuals (especially for rotations) on end nodes.

    in reply to: p-delta analysis strange behaviour #5210
    NextFEM Admin
    Keymaster

    Dear Alain,
    the beam formulation for built-in solver does not account for automatic mesher or p-delta effects correction for a single beam element.
    As a result, for p-delta and second-order effects, you have to consider more than one element for a model. Fortunately, all the model having internal nodes (e.g. structures) does not suffer from this.
    Considering the single-beam model, the moment at middle-span for LC1 is the same for all loadcases, but translated of the initial/ending moment (e.g. 34.186 – 7.629 = 26.55). The unrealistic initial and ending moment is due to the fact that the iterative solver cannot compensate the residual in internal nodes.

    in reply to: Thanks for implementing alignShellXaxis() Method #5193
    NextFEM Admin
    Keymaster

    Dear Luciano,
    your post is much appreciated! Thanks also for sharing your python script!

    in reply to: Importing a mesh generated by gmesh #5175
    NextFEM Admin
    Keymaster

    Thanks, Luciano. In the next patch you’ll find alignShellXaxis API function.

    in reply to: Importing a mesh generated by gmesh #5173
    NextFEM Admin
    Keymaster

    Dear Luciano,
    you obtain “bad” diagram because you don’t have aligned shell local axes. Every force/moment for shells is plotted against local axes for NextFEM Designer.
    We currently read the mesh given by Gmsh (not via API, but from GUI only).

    To solve the problem, align the local axes with Assign / Local axes command.
    ps.
    we have free internal tria mesher. For regular slab as yours, a structured mesh (made by division) is more suitable. By using a mesh like the one you have, you’re implicitly introducing approximations in results, because finite elements involved (quad) are made to be more accurate when regular (e.g. square).

    in reply to: display maximum beam span moment #5161
    NextFEM Admin
    Keymaster

    You already have such option in Options / mask Solver / Mesh and output preferences box / Beam max output stations

    in reply to: display maximum beam span moment #5159
    NextFEM Admin
    Keymaster

    Hello,
    the beam output is shown at fixed beam stations (hence not necessarily including maximum), unless you activate “More output stations”.

    in reply to: WoodCheck deflection limit state #5149
    NextFEM Admin
    Keymaster

    psi values can be specified from the Load combination generation mask (Assign / Generate combinations).

    in reply to: WoodCheck deflection limit state #5146
    NextFEM Admin
    Keymaster

    Hello,
    the principal variable loading case is assumed automatically as the case with the highest combination multiplier amongst all the variable cases. In you model, it is Q-CatH. This is always conservative, as the greatest factor in combination leads to the higher factor for deflection calculation as per NTC2018 C4.4.7.

    With kdef=0.8 (SCL=2) you may have (values in m):
    Secondary-variable Neve: (psi0 + psi2 * kdef) * f = 0.0004886155
    Permanent G1-PP: (1 + kdef) * f = 0.00010358946
    Permanent G2-Cop: (1 + kdef) * f = 0.0017873568
    Principal-variable Q-CatH: (1 + psi2 * kdef) * f = 0.00053534396
    Secondary-variable Vento_press: (psi0 + psi2 * kdef) * f = 0.000373014

    for a final sum of 0.00328791972.
    It seems the model you sent behaves differently – we’re investigating the issue, please keep your program up to date – if this is the case, we’ll release a patch asap.

    in reply to: Dynamic Substructuring or component mode synthesis #5132
    NextFEM Admin
    Keymaster

    Hello,
    thanks for your interest in NextFEM Designer. Actually, the program can perform implicit dynamic analysis – there’s no specialization for what you ask.

    in reply to: meshing of simple skew plate #5120
    NextFEM Admin
    Keymaster

    In the next patch your sample model will be supported (when quad with opposite edges are parallel) – otherwise, mesh area command should be used for complex boundaries.

    in reply to: flexural stiffness modification of cracked section #5119
    NextFEM Admin
    Keymaster

    The option is on the material level because otherwise you can assing inconsistent beam stiffnesses. If you need to act to a single DoF (eg. axial or shear only) you can act at a section level (see section properties, Properties tab) by changing A, Avz, Avy, Jy, Jz, and so on.

    in reply to: rigid end offset with OpenSees solver #5118
    NextFEM Admin
    Keymaster

    Hello,
    it is only a matter of visualization – in the next patch you’ll see corrected diagrams.

    in reply to: meshing of simple skew plate #5110
    NextFEM Admin
    Keymaster

    Hello,
    skew elements cannot be divided by this tool. This is because the tool works only on regular elements.

    in reply to: flexural stiffness modification of cracked section #5109
    NextFEM Admin
    Keymaster

    Hello,
    this is a property of the material. See Materials / select a material and then click on Modify Material… / Tools menu / Set stiffness factor.

Viewing 15 posts - 46 through 60 (of 261 total)