ediabaslib

Configuration generator

The configuration generator is a tool that simplifies generation of XML configuration files.
The generator options menu has the following entries:

• Interface: If a configuration has been loaded on the main page, the same communication interface is also used by the generator as default. With this menu entry a different communication interface could be selected.
  For testing without a vehicle, the interface type Simulation has to be selected. In this case selection of a valid simulation directory containing .sim files is also required.
• Simulation directory: If the interface type Simulation has been selected, this menu entry allows to select the simulation directory.
  If no simulation files are present in the selected directory, the checkbox is unset and the communication is disabled.
• Adapter: With this menu the Bluetooth adapter could be selected. If the device is not coupled already, searching for new devices is possible. This menu is only enabled if interface type BLUETOOTH has been selected.
• Adapter configuration: When using a FTDI USB, Bluetooth or WiFi (with the Replacement firmware for ELM327) adapter this menu allows the adapter configuration. Depending on the adapter type only the CAN baudrate/K-Line interface or more specific parameters could be specified.
• Add errors page: When this checkbox is selected (which is the default) and Errors page will be generated when writing the configuration file. This page will read the error memory of all detected ECUs.
• Detect motorbikes: Activates special detection telegrams for motorbikes. This is not enabled by default and slows down normal car detection.
• Configuration: With this submenu you could select if the configuration is created automatically or manually:
  • Automatic: The ECU configuration will be read from the vehicle with the Read button. This option is only available in BMW mode.
  • Manual X: A manual configuration is stored in the storage with the number X. The ECUs for the configuration have to be added manually with the submenu from the Edit button. Therefore you have to identify the required .GRP or .PRG files on the info page of each ECU in INPA.

.GRP file name is D_MOTOR.GRP and .PRG file name is D60M47A0.PRG

• Data logging: Selecting this menu entry will open a sub menu with multiple data logging options:
  • Create trace file: If the checkbox of this menu is active, a ifh.trc file will be created when executing jobs. The trace file will be created in the LogConfigTools subdirectory.
  • Append trace file: If this checkbox is enabled the trace file is always appended. Otherwise the trace file will be overridden after selection of a vehicle type.
• Translations: (Only for non German languages and BMW mode) This menu opens a submenu that allows configuration of automatic ECU text translation with Yandex.Translate:
  • Translate ECU text: If this menu item is checked, automatic ECU text translation is active.
  • Translation configuration: For automatic translation with various translation providers. For translation a (free) API Key is required. This menu assists to select and configure a translation provider.
  • Clear translation cache: The translations are stored together with the ECU configuration files. To enforce a new translation this menu resets the translation cache.
• Online help: Displays this help page. The vehicle type is detected automatically when pressing the Read button (automatic mode).
  If the manual mode is used this button is named Edit and opens a submenu that allows to add or remove ECU files. Therefore you have to identify the required .GRP or .PRG files on the info page of each ECU in INPA. In VAG mode it’s possible to search for ECUs, but this process is very time consuming.

If the analysis is successful, the detected ECUs are listed and the VIN is displayed in the title bar. The VIN will later be used as subdirectory name for storing the generated configuration.
If an ECU is completely silent (defective) it will not show up in the list!
After selecting an ECU list entry it’s Job page will be displayed. This is the main configuration page for the jobs results that will be added to the configuration file.
The page has the following properties:

• Search field: With the search field in the title bar it’s possible to filter jobs and results that match the filter text.
  It’s either possible to filter the jobs or the results, depending from last selected item type (job or result).
  When changing the item type, the search filter is cleared and closed.
• Page name: This is the title (tab) name for the page in the configuration file.
• ECU name: With this field the name of ECU on the Errors page could be changed.
• Display type: With his check box a graphical (gauge) display for the results could be enabled. The result will be only displayed if Graphical design is set to value other than hidden.
• Font size: The font size of the displayed data on the main page could be specified in 3 steps (Small, Medium and Large).
• Job list: Here all available jobs are listed. Only if the job has a check mark it will be executed later. In the area Comments for job the comments for the selected job will be shown.
  If the BMW database is used, only the known jobs are listed by default. Activating the option show all jobs will display all jobs.
• Job result: Here one more more job results could be selected (with a check mark) that will be displayed later on the page) For the currently selected result the data type and comment will be shown below.
• Display text: This is the text that will be displayed on the page beside the job result.
• Display order: Here the index of the display order could be specified. The default value is 0. If two values are identical, the original order is retained.
• Graphical design: If Display type is set to Graphical display this settings will get visible. The following design types are available:
  • Hidden: The result will not be displayed. If the result value type is not integer or real this is the only option.
  • Simple gauge square: A simple gauge with square border will be displayed.
  • Simple gauge round: A simple gauge with round border will be displayed.
  • Simple gauge with dot: A simple gauge with round border and a dot instead of bar graph will be displayed.

  For the gauge display the value range min value and max value has to be specified also.

• Tag for data logging: If the Log data option is enabled on the main page the result data will get this tag in the log file. If the entry is empty no data will be logged.
• Output format: Here the output format of the result data could be modified. The format specification is in the form of Ediabas result types and formats. Depending on the job data type more or less result types will be listed.
• Read: This button executes the selected job and displays the result in the specified format next to the button.
• Search results: If the result list for a job becomes too large, the results could be filtered with the search widget of the title bar.
• Additional functions: If available in this area some special functions are displayed.
  • Ediabas tool: This button swithes directly to the EDIABAS tool with the current SGBD loaded.
  • Actuator functions: (BMW only) Known actuator functions from the BMW database could be executed directly.
  • Coding: (VAG only) Execute coding funtions.
  • Coding 2: (VAG only) Execute coding 2 funtions.
  • Adaption: (VAG only) Execute adaption funtions.
  • Login: (VAG only) Execute login funtions.
  • Security access: (VAG only) Execute security access funtions.

With the Save button on the main configuration page the configuration will be stored and used as default on the main page. Hint: A long click on the ECU list opens a submenu that allows to change the order of the ECU entries in the list.

This site is open source. Improve this page.