This chapter will break down the usage of the XCP - Signal Config Filter Editor (SCFE).
After reading this article, you should have the knowledge:
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
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.
To create a new map file for your filter, go into the SCFE and:
|cycletime||Milliseconds||Old behaviour: Cyclic transmission of a buffer. Default -1.
Note: this variable will not effect anything and will be disabled in the next releases.
|daq_event||cString||Defines the DAQ event channel|
|daq_prescaler||tUInt32||Transmission rate prescaler (=>1)|
|polling_interval||tUInt32||Defines the polling interval|
|bits||tUInt||For bit field elements|
|child_index||tUInt32||Used as Structindex|
|count||tInt||For array like signals, this specifies the dimension|
|limits||tInt||Can be used to override the property setting for global limit handling|
|macro||cString||Name 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.
|name||cString||Name of the structure element|
|raw_value||tBool||Switch if a raw value is used|
|sign_signal||cString||Note: 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.
|signal||cString||The exact notation of the SignalName as in the corresponding A2L file|
|type||tElementDataType||Data type of the structure element|
|unit_conversion||tBool||For read-in "unit_conversion"|
|value||cVariant||Default value of the signal|
We would like to roundup the article by explaining further SCFE functionalities.
With the help of the file menu Configuration files and database files are handled.
The following menu points are available:
New Config: A new and empty map file will be generated. The 'Configuration' view will be empty.
Open Config...: An existing map file can be opened. The content of the file will be displayed in the 'Configuration' view.
Save Config: The current content of the 'Configuration' view will be saved to the currently loaded map file.
Save Config as...: The current content of the 'Configuration' view will be saved in a new map file.
Export Media Description...: With the help of this menu entry you can create a media description file for the current configuration.
Add Database: An existing database file (e.g. *.a2l) has to be selected. The content of the file will be added to the 'Database' view as a new node.
The 'Mode' menu offers additional operations that can be executed. The following menu entries are available:
Link Mode: The link mode can be (de-)activated. With activated link mode it is possible to relink existing structure elements in the configuration tree to another database signal. If the link mode is activated the text "Link Mode is active!" is shown in the statusbar.
Check...: The current configuration will be checked. If an error is detected a message box is shown.