The tool’s advanced user operation concept – with an intuitive menu ribbon that is structured according to feature sets – simplifies access of frequently used functions. In ECU calibration work, the necessary sharing of parameter sets within a team is now convenient and transparent.
Video streams, raw radar data and internal ECU signals place enormous demands on data acquisition, especially in the areas of ADAS development and autonomous driving. For these applications, CANape 15.0 offers the “High Performance Mode” for measuring sensors and ECUs. In addition, this extension enables time-synchronous recording over multiple PCs. This enables implementation of measurement data rates of more than 1 GByte per second.
The redesigned graphical user interface is now organized by feature sets to enable fast intuitive operation of CANape. The ribbon combines menu control, dialogues and toolbar. Clearly recognizable graphic symbols make it easier for the developer to use the various functions.
Calibrating several thousand ECU parameters is only possible with teamwork. Data exchange based on file hand-offs between individual users runs the risk that parameter changes may be lost by overwriting. The new “vCDM Teams” option in CANape assures convenient and loss-free editing of parameter sets within a team. It identifies, displays, and helps resolve conflicts that result from multiple users making parameter changes simultaneously. Thus the team always works with the same data revision level – either on a server or in the cloud.
CANape 15.0 now supports the “Occupancy Grid” surroundings model that is frequently used to develop autonomous vehicles. By using colour functions and the Occupancy Grid view, the user can visualize and validate the vehicle surroundings as determined by the ECU. The Occupancy Grid can be displayed (three-dimensionally) in the video window, in a bird’s eye view or in GPS window.
In the framework of model-based software development, the developer can now configure and display functions as blocks in CANape 15.0. The “Algorithm Designer”