Forum
Important Notice for New User Registrations
To combat an increasing number of spam and bot registrations, we now manually approve all new user registrations. While this may cause a delay until your account is approved, this step is essential to ensure the quality and security of this forum.
To help us verify your registration as legitimate, please use a clear name as user name or an official email address (such as a work, university, or similar address). If you’re concerned that we may not recognize your registration as non-spam, feel free to email us at with a request to approve your username.
STRUT_TORQUETUBE_CONSTRAINTS
Quote from AsIlll on 10. December 2024, 10:06Hi David,
It seems that the The STRUT_BLADE_CONSTRAINTS table and The STRUT_TORQUETUBE_CONSTRAINTS table in the user guide https://docs.qblade.org/src/user/turbine/structure.html#blade-parameters use the same example list. Is it a problem ?
BR,
AsIlll123
Hi David,
It seems that the The STRUT_BLADE_CONSTRAINTS table and The STRUT_TORQUETUBE_CONSTRAINTS table in the user guide https://docs.qblade.org/src/user/turbine/structure.html#blade-parameters use the same example list. Is it a problem ?
BR,
AsIlll123
Uploaded files:- You need to login to have access to uploads.
Quote from David on 10. December 2024, 23:21Hi AsIlll,
you are correct—the content of both tables is identical, but the keyword is not. While both tables contain the same degrees of freedom for Strut 1 of Blade 1 and Blade 2, the distinction lies in how these constraints are applied:
- The first table applies these constraints between the strut and the blade, as indicated by the keyword STRUT_BLADE_CONSTRAINTS.
- The second table applies these constraints between the strut and the torque tube, using the keyword STRUT_TORQUETUBE_CONSTRAINTS.
BR,
David
Hi AsIlll,
you are correct—the content of both tables is identical, but the keyword is not. While both tables contain the same degrees of freedom for Strut 1 of Blade 1 and Blade 2, the distinction lies in how these constraints are applied:
- The first table applies these constraints between the strut and the blade, as indicated by the keyword STRUT_BLADE_CONSTRAINTS.
- The second table applies these constraints between the strut and the torque tube, using the keyword STRUT_TORQUETUBE_CONSTRAINTS.
BR,
David
Quote from AsIlll on 11. December 2024, 02:31Hi David,
I set the content of the struct table like this :
STRUT_TORQUETUBE_CONSTRAINTS
STR_ID BLD_ID DoF_X DoF_Y DoF_Z DoF_rX DoF_rY DoF_rZ
1 1 1 1 1 1 1 1
1 2 1 1 1 1 1 1
1 3 1 1 1 1 1 1
2 1 1 1 1 1 1 1
2 2 1 1 1 1 1 1
2 3 1 1 1 1 1 1But it fails to work, the illustration of the turbine in the ramping process is given in the STruct1.png. I do not know what is wrong, could you give me some advice ?
BR,
AsIlll
Hi David,
I set the content of the struct table like this :
STRUT_TORQUETUBE_CONSTRAINTS
STR_ID BLD_ID DoF_X DoF_Y DoF_Z DoF_rX DoF_rY DoF_rZ
1 1 1 1 1 1 1 1
1 2 1 1 1 1 1 1
1 3 1 1 1 1 1 1
2 1 1 1 1 1 1 1
2 2 1 1 1 1 1 1
2 3 1 1 1 1 1 1
But it fails to work, the illustration of the turbine in the ramping process is given in the STruct1.png. I do not know what is wrong, could you give me some advice ?
BR,
AsIlll
Uploaded files:- You need to login to have access to uploads.
Quote from David on 11. December 2024, 15:25Hi AsIlll,
the STRUT_TORQUETUBE_CONSTRAINTS and STRUT_BLADE_CONSTRAINTS tables are designed for scenarios where certain degrees of freedom (DOFs) are intentionally left unconstrained, such as when modeling hinged connections or similar mechanisms. By default, each strut is rigidly constrained to both the torquetube and the blade. However, in your case, all DOFs are constrained by setting the entries to
1
. This configuration reflects the default behavior, rendering these tables unnecessary.The likely reason your struts are not connecting to the torquetube is that the torquetube does not extend to the location where the top struts are meant to attach.
To resolve this, try extending the torquetube by adjusting the TRQTBHEIGHT parameter.
BR,
David
David
Hi AsIlll,
the STRUT_TORQUETUBE_CONSTRAINTS and STRUT_BLADE_CONSTRAINTS tables are designed for scenarios where certain degrees of freedom (DOFs) are intentionally left unconstrained, such as when modeling hinged connections or similar mechanisms. By default, each strut is rigidly constrained to both the torquetube and the blade. However, in your case, all DOFs are constrained by setting the entries to 1
. This configuration reflects the default behavior, rendering these tables unnecessary.
The likely reason your struts are not connecting to the torquetube is that the torquetube does not extend to the location where the top struts are meant to attach.
To resolve this, try extending the torquetube by adjusting the TRQTBHEIGHT parameter.
BR,
David
David
Quote from AsIlll on 17. December 2024, 08:17Hi David
Thank you for your advice ! I extend the torquetube height and then it works well.
BR,
AsIlll
Hi David
Thank you for your advice ! I extend the torquetube height and then it works well.
BR,
AsIlll