Mass and CoG of beam elements

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Hypermesh 2017.2

Cbeam elements do not have mass when calculated in hypermesh>tools>mass calc or post>summary>ctr_of_gravity.

But when running in optistruct it does have the mass as expected.

I wanted to check the CoG of my model but for the Cbeam elements there is no mass until I solve the model.

Is there something wrong with the model or is it a glitch?

 

<?xml version="1.0" encoding="UTF-8"?>beam1.JPG

<?xml version="1.0" encoding="UTF-8"?>beam2.JPG

<?xml version="1.0" encoding="UTF-8"?>beam3.JPG

<?xml version="1.0" encoding="UTF-8"?>summary.JPG

<?xml version="1.0" encoding="UTF-8"?>out mass.JPG

<?xml version="1.0" encoding="UTF-8"?>Beam 1D_3D_display.jpg

Tagged:

Answers

  • Pranav Hari
    Pranav Hari Altair Community Member
    edited February 2019

    Hi TimBrown

     

    Can you please share the model file.

    You can use the secure drop box link.

    https://ftin.india.altair.com:8443/filedrop/~Ma3TaE

  • tinh
    tinh Altair Community Member
    edited February 2019

    I made a beam model and panel Summay gives exact mass of it.

     

    If OS gives that mass, try importing *.fem file again to check mass by Summary panel

     

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2019

    I have been advised to update from 2017.2 to 2017.3:

     

    'I believe this was a known issue and has been fixed in the latest version HyperWorks Desktop 2017.3.

    Can you please upgrade and let us know if you still continue to see this?'

     

    I will try this and update the thread first.

     

    Thanks for the feedback.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2019

    I made a beam model and panel Summay gives exact mass of it.

     

    If OS gives that mass, try importing *.fem file again to check mass by Summary panel

     

    I have just tried this with 2017.2 and it was the same, thanks for the idea.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2019

    Updating to 2017.3 has solved the issue

     

    Thanks