Hello,
for annotation you find attached a list of the 44 available channels of the FlexGTR Pedestrian Leg Impactor and its ISO Codes. The chart has been created and discussed in the Technical Evaluation Group of the FlexGTR.
Thanks for consideration.
Best regards
Matthias Winkler
MESSRING Systembau MSG GmbH
ISO Code suggestion for the FlexGTR
-
- Posts: 3
- Joined: Thu Feb 19, 2009 7:29 am
- Company: MESSRING Systembau MSG GmbH
- Location: MESSRING, Krailling (Germany)
ISO Code suggestion for the FlexGTR
- Attachments
-
- Suggestion ISO-MME-Codes FlexGTR_090227ISO.pdf
- FlexGTR channel overview
- (163.2 KiB) Downloaded 754 times
-
- Posts: 441
- Joined: Tue Apr 24, 2007 9:14 am
- Company: IAT mbh
- Location: IAT Berlin - Germany
- Contact:
Re: ISO Code suggestion for the FlexGTR
Hello Matthias,
thank you for the information on the PF impactor. I have discussed the coding with Peter Derpmann Hagenstroem.
We will include the coding proposal in the next release of the ISO MME Database (V1.6). We will change the TOB (ISO[1]) to "D" for all codes. This is the coding for "Dummy /Dummy Impactor" and used for all other Pedestrian Impactors also. The "PF" is alread included in the version 1.5 of the Coding Database.
We realised that the construction (AC,... ligaments) and impact direction for the"PF" design now clarifies that a lateral impact of the leg against the vehicle front is simulated with this impactor. This is sligthly different from the older (more simple) lower leg. Here we have coded the impact direction with X.
Especially it is confusing, that the PF impactor seems to be hit at the medial side (inner side, right side in the supplied photo). Is this correct??
Just to explain this:
The intention for the old coding has been that is was not clear from the old design if the leg impactor simulates a lateral or frontal impact to the leg. Therefore we decided that the flight direction of this Test Object will be X.
So for the "PF" impactor the impact direction is coded with Y. We will respect this discrepancy to the coding for the older free flight lower leg, but actually will not change the old coding.
I also realised that the numbering of the Femur and Tibia Accelerations is not "unidirectional" (like from the top to the bottom) but from the Knee to the impactor end. This is not typical for numbers in coding. If the numbering of the segments is an official numbering for the PF impactor it make sense to use it. If not I would propose to number from the top down for the Femur and the Tibia also.
There is a need to introduce new Fine Location 1 codes:
AC = Anterior Cruciate Ligament
LC = Lateral Collateral Ligament
MC = Medial Collateral Ligament
PC = Posterior Cruciate Ligament
Actually these are not defined in the database. If anyone suggests a (future) conflict with these Fine Location 1 codes please send comments!
Could you supply to us also some information on the Injury Criteria that are under discussion for this test device?
If so we can also define the coding of the CVC's.
Bye,
Dirk
thank you for the information on the PF impactor. I have discussed the coding with Peter Derpmann Hagenstroem.
We will include the coding proposal in the next release of the ISO MME Database (V1.6). We will change the TOB (ISO[1]) to "D" for all codes. This is the coding for "Dummy /Dummy Impactor" and used for all other Pedestrian Impactors also. The "PF" is alread included in the version 1.5 of the Coding Database.
We realised that the construction (AC,... ligaments) and impact direction for the"PF" design now clarifies that a lateral impact of the leg against the vehicle front is simulated with this impactor. This is sligthly different from the older (more simple) lower leg. Here we have coded the impact direction with X.
Especially it is confusing, that the PF impactor seems to be hit at the medial side (inner side, right side in the supplied photo). Is this correct??
Just to explain this:
The intention for the old coding has been that is was not clear from the old design if the leg impactor simulates a lateral or frontal impact to the leg. Therefore we decided that the flight direction of this Test Object will be X.
So for the "PF" impactor the impact direction is coded with Y. We will respect this discrepancy to the coding for the older free flight lower leg, but actually will not change the old coding.
I also realised that the numbering of the Femur and Tibia Accelerations is not "unidirectional" (like from the top to the bottom) but from the Knee to the impactor end. This is not typical for numbers in coding. If the numbering of the segments is an official numbering for the PF impactor it make sense to use it. If not I would propose to number from the top down for the Femur and the Tibia also.
There is a need to introduce new Fine Location 1 codes:
AC = Anterior Cruciate Ligament
LC = Lateral Collateral Ligament
MC = Medial Collateral Ligament
PC = Posterior Cruciate Ligament
Actually these are not defined in the database. If anyone suggests a (future) conflict with these Fine Location 1 codes please send comments!
Could you supply to us also some information on the Injury Criteria that are under discussion for this test device?
If so we can also define the coding of the CVC's.
Bye,
Dirk
-
- Posts: 3
- Joined: Thu Feb 19, 2009 7:29 am
- Company: MESSRING Systembau MSG GmbH
- Location: MESSRING, Krailling (Germany)
Re: ISO Code suggestion for the FlexGTR
Hello Dirk,
Thanks for accepting the proposal and your feedback. Regarding the open questions I can answer as follows:
1. Thanks for adding the “D” for the test object. I have changed it in the chart.
2. I have adopted the “PF” for FL3 for the FlexGTR as successor of the FlexPLI.
3. The FlexGTR simulates the right leg of a pedestrian crossing the car front from the left to the right. That means the leg is hit laterally at the outer side of the knee. In the pic you face the front of the leg. (To adapt the FlexGTR to the standard dummy coordinate system regarding SAE J1733 we decide to set the impact direction “Y”.)
4. There was a mistake in the numbering of the segment accels and the strain gages in the code chart from 27.02.09. I have changed the femur accels to the inverse order. That means there is a uniform ascending numbering from the knee to the upper end of the femur and the lower end of the tibia. This became common procedure in the user group during development and therefore it was adopted to the ISO-Code. I can announce this “conflict with the standard” in the next meeting to get to know if there is a need and what the effort to adapt the documentation is.
5. The evaluation procedure for the FlexGTR data is not fixed yet. I can not state anything about generated channels before the next FlexTEG meeting. I will announce also this issue.
I have put according revision of the code chart to this text (see attachment).
Thanks a lot.
Regards
Matthias
Thanks for accepting the proposal and your feedback. Regarding the open questions I can answer as follows:
1. Thanks for adding the “D” for the test object. I have changed it in the chart.
2. I have adopted the “PF” for FL3 for the FlexGTR as successor of the FlexPLI.
3. The FlexGTR simulates the right leg of a pedestrian crossing the car front from the left to the right. That means the leg is hit laterally at the outer side of the knee. In the pic you face the front of the leg. (To adapt the FlexGTR to the standard dummy coordinate system regarding SAE J1733 we decide to set the impact direction “Y”.)
4. There was a mistake in the numbering of the segment accels and the strain gages in the code chart from 27.02.09. I have changed the femur accels to the inverse order. That means there is a uniform ascending numbering from the knee to the upper end of the femur and the lower end of the tibia. This became common procedure in the user group during development and therefore it was adopted to the ISO-Code. I can announce this “conflict with the standard” in the next meeting to get to know if there is a need and what the effort to adapt the documentation is.
5. The evaluation procedure for the FlexGTR data is not fixed yet. I can not state anything about generated channels before the next FlexTEG meeting. I will announce also this issue.
I have put according revision of the code chart to this text (see attachment).
Thanks a lot.
Regards
Matthias
- Attachments
-
- Suggestion ISO-MME-Codes FlexGTR_090518ISO.xls
- Revision 18.05.2009
- (372 KiB) Downloaded 778 times
-
- Posts: 3
- Joined: Thu Feb 19, 2009 7:29 am
- Company: MESSRING Systembau MSG GmbH
- Location: MESSRING, Krailling (Germany)
Re: ISO Code suggestion for the FlexGTR
Hello,
During the test series in the FlexGTR Technical Evaluation Group and its last meeting the ISO-MME Code for the Leg Impactor has been discussed once more.
One open question out of the ISO-MME forum could be clarified: Are additional codes for the CVC’s necessary? – No, because the Injury Criteria are not calculated. Thresholds have been defined directly in the measured dimensions of the Tibia Moment, MCL, ACL and PCL Elongation.
I have attached the last revision of the FlexGTR-ISO-Code overview with a changing of the direction code for the Knee Elongations (yellow cells). The coding has been changed from “Z” to “0”, due to the fact that the pots are not aligned straight in Z direction. So “0” as “undefined” is preferable to prevent confusion.
Additionally it has been stated, that the channel number order from the knee to the upper and lower end of the impactor is kept as shown in the figures of the attached document.
Thanks for annotation.
Best regards
Matthias Winkler
MESSRING Systembau MSG GmbH
During the test series in the FlexGTR Technical Evaluation Group and its last meeting the ISO-MME Code for the Leg Impactor has been discussed once more.
One open question out of the ISO-MME forum could be clarified: Are additional codes for the CVC’s necessary? – No, because the Injury Criteria are not calculated. Thresholds have been defined directly in the measured dimensions of the Tibia Moment, MCL, ACL and PCL Elongation.
I have attached the last revision of the FlexGTR-ISO-Code overview with a changing of the direction code for the Knee Elongations (yellow cells). The coding has been changed from “Z” to “0”, due to the fact that the pots are not aligned straight in Z direction. So “0” as “undefined” is preferable to prevent confusion.
Additionally it has been stated, that the channel number order from the knee to the upper and lower end of the impactor is kept as shown in the figures of the attached document.
Thanks for annotation.
Best regards
Matthias Winkler
MESSRING Systembau MSG GmbH
- Attachments
-
- Suggestion ISO-MME-Codes FlexGTR_091029ISO.xls
- (372.5 KiB) Downloaded 734 times
-
- Posts: 441
- Joined: Tue Apr 24, 2007 9:14 am
- Company: IAT mbh
- Location: IAT Berlin - Germany
- Contact:
Re: ISO Code suggestion for the FlexGTR
Dear Matthias,
thank you for the information. We will await the results of the Round-Robin testing for the Flex GTR before finally including the codes in to the database. Please inform us when the verification is done.
Bye
Dirk
thank you for the information. We will await the results of the Round-Robin testing for the Flex GTR before finally including the codes in to the database. Please inform us when the verification is done.
Bye
Dirk