New MainLocations for Active Safety Channels

Suggestions for new codes
Locked
derpmann
Posts: 460
Joined: Tue Apr 24, 2007 5:32 am
Location: Volkswagen AG, Wolfsburg - Germany

New MainLocations for Active Safety Channels

Post by derpmann »

Dear colleagues,
it is possible to exchange measurement data from active safety tests using the MME data format.
EuroNCAP will go this way and has a list of Channel Codes integrated in their Technical Bulletin 21.
Please see chapter 2.14-2.16 in viewtopic.php?f=38&t=444 .

According to this proposal and our former discussion viewtopic.php?f=145&t=476
we need some additional MainLocations for different targets:
  • PEDA for the pedestrian adult target
  • PEDC for the pedestrian child target
  • CYCL for the cyclist target
and for the typical events and time channels:
  • TTTC Time to Collision
  • TAEB Time when AEB activates
  • TFCW Time when FCW activates
  • TLKA Time when LKA activates
  • TLDW Time when LDW activates
  • TLCR Time when vehicle crosses a line
  • TIMP Time when vehicle impacts the target
Best regards
Peter
derpmann
Posts: 460
Joined: Tue Apr 24, 2007 5:32 am
Location: Volkswagen AG, Wolfsburg - Germany

Re: New MainLocations for Active Safety Channels

Post by derpmann »

Dear colleagues,
in the meeting at January 29th 2020 the TaskForce agreed to the proposal.

Reasons:
The time and event channels are necessary for all NCAP tests.
They start with the letter T and contain the common 3 character abbreviations in active safety tests.

For Car To Car (C2C) and Car To VulnerableRoadUser (VRU) scenarios the structure mounted on the carrier
can simulate a vehicle, an adult pedestrian , a child pedestrian and a bicyclist.
The connected measurements and limits differ seriously. This necessitates the usage of different channel codes.

Alternative solutions:
  1. In a first attempt the targets could be described by different testobjects.
    This leads to an inefficient increase of codes conflicting with the passive safety testobjects.
  2. The usage of FineLocation3 leads to conflicts with existing codes:
    for example CY = Center in Y Direction, A? used for Airbags, P? used for pedestrian impactors, ...
  3. The usage of MainLocations is similar to the needs for filmanalysis or static data measurements,
    to describe the structure on the carrier.
Result:
  1. The Testobject of the target is 2
  2. The MainLocation is VEHC, PEDA, PEDC or CYCL depending on the mounted structure
  3. The FineLocation3 remains free for the fine specification of the measurement
Best regards
Peter
Locked

Return to “Additional codes”