XCP - Signal Config Filter Editor

This chapter will break down the usage of the XCP - Signal Config Filter Editor (SCFE).

After reading this article, you should have the knowledge:

General usage

In general an ECU is described with an A2L file which includes all signals, parameters, DAQ events and much more.
The SCFE window is used to select signals and parameters from an A2L file and map them to the created pins for the

So it is possible to configure the XCP Encoder Filter or the XCP Decoder Filter with the signals and parameters you need. For example you want to decode the velocity value of your car (which is measured by your connected engine control unit). So you have to select the velocity signal from your A2L and create a output pin with this signal.

Open the SCFE window

You have to open the context menu of the En-/Decode-Filter and choose 'Signal Config Filter Editor'. The dialog like the one you can see below will be displayed. If you have set the MapFilename property of the En-/Decode-Filter, the SCFE will show previously configured pins within the 'Configuration' view of the SCFE. Otherwise you won't see any pins or databases.



Create a new map file

To create a new map file for your filter, go into the SCFE and:

  1. Create a new configuration by choosing 'File' --> 'New Config' --> 'New Config'
  2. Add the A2L file corresponding to your ECU, by using the menu point 'File' --> 'Add Database ...'
  3. After the selected file is parsed, you will see all signals and parameters of your A2L file in the 'Database' view
  4. Safety first, save your config
  5. Within the 'Configuration' view you can add pins to your configuration by open the context menu and clicking 'Add Output Pin' or 'Add Input Pin'

  6. Now it's time to configure the added pins. If a pin is selected, you can see its properties in the 'Properties' view. It's important to edit the properties to enable the full functionality of the XCP communication:

    PropertyValueDescription
    cycletimeMillisecondsOld behaviour: Cyclic transmission of a buffer. Default -1.
    Note: this variable will not effect anything and will be disabled in the next releases.
    daq_eventcStringDefines the DAQ event channel
    daq_prescalertUInt32Transmission rate prescaler (=>1)
    namecStringPin name
    polling_intervaltUInt32Defines the polling interval

  7. After naming and configuring the pin you can drag and drop one or more signals from the 'Database' view to your new pin.
    So the configruation could look like this:

  8. Like before, you have to configure your used signals/parameters via the 'Properties' view:

    PropertyValueDescription
    bitstUIntFor bit field elements
    child_indextUInt32Used as Structindex
    corrective_factortFloat64Additional factor
    corrective_offsettFloat64Additional offset
    counttIntFor array like signals, this specifies the dimension
    limitstIntCan be used to override the property setting for global limit handling
    macrocStringName of a macro that should be executed to fill the structure element
    Note: this variable will not effect anything, but will be enabled in one of the next releases.
    namecStringName of the structure element
    raw_valuetBoolSwitch if a raw value is used
    sign_signalcStringNote: The sign_signal attribute of an element node is only within the ADTF_DeviceToolbox necessary.
    Leave this proberty always empty, otherwise it is not possible to init your session.
    signalcStringThe exact notation of the SignalName as in the corresponding A2L file
    typetElementDataTypeData type of the structure element
    unit_conversiontBoolFor read-in "unit_conversion"
    valuecVariantDefault value of the signal

  9. After you have completed the configuration step save the mapping by clicking the 'OK'-Button.
    The currently opend map file will be used by the selected filter, which includes now your new configured pin.

Summary

We would like to roundup the article by explaining further SCFE functionalities.

The 'File' - menu

With the help of the file menu Configuration files and database files are handled.
The following menu points are available:

The 'Mode' menu

The 'Mode' menu offers additional operations that can be executed. The following menu entries are available: