CLC Manager 2.0
CLC Manager 2.0
CLC Manager 2.0
CLC Manager 2.0
CLC Manager 2.0
CLC Manager 2.0

CLC Manager 2.0

Web-based Communication Life­cycle Manager, based on the ODX standard. With integrated code generator

Key Features

  • Web-based tool
  • Management of all fieldbus-based data from specification to release
  • Development, mapping and maintenance of the communication interfaces of ECUs
  • Description of the entire data flow between ECUs and in the ECU itself
  • Simple linking with the Sontheim MDT®
  • ODX 2.2.0 support


Communication Lifecycle Manager 2.0 (CLCM 2.0)
The CLCM 2.0 of Sontheim Industrie Elektronik GmbH is a central system for the management and creation of diagnostic and com­mu­ni­ca­tion de­scrip­tions of ECUs and entire vehicles. It is a client-server based web application that allows several users to work together on a project. No client installation is required and the server can be accessed from different platforms via the browser. The CLCM 2.0 can be integrated into the existing in­fra­struc­ture and de­vel­opment process. Thus it can optimally accompany all steps in the development of ECUs and vehicles.

All advantages at a glance:

  • High-level overall vehicle structure du­ring the re­quire­ment phase
  • More precise specification of the ECUs du­ring the im­ple­men­ta­tion phase
  • Vali­da­tion of the de­scribed dia­gnos­tic and com­mu­ni­cation interfaces and the mapped bus systems during the test phase
  • Provision of generated source code, documentation and diagnostic description after the release

Description of diagnostics and com­munication
The diagnostic interface of the ECUs is defined in ODX 2.2.0 format. In addition, a description of the communication between the ECUs within the vehicle network can be added. The described dia­gnos­tic data serve as a database for source code generation and doc­u­men­ta­tion. The data is stored on a database server, which enables the man­age­ment of large diagnostic projects. Existing legacy data or data provided by the supplier can be imported at any time. An in­te­gra­ted vers­io­ning history displays all chan­ges in the database and allows access to older data statuses for export or display.

The CLCM 2.0 is independent of the protocol and com­mu­ni­ca­tion system used to describe the diagnostic and com­mu­ni­ca­tion data. Thus various technologies are supported, including: CAN, K-Line, Ethernet, EtherCAT, J1939, KWP2000onCAN, UDS, CANOpen, UDP, TCP/IP etc.

Code Generator
The CLCM 2.0 has a customizable code generator that can be used to create source code and documentation based on the dia­gnos­tic data. The output is fully cus­to­miz­able and can be used by dif­fer­ent plat­forms and pro­gram­ming languages. This allows in­te­gra­tion into ex­is­ting software modules and libraries.

Possible areas of application are:

  • Source code for ECU software, dia­gnos­tic app­li­ca­tions and test environments
  • Documentation for the development, production and service departments

The code generator can be integrated into the customer-specific build infrastructure.

Extension API
The CLCM 2.0 has an extension API that allows you to change the default views and create new cus­tom views. Extensions are written in a .NET pro­gram­ming language (e.g. C#) and have access to the complete diagnostic data of the projects.

User Management

  • Access to data and files can be restricted for spe­cif­ic user groups and individual users.
  • Functions can be switched on and off for spe­cif­ic user groups and in­di­vi­dual users.
  • Supports authentication via Active Di­rec­tory

Technical Data

ODX dataDescription of all vehicle diagnostic and ECU data in XML
Extended to complete image of all communication data
Hierarchy models to avoid duplicate data
Data abstraction, overwriting and repeated use by reference diagnostic services
Diagnostic servicesDescription of diagnostic data such as request/response, param, DataObjectProp, CompuMethod, Unit;
Repeated use by references
RequirementsData collection of the communication interfaces and the vehicle/machine structure;
Protocol-independent data input
ImplementationDetailed implementation of the interfaces
Import function for .dbc and a2I
Project view for ODX files, style sheets and test setups
Detailed view for comfortable creation of ODX data Table view for editing ODX data even without ODX knowledge
TestExecution of communication processes in a test environment
Creation of test specifications and protocols
Adaptation of the test view via style sheets
Comparison with reference values
Release and diagnosisCode generator for different platforms and programming languages
Diagnostic interface to MDT®; Document management via XSLT, data is converted into .pdf or .doc
Firmware release with management and history of different firmware versions
Server requirements (minimum)Windows Server 2016; IIS 10.0; SQL Server 2016; CPU: 4 cores; RAM: 6 GB; Memory: 75 GB
Client requirements (minimum)Webbrowser (Chrome, Firefox, Edge)

Related Products

MDT 2.0 - Modular Authoring System based on standards

MDT® 2.0

Modular authoring sys­tem for the cre­a­tion of complex dia­gnos­tic app­li­ca­tions in the auto­motive sector. Based on ODX and OTX stan­dard and an MCD-3D server.

  • ODX support according to ISO 22901-1
  • OTX support according to ISO 13209
  • MCD-3D Server
  • Platform independent
High-performance Vehicle Communication Interfaces


High-performance Ve­hi­cle Com­mu­ni­ca­tion In­ter­faces for de­vel­op­ment, pro­duc­tion and ser­vice app­li­ca­tions in the auto­mo­tive sector.

  • Up to 6× CAN interface
  • WLAN, LAN, Bluetooth, USB, ...
  • LIN, RS232, RS485, ...
  • With logging function
CANexplorer 4 - Fieldbus analysis software with intuitive handling

CANexplorer 4

Don’t lose any time du­ring CAN bus dia­gnos­tics and ben­e­fit from the mo­du­lar soft­ware for ac­qui­si­tion, proces­sing, dis­play and trans­mis­sion of CAN data.

  • Fieldbus analysis tool
  • User-defined measurement setups
  • Receive, process, send and abstract
  • J1939 and CANopen protocol support