Additional descriptor for "Intended Velocity"

[DiVe]

Dear colleagues,

there was a request to store the "intended velocity" with a test object.
The idea originated in the active safety extension discussion in the sub group.

If there are applications in the Passive Safety that will contribute from that,
we can add this also to RED A to give some direction for a unified approach.

A first idea for the implementation/discussion is (alternatives):

2022-10-19 16_39_11-MME-Attributes_for_active_Safety.xlsx - Excel.png (7.23 KiB) Viewed 1799 times

Some ideas for the usage of this descriptor are:
a) Transport the "reverence or equivalent test speed": The initial velocity of a reversed sled is zero.
b) Transport the initial speed of a test object in a test with pre-test-brakeing
...

If you see a need or and/or an application, please comment here.

Kind regards,
Dirk

[DiVe]

Dear colleagues,

as decided on the Task Force Meeting (2023-09-20):
The intended velocity will be coded for each test object as:

Code: Select all

Nominal vel. test object X	
Nom. lat. vel. test object X	

like

Code: Select all

Nominal vel. test object 1  :	
Nom. lat. vel. test object 1:	

These descriptors are optional.

This will be added to RED A 2023.

see also: viewtopic.php?t=675

[DiVe]

see also the related topic for:
Additional descriptor for "Lateral velocity"
viewtopic.php?t=706

The extension for Intended velocity will be documented in the next RED A (estimated Q1/2024)