How are results organized in Adams/PostProcessor ? It looks like to me if several request use same result set name then request is not in result container, i.e. roll_center_location is not in testrig (result container), If just one request like i.e. camber angle uses one result set name, then it is in results set container.
Is my observation correct, or there is some other logic behind organization of requests in processor?
I believe that same goes with turn radius, both of them AFAIK give same results
According help:
Description
The turn radius is the distance measured in the ground plane from the vehicle center line to the turn center along the y-axis (see the figure for Ackerman Angle). Turn radius is positive for right turns and negative for left turns.
Units Length
Request Names turn_radius.left
turn_radius.right
Inputs Steer angle (see Steer Angle)
Track width
Wheelbase
Wheel-center orientations - left and right
Method
Adams Car determines the inside wheel by checking the sign of the steer angles. It computes turn radius using the inside tire orientation.
Left turn:
turn_radius.left = - [Wheel Base (DCOSY/DCOSX) + Track/2]
Right turn:
turn_radius.right = [Wheel Base x (DCOSY/DCOSX) + Track/2]
Symmetric vehicle:
Wheelbase=2000
W.C._left=0.0, -800.0, 300.0
W.C._right=0.0, 800.0, 300.0
Track=1600
Left turn
For right turn
Both request components are giving same results.
In Case of non symmetric vehicle
Non-symmetric vehicle:
Wheelbase=2000
W.C._left=0.0, -800.0, 300.0
W.C._right=0.0, 1100.0, 300.0
Track=1900
Left turn
Right turn
What is here little confusing is symmetry plane of vehicle, track is not something like for left wheel 800, for right wheel 1100, but is is using 950 mm for both of them. AFAIK track should be different for left and right wheel.
Also longitudinal non-symmetry of left and right wheel is giving same turn radius results for left and right component.
I believe that same goes with turn radius, both of them AFAIK give same results
According help:
Description
The turn radius is the distance measured in the ground plane from the vehicle center line to the turn center along the y-axis (see the figure for Ackerman Angle). Turn radius is positive for right turns and negative for left turns.
Units Length
Request Names turn_radius.left
turn_radius.right
Inputs Steer angle (see Steer Angle)
Track width
Wheelbase
Wheel-center orientations - left and right
Method
Adams Car determines the inside wheel by checking the sign of the steer angles. It computes turn radius using the inside tire orientation.
Left turn:
turn_radius.left = - [Wheel Base (DCOSY/DCOSX) + Track/2]
Right turn:
turn_radius.right = [Wheel Base x (DCOSY/DCOSX) + Track/2]
Symmetric vehicle:
Wheelbase=2000
W.C._left=0.0, -800.0, 300.0
W.C._right=0.0, 800.0, 300.0
Track=1600
Left turn
For right turn
Both request components are giving same results.
In Case of non symmetric vehicle
Non-symmetric vehicle:
Wheelbase=2000
W.C._left=0.0, -800.0, 300.0
W.C._right=0.0, 1100.0, 300.0
Track=1900
Left turn
Right turn
What is here little confusing is symmetry plane of vehicle, track is not something like for left wheel 800, for right wheel 1100, but is is using 950 mm for both of them. AFAIK track should be different for left and right wheel.
Also longitudinal non-symmetry of left and right wheel is giving same turn radius results for left and right component.