ISO-MME

Dear All,

in the CP005 (V1.1) document from EuroNCAP there is a additional Descriptor used
to determine the origin of the dataset in general.
(The information for each channel is already existing as "Data source".)

This is used to distinguish between data from numerical simulation and testing ...

Proposal is accepted and the following extensions have been implemented in the database:

Topic is closed.

Dear All,

I have added the codes for "Airbag" and "AirbagSim" to the current database proposal vor 1.6.3/1.7,
I needed to add also the new code part "AV" for FL3:
2025-07-22 17_16_28-Access - mme_code _ Database- D__Daten_03_Projekte_10_ISO_02_DB_##Work_01_Versio.png

to comply to all coding ...

Dear all,
in the database I have now prepared the following extensions for the ew Airbag coding:
Extensions for FL1:
2025-06-06 13_26_14-Access - mme_code _ Database- D__Daten_03_Projekte_10_ISO_02_DB_##Work_01_Versio.png

Changes for FL2:
2025-06-06 14_29_28-Access - mme_code _ Database- D ...

Dear All,
after the meeting I have received the final presentation for the VDA Airbag Coding approach.

Please find a copy here attached.

...please find here the updated document after the meeting 2025-06-05:

Point for discussion from the meeting 2025-06-05:

Code the 1D equivalent better as:

a) 2025-06-05 16_36_48-D__Daten_#Config_EPIM_Dive_7.epim - EssentialPIM Pro.png

pros: - same ML as other calulated codes
cons: - direction will be used to make the connection to the 1D result

b) 2025-06-05 16 ...

Dear All,
for the Meeting on the 5th of June 2025 please find the latest version of the RED A for discussion.
I have added a Data format section as "A.0" at the start that included a subset from the types of RED A from version 2.
All latest changes are in violet color in the document.
ISO_TS13499 ...

Dear All,

in the discussion at the meeting (2025-04-29) the following decisions have been made:
- the coding for the existing sensors and calculations should be untouched
(existing processes and existing data will still be valid regarding the coding)
- the new approach for the calculated channels ...

Dear All,
please find here some proposals for the coding approach.
Actually, these "new" codes are only relevant for the calculated channels.
The base channels could be named in the same way for 2D, 3D
as they are the same measurements (as long as the geometric design is the same).
2D and 3D will ...

Dear All,

as mentioned in the topic "Dummy certification/Introduction&Discussion"
https://www.iso-mme.org/forum/viewtopic.php?t=63

we will need the Main Location "PEND" to code in the desired way
documented under: "Codes for Testrig Channels"
https://www.iso-mme.org/forum/viewtopic.php?t=714

Are ...

Discussed on the Task Force meeting 2025-03-05:

The coding "DF" will be available and is not used so far in the coding database.

The codings for other defomable element are listed also in the figure:
"Other objects" figure "ISO_OBJ_1_16x.emf" or the RED C.
2020_06_17_ISO_TS13499_RED_C_1_6_2_page ...

The Data Status: "Partially failed" will allow to calculate and analyse a signal in a specific time range.

To specify the valid or invalid ranges it will be desirable to provide additional information on
the intervals in a well defined way.
So, alnalysis software can automatically limit the ...

We discussed on the Task Force Meeting 2025-03-05:

- A new digit at the end of the channel title ? i.e. replacing "V" by another one ? (all the fine locations digits are used)
For special filtering use in the ISOCode on position 16 the "S" for special filtering.
Still, then you will loose the ...

On the task force meeting 2025-03-05 we created some more ideas:

FC = Force Change
FG = Force Gradient (!)
FS = Force Slope (!)
FA = Force rAte
RF = Rate of Force

Decision on next meeting (29th of April 2025).