ISO-MME

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).

There is a request from Humanetics to step forward with the coding list of the THOR AV.
In the topic: https://www.iso-mme.org/forum/viewtopic.php?p=1249
we defined the base FL3 code for this kind of dummies.

For the specific variant of Humanetics a channel list and may figures are desired to ...

Dear All,
there is an ongoing discussion on the calculation of the 1D TRAC (like in ECE R135, WS Dummy certification) displacement
from a 3D MTRAC in the WS.
The ancorage point of the 1D TRAC on the spine was different as in the current 2D and 3D devices.
So the current 2D instrumentation can only ...

Dear All,

for the discussion I have the following topics related to the Data Status:
Sorting of the list from "Good" to "Bad"
Is NOVALUE to be treated as "data invalid" or as "ok"?
Partially failed should be combined with a valid time range for the analysis (or a list of invalid intervals ...

Dear All,

to cover all parts of the proposed HV coding I need to add the following codes for FL3:

R0 = R0 Voltage; comment: as reference for HV measurement
CH = Chassis; comment: as reference for HV measurement

I have prepared this change for a final decision on the next meeting.
2024-11-25 22 ...

Dear All,

please find the related figures for review and discussion at the board:
viewforum.php?f=159

Dear All,

based on the findings on the Task Force meeting today, I have prepared an updated version of the RED A proposal.
The changes are:

Velocity descriptors (page 8 )
Implemented new namings that uses the abbreviation "TOB" for better readability
and less abbreviated words in the ...

A new proposal using the TOB abbreviation could be:
Better readability (less abreviations).
Please vote

Kind regards,
Dirk

Dear All,
this topic is also related to the new proposal vor RED A:
viewtopic.php?t=718

Here we have also a proposal for the additional velocity information:

Dear Mr Washausen,

my concern is, that it will not be clear which value belongs to which device without further
information.

Just another idea for the discussion:
Can we use descriptors with "counters" and add the information on the related device?
Like:

Nominal vel. test object X :18.889 ...

Dear Mr. Washausen,

I would agree that an abbreviation for "test object" will improve the readability of the descriptors.
Leaving more space for relevant words and characters.

I would propose to use "TOB" as abbreviation instead of TO.

Kind regards,
Dirk