pyBmodes version
1.60.0
Python version
3.11.8
How did you install pyBmodes?
pip install pybmodes (from PyPI)
Operating system
Window 11
What happened?
"Blade inertia = zeros is the rigid-RNA convention, not a dropped term. The blades are lumped as a translational point mass at the rotor apex, so their dominant contribution, the parallel-axis term N_bl · m_blade · apex², is in the tower-top tensor. Only the blades' own spanwise spin inertia is left out, which is what ElastoDyn does as well (the blade rotational dynamics live in their own DOFs, not the tower lump). The blade mass itself is integrated from the inertia_matrix mass-per-length over the span." Last issue I made, you responded
Stated is true for the code but I disagree for what is actually present in the model
What did you expect?
However, that assumes you was give the point mass at the hub of the blades and the inertia from parallel axis theorem was zero.
However i would argue the code is forgetting you have translation the point masses spanwise to the root of blade (actually to hub centre) which means we are missing N_bl · sum(m_blade_i · (r_i +hub_R)², which does add good amount of inertia. Yes you are still forgetting about I_o (spanwise spin inertia) which has already been explained why.
Take each blade inertia from translated masses to hub and do it same time in 3D/2D plane, so you don't have to do any rotations due to azimuth.
I believe there should be additional inertia from the section point mass translations
Minimal reproducer
Traceback or unexpected output
Anything else?
No response
pyBmodes version
1.60.0
Python version
3.11.8
How did you install pyBmodes?
pip install pybmodes (from PyPI)
Operating system
Window 11
What happened?
"Blade inertia = zeros is the rigid-RNA convention, not a dropped term. The blades are lumped as a translational point mass at the rotor apex, so their dominant contribution, the parallel-axis term N_bl · m_blade · apex², is in the tower-top tensor. Only the blades' own spanwise spin inertia is left out, which is what ElastoDyn does as well (the blade rotational dynamics live in their own DOFs, not the tower lump). The blade mass itself is integrated from the inertia_matrix mass-per-length over the span." Last issue I made, you responded
Stated is true for the code but I disagree for what is actually present in the model
What did you expect?
However, that assumes you was give the point mass at the hub of the blades and the inertia from parallel axis theorem was zero.
However i would argue the code is forgetting you have translation the point masses spanwise to the root of blade (actually to hub centre) which means we are missing N_bl · sum(m_blade_i · (r_i +hub_R)², which does add good amount of inertia. Yes you are still forgetting about I_o (spanwise spin inertia) which has already been explained why.
Take each blade inertia from translated masses to hub and do it same time in 3D/2D plane, so you don't have to do any rotations due to azimuth.
I believe there should be additional inertia from the section point mass translations
Minimal reproducer
Traceback or unexpected output
Anything else?
No response