Vehicle Dynamics 3DOF Single Track Block doesn't seem to include drag equations.

14 visualizzazioni (ultimi 30 giorni)
For the Vehicle Body 3 DOF block in the Vehicle Dynamics Blockset, I've configured it to run in single track mode. The documentation includes equations for drag forces under the dual track section, but not the single track section, which led me to believe that the drag forces are only relevant for the dual track block.
This does not seem to be the case, as I'm observing the drag forces in the output of the single track block to be nonzero. It makes sense that drag would be accounted for in both single track and dual track modes, but why then are the drag forces only described in the dual track equations?
Furthermore, the single track documentation does mention drag forces, saying that external forces = drag forces + input forces:
But then when I observe the external body forces as output by the block, they are always 0 despite the drag forces being nonzero. Seems like there might be a term overload with "external forces" referring both to the external input forces as well as the drag + input combined force.
External force input:
What I thought would be the computed external force output (drag + input forces), but is always 0 when input force is 0:
  5 Commenti
Daniel
Daniel il 23 Dic 2024
Also, the block implementation does not even appear to match the drag equations from the docs. When I manually calculate the expected result from the provided equations, I'm getting [-87.3, 0, -29.1], but you can see from this screenshot that the block is computing [87.3, 0, -29.1].
This -K- block is scaling the air velocity vector by [4;4;0], then that is fed into the tanh block. The [3x1] block below that is set to [0;0;1] and is subtracted from the output of the tanh block. None of this is specified in the drag forces section of the 3 DOF Body documentation, so I'm very confused what's going on here.
Daniel
Daniel il 23 Dic 2024
And to add another issue to the list, the documentation specifies that defaults to [0:0.01:0.3], and defaults to [0:0.03:0.9], but these default to [0 1e-6:0.01:0.3] and [0 0.01:0.01:0.3], respectively.

Accedi per commentare.

Risposte (1)

Shivam Gothi
Shivam Gothi il 24 Dic 2024
Hello @Daniel,
Lets address the issues one by one:
1) Drag equations not included for Single track:
Refer to the below section of documentation.
The section named "Drag" is not included in either of the "Dual track" or "single track" section. It is printed as a seperate section, indicating that the same drag equations are valid for both, single track and dual track mode.
2) What exactly are the external forces?
I read the documentation. As per my understanding, the "Fext" appears as an input port upon selecting "External Forces" checkbox, found under "Input signals" drop-down. This "Fext" is the external input force acting on the CG of vehical (It has to be provided by the user as an input). It is not the sum of "Drag forces + external input forces". This "Fext" is represented by notation: () in the documentation.
The block calculates resultant external forces (represented by notation: ()), by adding "Drag forces () + external input forces" (), as shown in the below equation.
It uses this () to calculate other forces as shown in the below screen-shot.
3) How the equations of "drag forces" calculated ? What is the purpose of gain blocks [4;4;0] and [0;0;1] ?
The purpose of "tanh()" block is to find the direction of relative wind. Although, signum function can be used for this purpose, but the issue is, it may cause chattering problem. Refer to the graphs of both the functions. Signum function has discontinuity at zero, but tanh() is continuous function, for all values.
If you observe carefully, the output of "tanh()" block will be (-1) or (1) under normal operations. It just indicates the direction of relative wind. The gain "4" is multiplied to ensure that we stay in the yellow highlighted region, as shown below.
The gain of [0,0,1] is subtracted to ensure that "z" component of the force is (-1).
The wind direction vector is then multiplied with the calculated force in order to find force vector.
4) The defaut values of "" and "" stated in the documentation does not matches with the actual default values.
As correctly pointed out by you,
The default value of "" stated in the documentation is: [0:0.03:0.9]
The default value of "" stated in the documentation is: [0:0.01:0.3]
The actual default value of "" is: [0 0.01:0.01:0.9]
The actual default value of "" is: [0 1e-6:0.01:0.3]
But, you can observe that 1e-6 is very small and the vector [0 1e-6:0.01:0.3] will closely resemble the value [0 0:0.01:0.3]
You can contact Mathworks Technical support for the clearification.
I hope you find the information useful !
  5 Commenti
Daniel
Daniel il 25 Gen 2025 alle 21:50
Agreed. Going off that, if the z-component of the drag force vector is always multiplied by -1, then why doesn't the documentation just flip the sign for F_dz.
Paul
Paul il 26 Gen 2025 alle 3:22
If you think the doc page needs to be improved you can click a star at the bottom of the doc page to rate it after which a box will pop up in which you can leave a comment.
Or, if you think the block is not implemented incorrectly or needs to be improved you can open a case with Tech Support. They are always very responsive.

Accedi per commentare.

Categorie

Scopri di più su Startup and Shutdown in Help Center e File Exchange

Prodotti


Release

R2024b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by