All vehicle manufacturer specific diagnostic features are implemented and encapsulated in CANdesc. This gives the ECU application a clear signal interface. Reutilization of the ECU application is thereby supported.
CANdesc covers
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.
Supplemental Services
Vector offers the following types of project services: