Search found 355 matches

by DiVe
Wed Oct 18, 2023 12:00 pm
Forum: Additional codes
Topic: aPLI Coding for Bending Moment with Factors
Replies: 2
Views: 545

Re: aPLI Coding for Bending Moment with Factors

Based on the discussion at the AK3 Meeting (2023-10-18, VDA) this topic is postponed.
Currently the differences of the two setups are evaluated regarding the realistic differences
in the sensor calibration/sensitivity.
by DiVe
Tue Oct 17, 2023 10:42 am
Forum: Additional codes
Topic: aPLI Coding for Bending Moment with Factors
Replies: 2
Views: 545

Re: aPLI Coding for Bending Moment with Factors

Please find a parallel topic regarding the implementation of channel codes at:
viewtopic.php?t=701
by DiVe
Tue Oct 17, 2023 10:41 am
Forum: Additional codes
Topic: Additional code for aPLI Moment Channels
Replies: 3
Views: 550

Re: Additional code for aPLI Moment Channels

This topic will be linked to the topic from Paul:
viewtopic.php?t=697
by DiVe
Tue Oct 17, 2023 10:39 am
Forum: Clarification
Topic: Allowed characters for Descriptor Values
Replies: 0
Views: 806

Allowed characters for Descriptor Values

DRAFT In the specification of the ISO MME (V1.x) several descriptor values are given the attribute: "alphanumeric" Indeed this is not very specific. You will find (https://en.wiktionary.org/wiki/alphanumeric): 2023-10-17 12_20_44-alphanumeric - Wiktionary, the free dictionary – Mozilla Fi...
by DiVe
Tue Oct 17, 2023 10:14 am
Forum: Additional codes
Topic: Additional code for aPLI Moment Channels
Replies: 3
Views: 550

Re: Additional code for aPLI Moment Channels

... some reference for the compensation factor for the aPLI:
by DiVe
Tue Oct 17, 2023 9:57 am
Forum: WorldSID (WS, WF)
Topic: WordSID 5th (WF)
Replies: 0
Views: 869

WordSID 5th (WF)

A request has been placed to prepare the figure for the WorldSID 5th dummy. The base FL3 coding is already defined. the design is similar to the WS. the shoulder MTRAC is replaced by a string pot an alternative instrumentation with RibEye is relevant as this is evaluated by NHTSA What is needed: Rec...
by DiVe
Tue Oct 17, 2023 9:17 am
Forum: Additional codes
Topic: Additional code for aPLI Moment Channels
Replies: 3
Views: 550

Additional code for aPLI Moment Channels

Dear Colleagues, there is a request for the handling of the Moment Channel Codes for the aPLI . Basically the codes are already defined and could be found in the database as well as in the figures: 2023-10-13 15_22_21-C__Users_vetter_Desktop_ISO_ MME_aPLI_TibiaMoment Codes.png - Greenshot Editor.png...
by DiVe
Wed Sep 20, 2023 4:55 pm
Forum: Additional codes
Topic: Additional codes for WS THSP AVX/AVZ?
Replies: 5
Views: 1656

Re: Additional codes for WS THSP AVX/AVZ?

Added Codes to database 1.6.3p1:
2023-09-20 18_54_22-Access - mme_code _ Database- D__Daten_03_Projekte_10_ISO_02_DB_##Work_01_Versio.png
2023-09-20 18_54_22-Access - mme_code _ Database- D__Daten_03_Projekte_10_ISO_02_DB_##Work_01_Versio.png (13.23 KiB) Viewed 560 times
Item closed.
by DiVe
Wed Sep 20, 2023 4:27 pm
Forum: Active Safety Codes
Topic: Additional field descriptors in MME file for active safety
Replies: 4
Views: 1428

Re: Additional field descriptors in MME file for active safety

Dear colleagues, as decided on the Task Force Meeting (2023-09-20) for the part of this topic that is related to "Intended Velocity" The intended velocity will be coded for each test object as: Nominal vel. test object X Nom. lat. vel. test object X like Nominal vel. test object 1 : Nom. l...
by DiVe
Wed Sep 20, 2023 2:01 pm
Forum: Additional codes
Topic: Additional descriptor for "Intended Velocity"
Replies: 2
Views: 886

Re: Additional descriptor for "Intended Velocity"

Dear colleagues, as decided on the Task Force Meeting (2023-09-20): The intended velocity will be coded for each test object as: Nominal vel. test object X Nom. lat. vel. test object X like Nominal vel. test object 1 : Nom. lat. vel. test object 1: These descriptors are optional. This will be added ...
by DiVe
Mon Aug 21, 2023 9:23 am
Forum: RED A (1.6.x)
Topic: RED A (1.6) - Examples and Hints - Revision 3 (2023)
Replies: 1
Views: 858

Re: RED A (1.6) - Examples and Hints - Revision 3 (2023)

I forward here some feedback to update review the Video Codec recommendations in 2.3.2 / 2.3.4:


2023-08-21 11_18_50-2020_06_17_ISO_TS13499_RED_A_1_6_2 - PDF-XChange Editor.png
2023-08-21 11_18_50-2020_06_17_ISO_TS13499_RED_A_1_6_2 - PDF-XChange Editor.png (14.58 KiB) Viewed 827 times
2023-08-21 11_19_54-2020_06_17_ISO_TS13499_RED_A_1_6_2 - PDF-XChange Editor.png
2023-08-21 11_19_54-2020_06_17_ISO_TS13499_RED_A_1_6_2 - PDF-XChange Editor.png (82.33 KiB) Viewed 827 times
by DiVe
Thu Aug 17, 2023 8:45 am
Forum: RED A (1.6.x)
Topic: RED A (1.6) - Examples and Hints - Revision 3 (2023)
Replies: 1
Views: 858

RED A (1.6) - Examples and Hints - Revision 3 (2023)

Dear colleagues, this is a new topic to collect the important extensions for the next version of the REDs for 2023. I will start here a list with some extensions from my perspective and hope for more contributions. Please feel free to also provide proposals of text or tables of how to add this to RE...
by DiVe
Mon Jul 31, 2023 8:34 am
Forum: Additional codes
Topic: Airbag Coding
Replies: 1
Views: 558

Re: Airbag Coding

Dear colleages,
please find here, as reference, the actually available figures for Airbag Coding:
ISOMME-Airbag-Codes-2020.pdf
(28.31 KiB) Downloaded 116 times
by DiVe
Mon Jul 31, 2023 7:45 am
Forum: Additional codes
Topic: Airbag Coding
Replies: 1
Views: 558

Airbag Coding

Dear colleagues, there is a request and proposal from BMW to discuss and document a more complete coding approach for the measurement channels related to Airbags. You will find a proposal attached. We will have a discussion in the next task force meeting and hope for feedback, experiences and advice...
by DiVe
Fri Jul 21, 2023 12:31 pm
Forum: Additional codes
Topic: MME attribute for the impact point of pedestrian protection tests
Replies: 1
Views: 469

Re: MME attribute for the impact point of pedestrian protection tests

Dear Sebastian, two comments for the proposal from my side: 1.If we go for a test type specific naming with "Pedestrian" of the descriptors, we should use optional (dot) descriptors. 2.In active safety we have used a specific notation for value pairs. Infact that was for multiple pairs in ...

Go to advanced search