Skip to end of metadata
Go to start of metadata

Graphical User Interface

The screenshot above will give you a quick impression about how the viewer could look. The viewer is based on Qt so there are widgets you could move around and resize how you like. Your settings of position and size of the widgets are stored when you close the viewer so that you have exact the same window when you start at the next time.

To get a better understanding about the DLT viewer parts they will be explained in more detail.

Menu and toolbar

In the window title you can find the absolute path of your project file and the project name. If you start the DLT viewer with no default project file it will create an unnamed project. After the project name you can read the version of the DLT viewer. In any case of contact with the development team, please report the version of the DLT viewer.

The menu consists of

  • File
  • Search
  • Project
  • Config
  • DLT
  • Filter
  • Plugin
  • View
  • Help

. . . which provides the main functionality to the user which will be described later.

Project widget

The project widget allows you to configure and control the project, load an existing project, save a change configuration to the DLT daemon and do many other stuff. The project is split into three configuration parts.

  • The Config which contains all connected ECUs/Devices. Each

Device contains its provided applications. Each application provides its used contexts.

  • The Plugin part shows the loaded Plugins. The development team

provides a Plugin SDK to you. You are able to write your own DLT viewer plugins to decode messages or display a GUI. Here is more information about the Plugin SDK. TBD In the Settings you can select a default project, which is loaded during start-up.

  • The Filter part configures the Filters and Marker, which are used

show or mark only specific DLT messages.

DLT Message Table

In the DLT Message table you see all DLT messages in the current selected DLT log file. You can scroll through the whole log file. New received DLT messages are written into the DLT log file. If AutoScroll is enabled in the settings the table scroll always to the end, when new DLT messages are received.

Description of the columns:

  • Index Index shows the number of the DLT message in the DLT log

file, the header shows all header parameters

  • Time Time when the messages was sent.
  • Timestamp Time since the startup of the HU
  • Count Cyclical counter, one per context. Can be used to detect lost


  • Ecuid Name of the sending ECU
  • Apid Indetifier of the message sender application. Defined by the


  • Ctid Context indentifier of the message sender. Defined by the

sender context.

  • Type Type of the message. Log/Trace
  • Subtype Trace type, or Log level.
  • Mode Verbose/Non-Verbose
  • Args How many arguments are in the payload.
  • Payload The payload shows all parameters of the log message.

If a filter is configured, you will see only these DLT messages, which match the filter. Remove all filters, if you want to see all messages. If some plugins are configured and a DLT message matches a plugin the decoded information for Header and Payload is displayed. DLT log files can be loaded or saved in the file menu.

DLT Viewer Plugin

Every DLT Viewer Plugin is opened in a widget, if the plugin is enabled and shown. The DLT Viewer Plugin is shown in the screenshot. You can move every widget at a different position. The poition of the widget is restored after restart of the DLT Viewer.

The Footer shows the following information:

  • The complete filename of the currently opened DLT File
  • The version numbers of the SW of the target, if the DLT file contains any DLT messages with version information.
  • Statistics about received bytes via target connections.

<< DLT Viewer Manual || View DLT files >>

Copied from MediaWiki
Last Edit: 14:56, 7 January 2014‎ Alexander.wenzel

  • No labels