ISO-MME

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

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

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

Dear Matthieu, - A new digit at the end of the channel title ? i.e. replacing "V" by another one ? (all the fine locations digits are used) That would be difficult as there might be different intervals used in the moving average. Actually, i expect that most video tracking data is smoothed...

Based on the first document I checked the descriptor length in the proposal and send some comments:
And the comments from the E-Mail:
Kind regards,
Dirk

Dear All, we started the discussion with Corinna Klug and received valuable feedback. Mrs Klug has provides alternative descriptor names and the topic will be discussed internal at EuroNCAP. Please find here the state of work as EXCEL-tables: MME-Files-VTC.xlsx ISO_MME_Channels_Frontal_Simulations.x...

Dear Trevor, we do it the same way in our analysis software. We combine the impact side information of the test object with the "seating position" (vehicle zone): Impact side LE -> SP 1 and 4 (and 7,...) are Near side; SP 3 and 6 (and 9,...) are Far Side Impact Side RI -> SP 3 and 6 (and 9...

Dear All, we have coded in 2016 the calculated channels for the Ankle Moments that are proposed for future use with the USNCAP rating. ANKL_THOR_Codes.png In the NHTSA Dummy certification manuals these codes will be used without the FL2 Code "LO". ANKL_THOR_Codes_NHTSA.png Would we like to...

In all Dummy figures that covers Chect/Abdomen deflection a link/reference to the figures regarding "Chest Deflection" measurement should be added. So, alternative instrumentation options and coding could be found better. Reference RED C? Naming of the Figures will vary: ISO_CHST_1_162_202...

Dear All, please find here the document under discussion for the RED A 2024. The changes cover the following forum topics: Precise formulation for 999+ channels (A.2.2.8): https://www.iso-mme.org/forum/viewtopic.php?t=684 additional descriptor for "nominal/intended velocity" (A.2.1.1): htt...

The specific temperature sensor location of the ISO/TR 27957 needs to be reflected in the Dummy Figures. In the Topic "WorldSID (WS) - 2024???? revision" : https://www.iso-mme.org/forum/viewtopic.php?t=716 we start the implemenation for the WS, based on the NHTSA Dummy Qualification requir...