News: Contact us to upgrade your software!

Author Topic: Non-FEA Panel - multiple pressure only loadcases  (Read 24919 times)

MattA

  • Client
  • **
  • Posts: 5
    •  
Non-FEA Panel - multiple pressure only loadcases
« on: July 13, 2018, 11:02:36 AM »
Hi,

I have created a panel (metallic orthogrid) as a non-FEA project and set fixed geometry.  I applied a +0.01 pressure as LC101 and a -0.01 pressure as LC102.  There are no other loads, only pressure.  All margins came back as being LC101.  I then set LC101 pressure to 0, and it returned no margins.  However, when I set LC101 to -0.01 it returned lower margins than the +ve pressure case.  My conclusion from this is that it is only running the first loadcase.

I have checked that all loadcases are activated.  I am using 7.3.37

Any thoughts?

MattA

  • Client
  • **
  • Posts: 5
    •  
Re: Non-FEA Panel - multiple pressure only loadcases
« Reply #1 on: July 13, 2018, 11:16:50 AM »
As a further investigation, if I run the 2 loadcases and put a very small running load for Nx, Hypersizer then runs both loadcases and I get margins against multiple loadcases.  Is this a bug?

Stephen

  • Administrator
  • *****
  • Posts: 70
    •  
Re: Non-FEA Panel - multiple pressure only loadcases
« Reply #2 on: July 13, 2018, 11:52:18 AM »
Hi Matt,

It looks like this is indeed a bug. It seems that HyperSizer is not running the second loadcase because it thinks there are no loads applied; it is apparently not checking the pressure field. I've submitted a report to our developers to investigate and fix, but I think you've found the best work-around in the meantime (applying a very small Nx). Sorry for the inconvenience, we will work to fix this in an upcoming release.

-Stephen

MattA

  • Client
  • **
  • Posts: 5
    •  
Re: Non-FEA Panel - multiple pressure only loadcases
« Reply #3 on: July 15, 2018, 08:06:11 AM »
Super, thanks for confirming and reporting it Stephen.

eric

  • Client
  • **
  • Posts: 12
    •  
Re: Non-FEA Panel - multiple pressure only loadcases
« Reply #4 on: July 15, 2018, 07:28:33 PM »
Deja-vu...this same thing caught me too a while back.  Putting a dummy load in there also worked for me.  Hopefully can be fixed in the next iteration!