New Dummy: Replacing One Dummy With Another
New Dummy: Replacing One Dummy With Another
Example problem: new 95th %ile dummy replaces old 50th %ileHere a belted 50th percentile dummy has been replaced (via ) by a larger 95th percentile version. ![]()
|
||
|
It can be seen that the existing seatbelt (black) now penetrates the chest and the pelvis, so it clearly needs to be refitted. However if you go directly to the seatbelt fitter and attempt a or an you will get a message something like this:
This has happened because the part sets used to define the belt-to-dummy contact do not exist in the new dummy, and the nodes used to define the path points are also either missing or in totally different locations. It will be necessary to redefine the parts on the dummy contacted by the belt, and also to move the belt path points back out onto the dummy surface. |
||
Solution part 1: redefine the "dummy" surface
( Note : If your new dummy is sufficiently similar to the old, for example if the relevant part set labels are the same in both, this section may be green and you will not need to redefine the dummy. However this example assumes the worst case with no useful information being carried over. ) Use to select parts or elements of the dummy to be contacted by the belt. Points to consider when selecting parts for belt-to-dummy contact are: |
|
|
Once you have defined some parts the icon of the dummy
should go green:
You can check that you have selected a sensible range of elements using , and you can change the selection at any time by using and as required. To start again from scratch use , which will delete all elements in the the "dummy" definition. |
Solution part 2: correct the belt path
|
|||||
|
At present most of the intermediate belt points ( P ) are inside the dummy, because the new dummy is larger, and they need to be moved out onto its surface if the belt is to fit over rather than inside the dummy. In addition it is best of the majority of the belt points in the dummy region are defined by nodes on the dummy, rather than just plain points, since that way if the dummy is repositioned its nodes will move, and the path points will move with them.
(
Belt fitting after repositioning the dummy will still work if only
some path points are defined by nodes. Those in between, defined only
by coordinates, will have these coordinates interpolated from the motion
of their their neighbouring points that are at nodes. However this process
is more likely to be satisfactory if the majority of path points are at
nodes.
)
|
|||||
|
Each time you change the definition of the "dummy" the path is scanned automatically to try to find nodes near to each path point, and this panel will be updated accordingly. There are tolerances built into this process and you can perform these checks manually with different tolerances as follows:
|
|||||
|
The default tolerance for Check path coords is 5mm, and for Find new Nodes is 50mm. These defaults may be changed by the following preferences:
The status of what has been found is reported for nodes, and the ideal is that all points in the path find a node on the "dummy" or the vehicle "structure" and have a green tick against them. |
|||||
|
Here is an artifical example in which only dummy structure in the torso region has had parts defined, and the pelvis region has been omitted. There are 11 path points in total, but only 8 have found nodes: 4 on the dummy and 4 on the vehicle structure. This is marked as "OK" but with the qualification that 3 path points are not on nodes, and these can be seen marked as ( P ) on the path diagram. In this example this is plainly an error that is easily corrected by adding more "dummy" definition parts, but in other cases it may be acceptable to have isolated path points that are not located at nodes. If you have this situation you will have to examine your structure to determine whether or not the result is acceptable. ![]() |
|||||
|
If you have trouble identifying where the path points are on the dummy you can use the different views (+XY, etc) to get a better picture. Also for the duration of the New Dummy process the plot in the graphics window will show the current belt path, labelled with point numbers and node status at each point. ![]() |
|||||
Solution part 3: Update and refit |
|
|
Once you have defined the dummy and sorted out the belt points you will be able to Update Dummy and Belt Path to save the corrected definition, after which an or possibly a manual will refit the belt. Here is the example above after an , showing that the belt path has been successfully projected out to the surface of the dummy, fitting round the larger 95th %ile chest. ![]() |
|
Possible problems, and how to fix them.Fitting a belt from a smaller dummy onto a large one, as in this example, can result in problems that go beyond plain "matching path nodes to new points" as the following sequence shows. |
|
|
First appearances suggest that the process above has worked first time. However closer inspection of the end result of this example reveals that the belt is penetrating the upper right hand leg as shown by the close-up here, and this needs to be fixed. |
|
|
Going into the path editor ( , ) reveals that the twist of the fitting path in this upper leg region is wrong, resulting in the initial path penetrating the upper leg. This means that this section of the belt starts off on the "wrong" (inside) surface of the leg and does not pull itself out again. |
|
|
Using the path editor in mode that point #6 is rotated up out of the leg. Once corrected another refit now positions the belt successfully around the dummy. This is a particular case of the more general problem that moving a belt path from one dummy to another can pose problems that this function cannot always solve. It is a help, but not a panacea - please always check the end result! And be prepared to pay a visit to the belt path editor to adjust the belt path if necessary. |
|
When an existing belt + dummy combination needs to have dummy A replaced by similar dummy B the following operations are required:
When you first select
Initially it is likely that the Belt Path section of this panel will
look like this:
Your goal is to achieve a result that looks like the picture on the right
in which all path points have found nodes on the "dummy" structure
as defined in part 1 above.


