Logo Agriculture XPRT
Companies
Products
Services
Software
Training
Applications
Sign in
List your business
Sontheim Industrie Elektronik GmbH
About
Downloads
  2. Companies
  3. Sontheim Industrie Elektronik GmbH
  4. Software
  5. Sontheim CLC Manager - Version 2.0 - ...

Sontheim CLC Manager - Version 2.0 -Web-based Communication Life­cycle Manager

SHARE

Web-based Communication Life­cycle Manager, based on the ODX standard. With integrated code generator. 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.

Most popular related searches
cloud-based management

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
  • 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
  • ODX data:
    • Description 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 services: Description of diagnostic data such as request/response, param, DataObjectProp, CompuMethod, Unit;
  • Repeated use by references
  • Requirements: Data collection of the communication interfaces and the vehicle/machine structure;
  • Protocol-independent data input
  • Implementation:
    • Detailed 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
  • Test:
    • Execution 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 diagnosis:
    • Code 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)