News

Download

With Service Pack 2 (Update to 3.0 Build 45), the following changes become effective:

Tool features:

• Support of AUTOSAR schema version 3.1.4 and 3.0.6 in import/export and ECU-C synchronization.
• In addition to importing an ECU-Extract of System-Description the import of a System-Description containing more than one ECU is now supported by selecting the ECU to import.
• RTE measurement supported by specifying the according parameters at the Calibration Elements, Calibration Parameters, Inter-Runnable Variables, and in the global generation parameters.
• Specification of an Rx-Filter is now possible at the receiver communication specification.
• Minimum start interval can now be specified in the runnable properties.
• Double data mapping for a signal is now allowed if the Tx/Rx direction differs, i.e. the same signal can be used as sender and receiver.

Usability enhancements:

• Newly created ECU projects using the DaVinci Project Assistant now contain default entries for generators/configurators.
• Automatic creation of server runnables can now be configured with an additional pre- or post-fix for the runnable name.
• New feature in the signal data-mapping editor to create ECU delegation port prototypes, which matches the Tx/Rx-Signals of an ECU project.
• ECU-C file synchronization no longer requires a specific AUTOSAR package structure.
• Graphic export to the Windows clipboard can now be initiated with Ctrl-G. Graphic file export now supports exporting of all Sheets in one step.

Fixed issues:

• Multiple instantiation of service components in the service mapping editor is now prevented.
• Wrong consistency check message about overflow in 64 bit data type range fixed.
• In some dialogs the edit controls were disabled instead of read-only which inhibits copying of the text content.
• Unexpected additional enumeration data type was created during ARXML import if COMPU-CONSTs exists for non-integer data-types.
• Missing consistency check for init values at the port's communication specification if two SWC receiving the same signal, but the port interfaces have different init values.
• Inconsistent rounding of imported values in DBC and ARXML with a precision of more than 15 digits fixed.
• Consistency check for different receiver invalid handling didn't work for external communication.
• Unexpected empty XML element was exported for calibration parameters without init value.
• Show reference in object usage dialogs didn't work if the object usage dialog was started on a object from within the search result list.
• Changing an ECU-Project's ECU-C-File does not always trigger an ECU-C sync if another tools hold an ECU-C lock.
• Updating an ECU-Project with a file that contains frames with equal (case-insensitive) SHORT-NAMEs had failed.
• Automatic ECU-C synchronization haven't detected generation parameter changes if the parameters were changed the second time.
• ECU-C file couldn't be found in DCF Utility because of using relative paths.
• ECU-Project settings couldn't be edited with DaVinci Project Assistant if the DPA file reference contains a relative path.
• Import ARXML from path containing Japanese characters failed
• Parameters for Component Implementation Template Generation and Contract Phase Header Generation were mixed up in newly created ECU-Projects using the DaVinci Project Assistant
• Too many ECU-C signals were created if PDU routing is designed when a frame is transmitted but not all signals have a tx relation
• DaVinci crashed when a multi-selection of ECU-Projects is about to be exported to ARXML
• DCF workspace couldn't be saved after modification if a Port-Prototype was deleted which was referenced by a Runnable's trigger
• DaVinci crashed after deletion of the mode declaration group prototype with already used name
• Compiler/Linker error due to inconsistent callback definitions for ports without port access but AliveTimout > 0
• Tx callback was exported for Rx signal if the signal was sent and received on the same network
• Task type was not correctly imported from ECU-C if different Os BSWMD contains a platform specific package
• In rare cases update of an ECU-Project via XML import with ECU-Extract and ECU-C file failed with error message "Item already exists"
• Importing an ECU-Extract using the Diff&Merge feature had corrupted the data mapping if additional signals or signal groups have been added
• Service mapping was missing when exporting service layer components to ARXML or DCF

[more about DaVinci Developer...]