CANdesc

Vehicle Manufacturers:

CANdesc offers assurance to the vehicle manufacturer that the diagnostic specification is implemented uniformly in all ECUs of a vehicle model. Using CANdesc and CANdelaStudio, the comprehensive CANdela approach to diagnostics, provides the greatest benefit.

The diagnostic functionalities and diagnostic data for an ECU are described in the specification phase using CANdelaStudio and stored in a consistent database (CANdela). This ECU diagnostic specification can directly be used to generate the CANdesc code. Changes in this specification during the vehicle development can therefore be cost-efficiently updated in the ECU by a simple re-generation. This guarantees that the specification and the implementation always fit together.

The vehicle and ECU manufacturer can use the CANdela data base also for parameterization of test systems. Thus a continuous process chain beginning with the specification, continuing with implementation and finishing with integration and functional testing can be offered.

ECU Manufacturers:

CANdesc covers the vehicle manufacturer diagnostic protocol and transported data completely. This assures that

• timing and content requirements of the diagnostic protocol are implemented correctly.
• simplification of a product line concept in the diagnostic area in spite of multiple ECU variants and vehicle manufacturers is possible
• development costs for implementation and testing effort are reduced
• Predictability of the correct and complete diagnostic implementation is significantly increased.

Code size

Of course, the size of the automatically generated code in terms of RAM and ROM is greater than that of manually optimized modules. However, if one considers the "dead paths" (approx. 10%-20%) and often suboptimal extensions that occur over the duration of a project with manually written code, the size of the automatically generated code is generally no greater than that of manually encoded modules.

Example of code size

Microprocessor: Motorola HC12, MC9S12DP256;
Cosmic compiler 4.5 with an implementation of 10 diagnostic services and 30 subfunctions with data packets:
Code size: approx. 5.5 kByte
Tables and constants: approx. 700 bytes
RAM: approx. 70 bytes plus bytes for the diagnostic buffer.
For average sized applications with approx. 120 sub functions the code size increases to approx. 9kByte.

[continue to "Functions"]