Central tool for the creation of the description of the communication between all ECUs within a vehicle.
The Communication life cycle manager (CLCM)
The CLC Manager of the company Sontheim serves as a central tool for the complete data management of the communication between all controllers within a vehicle, based on ODX standard. Based on ODX not only the communication is described here with the diagnostic tester also of the control units with each other. This database can then serve as a basis for the creation of source code and documentation. With the beginning of the development for the functions of a vehicle the CLC Manager already supports to define the complete vehicle network and communication of the control units with each other. The CLC Manager provides functions to create and manage the entire communication. What starts in the first step as a rough description of communication on application ECU or task level, is then specified by the specifications of the protocols and the lines of communications.
Integrated test functions
Now this data description can serve as the basis for the source code generation, diagnostic application and documentation. In addition, this data can be used to test the implemented functions in the control unit. To do this, the CLC Manager executes the request on the defined communication system and compares the results obtained with test scores. These test values can be defined at any time in the development process. The test results are placed in a test log.
Multi protocoll and physical layer support
The CLC Manager is completely independent of the used protocols and the communication system. As an example the following systems are to mention, which are already used in current applications: CAN, K-line, Ethernet, EtherCAT, J1939, KWP2000onCAN, UDS, CANOpen, UDP, TCP/IP, etc.
Clearly structured representation of the vehicle infrastructure
The CLC Manager offers different views on the data of a vehicle. The information can be represented as ECU-, log-, or task orientated. This simplifies the handling of data and provides an optimal overview of the communication in the vehicle at any time. An automatically created graphically description represents the existing ECU and bus systems. This view shows the different software levels of the control units which were released together and allows the direct jump into the details of a control.
Source code generator
The source code generator of CLC Manager is based on a configurable style sheet. This style sheet can be used to reshape the ODX data source in any other format. The CLC Manager is not bound to a specific language or a specific file format here. As examples, you could specify .c, .cpp, .h, .dbc, .csv, etc.. The CLC Manager offers the possibility to integrate the generation of source code in an automated bulidprocess via a command line call.
Clear and configurable editing and display options
The CLC Manager has a table view which makes it possible to generate user depending views of the data. For example, a control developer uses the CLC Manager to create new services which do not change in the basic structure and change only identifier and data uses. As an example the ODX information can be filtrated for this purpose restricted information and can be displayed. The table view provides the ability to create new services, so that the user enters only the required data. The complete including underlying structure is automatically created.
Test ability of the defined data
The test view window provides the opportunity to examine the services on the target system or against a simulation. Therefore, the data acquisition mechanism which is already in the modular diagnostic tool chain (MDT) is used to send the messages to the CAN bus and to interpret the answers according to the description. The services to be tested can be queried individually as well as in a block cyclically. The test project can be stored here for reuse and the results can then be placed in a test protocol.
Description of all vehicle diagnostic data and ECU data in XML;
Extended ODX for full description of all communication data;
Layer models for avoiding duplicated data;
Data abstraction, overwriting, and replicating data via references
Description of diagnostic data like request/response, Param, DataObjectProp, CompuMethod, Unit;
Replication via references
Data collection of communication interfaces and vehicle/machine structure;
Creation of data independent from protocols
Detailed implementation of Interfaces;
Import function for .dbc und a2I;
Project view for ODX-files, style sheets and Test Setups;
Detail view for convenient creation of ODX-data;
Table view for editing ODX-data even without ODX
Execution of communication processes in a test Environment;
Creation of test specifications and protocols;
Adaptation of the test view via style Sheets;
Comparison to reference values
Release and diagnostics
Code-generator for different platforms and programming languages;
Diagnostic-interface towards MDT;
Document handling via XSLT, data will be converted into .pdf or .doc;
Firmware release organisation and history of different firmware versions
Minimum system requirements
2 GHz or higher
1 GB RAM
Min. resolution of 800 × 600
Recommended system requirements
3 GHz or higher
2 GB RAM
Supported operating systems
available for Windows XP, Vista & 7
Supported CAN interfaces
CANUSB, CANfox, CANUSBlight, PowerCAN-PCI V1 and V2, PowerCAN-PC104+, PowerCAN-PCI104 V2