custom channels




Every test has it's predefined list of required and optional input channels, based on the internal evaluation. When implementing custom KPIs, sometimes additional channels are required. These can be an additional interal channels from the MXeval channel library or a custom channel. Custom channels can be managed with the Custom Channel browser.


Custom channel browser


When new channels are required for a custom KPI calculation, that are not listed in MXeval's internal channel list, new custom channels can be created with the Custom Channel Browser.

Every channel has the following properties attached:


  • Name

Name of the channel
  • Fieldname

Programmatic fieldname of the channel. This Fieldname is required when using custom code implementation (e.g. Custom KPIs or Custom Channel Configuration)

The fieldname is a unique identifier for the channel!
  • Unit

Unit of the channel
  • Size

Size of the channel

  • 1xN (vector): Signal input (e.g. steering wheel angle)
  • 1x1 (scalar): Constant scalar input (e.g. vehicle width)
  • Class

Class of the channel

  • double: Numeric input (e.g. steering wheel angle)
  • char: Character input (e.g. comment)
  • Plausibility Range

Range of the signal, where it is assumed to be valid. 

In the signal validation right before the evaluation, every channel gets validated. If the signal values are outside of the defined plausibility range, there will be a corresponding warning.

This helps to quickly identify problems within the evaluation, which are often caused by issues with the input signals.
  • Description

Description of the channel, to provide additional information about it.


All of these properties can be directly inpected at the Standard Channel Configuration.