DaVinci Developer Release Notes

Copyright (c) 2016 Vector Informatik GmbH. All rights reserved.

Table of contents

DaVinci Developer Version 3.12 (SP3)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Various Diff/Merge extensions to support sub-elements e.g. internal behavior
• Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

• Create port with data-type from signal now suppresses transformed signals
• Delete of End-to-End connections with multi-select is now supported
• ArrayElement-ReferenceName is now configurable
• Additionally merged usability enhancements from service packs of previous releases:
• Tool version check is now skipped for workspaces without having a ECU-Project
• Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
• The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Consistency check 40454 didn't consider array element mapping according to AUTOSAR Constr_1004
• Delegation ports with several data mappings for different variants weren't supported
• Communication and data mapping was lost after import of an ECU-Extract having several clusters with the same name
• "Adapt structure of record type" function created non-matching init value for nested complex data-types
• AR3 to AR4 workspace conversion showed the error message 40338 inconsistent data type mappings when using real data-types
• Loading a workspace with external DCF references failed with message "Item with name is read-only" if the loaded DCF referenced another DCF with custom generic attributes
• Existing Type-Reference couldn't be selected as Inter-Runnable-Variable data-type
• ARXML export duplicated the data mapping if the signal was mapped and the signal was part of a signal group
• Constant reference wasn't imported correctly for calibration parameters with 'per instance' scope
• Create port from signal group didn't consider the variant assignment
• The separate variant assignment for group signal mappings wasn't deactivated if the signal group is already mapped
• Additionally merged issues from service packs of previous releases:
• Signal's init/invalid value was always "" in the properties dialog
• Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
• Data-Mapping couldn't handle mapped ports without port-interfaces
• Connections were deleted during ARXML import even if the import mode preset should avoid that
• The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
• Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
• When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
• Contract phase generation couldn't be used at the ECU-Project
• Crash during SWC check on runnable data accesses by value has been fixed
• Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• In some cases a double click on a .dcf file started the wrong DaVinci Developer version
• Create port from signal didn't create correct init values in all cases
• Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
• A component type DCF file accidently contained data constr elements
• Init value constant contained duplicate record elements after merge
• GUI crashed when calling "Show in other views" on a found object
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
• Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
• Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

(top)

DaVinci Developer Version 3.12 (SP2)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Mapping of CharacteristicTable and Axis application data types to the corresponding Record and Array implementation data types has been added
• Service need support has been completed according to AUTOSAR 4.2.2
• Find function for objects with duplicate UUIDs has been added

Usability enhancements

• Interaction and error handling between DaVinci Configurator and DaVinci Developer has been enhanced to get more information during project update
• Additionally merged usability enhancements from service packs of previous releases:
• Search of unused Data-Types has been split to allow separate search for Application and Implementation Data-Types
• Data-Type mapping can be optionally ignored for easier finding of unused Application/Implementation types
• The range setting of 0..0 for CompuScales which didn't define an upper/lower limit is now supported as optional in ARXML export
• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• No error was returned to DaVinci Configurator if a project update fails due to an invalid ARXML file
• Consistency check 40284 concerning multiple used names appeared without further name information
• A constant's unit wasn't imported if a communication specification contained an application value specification with a unit reference
• Unmap of a variant data-mapping crashed if it have been previously mapped after saving the workspace.
• Additionally merged issues from service packs of previous releases:
• Port-Interface was listed as unused even if a blueprint port prototype or an interface mapping existed
• Object usage on a port interfaces didn't show the referencing port interface mapping set
• It was unable to define a init value at the ComSpec because the properties button wasn't visible
• Crash during SWC check on runnable data accesses by value has been fixed
• Error message during workspace saving leaded into a crash if the option "Delete unreferenced files from DCF Workspace" was set
• Invalid value of a implementation record couldn't be set if the dialog changes weren't applied immediately
• Import didn't not support the merge of multi-mapping of NvBlockDescriptors
• Renaming of End-to-End protections could cause problems during later updates because the End-to-End protections couldn't be found anymore
• Compatibility of Application Value and Constant Reference wasn't checked
• Data-Type element information wasn't stored correctly at the root data type and vice versa
• The exported or saved component type file didn't contained all runnables
• Multiple System-Mappings (e.g. one for data mappings and another one for pnc mappings) couldn't be imported correctly.
• Loading a workspace was aborted with a NullReferenceException if the project contained multiple identical data mappings with unresolvable references
• ARXML import didn't succeed due to an endless loop if the ARXML contained array definitions with a huge array size
• Application ports couldn't be assigned anymore at the RoleBasedPortAssignments
• Mode Declaration Value range wasn't checked and the value was set to 0
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Function "Replace legacy data types" wasn't executed if LibraryBrowser had the focus
• Wrong unused item was deleted if item with the same name existed in different packages
• Physical to internal compu scales weren't displayed and were deleted when leaving the dialog
• The data transformation flag of a signal couldn't be set due to a read-only checkbox in the dialog
• Bitfields greater than 31 bits weren't handles correctly in consistency check and dialog
• Offset of End-to-End Protection profile 5 wasn't editable
• Signal group dialog accidently allows editing the signal group name and group signal set
• Create port prototype threw an "Invalid pointer" exception if signals of a signal group didn't have a base-type defined
• ARXML export wasn't possible with multi selection of Port Blueprints or Blueprint Mappings Sets
• Consistency check 40439 didn't reflect AUTOSAR constr_1295 correctly
• Crash during SWC check on runnable data accesses by value has been fixed
• Contract phase generation couldn't be used at the ECU-Project
• When using the "Propagate Alive Timeout" function a wrong value was set after loading the value from the communication extract
• Multi-select unmap of data mapping didn't work for complex data elements
• Renaming a package didn't work correctly for DCF workspaces
• Data-mapping of atomic ports lead to "Unsupported communication pattern" errors because create ECU-Delegation port didn't consider new connections
• Create Port Prototypes didn't reference newly created global constants
• Constant References could be created without a destination constant
• Invalid mode accesses are created while importing an AUTOSAR3 file with P-Ports into an AUTOSAR4 workspace
• Rte generator threw an error "[Internal Error] RTE - Could not read GenAPI data" if an argument order index of an Operation-Prototype wasn't unique
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.12 (SP1)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Support of Characteristic Table (Curve, Map, Cuboid) and COM_AXIS application data types has been added

Usability enhancements

• The consistency check 40043 "Missing init values for open ports" is now optional and can be disabled through a workspace setting
• The consistency check 40286 "Multiple usage of the same name" is now optional and can be disabled through a workspace setting
• Updating a project or saving a workspace took very long if many complex data mappings were defined
• Additionally merged usability enhancements from service packs of previous releases:
• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• A signal's data transformation flag was falsely set during creating a data mapping
• Formula-Expression of composite constant values were not converted to a valid numeric value
• Consistency check 40439 didn't reflect AUTOSAR constr_1295 correctly
• Additionally merged issues from service packs of previous releases:
• Multi-select unmap of data mapping didn't work for complex data elements
• Renaming a package didn't work correctly for DCF workspaces
• Data-mapping of atomic ports lead to "Unsupported communication pattern" errors because create ECU-Delegation port didn't consider new connections
• Create Port Prototypes didn't reference newly created global constants
• Constant References could be created without a destination constant
• Invalid mode accesses are created while importing an AUTOSAR3 file with P-Ports into an AUTOSAR4 workspace
• Rte generator threw an error "[Internal Error] RTE - Could not read GenAPI data" if an argument order index of an Operation-Prototype wasn't unique
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.12

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• AUTOSAR schema 4.2.2 is now supported
• Variable array size handling has been adapted to AUTOSAR 4.2.2 specification
• The "Activation Reasons" can now be specified at the runnables and assigned to a trigger
• The port interface mapping now supports sub-element mapping for Rx-Group Signals

Usability enhancements

• An additional check has been implemented to ensure that the compu-method category of implementation data types is either BITFIELD_TEXTTABLE or TEXTTABLE

Fixed issues

• It wasn't possible to map a leaf data element of a complex data element to a group signal if the complex data element itself contained one or more complex data elements.
• Data mapping contained invalid references to elements of multi-dimensional arrays if a signal group and its group signals are mapped to a multi-dimensional array.
• Installer text was truncated if the setup process has been interrupted manually before completion
• Data types in AUTOSAR3 format loosed their compu-method during import into an AUTOSAR 4 workspace.

(top)

DaVinci Developer Version 3.11 (SP3)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Various Diff/Merge extensions to support sub-elements e.g. internal behavior
• Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

• Tool version check is now skipped for workspaces without having a ECU-Project
• Additionally merged usability enhancements from service packs of previous releases:
• Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
• The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Signal's init/invalid value was always "" in the properties dialog
• Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
• Data-Mapping couldn't handle mapped ports without port-interfaces
• Connections were deleted during ARXML import even if the import mode preset should avoid that
• The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
• Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
• Additionally merged issues from service packs of previous releases:
• When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
• Contract phase generation couldn't be used at the ECU-Project
• Crash during SWC check on runnable data accesses by value has been fixed
• Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• In some cases a double click on a .dcf file started the wrong DaVinci Developer version
• Create port from signal didn't create correct init values in all cases
• Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
• A component type DCF file accidently contained data constr elements
• Init value constant contained duplicate record elements after merge
• GUI crashed when calling "Show in other views" on a found object
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
• Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
• Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

(top)

DaVinci Developer Version 3.11 (SP2)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Find function for objects with duplicate UUIDs has been added

Usability enhancements

• Search of unused Data-Types has been split to allow separate search for Application and Implementation Data-Types
• Data-Type mapping can be optionally ignored for easier finding of unused Application/Implementation types
• Additionally merged usability enhancements from service packs of previous releases:
• The range setting of 0..0 for CompuScales which didn't define an upper/lower limit is now supported as optional in ARXML export
• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• Port-Interface was listed as unused even if a blueprint port prototype or an interface mapping existed
• Object usage on a port interfaces didn't show the referencing port interface mapping set
• It was unable to define a init value at the ComSpec because the properties button wasn't visible
• Crash during SWC check on runnable data accesses by value has been fixed
• Error message during workspace saving leaded into a crash if the option "Delete unreferenced files from DCF Workspace" was set
• Invalid value of a implementation record couldn't be set if the dialog changes weren't applied immediately
• Additionally merged issues from service packs of previous releases:
• Import didn't not support the merge of multi-mapping of NvBlockDescriptors
• Renaming of End-to-End protections could cause problems during later updates because the End-to-End protections couldn't be found anymore
• Compatibility of Application Value and Constant Reference wasn't checked
• Data-Type element information wasn't stored correctly at the root data type and vice versa
• The exported or saved component type file didn't contained all runnables
• Multiple System-Mappings (e.g. one for data mappings and another one for pnc mappings) couldn't be imported correctly.
• Loading a workspace was aborted with a NullReferenceException if the project contained multiple identical data mappings with unresolvable references
• ARXML import didn't succeed due to an endless loop if the ARXML contained array definitions with a huge array size
• Application ports couldn't be assigned anymore at the RoleBasedPortAssignments
• Mode Declaration Value range wasn't checked and the value was set to 0
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Function "Replace legacy data types" wasn't executed if LibraryBrowser had the focus
• Wrong unused item was deleted if item with the same name existed in different packages
• Physical to internal compu scales weren't displayed and were deleted when leaving the dialog
• The data transformation flag of a signal couldn't be set due to a read-only checkbox in the dialog
• Bitfields greater than 31 bits weren't handles correctly in consistency check and dialog
• Offset of End-to-End Protection profile 5 wasn't editable
• Signal group dialog accidently allows editing the signal group name and group signal set
• Create port prototype threw an "Invalid pointer" exception if signals of a signal group didn't have a base-type defined
• ARXML export wasn't possible with multi selection of Port Blueprints or Blueprint Mappings Sets
• Consistency check 40439 didn't reflect AUTOSAR constr_1295 correctly
• Crash during SWC check on runnable data accesses by value has been fixed
• Contract phase generation couldn't be used at the ECU-Project
• When using the "Propagate Alive Timeout" function a wrong value was set after loading the value from the communication extract
• Multi-select unmap of data mapping didn't work for complex data elements
• Renaming a package didn't work correctly for DCF workspaces
• Data-mapping of atomic ports lead to "Unsupported communication pattern" errors because create ECU-Delegation port didn't consider new connections
• Create Port Prototypes didn't reference newly created global constants
• Constant References could be created without a destination constant
• Invalid mode accesses are created while importing an AUTOSAR3 file with P-Ports into an AUTOSAR4 workspace
• Rte generator threw an error "[Internal Error] RTE - Could not read GenAPI data" if an argument order index of an Operation-Prototype wasn't unique
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.11 (SP1)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• The official 'ServiceProvider' attribute is now supported to annotate the BSW Module origin
• The pointer datatype DATA_REFERENCE is now fully supported
• End-to-End protections without port references but with signal group references are now supported
• 'Create Port Prototypes' functionality now supports the signal group degradation use case

Usability enhancements

• Invalid generic attribute definition files are now displayed in the Action-Log during workspace loading
• Additional check has been added to ensure that the compu-methods category of an implementation data-type is either BITFIELD_TEXTTABLE or TEXTTABLE
• Additionally merged usability enhancements from service packs of previous releases:
• The import option 'Substitute missing objects' is now active by default for new workspaces. The import defaults can be set via the workspace settings dialog.
• Enhanced contract phase template generation dialog; automatically offers the Rte generator from the referenced SIP if available
• Menu command to reset the toolbar and docking window layout has been added
• Find results view now displays the parent element in a separate column
• Multi-select and default settings usability enhancements for End-to-End Protection configuration
• The available filter options from the import dialog are now available via command line DVImEx
• Structure graphics is now changeable even if the composition type is locked
• Multi-select editing of Communication Specification values is now supported
• A dedicated 'order index' column has been added for lists that have a relevant order in the ARXML schema
• Import options 'substitute missing objects' and 'check for differences' are now supported in the same import step
• Enhancements in consistency checks for NV components
• Import dialog now contains a simplified file/folder selection button
• Additional consistency check to avoid data types referencing a data type with the same name

Fixed issues

• The data-type-mapping-refs were cleared during update of the diagnostics data using the special import mode
• When creating a server runnable from a nv-component the name of the server-runnable was created with the pattern 'port-prototype'_'operation_name' which could lead into name clashes
• DaVinci DEV crashed without any error message if the direction of a port prototype was changed while a runnable data access existed
• Additionally merged issues from service packs of previous releases:
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• Modifications in the recent import file list caused a workspace modification
• ARXML import merge aborted when trying to merge an union data type.
• Import with function 'check for differences' aborted if a new element had to be created but its package already exists
• After creating a port from a signal using the 'Create Port Prototypes' function the port was not compatible to the signal if a physical constraint was specified
• Data mapping of a complex element to a transformed signal causes inconsistencies in the data mapping view
• Additionally merged issues from service packs of previous releases:
• AUTOSAR 4 import of Group-Signals didn't update all signal references correctly which resulted in an illegal file split error in DaVinci Configurator Pro
• AUTOSAR 4 import of a negative exponential value ignored the sign
• Export option 'Create UUIDs' wrote identical UUIDs for all signal- and frame ports
• Creating an OnTransitionTrigger from the runnable context menu didn't work
• Not all Asian characters could be used in description fields
• Find unused object menu was sometimes disabled
• Create Port-Prototypes function didn't create record data-types for signal groups
• Developer crashed when importing an enumeration data type with physical and internal constraints
• AUTOSAR 4: Signal-Port time out value was not imported
• AUTOSAR 4: Not all Parameter-Accesses were exported for modelled calibration elements
• An internal exception occurred on ARXML import if an existing component type had a different internal behavior name and a runnable with the same name
• Importing an AUTOSAR 3 array without type-reference into an AUTOSAR 4 workspace created an invalid the data-type
• Duplicate UUIDs occurred when creating a Multiple-ECU project from ECU Extracts containing UUIDs
• The name of an imported argument prototype wasn't imported correctly
• End-to-End protection data IDs were mixed up when opening an old workspace saved with DaVinci Developer 3.2
• Unlocking a composition didn't allow moving its ports/component prototypes until the ECU-Project editor was reopened
• Create port from signal didn't worked for multiple signals if the data mapping wasn't created in the same step
• Crash was fixed when leaving the NV Block descriptor page of a NV Component editor without having a Block Descriptor defined
• NV component couldn't be configured in the local composition view
• Inter-Runnable-Variable data type wasn't exported to DCF if their component type contained an Inter-Runnable-Variable with a unique data type which wasn't used in any other case
• Blueprints couldn’t be exported to DCF
• Crash fixed if context component for create port prototypes was selected as "none"
• AUTOSAR4: init value of NV block description (ram or rom) couldn't be unset
• AUTOSAR4: Substitute missing objects showed irrelevant unresolved references
• The data type reference of a calibration element prototype wasn't set after import
• Import of a DCF package accidently sets the workspace option "Load Service Components when opening the workspace" to a wrong value
• Copying a runnable broke the data model and causes undesired wait points
• Duplicating an Object copied the original UUID instead of creating a new one.
• HTML links in descriptions didn't appear in the report
• Data mapping view didn't display the correct direction of signals which were sent/received as single signal and as part of a signal-group

(top)

DaVinci Developer Version 3.11

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• COM-based Transformer can now be configured; supporting End-to-End Protection profiles 1+2
• Enhancements of NV Block SWC:
  • supporting now also Client/Server- and ModeSwitch-interfaces
  • explicit modelling of different writing strategies
  • multiple NvBlock to port mappings for dual-sided RAM block access

Usability enhancements

• Enhanced contract phase template generation dialog; automatically offers the Rte generator from the referenced SIP if available
• Enhanced tool interaction allows to create Service-Ports directly from within DaVinci Configurator Pro

Fixed issues

• In rare cases the library tree contained obsolete items due to a missing update
• UUIDs of SwcServiceDependencies and NvBlockDescriptors were missing in the ARXML export
• Tool crashed when a locked component type was assigned to the DataTypeMappingSet in the Data-Type-Mapping-Set dialog
• If the workspace was part of a DPA project a XML parser error code 0x800C0006 was shown when opening a DCF workspace from Windows Explorer with a double click

(top)

DaVinci Developer Version 3.10 (SP5)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Additionally merged tool features from service packs of previous releases:
• Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

• Additionally merged usability enhancements from service packs of previous releases:
• Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
• The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Additionally merged issues from service packs of previous releases:
• When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
• Contract phase generation couldn't be used at the ECU-Project
• Crash during SWC check on runnable data accesses by value has been fixed
• Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• In some cases a double click on a .dcf file started the wrong DaVinci Developer version
• Create port from signal didn't create correct init values in all cases
• Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
• A component type DCF file accidently contained data constr elements
• Init value constant contained duplicate record elements after merge
• GUI crashed when calling "Show in other views" on a found object
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
• Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
• Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

(top)

DaVinci Developer Version 3.10 (SP4)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Find function for objects with duplicate UUIDs has been added

Usability enhancements

• The range setting of 0..0 for CompuScales which didn't define an upper/lower limit is now supported as optional in ARXML export
• Additionally merged usability enhancements from service packs of previous releases:
• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Function "Replace legacy data types" wasn't executed if LibraryBrowser had the focus
• Wrong unused item was deleted if item with the same name existed in different packages
• Physical to internal compu scales weren't displayed and were deleted when leaving the dialog
• The data transformation flag of a signal couldn't be set due to a read-only checkbox in the dialog
• Bitfields greater than 31 bits weren't handles correctly in consistency check and dialog
• Offset of End-to-End Protection profile 5 wasn't editable
• Signal group dialog accidently allows editing the signal group name and group signal set
• Create port prototype threw an "Invalid pointer" exception if signals of a signal group didn't have a base-type defined
• ARXML export wasn't possible with multi selection of Port Blueprints or Blueprint Mappings Sets
• Consistency check 40439 didn't reflect AUTOSAR constr_1295 correctly
• Crash during SWC check on runnable data accesses by value has been fixed
• Contract phase generation couldn't be used at the ECU-Project
• When using the "Propagate Alive Timeout" function a wrong value was set after loading the value from the communication extract
• Additionally merged issues from service packs of previous releases:
• Multi-select unmap of data mapping didn't work for complex data elements
• Renaming a package didn't work correctly for DCF workspaces
• Data-mapping of atomic ports lead to "Unsupported communication pattern" errors because create ECU-Delegation port didn't consider new connections
• Create Port Prototypes didn't reference newly created global constants
• Constant References could be created without a destination constant
• Invalid mode accesses are created while importing an AUTOSAR3 file with P-Ports into an AUTOSAR4 workspace
• Rte generator threw an error "[Internal Error] RTE - Could not read GenAPI data" if an argument order index of an Operation-Prototype wasn't unique
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.10 (SP3)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• End-to-End protections without port references but with signal group references are now supported
• 'Create Port Prototypes' functionality now supports the signal group degradation use case

Usability enhancements

• The import option 'Substitute missing objects' is now active by default for new workspaces. The import defaults can be set via the workspace settings dialog.
• Enhanced contract phase template generation dialog; automatically offers the Rte generator from the referenced SIP if available
• Menu command to reset the toolbar and docking window layout has been added
• Find results view now displays the parent element in a separate column
• Multi-select and default settings usability enhancements for End-to-End Protection configuration
• The available filter options from the import dialog are now available via command line DVImEx
• Structure graphics is now changeable even if the composition type is locked
• Multi-select editing of Communication Specification values is now supported
• A dedicated 'order index' column has been added for lists that have a relevant order in the ARXML schema
• Import options 'substitute missing objects' and 'check for differences' are now supported in the same import step
• Enhancements in consistency checks for NV components
• Import dialog now contains a simplified file/folder selection button
• Additional consistency check to avoid data types referencing a data type with the same name

Fixed issues

• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• Modifications in the recent import file list caused a workspace modification
• ARXML import merge aborted when trying to merge an union data type.
• Import with function 'check for differences' aborted if a new element had to be created but its package already exists
• After creating a port from a signal using the 'Create Port Prototypes' function the port was not compatible to the signal if a physical constraint was specified
• Additionally merged issues from service packs of previous releases:
• Data mapping of a complex element to a transformed signal causes inconsistencies in the data mapping view
• Additionally merged issues from service packs of previous releases:
• AUTOSAR 4 import of Group-Signals didn't update all signal references correctly which resulted in an illegal file split error in DaVinci Configurator Pro
• AUTOSAR 4 import of a negative exponential value ignored the sign
• Export option 'Create UUIDs' wrote identical UUIDs for all signal- and frame ports
• Creating an OnTransitionTrigger from the runnable context menu didn't work
• Not all Asian characters could be used in description fields
• Find unused object menu was sometimes disabled
• Create Port-Prototypes function didn't create record data-types for signal groups
• Developer crashed when importing an enumeration data type with physical and internal constraints
• AUTOSAR 4: Signal-Port time out value was not imported
• AUTOSAR 4: Not all Parameter-Accesses were exported for modelled calibration elements
• An internal exception occurred on ARXML import if an existing component type had a different internal behavior name and a runnable with the same name
• Importing an AUTOSAR 3 array without type-reference into an AUTOSAR 4 workspace created an invalid the data-type
• Duplicate UUIDs occurred when creating a Multiple-ECU project from ECU Extracts containing UUIDs
• The name of an imported argument prototype wasn't imported correctly
• End-to-End protection data IDs were mixed up when opening an old workspace saved with DaVinci Developer 3.2
• Unlocking a composition didn't allow moving its ports/component prototypes until the ECU-Project editor was reopened
• Create port from signal didn't worked for multiple signals if the data mapping wasn't created in the same step
• Crash was fixed when leaving the NV Block descriptor page of a NV Component editor without having a Block Descriptor defined
• NV component couldn't be configured in the local composition view
• Inter-Runnable-Variable data type wasn't exported to DCF if their component type contained an Inter-Runnable-Variable with a unique data type which wasn't used in any other case
• Blueprints couldn’t be exported to DCF
• Crash fixed if context component for create port prototypes was selected as "none"
• AUTOSAR4: init value of NV block description (ram or rom) couldn't be unset
• AUTOSAR4: Substitute missing objects showed irrelevant unresolved references
• The data type reference of a calibration element prototype wasn't set after import
• Import of a DCF package accidently sets the workspace option "Load Service Components when opening the workspace" to a wrong value
• Copying a runnable broke the data model and causes undesired wait points
• Duplicating an Object copied the original UUID instead of creating a new one.
• HTML links in descriptions didn't appear in the report
• Data mapping view didn't display the correct direction of signals which were sent/received as single signal and as part of a signal-group

(top)

DaVinci Developer Version 3.10 (SP2)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Various roundups and extensions have been implemented for the Diff/Merge functionality, especially support for NV-Data-Interfaces and Packages
• Function "Create Port Prototypes" can now be used on signals that don't have a base type

Usability enhancements

• ARXML import dialog can now load an external .txt file that contains a list of the file name references to be imported. Paths can be absolute, relative (to the .txt itself) and just the filename itself (same directory).
• Saving a DCF workspace can now remove files for deleted objects. This option can be activated in the workspace settings.

Fixed issues

• If falsely an invalid Invoke Operations Port-Access was defined on a non-Client port, the DCF workspace couldn't be loaded anymore
• A project wasn't updated correctly if the elements were part of a package named "Autosar_Platform".
• Exporting a Mode Declaration Group contained the category. This category is now corrected to the ALPHABETICAL_ORDER or EXPLICIT_ORDER.
• In some cases the diff/merge crashed when importing communication data with "check for differences" option.
• Importing an new ECU SW-Composition delegation port in a previous workspace with "check for differences" option enabled, the data mapping of this port wasn't created.
• Error 40391 "Invalid integer for criterion" was reported if the project contained more than 4 variants
• For some object types the package icon was missing in the Library Browser's type view
• Item is read-only error occurs when opening a SWC composition that contained a read-only atomic SWCs with an outdated interface graphic.
• The references to a Mapping Set from a NvBlockComponent were not persistent
• Automatic data type mapping falsely created a fix-size implementation array for a dynamic-size application array
• Function "Create Server Runnables" created duplicate runnables and allowed invalid prefix / postfix strings

(top)

DaVinci Developer Version 3.10 (SP1)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Vector FlexNet Pool License model is now supported
• Support for signals which are transmitted over container PDUs has been added

Fixed issues

• Exception was raised when adding a file to the ARXML import list if a J1939 cluster contained a NODE-NAME and the ECU-INSTANCE attribute
• DVImEx command line tool falsely showed the message "Referenced DPA file from the DCF workspace differs to the load DPA file" if a relative path was given
• TP Signals weren't displayed with the correct frame in the Data-Mapping view for the 1:N use case
• Some smaller GUI roundups and fixes have been made when using union data types

(top)

DaVinci Developer Version 3.10

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Mapping of Data-Prototypes in different Port-Interfaces is now supported
• Text table mapping for Bit fields is now available
• Background event trigger can now be defined at the runnable
• End-to-End protection profiles 5 and 6 are now supported
• UTF-16 base type encoding can now be specified
• UNION data types are now supported

Usability enhancements

• More detailed log messages during ARXML import if generic attributes reference obsolete objects
• Additional checks to detect more NvM Service Need inconsistencies
• AUTOSAR Platform types are now defined in a separate ARXML file and automatically used for new projects
• The path to the .dpa project file is now stored in the .dcf file to allow manual adaptation

Fixed issues

• ARXML import throws an error if the same Client/Server interface was defined in multiple files which were imported in the same step
• Consistency check reports incompatible data types if the Type-Emitter where different
• Communication information was accidently removed when importing a SYSTEM with software design but without communication

(top)

DaVinci Developer Version 3.9 (SP4)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Usability enhancements

• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• Multi-select unmap of data mapping didn't work for complex data elements
• Renaming a package didn't work correctly for DCF workspaces
• Data-mapping of atomic ports lead to "Unsupported communication pattern" errors because create ECU-Delegation port didn't consider new connections
• Create Port Prototypes didn't reference newly created global constants
• Constant References could be created without a destination constant
• Invalid mode accesses are created while importing an AUTOSAR3 file with P-Ports into an AUTOSAR4 workspace
• Additionally merged issues from service packs of previous releases:
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.9 (SP3)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Fixed issues

• Standard Nvm interfaces were missing on creating a new AR 4.1.3 workspace
• Migration of a DCF workspace to a different AUTOSAR schema version wasn't possible because the SaveAs menu entry was disabled
• Record Constant dialog couldn't be opened for the port prototype if a Com-Spec wasn't defined at the data element of the port
• Create Port Prototypes function created an invalid init value for complex data types
• ARXML import threw a fatal error if the same client-server interface was specified in different files and the files were imported at the same time
• The automatic Application to Implementation Data-Type Mapping falsely created a fix-size Impl-array for a dynamic-size Appl-array and reported this as invalid mapping
• Not all Asian characters could be used in description fields

(top)

DaVinci Developer Version 3.9 (SP2)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Compatibility checks for Bit fields have been improved

Usability enhancements

• Output of check message 40224: "Unused data element prototype" can now be omitted by the option "Report unused Data Elements" in the workspace setting dialog
• Command line tool DVImEx now supports the "SubstituteMissingObjects" option
• For iterative import/export workflow purposes an additional import option "Keep existing UUIDs" is now available
• Additional function "Adopt structure..." to align the value definition structure to the structure of the actual data type
• In selection dialogs the init values are now filtered according to the data type

Fixed issues

• Referenced mode declaration groups were missing in DCF export when data type mapping sets where used
• In rare cases the relative DPA project file path couldn't be found if the current directory had been changed via the open file dialog
• End-to-End protection consistency check didn't worked within compositions
• Port access settings of runnables were invalid after they were copied in the runnable list
• Frame assignment was not visible for Signal-PDUs which were connected to a NPDU via the TP-Connection
• Multiple recursive usage of constant references leaded to an exception
• Data mapping for Signal-Groups didn't worked if Sub-Elements were incompatible
• Cancel button for "InitValue" of Record- and Array data types had no effect

(top)

DaVinci Developer Version 3.9 (SP1)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• AUTOSAR schema 4.2.1 is now supported
• Memory Section assignment is now available for NvBlockDescriptor:RAMBlock
• PR-Ports can now be used for Mode-Ports and NvData-Ports
• Bit field data types are now supported by using the BITFIELD_TEXTTABLE in the compu-method

Usability enhancements

• Workspace interaction with DaVinci Configurator has been enhanced by using a lock file mechanism during workspace save
• Creation of a Data-Mapping for a variant signal now evaluates the variant information to set the same variant condition

Fixed issues

• Data element properties couldn't be opened from within the Data Mapping signal view
• Interfaces View in software component editor was falsely disabled for NvComponents
• Most recently used workspace list showed the location of the temporary workspace after a project update using DaVinci Configurator
• Frame was not imported if a frame triggering specifies RX-IDENTIFIER-RANGE instead of IDENTIFIER
• DCF workspace couldn't be loaded if the port direction was changed without performing a consistency check which will correct the port connector
• Error message 'Current special import can only import System Template files' was thrown when using special import feature
• Tool tip didn't work when hovering over a array constant with many values
• LIN-PDUs without frame triggerings couldn't be imported
• Consistency checks for NV-Component init values have been corrected
• DCF workspace contained elements with the same UUID if the component type was duplicated by the copy function in the Library-View
• It was falsely possible to update the project in DaVinci Configurator when the workspace was opened in DaVinci Developer
• PR-Port generation didn't work in case of a complex data type

(top)

DaVinci Developer Version 3.9

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Post-Build selectable use-case is now supported by using AUTOSAR Variant Handling for data-mapping with variation points at the communication
• General support of PDUs without frames has been implemented for all cluster types
• Communication data has been restructured so that DaVinci Developer can directly work on DaVinci Configurator's communication files
• COM signals with shared ISignalToIPDUMapping are now supported
• uint64 and sint64 are now supported as platform types
• Server argument implementation policy attribute is now supported in the operation prototype dialog
• Port access mode 'ReceivePointByValue' is now supported
• End-to-End protection now supports profile 4 for Client/Server inter-ECU communication
• Optional definition of service need parameters

Usability enhancements

• Additional 'Check Workspace' button is now available in the toolbar
• Project update has been simplified to update the DaVinci Developer workspace without user interaction

Fixed issues

• 'Complete Ports' functionality produced wrong opposite ports if a context component type was used
• 'Save As...' functionality has been disabled for projects with DaVinci Configurator Pro because it corrupted the external file references
• HTML links in the description field were not correctly displayed in the report
• The Diagnostics Event Need value 'ConsiderPTO Status' was not correctly set by ARXML import
• Project update with DaVinci Configurator Pro command line tool ended with error -1060110332 (0xC0D00004)
• Port Defined Argument Value could falsely be defined on non-server ports
• Consistency check of the Rte generator falsely reports consistency errors when started within DaVinci Developer
• Consistency check of service needs caused memory leaks

(top)

DaVinci Developer Version 3.8 (SP4)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• End-to-End protections without port references but with signal group references are now supported
• The 'Create PortPrototype from Signal' functionality now supports the signal group degradation use case

Usability enhancements

• The import option 'Substitute missing objects' is now active by default for new workspaces. The import defaults can be set via the workspace settings dialog.
• Additionally merged enhancements from service packs of previous releases:
• Enhanced contract phase template generation dialog; automatically offers the Rte generator from the referenced SIP if available
• Menu command to reset the toolbar and docking window layout has been added
• Find results view now displays the parent element in a separate column
• Multi-select and default settings usability enhancements for End-to-End Protection configuration
• The available filter options from the import dialog are now available via command line DVImEx
• Structure graphics is now changeable even if the composition type is locked
• Multi-select editing of Communication Specification values is now supported
• A dedicated 'order index' column has been added for lists that have a relevant order in the ARXML schema
• Import options 'substitute missing objects' and 'check for differences' are now supported in the same import step
• Enhancements in consistency checks for NV components
• Import dialog now contains a simplified file/folder selection button
• Additional consistency check to avoid data types referencing a data type with the same name

Fixed issues

• Data mapping of a complex element to a transformed signal causes inconsistencies in the data mapping view
• Additionally merged issues from service packs of previous releases:
• AUTOSAR 4 import of Group-Signals didn't update all signal references correctly which resulted in an illegal file split error in DaVinci Configurator Pro
• AUTOSAR 4 import of a negative exponential value ignored the sign
• Export option 'Create UUIDs' wrote identical UUIDs for all signal- and frame ports
• Creating an OnTransitionTrigger from the runnable context menu didn't work
• Not all Asian characters could be used in description fields
• Find unused object menu was sometimes disabled
• Create Port-Prototypes function didn't create record data-types for signal groups
• Developer crashed when importing an enumeration data type with physical and internal constraints
• AUTOSAR 4: Signal-Port time out value was not imported
• AUTOSAR 4: Not all Parameter-Accesses were exported for modelled calibration elements
• An internal exception occurred on ARXML import if an existing component type had a different internal behavior name and a runnable with the same name
• Importing an AUTOSAR 3 array without type-reference into an AUTOSAR 4 workspace created an invalid the data-type
• Duplicate UUIDs occurred when creating a Multiple-ECU project from ECU Extracts containing UUIDs
• The name of an imported argument prototype wasn't imported correctly
• End-to-End protection data IDs were mixed up when opening an old workspace saved with DaVinci Developer 3.2
• Unlocking a composition didn't allow moving its ports/component prototypes until the ECU-Project editor was reopened
• Create port from signal didn't worked for multiple signals if the data mapping wasn't created in the same step
• Crash was fixed when leaving the NV Block descriptor page of a NV Component editor without having a Block Descriptor defined
• NV component couldn't be configured in the local composition view
• Inter-Runnable-Variable data type wasn't exported to DCF if their component type contained an Inter-Runnable-Variable with a unique data type which wasn't used in any other case
• Blueprints couldn’t be exported to DCF
• Crash fixed if context component for create port prototypes was selected as "none"
• AUTOSAR4: init value of NV block description (ram or rom) couldn't be unset
• AUTOSAR4: Substitute missing objects showed irrelevant unresolved references
• The data type reference of a calibration element prototype wasn't set after import
• Import of a DCF package accidently sets the workspace option "Load Service Components when opening the workspace" to a wrong value
• Copying a runnable broke the data model and causes undesired wait points
• Duplicating an Object copied the original UUID instead of creating a new one.
• HTML links in descriptions didn't appear in the report
• Data mapping view didn't display the correct direction of signals which were sent/received as single signal and as part of a signal-group

(top)

DaVinci Developer Version 3.8 (SP3)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Usability enhancements

• Missing compu-method category in ARXML file is now added by the import with a reasonable value
• Additional option in SaveAs... to migrate the version of an existing DCF workspace in-place without changing the project structure
• External service components change detection doesn't show the import dialog any more
• Check for multiple signal group mappings is now enhanced enhancement for PR-Ports
• Multiple selection of objects in several packages is now supported in the Library-View package tab

Fixed issues

• The data reception trigger couldn't be created for a NV-DataElement
• DCF workspace couldn't be loaded if data accesses exist without data element prototype
• Setting to deactivate End-to-End protection consistency checks was loaded always enabled
• Newly created data type/constant was added to the default package instead of the selected package
• Auto connect created redundant connections for PR-ports if they were already connected
• Obsolete data mappings were displayed in the signal mode of the data mapping view when the data transformation was enabled

(top)

DaVinci Developer Version 3.8 (SP2)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Usability enhancements

• An additional "Check Workspace" button is now available to check the full workspace independent from the selected element
• The layout and content of NV Block Component Types has been adapted to match the NvM Block Needs page of regular SWC types

Fixed issues

• AUTOSAR 3 workspaces could still be created which is no longer supported in this release
• References to compu method and data constraints were missing if Signals are defined prior to the referenced elements in the ARXML file
• An empty NUMERIC-VALUE-SPECIFICATION was exported if a communication specification hadn't defined any init value
• In rare cases DCF workspace couldn't be saved due to duplicate short names
• AUTOSAR 3 cross-import didn't understand hex string values like "A0:A1:A2"
• The Rte generation added ComGroupSignals to the ECU-C configuration although they are not related to the ComSignalGroup
• Memory leaks occurred during consistency check of service needs
• Wrong focus selection handling in service needs edit files has been corrected

(top)

DaVinci Developer Version 3.8 (SP1)

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Export to AUTOSAR schema version 4.1.1 is now supported
• Application-Ports are now supported at Service Components

Fixed issues

• Keyboard-navigation through editors(Ctrl+HOME/Ctrl+END) didn't work anymore
• Invalid NvM ServiceNeeds configuration wasn't exported to ARXML
• Import of component type was canceled if a port defined argument value existed and its value didn't define a short label.
• ARXML import crashed when importing an inconsistent array data type
• AUTOSAR 3 cross-import didn't import the system signals into the specified package
• "Parameter is incorrect" exception was threw during copying a data element
• Data exchange analysis showed no communication if an incompatible connector existed in the software design
• "Adapt Connected Port Prototypes" functionality failed when using PR-Ports
• Port assignments at the service needs got lost when opening a DaVinci DEV 3.6 workspace
• ARXML import update use-case didn't work with init-triggers in 4.1.2 format
• PR-Ports aren't shown as “compatible” in the Connector Dialog

(top)

DaVinci Developer Version 3.8

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Combined provide-require-ports (PRPortPrototype) can be defined in the software design
• Explicit modelling of E_OK as application error is now possible
• Service Needs have been extended for NvM Top-Down service configuration
• OBD Ratio Service Need has been added
• Introducing Sender/Receiver Serialization via Transformer concept (AR4.2.1 preview-feature)
  • Data transformation currently only supported for SOME/IP serialization
  • Inter-Ecu Client/Server Communication is available for signals using data transformation
  • Specific End-to-End protection profiles for data transformation have been added
  • End-to-End protection is now supporting also primitive data elements

Usability enhancements

• Init-Runnables are described with the standardized AUTOSAR InitEvent
• TypeReferences now support Data-Constraints
• Data Exchange Analysis now displays the effective Init-Value

(top)

DaVinci Developer Version 3.7 (SP8)

Tool features

• AUTOSAR 3 ECU-C synchronization now supports application refs of OS resources if the OS applications use exclusive areas as interruption mechanism
• Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

• Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
• The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
• Contract phase generation couldn't be used at the ECU-Project
• Crash during SWC check on runnable data accesses by value has been fixed
• Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• In some cases a double click on a .dcf file started the wrong DaVinci Developer version
• Create port from signal didn't create correct init values in all cases
• Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
• A component type DCF file accidently contained data constr elements
• Init value constant contained duplicate record elements after merge
• GUI crashed when calling "Show in other views" on a found object
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
• Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
• Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

(top)

DaVinci Developer Version 3.7 (SP7)

Usability enhancements

• DVImEx command line tool now prints timestamps in the log output
• Using the 'OpenWith' functionality in Windows Explorer now checks if the correct DaVinci Developer version is used for a referenced .dpa project

Fixed issues

• AUTOSAR 3 enumerators were not persistent if entered or changed via the GUI
• AUTOSAR 3 import created superfluous delegation ports for extended connections/mappings
• AUTOSAR 3 export created the same UUID for an init runnable trigger and the runnable itself
• AUTOSAR 3 export converted an application layer CDD to a service layer CDD
• AUTOSAR 3 export created identical names for a RecordElementConstant literal name and the RecordElement name
• Rte generator threw an error "[Internal Error] RTE - Could not read GenAPI data" if an argument order index of an Operation-Prototype wasn't unique
• Data-Mapping wasn't correct if a signal was received as single signal and was contained but not received as part of a group
• Update in the package view was missing when short-names have been changed
• Signals couldn't be mapped on primitive data elements if they were part of a signal group
• EnableUpdate flag handling in the Com-Spec dialog was wrong if UsesE2EProtection flag was cleared
• The attributes of a NvMBlockServiceNeed couldn't be edited via a PIM
• Create Port from Signal didn't create init values correctly
• Object-Usage of port prototype blueprint didn't show the referencing objects
• Object-Usage dialog didn't display the correct icons in all cases
• The menu commands for generation of "Contract Phase Headers" and "Component Implementation Templates" were mixed up
• Obsolete RoleBasedPortAssignments were not deleted
• Port terminator annotation wasn't always persistent

(top)

DaVinci Developer Version 3.7 (SP6)

Tool features

• End-to-End protections without port references but with signal group references are now supported
• 'Create PortPrototypes' functionality now supports the signal group degradation use case

Usability enhancements

• Enhanced contract phase template generation dialog; automatically offers the Rte generator from the referenced SIP if available
• Menu command to reset the toolbar and docking window layout has been added
• Find results view now displays the parent element in a separate column

Fixed issues

• AUTOSAR 4 import of Group-Signals didn't update all signal references correctly which resulted in an illegal file split error in DaVinci Configurator Pro
• AUTOSAR 4 import of a negative exponential value ignored the sign
• Export option 'Create UUIDs' wrote identical UUIDs for all signal- and frame ports
• Creating an OnTransitionTrigger from the runnable context menu didn't work

(top)

DaVinci Developer Version 3.7 (SP5)

Usability enhancements

• Multi-select and default settings usability enhancements for End-to-End Protection configuration
• The available filter options from the Import dialog are now available via command line DVImEx
• Structure graphics is now changeable even if the composition type is locked
• Multi-select editing of Communication Specification values is now supported
• A dedicated 'order index' column has been added for lists that have a relevant order in the ARXML schema

Fixed issues

• Not all Asian characters could be used in description fields
• Find unused object menu was sometimes disabled
• Create Port-Prototypes function didn't create record data-types for signal groups
• Developer crashed when importing an enumeration data type with physical and internal constraints
• AUTOSAR 4: Signal-Port time out value was not imported
• AUTOSAR 4: Not all Parameter-Accesses were exported for modelled calibration elements
• An internal exception occurred on ARXML import if an existing component type had a different internal behavior name and a runnable with the same name
• Importing an AUTOSAR 3 array without type-reference into an AUTOSAR 4 workspace created an invalid the data-type
• Duplicate UUIDs occurred when creating a Multiple-ECU project from ECU Extracts containing UUIDs
• The name of an imported argument prototype wasn't imported correctly
• End-to-End protection data IDs were mixed up when opening an old workspace saved with DaVinci Developer 3.2
• Unlocking a composition didn't allow moving its ports/component prototypes until the ECU-Project editor was reopened
• Create port from signal didn't worked for multiple signals if the data mapping wasn't created in the same step

(top)

DaVinci Developer Version 3.7 (SP4)

Tool features

• Export of ARXML files with AUTOSAR schema 4.1.1 is now supported
• Support of signals sent on several frames on several channels of a cluster has been added
• Text-ValueSpecification can now be used as init value for an Enum Data-Type
• AUTOSAR 3: Service Mapping for S/R Ports supports now n:1 connections

Usability enhancements

• Automatic data-mapping can now be disabled while creating port-prototypes
• Select-All in Library view no works as a 'deep select' on all subjacent items
• 'Flip Direction' command is now available at port prototypes in the Component Editor
• After Copy&Paste of port prototypes to the port list, the new ports are now selected automatically

Fixed issues

• ECU-C synchronization added unnecessary COM-Callbacks if the same OS application was used by multiple tasks
• Illegal file split was created during project update if signals have been moved into a signal group of a different package
• End-to-End Protection profiles _XOR and _XOR+2 didn't allow a DataID of 0
• DVImEx command line tool didn't export all referenced elements
• Record element literals were not unique after adapting record constants to a modified structure
• The DCF save of a software component was incomplete if obsolete Port-Accesses existed
• Crash during ARXML import fixed if AUTOSAR 3 objects are imported in a new, empty DEV workspace with the ''Substitute missing Objects' flag enabled.
• Import/export of the SYSTEM element didn't preserve the original system name
• Unconnected data mappings of TX/RX signal with two different data elements were not persistent in AUTOSAR 3 DCF workspaces
• Signals with an invalid-value and an init-value lead to a duplicate short-name in AUTOSAR 4
• Signals were missing after AUTOSAR 4 import if the ECU-Extract contained one or more Ethernet clusters.
• Calibration-Support flag of NvBlockSwComponentTypes and ServiceComponentTypes was not written to the ECU-Configuration file
• DCF utility tool didn't support DCF workspace with AUTOSAR 4.1.3 schema
• After using the function 'Adapt connected Ports' an error message 'Typeconflict (code 0x80020005)' was produced when opening the port properties.

(top)

DaVinci Developer Version 3.7 (SP3)

Tool features

• Import of ARXML files with AUTOSAR schema 4.1.3 is now supported

Usability enhancements

• AUTOSAR 3 import now reports an error if multiple component types reference the same internal behavior

Fixed issues

• Create Port Prototype functionality sets the wrong package for existing data types
• AUTOSAR 3 IMC import/update for a Multiple-Config project produced a 'fake' error message that renamed objects exists but no objects were actually renamed
• AUTOSAR 4 import caused a stack overflow exception when importing an array without sub-elements
• Init-Trigger handling was corrected to support legacy convention with a '0' cycle time

(top)

DaVinci Developer Version 3.7 (SP2)

Usability enhancements

• Performance enhancement when loading communication data of a DCF workspace
• Separate layout toolbar for direct modification of graphic port layout

Fixed issues

• 'Substitute missing objects' functionality didn't work anymore with AUTOSAR 4 import files
• Error message 'Invalid pointer code 0x80004003' was thrown when using "Create Port Prototypes" dialog
• Crash fixed when creating a reference from PIM to NvMBlockNeed or the other way around
• DaVinci Difference Analyzer command line didn't accept FlexNet license on 64bit Windows
• Port defined argument values at Application Components couldn't be stored correctly in DCF format and AUTOSAR 3 export
• AUTOSAR 3 import of enumerations didn't work if an enumeration value had the same name but a different position

(top)

DaVinci Developer Version 3.7 (SP1)

Fixed issues

• The 'Last Import' timestamp in the ECU-Project's properties dialog was wrong if service components were loaded on opening the workspace
• Unmodified software components where falsely updated on DCF saving if package information was imported which was actually the same
• Import an existing software component with 'Keep Realization' option was wrong if existing ports with runnable accesses were deleted
• When importing a communication specification of a composition port with an init value of type constant reference the reference was not set
• When changing the kind of communication from queued to unqueued and vice versa, the corresponding communication specifications of ports were not updated on DCF saving
• The 'Find unused Base Types' functionality didn't consider new references of mapped signals
• Some ports were missing after import of an imc file for a multiple configuration project if a port with the same name but different port interface already exists
• After import of the mecu file for a multiple ECU project the data mapping was incomplete if a signal group and their group-signals were mapped in different identities

(top)

DaVinci Developer Version 3.7

Tool features

• General support for AUTOSAR schema 4.1.1 and 4.1.2
• AUTOSAR 4 Port-Groups for definition of Virtual Functions Clusters
• J1939-CLUSTER is now supported with AUTOSAR schema 4.1.1 and 4.1.2
• Enhanced PDU design for Ethernet/IP-Cluster to allow PDUs without frame mapping
• Create Port Prototype from data mapping based on a given signal as available for AUTOSAR 3 can now be used for AUTOSAR 4 too
• Adapt Data Type for Data Element based on a given signal as available for AUTOSAR 3 can now be used for AUTOSAR 4 too
• Various Service Needs extensions and GUI reworks with support of Role-Based port assignment
• Improved definition of invalid value of application data types

Usability enhancements

• Various improvements in roundtrip workflow between DaVinci Developer and DaVinci Configurator Pro
• Some additional data-mapping and compatibility checks for AUTOSAR 4 data types
• End-To-End Protections now have a default package like other design objects

Fixed issues

• The 'check for differences' functionality created a new ECU-Project if the project name differed from the System Extract name
• The 'check for differences' functionality is now disabled in project update use-case since it corrupted the workspace data
• The data-type invalid value couldn't handle float values
• Circular constant references caused a crash when opening such a constant in an editor
• Incompatible init value was reported even if the data-types are compatible
• DCF Utility couldn't handle AUTOSAR 4 DCF workspaces correctly and falsely reported corrupted ARXML files
• Generic attributes of nested data types where incorrectly stored in AUTOSAR 4 DCF workspaces
• DCF workspace couldn't be loaded anymore if a component type or ECU-Project contains an attached file

(top)

DaVinci Developer Version 3.6 (SP4)

Usability enhancements

• Import options 'substitute missing objects' and 'check for differences' are now supported in the same import step
• Enhancements in consistency checks for NV components
• Import dialog now contains a simplified file/folder selection button
• Additional consistency check to avoid data types referencing a data type with the same name

Fixed issues

• Crash was fixed when leaving the NV Block descriptor page of a NV Component editor without having a Block Descriptor defined
• NV component couldn't be configured in the local composition view
• Inter-Runnable-Variable data type wasn't exported to DCF if their component type contained an Inter-Runnable-Variable with a unique data type which wasn't used in any other case
• Blueprints couldn’t be exported to DCF
• Crash fixed if context component for create port prototypes was selected as "none"
• AUTOSAR4: init value of NV block description (ram or rom) couldn't be unset
• AUTOSAR4: Substitute missing objects showed irrelevant unresolved references
• The data type reference of a calibration element prototype wasn't set after import
• Import of a DCF package accidently sets the workspace option "Load Service Components when opening the workspace" to a wrong value
• Copying a runnable broke the data model and causes undesired wait points
• Duplicating an Object copied the original UUID instead of creating a new one.
• HTML links in descriptions didn't appear in the report
• Data mapping view didn't display the correct direction of signals which were sent/received as single signal and as part of a signal-group

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.6 (SP3)

Usability enhancements

• Category items in the Library Browser now have a 'Select All' functionality
• Separate layout toolbar for direct modification of graphic port layout
• Data Type Mapping Set dialog now supports multiple selection and modification through context menu

Fixed issues

• Unmodified objects will no longer update files in the DCF workspace

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.6 (SP2)

Usability enhancements

• Description field in property dialogs or property view now supports hyperlinks with link execution

Fixed issues

• Local .CPG FlexNet license couldn't be checked out if multiple DaVinci Developer licenses are activated in parallel
• ECU-C synchronization of OsSpinlock wrote invalid OsApplication-Refs
• Exporting a nested composite data mapping failed and the ECU-Extract didn't contain the data mapping of the nested array
• An ARXML export became invalid on exporting a symbol-value of component type which didn't fulfill the C-Identifiable pattern.

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.6 (SP1)

Usability enhancements

• Enhanced display of information in the 'About Dialog' if no valid license can be found.
• Performance enhancements during loading/saving DCF workspace and ECU-C synchronization

Fixed issues

• Copy/Paste didn't work if the workspace path contains the "," character
• Duplicate Software Component appeared in LibraryBrowser when re-opened the workspace after creating a workspace snapshot
• The 'find unused' function for TypeMappingSets showed also elements in use
• Workspace elements were editable even if the corresponding DCF arxml file was read-only
• An exception occurred when importing an incomplete AUTOSAR 4 assembly connection
• The size-property or record structure of nested array constants were not updated during import into a workspace already containing this constant
• Error 'No such interface supported' with code 0x80004002 was shown twice when importing a Service-SWC by the file observation function
• DataMapping contained a network signal without a name, message, and network, if a signal was part of at least two signal groups and each of them was received or transmitted on a frame
• Implementation data types couldn't be deleted from within the Package View

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.6

Tool features

• Support for Port-Prototype blueprints in the software design
• Multi-core design is now supported by assigning a core to an OS-Application in AUTOSAR 3
• N:1 communication is now supported in AUTOSAR 4
• TP transmitted signals are now available for Data-Mapping in AUTOSAR 4
• Support of NvData-Interface and NvBlock-Component-Types in AUTOSAR 4
• System-Signals with 'dynamicLength' are now supported to address the specific use-cases for J1939 and IP
• The AUTOSAR UUID attribute is now stored for all Objects for a better roundtrip support, new Objects can also be exported with a UUID
• ARXML import of IP cluster descriptions also from AUTOSAR 4.1.1 format
• The Vector AUTOSAR Explorer is now delivered as part of the DaVinci DEV setup

Usability enhancements

• Enhanced interaction between DaVinci DEV and DaVinci CFG to detect renamed objects and refactured references accordingly
• Support of externally defined service component files which are loaded automatically as read-only elements into DaVinci DEV
• Some enhancements in aligning graphic elements and taken over attributes when copying graphic elements

Fixed issues

• AUTOSAR 4 import falsely reported duplicate item names although the file contained unique names
• AUTOSAR 4 import didn't overwrite the array size of an existing constant
• AUTOSAR 4 consistency check falsely reported an incompatible End-to-End Protection although it was valid
• Exporting a DCF workspace using DVImEx.exe threw an unknown error if the -s command line switch wasn't specified
• Property view displayed wrong item after selecting a software component prototype

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.5 (SP4)

Usability enhancements

• For graphic operations a UNDO functionality is now available
• Definition of constants has been enhanced by supporting multi-selection and in-place editing
• The HTML report now displays 'Queue Length: - ' if a data element is unqueued.

Fixed issues

• GUI falsely allowed usage of multiple underscores for the record element name of record constants
• GUI didn't allow leading underscore for the Symbol Values of Implementation Datatypes
• AUTOSAR 3 import in 'Communication only' mode didn't set the correct package information and doesn't update dependent elements
• Diff&Merge aborted with an unrelated error if the ARXML export wasn't possible
• PDUs without package couldn't be merged during AUTOSAR 3 import if the workspace already contains the PDUs without packages
• Error during DCF saving concerning consistency ID 40116 if a trigger name clash exists
• Data mapping wasn't recognized in DaVinci Configurator Pro if DaVinci Developer setting 'use default packages' was enabled
• During ARXML import the merge of existing Port-API Options was wrong if multiple port prototypes on different component types had the same name
• Data mapping view showed superfluous group signal rows which cannot be unmapped if a signal group was mapped to multiple frames and the received group signal sets were different
• ECU-C synchronization configured invalid Com callbacks if system signal was received by multiple frames and additionally as part of a system signal group
• ECU-C synchronization showed a different ComSignal name postfix if the corresponding PDUs are configured as SplitTxRxPDUs and Tx-OverlayingPDUs
• ECU-C synchronization reported invalid system signal references
• Invalid ComSignal/ISignalToIPDUMapping references were falsely reported if the corresponding ISignalTriggering didn't reference a signal port
• Component Prototype properties dialog couldn't be opened from within the component type selection dialog
• Packages could be deleted without error message even if they are in use
• Copying multiple elements in a list based view didn't work correctly and showed an error message

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.5 (SP3)

Usability enhancements

• Enhanced display of information in the 'About Dialog' if no valid license can be found.
• Performance enhancements during loading/saving DCF workspace and ECU-C synchronization
• New technical reference for AUTOSAR 4 Data Type design

Fixed issues

• In rare cases the FlexNet license couldn't be checked out from a license server
• Check for corrupted files in DCFUtility failed when using AUTOSAR 4 workspaces
• DCFUtility showed "incompatible file version 0x6c00" error message when opening the ECU-Project binary file
• Error occurred when importing an ECU SW-Composition port with a Com-Spec without init value
• SUPPORTS-ASYNCHRONOUS-MODE-SWITCH = true leaded to missing port accesses
• The generated Rte code contained wrong ComSignal handles and/or ComSignal handles were missing.
• Loading a AUTOSAR 3 DCF workspace didn't finish in a reasonable time if End-to-End protections with deep SWC hierarchies existed

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.5 (SP2)

Tool features

• New Data Exchange Analysis view in the ECU-Project to get an overview of the resulting port data exchange, operation invocation or signal flow within the ECU

Usability enhancements

• Some AUTOSAR 4 specific basic data type checks have been implemented to ensure a valid base type, native declaration und unique naming
• Data type map consistency check message with ID 30050 has been improved by showing the concrete data type which has to be fixed
• The "Find Unsed Data Types" functionality has been improved to support all AUTOSAR 4 data type definitions
• In multiple configuration projects, delegation ports with the same name but different data types are now automatically postfixed with the identity name

Fixed issues

• After a new Project Assistant project has been created the corresponding workspace wasn't opened directly
• AUTOSAR 4 import of connections didn't work for empty component types
• Defined End-to-End connections to unconnected composition ports were lost during saving/loading a DCF workspace
• Renaming of objects like Mode Declaration Groups didn't trigger all affected files to be updated in a DCF workspace
• An existing Compu Method Reference couldn't be removed in the dialog by selecting the "none" entry
• Init values at Inter-Runnable variables weren't checked correctly for data type compatibility
• Timeout values with different units were reported as different although they were equal
• Complex Device Driver were imported as a service component type if no service- or application-ports were defined
• AUTOSAR 4 data constraints were not imported correctly if a compu-method specifies a compu-default-value
• Some memory leaks during AUTOASAR 4 import have been solved, which caused a crash during load of the DCF workspace
• Duplicated elements were imported if an element was defined in several files and contained sub-elements without a SHORT-NAME.
• The NvMBlock length and RomBlock address was not adapted during ECU-C synchronization if the NvBlockDescriptor's NvBlockNeed length was greater than 0
• Top-level connections derived from the data mapping were missing because the root composition in the ECU-Extract didn't contain connections
• Data mapping of an array DataElement to a signal wasn't supported for AUTOSAR 4 application data types
• Port prototypes, component prototypes and connections weren't deleted from the EcuSwComposition if the root composition type and/or package was renamed during updating the ECU-Extract
• After an AUTOSAR 4 communication update obsolete signal groups were still mapped on a frame
• Some communication elements were missing after opening a DCF workspace that contained PDU groups referencing other PDU groups
• Internal exception thrown during AUTOSAR 4 import if the project contained a PDU with the same name as in the imported file, except for character case.
• Message name in the data mapping view was missing if a signal was mapped on a PDU/Frame which contained signals mapped to several PDUs/Frames
• Compilation of the generated Rte code failed because of missing Rte functions in multiple configuration projects using extracts of a Multiple-ECU project
• Data IDs of different End-To-End connections were appended during update of a Multiple-ECU project
• The Array constant definition was restricted to 512 elements in the GUI
• The Rte generation showed an internal error about a missing COM signal if a signal was mapped standalone and as a group signal on different frames of the same cluster
• Click on the "Copy" button didn't have any effect in the ECU Composition Port Prototype list view.
• The "Adapt Connected Port Prototypes" functionality created invalid AUTOSAR 4 constant references
• DaVinci DEV crashed when deleting a record element constant which contained duplicate elements

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal

(top)

DaVinci Developer Version 3.5 (SP1)

Tool features

• Support for interrunnable variables with complex data types

Fixed issues

• Exported of ECU-Extract contained invalid SIGNAL-MAPPING elements if a system signal was received and transmitted on several clusters or frames
• Wrong consistency check messages were shown after the first ECU-C synchronization
• Rte generation failed with "internal error" if the workspace contained Nv ports and the workspace option 'Check and Generate Nv ports' was disabled.
• ComSignal-names were not correctly imported from the ECU-C file for AUTOSAR 3 Multi-ECU or Multi-Config project.
• The Software Component properties dialog cannot be closed if the Internal Behavior element contained a custom name without implementation element.
• The MECU file of Multi-ECU project couldn't be imported if the 'MasterExtract' XML element contained additional elements e.g. comments
• Crash on importing ECU-Extract fixed if End-to-End protections with END-TO-END-PROTECTION-I-SIGNAL-I-PDUS exists in the ARXML file.

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.5

Tool features

• Definition of End-to-End Protection is now supported for ECU internal connections
• Enhanced workflow support for the merge use-case: new Project Merge Assistant functionality available in the explorer context menu of a .dpa file
• Support of Nv Data Interface and Nv Block Component Types in AUTOSAR 3
• The SYMBOL property is now supported at the Software Component Type
• For the online calibration the 'RAM buffer size' is configurable under Generation Parameters
• Description at the COMPU-SCALE object is now supported

Usability enhancements

• Setup of a new Project Assistant project will now create standard End-to-End Protection generation calls in the Generator list
• DaVinci Developer component registration within Windows using the DaVinci Installation Manager is no longer required. Thus administrative rights are only required at setup time and no longer at runtime.
• Large performance enhancement when merging software components with the 'Check differences before import' option
• ECU Project report now contains more description fields

Fixed issues

• Non-ANSI characters were located in the standard data type description; they are removed now.
• The setting for 'UsesE2EProtection' will now always exported into XML, even if set to FALSE
• Importing an existing AUTOSAR 4 port interface with a different 'IsService' setting no longer throws an exception
• Creating a new AUTOSAR 4 project no longer throws an 'missing package reference' error when adding a new port prototype to the ECU Software Composition
• AUTOSAR 3 import merged CompuMethods with the same name and package even if they were not equal
• DVImEx command line tool didn't report an error if the specified item couldn't be found
• Removing packages which were used within a ECU software composition didn't throw an error
• Using 'Substitute missing objects' import option caused an exception if an application data type was resolved with a workspace element
• The default package assignment during import was not correct for CompuMethods and Units
• AUTOSAR 4 communication update removed an existing LIN cluster
• Generic attribute export was missing for port prototypes at the ECU software composition
• AUTOSAR 4 export aborted if an inconsistent port connection existed
• The find function didn't find Enumerators and Record-Elements
• Incompatible standard generator was reported when using command line Rte generator
• Error dialog with message "Failed to create empty document." was shown during ECU Project report containing software compositions
• Timestamp of observed external Service-Components were reset after workspace reloading when using DCF format
• Crash in import dialog if observed Service-Component file were added twice and one of the duplicates was removed

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.4

Tool features

• Automatic mapping of application- to implementation data types
• Configuration of 'Mode Transisiton' runnable triggers is now supported
• Design of pointer data types (DATA_REFERENCE) is now supported

Usability enhancements

• In the software design the Tab-key can be used to step to the next design element of the same type
• Some enhancements in grid alignment of connections and cross-sheet connectors
• Enhanced info message to detect objects in different packages with the same name but different content

Fixed issues

• Creation of circular references within record and array data types is now denied
• Consistency check for missing application data type was only executed during Rte generation but not in the tool
• Importing a data reference which does not specify an impl or target policy hasn't set the SwImplPolicy value to 'standard'
• Rte validation and generation aborted with the message "Could not open file" if the temporary files folder contained too many files following the same name pattern.

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3 (SP5)

Tool features

• Support of Signals has been added which were sent on several frames with several channels of a cluster

Usability enhancements

• Naming of 'Symbol' attribute in data type dialogs has been clarified. The term 'Code Symbol' and 'Short Name' is now used instead.
• Performance enhancement on import/check of data types

Fixed issues

• List display of large number of port prototypes was incorrect when using cursor keys for navigation
• Crash when pressing "n" in the Compu-Method dialog fixed
• The communication specification attributes were incorrectly/not adapted on a destination port.
• Some minor memory leaks fixed
• In rare cases the automatic Data-Mapping switched the sub-element mapping of signal groups

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3 (SP4)

Tool features

• New Data Exchange Analysis view in the ECU-Project to get an overview of the resulting port data exchange, operation invocation or signal flow within the ECU
• Port Defined Argument Values are now available at Application Components

Usability enhancements

• Performance enhancements during loading/saving DCF workspace and ECU-C synchronization
• Init-Runnable annotation is now supported in AUTOSAR 4 Admin-Data export
• Category items in the Library View now have a 'SelectAll' function

Fixed issues

• Editing port accesses using multiple selection led in a dialog error
• AUTOSAR 3 import of enumerations didn't work if an enumeration value had the same name but a different position
• Existing SWC implementation was removed during AUTOSAR 4 import if a SWC with the same name and empty structure was imported
• Internal data constraint couldn't be edit if set to -INF or +INF
• Error message 'item not found' during AUTOSAR 4 import fixed if an existing data type with compu-method was updated without a compu-method
• Wrong export of constant-reference item fixed if it actually didn't reference a constant
• Wrong export of the DEST attribute fixed if the component type is a complex device driver
• The data-constraint reference wasn't saved on closing the dialog with 'OK' after creating a new calibration element prototype
• Crash on re-opening a DCF workspace fixed that was caused by memory leaks
• Name clash fixed during export of End-to-End protections on atomic ports
• The 'Adapt connected port' functionality didn't consider all communication specification values like 'EnableUpdate'
• Consistency check message #40329 'unsupported N:M communication' wasn't displayed anymore
• Mapping of single signal to nested arrays and vice versa didn't work correctly
• Task property 'generate schedule calls' wasn't stored in the ECU-C file
• Invalid ComSignal/ISignalToIPDUMapping references were falsely reported if the corresponding ISignalTriggering didn't reference a signal port
• CalibrationSupport flag wasn't written to the ECU-C file for all atomic software components
• In some cases the 'Find Results' properties opened the wrong property dialog

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3 (SP3)

Tool features

• End-to-End protection resynchronization flags are now supported for AUTOSAR schema 4.0.3
• Data Mapping of single signal to array data types is now supported if the array is part of a complex structure
• Import feature "check for differences" is now available for AUTOSAR 4 Software Component Types

Usability enhancements

• Misleading general import message "Ignoring internal data constraints" is now replaced with a more specific one if the data constraints are incompatible
• Starting from an existing port it is now possible to create a foreign port, including a necessary connection
• Copy&Paste of Data-Element-Prototypes and Port-Prototypes is now supported from one interface/component to another
• The automatic data mapping has been enhanced to match sub-strings with the biggest possible string length
• The 'adapt connected port' function has been enhanced with additional options

Fixed issues

• The default package path assignment to CompuMethods and Units was wrong
• The properties button in the data selection dialog didn't work for AUTOSAR 4 data types
• Wrong import of indexed elements (e.g. Record-Elements) has been fixed if the elements have temporarily the same name during import process
• Import of Revision-Label at the InternalBehavior element was missing
• Consistency check was not correctly executed for Calibration Communication-Specifications
• The item locking state was not corrected stored for packages in DCF workspaces
• In ARXML export of DCF saving the generic attribute IMPORT_MODE_PRESET was missing at the ECU-SW-Composition delegation ports
• When importing an updated ECU-Extract an existing LIN-cluster was deleted.
• If the delegation port of an ECU software composition was inconsistent the ARXML export aborts with error message 'Internal exception occurred: The connection is missing a valid transmitter or receiver port'
• The Runnable Operation Access was not imported using a AUTOSAR 4 SoftwareComponentType in "overwrite" mode
• The Component Type dialog not forbids setting the 'supportsMultipleInstantiation' flag for Service SWCs.
• Internal exception during ARXML import has been fixed if an application data type was resolved using a workspace element
• The package import mode workspace and session setting was ignored by the ARXML import dialog. Thus it always selected the package import mode 'import from file'
• The ModeDeclarationGroups dialog was not correctly updated when explicit values of a mode have been changed
• The color highlighting of compatible ports was not consistent during manually drawing of a connection

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3 (SP2)

Tool features

• Cross-Importer is now available to import AUTOSAR 3 software components into an AUTOSAR 4 workspace
• End-to-End protection resynchronization flags are now supported for AUTOSAR schema 3.2.2 and 3.2.1
• Calibration communication specifications are now supported on Compositions too

Usability enhancements

• Constant selection dialog now additionally displays the constant value
• Workspace format has now to be chosen explicitly when creating a new workspace
• Some consistency checks have been enhanced to detect usage of identical names that lead into Rte generation errors
• XML-Importer Output messages have been improved to display more context information
• Separate consistency message details dialog has been replaced by an in-place display in the messages tab

Fixed issues

• "Save As..." didn't work if .dev workspace file was set to read-only
• Consistency check ID 20013 was thrown on invalid argument prototype which was not visible in the GUI
• Cryptic open workspace message was shown in the action log when using DCF workspace in a DPA project
• Item information was missing in the data type unit check message
• Find functionality didn't fully support AUTOSAR 4 types
• Obsolete menu entries appeared in AUTOSAR 4 design mode
• AUTOSAR 4 PARAMETER-PROVIDE-COM-SPEC was is not exported
• COM-Callbacks couldn't be configured depending on the 'enabledUpdate' setting
• Several problems concerning missing elements have been fixed in the AUTOSAR 4 import/export
• Crash in converting old .dev workspace fixed if inconsistent objects exist
• AUTOSAR 4 EcuAbstraction- or ComplexDeviceDriver were imported as services even if they used application ports
• AUTOSAR 4 import with "Substitute missing objects" didn't work with mode declarations

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3 (SP1)

Tool features

• The 'Enable Update' is now supported at the communication specification to configure the Rte_IsUpdated functionality
• N:1 Sender/Receiver Intra-ECU communication is now supported in case no internal senders were used
• Reporting of ECU Extracts and Software Components is now fully available for AUTOSAR 4
• ARXML export in schema version 4.0.2 is now available

Usability enhancements

• Definition of record order index can now be simply configured by moving the elements
• A separate icon has been introduced in the graphic for Nv Data Port Prototypes

Fixed issues

• Wrong check message for open delegation R-Ports without init values has been fixed
• End-to-End protection information was not fully imported/exported for AUTOSAR 4 format
• The option ''Overwrite import mode preset' didn’t work for AUTOSAR 4 import
• The 'create port prototype' functionality in the data mapping view failed with the message 'invalid pointer 0x80004003' when using signal groups
• A new workspace couldn't be created based on a Multiple Configuration project setup
• Superfluous Operation Argument Prototypes were not deleted when importing an ARXML file
• An invalid ARXML file was exported if the configuration contains diagnostic communication needs
• A modified software component graphic was not stored if the component type was locked during the graphic editor was open
• New calibration element prototypes could only be created by pressing 'Apply' in the dialog and not with 'OK'
• The properties window didn't display the signal attributes of the selected network signal in the data mapping view
• Multiple Configuration files couldn't be imported because the XML import dialog reported that the selected *.imc/*.mecu file was not supported.
• Unconnected Calibration Ports caused a Rte generation error
• AUTOSAR 4 export wrote lots of empty XML element tags
• A check was missing to report that a Service Mapping should not allow N:1 Client/Server communication

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types

(top)

DaVinci Developer Version 3.3

Tool features

• Workspace design mode: AUTOSAR 3 or AUTOSAR 4
• Import/Export of AUTOSAR 4.0.3
• Import/Export of AUTOSAR 3.2.2
• Support of DaVinci Configurator 5 projects: hide RTE configuration features
• Import of frames with multiple frame triggerings
• Selective import (communication only)
• AUTOSAR 4
  • Support of data type model (Application Data Types, Implementation Data Types, Base Types, Type Mapping Set)
  • Definition of constants as value without type reference
  • Compu Method, Unit and Data Constraint as library objects
  • Selection of included data types in context of a component type
  • Selection of data constraints and handle-invalid settings for data element prototypes
  • Local definition of init values constants in the communication specification
  • Definition of symbol for component types and data types
• AUTOSAR 3
  • Support of NV Data Interface
  • Support of Daimler E2E profiles

Usability enhancements

• Import Dialog: display AUTOSAR version of selected files
• Import Dialog: allow import of a file set with differing AUTOSAR minor versions
• Allow unconnected delegation ports (info instead of error message)
• Allow unconnected calibration R-ports
• Init value can be omitted, if the init value is defined at the connected port
• AUTOSAR 3: Display resulting physical range of a data type depending on the scaling

Limitations

• For AUTOSAR 4 design the following functionality is currently not available:
  • Create Port Prototype from data mapping based on a given signal
  • Adapt Data Type for Data Element based on a given signal
  • Find unused data types
  • Reporting of ECU-Extracts or Software Components

(top)

DaVinci Developer Version 3.2 (SP7)

Tool features

• Maximum enumerator name length has been increased from 255 to 32767 characters
• Support of Signals has been added which were sent on several frames with several channels of a cluster

Fixed issues

• In rare cases the automatic Data-Mapping switched the sub-element mapping of signal groups
• It was falsely allowed to add a second composition to an ECU-Project using Drag&Drop
• The Library's package view was not updated when creating a new root package within the package selection dialog

(top)

DaVinci Developer Version 3.2 (SP6)

Tool features

• Support of UUIDs on import/export at additional elements has been added

Usability enhancements

• Automatic service mapping has been enhanced to get better sub-string name matching

Fixed issues

• Autoconnect popup menu was corrupt and contained empty and wrong entries
• Option to show strict compatible ports only must be toggled to had an effect
• Rte code contained a wrong com signal (group) handle: the handle of a transmitted ComSignal is used instead of the handle fo the received ComSignal.
• A DCF workspace couldn't be opened anymore due to invalid SIGNAL-MAPPING elements if a system signal was received and transmitted on several clusters/frames
• Error message "Invalid pointer code 0x80004003" was thrown when using "Create Port Prototypes"

(top)

DaVinci Developer Version 3.2 (SP5)

Tool features

• Task Mapping has been improved to read the Schedule Manager configuration from the ECU-C

Usability enhancements

• Performance enhancements during loading/saving DCF workspace and ECU-C synchronization
• Automatic data mapping has been enhanced for Group-Signals with better name matching

Fixed issues

• Copy&Paste keyboard support (Ctrl+C and old Ctrl+Ins, ....) was missing in the output window
• Consistency check crashed in rare cases if the model contains unresolved references, e.g. caused by an import of an inconsistent ARXML file
• Calibration-Access of queued communication was exported with the wrong default value which should be 'not accessible'
• Misleading Action-Log message: 'CONTAINER /ActiveEcuC/Os/osSystemApplication: Os resource reference /ActiveEcuC/Os/RES_XYZ could not be resolved.' was reported
• Closing a dialog with "Cancel" initiated superfluous GUI updates on unmodified data
• 'Adapt Data Element to Signal' or 'Create Port Prototypes' falsely modified the record element order
• A software component was displayed twice in the graphic when dropped into a composition
• Export of ECU-Extract contained invalid SIGNAL-MAPPING elements if a system signal was received and transmitted on several clusters or frames

(top)

DaVinci Developer Version 3.2 (SP4)

Tool features

• New Data Exchange Analysis view in the ECU-Project to get an overview of the resulting port data exchange, operation invocation or signal flow within the ECU

Usability enhancements

• End-to-End Protections can now be re-assigned to another port and remain existent if the Data-Element-Prototype is removed
• During data mapping an existing data type is now automatically reused in the 'Create Port Prototype' functionality if the name and primitive types matches the new mapping
• The selection in the data mapping editor now remains, when opening and closing the 'Create Port Prototype' dialog
• Drag&Drop of multiple selected ports have been enhanced to keep their left/right position
• Delegation Ports can now be located automatically when positioned on several sheets and shifted to a sheet manually when unconnected

Fixed issues

• Crash in generic data selection dialogs fixed if the dialog was closed with a double-click without a selected item
• The Copy&Paste command from the context menu didn't work in the library window
• The RTE Generation aborted with the error 'An entry with the same key already exists' when an Application Error of an Operation Prototype was not uniquely named

(top)

DaVinci Developer Version 3.2 (SP3)

Tool features

• Display and edit of Port-Access and Trigger Short-Names of runnables are now available in the GUI

Usability enhancements

• Create ports from signals now allows direct specification of packages for the newly created objects
• ECU-Project and SWC report has been enhanced to display description fields
• Trusted functions, which weren't added by the RTE (without the 'Rte_' Prefix) are no longer displayed as error in the ECU-C synchronization difference view
• ARXML import performance using ''substitute missing objects' option has been significantly improved
• Separate consistency message details dialog has been replaced by an in-place display in the messages tab

Fixed issues

• Incompatible standard generator was reported when using command line Rte generator with an ECU-Project that didn't contain a generator definition
• Crash occurred while loading ECU-C file of a DCF workspace if the ECU-C file was split into module specific files but the main ECU-C was empty, i.e. all module definitions were missing
• Error dialog with message "Failed to create empty document." was shown during ECU-Project reporting if it contained hierarchies of Software-Compositions
• Button on a background view falsely worked on currently active view if two overlapping software component views were opened
• The info message (40288 DataType with the same name as a platform type) created for a DataType/Constant was propagated to the SWC as an error
• VFB Trace functions weren't correctly stored in DCF format if no other workspace modifications have been done.
• Crash occurred when importing an incomplete AUTOSAR file containing a SYSTEM but neither an ECU-INSTANCE nor an ECU-SW-COMPOSITION
• DVImEx didn't report a message when the specified item was not found in the data
• The find function didn't find Enumerators and Record-Elements
• The GenerateStub setting was overwritten even if a user configured value exists
• The operation call return trigger was removed from the ARXML if several runnables were triggered by the same operation call return trigger.
• Group-Signal selection for data mapping didn't show signals if the data mapping view is in 'Data-Element' perspective
• Connection was deleted during ARXML update although one of the connected port prototype's import mode was set to 'keep'

(top)

DaVinci Developer Version 3.2 (SP2)

Tool features

• Configuration support for End-To-End Protection resynchronization added
• Configuration of Rte generation parameters is now also available for Service Components
• Workspace checker command line tool got the new option '-s' to save the check modifications to the workspace

Usability enhancements

• Enhanced display of consistency check messages to allow grouping of similar messages by their ID
• ARXML import dialog now allows import of multiple files with different AUTOSAR 3.x schema versions
• Data type dialogs now display the physical ranges according to the configured scaling information
• Graphical Cross-Sheet Connectors now display the full port name with Component Prototype context
• Delete objects of different types with multi-selection is now supported

Fixed issues

• Memory leaks removed when loading/saving DCF workspace
• Port interfaces without data element prototypes caused empty element tags in the exported ARXML file
• Using the filter in the object selection dialog removed the package display
• ECU Project graphic display caused a memory corruption

(top)

DaVinci Developer Version 3.2 (SP1)

Fixed issues

• Loading a DCF workspace aborts with error message "Unknown Interface" if an obsolete task mapping was defined in the ECU-C file that refered to a deleted runnable or a deleted task
• Rte generation aborted due to inconsistency warnings threw by the Rte generator, which were tolerable in specific cases
• Rte generation aborted due to inconsistent record constant structure
• ARXML import crashed if a Signal-Group and a Signal caused a namespace conflict
• Missing object references in the ARXML file couldn't be resolved with existing workspace objects using "check for differences" option. This option is now disabled because "substitute missing objects" cannot be used when merging the objects.
• USB dongle access caused GUI freeze in some situations

(top)

DaVinci Developer Version 3.2

Tool features

• New Software Component Type to define End-to-End Protection Proxy Components

Usability enhancements

• Additional export Option added to omit the End-to-End Protection Configuration in the exported ARXML

Fixed issues

• Import of ARXML packages had overwritten existing package content instead of merging it
• Multiple Configuration projects couldn't be created if different package structure exists in the input files
• Root package could be illegally moved into an existing package structure that results in a deleted package even if the workspace wasn't saved
• Signal and Signal-Groups weren't allowed to have the same name. This limitation has been removed.

(top)

DaVinci Developer Version 3.1 (SP4)

Usability enhancements

• "Unmap Signal" in the context menu of the Data-Mapping view now supports multi-selection
• Rte trigger and runnable offset properties are now displayed in the properties view when selecting a task mapping table cell
• The "Show ..." option settings in the Data-Mapping dialog are now remembered between dialog sessions
• Multi-selection is now supported for complex constant values via In-Place editing
• Enhanced check for unique C-Symbols in generated Rte code to detect name inconsistencies prior to Rte generation
• Import dialog options are now persistently stored in the workspace to restore them as default on the next dialog session

Fixed issues

• Factor and offset of a data type scaling was mot imported if the ARXML didn't contain a denominator definition at the CompuMethod
• Modification of read/write generic attributes cannot be stored because the Data Element Prototype was read-only
• Loading DCF workspace consumed large amount of memory
• DataSendCompletionTrigger caused a missing Rte-Event reference error in the ECUC-Sync dialog.
• ECU-Project report didn't work for read-only workspaces
• Create DPA project out of existing files failed in DaVinci DEV if no workspace was selected
• Graphic was missing in the HTML report for newly created software components
• Rte generation ran out of memory when using huge complex data types
• The user defined block size on the NvNeed was not used for the ECU-C Synchronization. Instead a wrong calculated value was used.
• DCF workspace save was prevented by check message due to inconsistent import
• Adapt data element to match signals was not available for complex types
• Import of record constant caused unresolved reference error if obsolete record elements were referenced
• Under some circumstances newly created elements didn't get unique names within their package namespace
• The special import 'Overwrite import mode preset' didn't work with read-only items
• Manual service mapping allowed creation of redundant connections
• Import aborted with COM-error 'Invalid parameter' due to an unsupported encoding
• Adapt port prototypes function didn't copy the E2E and HandleNeverReceived settings
• DaVinci DEV runs out of memory because of memory leaks when saving DCF workspace. For DaVinci DEV 3.1 SP4 some leaks have been fixed but there still exists some more that will be fixed in a later version.

Limitations

• AUTOSAR 4.0 import is only possible for software components that don't use AUTOSAR 4.0 specific design features. I.e. only AUTOSAR 3.x related design features are supported.

(top)

DaVinci Developer Version 3.1 (SP3)

Tool features

• Report generator for ECU Projects and Software Component Compositions
• Full import of communication data from ECU-Extract defined with AUTOSAR schema version 4.0

Fixed issues

• Tool crashed because incompatible newer workspace could be opened with older tool
• Import aborted with "unknown error 0x80004005" if the ARXML file was located in a path containing Japanese characters, e.g. a folder on the desktop
• Some consistency check messages were not displayed in the messages tab after Rte code generation
• If the workspace was read-only the code generation couldn't be started because the generation dialog was read-only too
• USB dongle access caused GUI freeze in some situations

Limitations

• AUTOSAR 4.0 import is only possible for software components that don't use AUTOSAR 4.0 specific design features. I.e. only AUTOSAR 3.x related design features are supported.

(top)

DaVinci Developer Version 3.1 (SP2)

Tool features

• Import of Software Components and ECU-Extract defined with AUTOSAR schema version 4.0

Usability enhancements

• Better performance and improved layout of Software Component report

Fixed issues

• First service mapping was not displayed in the service mapping tree if more than one mapping information exists
• If a package has been moved within the package hierarchy the saving of a DCF workspace didn't save all package related items. This resulted in an error on loading the DCF workspace.
• Snapshot of a newly created DCF workspace didn't contain read-only information of data-types
• Workspace modified flag had been reset after creating a snapshot
• DCF workspace was not properly saved if a packages was renamed
• Properties view didn't display information for Atomic-Prototypes

Limitations

• AUTOSAR 4.0 import is only possible for software components that don't use AUTOSAR 4.0 specific design features. I.e. only AUTOSAR 3.x related design features are supported.

(top)

DaVinci Developer Version 3.1 (SP1)

Fixed issues

• DCF workspace couldn't be loaded due to an AUTOSAR schema violation if item short-names started with an underscore or a number
• Error message "Type library is not registered" was thrown on opening a workspace when DaVinci Developer 3.1 and 3.0 were installed in parallel on the same PC and an active 3.0 installation has been switched to 3.1 using the DaVinci Installation Manager
• Component Types were missing on DCF loading because of ambiguous names within a package
• It was unable to rename an item if the name differed only in character case
• ARXML export using DVImEx failed with workspace read-only error if DVImEx was started from within DaVinci Developer to export from the currently opened workspace.
• Rte synchronization was started even if the workspace was inconsistent
• Invalid record constant has thrown an "Unknown pointer" error during the consistency check of an ECU-Project

(top)

DaVinci Developer Version 3.1

Tool features

• Report generator for Software Components
• Support of AUTOSAR Byte-Arrays as primitive data-type
• Support of AUTOSAR Packages

Usability enhancements

• Specific Hex-Editor dialog to define string constants with non-printable characters
• Network signals without frame-mapping can now be used for data-mapping

Fixed issues

• Tool crashed during ARXML import into DCF workspace if the workspace files are read-only
• Rte generation failed if Signal-Group degradation with internal and external receivers existed
• No more error during backup restore after Project Assistant update, caused by the workspace still being used by DaVinci Developer
• Command line Rte generator falsely used the Rte Generator defined at the ECU-Project in the workspace
• An error dialog was missing when a constant was about to be deleted in the Library-Browser which was still in use by a signal

(top)

DaVinci Developer Version 3.0 (SP5)

Tool features

• Support of AUTOSAR schema version 3.2.1
• Introduction of object locked state to specify objects as read-only for tools editors and ARXML import
• A Port-Terminator has been introduced to distinguish between intentionally and unintentionally unconnected ports
• Configuration of the 'Handle Never Received' flag at the receiver communication specification added
• Configuration of the 'Uses End-to-End Protection' flag at the sender/receiver communication specification added
• Configuration of the 'Calibration Access' at the argument prototype of client/server port interfaces added
• End-to-End connections are now allowed for mixed internal and external receivers
• Service Software Component files can now be added to an observation list at the ECU-Project to automatically detect file modifications
• Creation of Support Request Package can be started from File-Menu to pack support relevant information into a ZIP-File
• Additional End-to-End Protection profiles to configure specific safety wrappers
• In the Task Mapping a dedicated timing requirement can be configured at a task, to ease the configuration of timesliced systems
• Difference Analyzer is now able to optionaly display added / removed / equal objects instead of displaying the differences only
• Workspace snapshots can now be created at any point in time to store intermediate copies of an open workspace. By restoring a snapshot the content of the workspace is rolled-back.

Usability enhancements

• New option in ARXML import dialog to resolve open references in ARXML files against existing objects in the workspace
• Depending on the 'allow generation of unsaved data' setting and the version compatibility of the RTE the user will be asked if the workspace should be saved and then automatically continue with the current action.
• If the "Synchronize workspace with ECU-Configuration file when loading a workspace" is deactivated an additional message is now shown if the ECU-Configuration file has been changed while DaVinci DEV was closed.
• When creating a Schedule Manager task in GENy, DaVinci DEV now automatically assigns the role "BSW Scheduler" to this task
• Generation dialog has been reworked to show more detailed generation process and error display
• A configurable check has been added to detect if the Invalid-Value lays within the Data-Type Range
• To allow an import, ServiceSWCs are converted automatically to ComplexDrivers if used in a regular Composition
• The command-line importer can now handle several ARXML files in one import step
• Harmonized the XML formalization of the ECUC-file in all Vector AUTOSAR tools

Fixed issues

• An error message was thrown when selecting a huge number of files (> 1000) for import in the file open dialog
• The modification state of the ECU-C file was checked too often under Windows 7
• Port defined argument values with the same name couldn't be imported at different ports of the same software component
• The category attribute was not exported at the CompuMethod
• AUTOSAR XML import aborted with "item is read-only" message if an object with the same name was part of several AUTOSAR XML files and defined in different AUTOSAR packages.
• Mapping of ECU delegation ports was missing in the exported ARXML if the port was not connected to a component type
• Tool crashed when the Software Design was opened after referenced port has been removed during ARXML import
• Color Highlighting of compatible ports in the structure graphic didn't work correctly with several instances of the same Component Type
• Init value specification at Calibration Parameter Com-Spec was ignored in consistency check and Rte code generation
• Different interpretation of file order in the Multiple-ECU overlay file causes error in ECU-C synchronization
• On certain unresolved references to Mode Declaration Groups or Modes itself the import was aborted
• The consistency-check for ambiguous short names in the exported ARXML is no longer case-sensitive
• When the short name of a child element was removed or not unique the according message dialog might have reappeared endlessly
• The OSApplication assignment to a Task is now stored in the ECUC-file even when no other OSObjects can be determined due to consistency errors
• Checking of differences during ARXML import aborts if ModeExecutionInhibitor objects are defined at the runnable
• Wrong error message in data mapping compatibility check has been thrown if the first record element was not mapped to a group signal
• In some cases the DCF workspace save runs out of memory if the software component structure of the ECU-Project contained lots of Compositions if a deep hierarchy
• The use invalid flag and scaling flag at the data types were not reset during import if there was no semantics information defined in the ARXML file
• In rare cases DaVinci DEV crashed during ECU-C synchronize if a port prototype has been deleted while it was referenced by a Data-Reception-Trigger.
• XML Parser error was thrown on Service Component update if an observed Service Component ARXML file was deleted
• Reference to an AUTOSAR constant couldn't be resolved using an existing constant from the workspace
• Com-Callback was missing for the "handle never received" and "End-to-End protection IsUpdated" use case
• Misleading inconsistency message was thrown on ECU-C synchronization if NvM configuration was out of sync
• Rte generation was always aborted even if the stop button has not been pressed in the current generation process
• ARXML import of a complex constant produced an 'Unknown Error' the referenced complex data type was imported from a different file
• Generated Rte code was invalid if a predefined standard data type was renamed to a predefined platform type, e.g. UInt32 -> uint32.
• In case of a split ECU-C project the Rte/NvM/Os module configurations were accidently added to the central ECU-C file and to the module specific ECU-C file.
• Template- and Contract-Header generation from the SWC-context menu didn't work for DCF workspaces
• The ARXML import in mode 'Overwrite' crashed due to an unresolved reference to a Mode-Declaration-Group
• Diff/Merge didn't import Port-API Options correctly
• ARXML import crashed in resolving missing reference by the substitute functionality
• Consistency check message 40231 was thrown because of wrong offset calculation
• In rare cases creating a new workspace crashed on Windows 7

(top)

DaVinci Developer Version 3.0 (SP4)

Tool features

• Definition of End-to-End Protected connections available at the ECU project delegation ports to enable external generation of safety wrappers
• Port defined argument values (PDAV) can now be edited at the service component ports
• Enhanced compatibility with MICROSAR RTE generators allows usage of previous Rte version 2.17.2 (and newer) as external generator for this DaVinci Developer release.
  You can find a detailed overview with the compatible MICROSAR RTE versions at www.vector.com/rte_davinci
  

Usability enhancements

• Icons of the various DaVinci tools got a unique abbreviation to differentiate the tools more easily
• Check message export function has been enhanced with the detailed description and respects now the sorting order as specified in the list view
• Creation of mapped signal ports can now additionally create Software Component ports and connect them to the created ECU-Delegation port

Fixed issues

• ARXML import of complex Data-Mapping was incomplete if an array data type to a signal group contains or is contained in another complex data type
• ARXML import of complex constants with CONSTANT-REFERENCEs was not correct
• Update of existing workspace with an ARXML import failed if a referenced Port-Interface or Mode-Declaration-Group was missing in the ARXML file
• If a service server port is mapped to a client port, it was not possible to map the port from the server side to another client port
• Consistency check of delegation connector ComSpec on ECU top-level was missing
• Consistency check #40259 created an inconsistency message even if the error trigger was correctly used with invalid handling
• Automatic creation of ports in data mapping failed in case of partially received signal group
• Consistency violation reported if scaled signal was mapped to an opaque data element
• Connectors in connector prototype list view were missing if a connector merge scenario was designed
• Relocation of a connection to a compatible delegation port was not visible due to missing graphic update
• DaVinci DEV freezes on certain handlings in the graphic if a large graphic model without sheets is designed
• Connection inconsistency error occurred due to wrong model update when changing the Component Type of a Component Prototype
• Service Mapping didn't show compatible ports correctly when using the 'show compatible Ports only' option in the selection dialog
• In some cases an error message was thrown during import update of LIN cluster with Sporadic Frames
• Import of Port Defined Argument Values with the same name was not possible
• Superflous COM_SendSignal calls existed in Rte code if the same System-Signal was mapped to several Tx/Rx-Frames
• Wrong consistency check message fixed that the Rx-Signal bit length didn't fit into the data element

(top)

DaVinci Developer Version 3.0 (SP3)

Tool features

• Microsoft Windows 7 is now supported
• DaVinci Installation Setup now allows maintenance of an existing installation and installation of a new instance in parallel with the same Service Pack version
• Parameter for RTE online calibration can now be configured in the context of the 'Generation Parameters' View
• Enhanced handling for Signal-Groups to allow that a receiver of a Signal-Group / complex Data-Type receives only a subset of the data
• DaVinci Project Assistant now supports setting up projects on DBC, LDF, FIBEX files that will automatically converted into an AUTOSAR ECU-Extract
• DaVinci Developer can now work on ECU-C files which are split into module specific files to allow different users to work on different modules in parallel
• Extension of Multiple-ECU support to explicit overlay Tx/Rx signals and allow PDU overlay of PDUs with optional signals
• New dialog for automatic connection of ports with enhanced matching algorithm and selection of desired connections in prior to apply the auto-connect
• For Project Assistant projects the DaVinci workspace format can now be changed from DEV to DCF and vice versa
• New command-line tool DVWspChecker, which allows consistency checking of an ECU-Project or Component-Type in the specified DVW- or DCF-workspace
• New configuration option to disable the init value check for unused ports (without port-access and without calibration parameter).
  IMPORTANT NOTE: disable the check requires MICROSAR RTE version 2.17.2 for correct code generation
  
• DaVinci Project Assistant now support creating of projects based on existing non-DPA projects and creation of DPA-projects with module-split ECU-C files

Usability enhancements

• Ports list view is now available for ECU Software Composition
• OS-Counter parameter will now initially set to Os/SystemTimer when creating new Alarms
• Consistency message results can now be exported into a log file
• DaVinci Project Assistant menu and Model Check menu is now available even if ECU-Project sub-items are selected
• Service mapping update no longer closes the complete editor tree after editing service mappings
• Graphical connections are now highlighted when selected a port or a cross-sheet connector
• Navigation in Software Design editor is now possible by clicking on a delegation port

Fixed issues

• Float number format in ECU-C has been adapted to match format used in DaVinci Configurator Pro and GENy to avoid file differences
• Fixed importing an ECU-Extract using the Diff&Merge feature to avoid corrupted communication information due to wrong merge algorithm
• ECU-C file consistency dialog no longer opens up when saving the workspace
• Obsolete check message is no longer displayed after fixing an inconsistent Data-Element-Prototype at the Component-Type's port
• Errors message for unconnected ports and non-matching Data-Element-Prototypes are now split into separate specific messages
• In some cases the DaVinci DEV application couldn't be closed through the task-bar menu
• Alive timeout handling was falsely enabled if the value was set to 0.0 instead to 0
• In some cases an editor update was missing on creation/deletion of runnables
• Service Need names were not checked for uniqueness
• ComSignal(Group)s were not found in ECU-C in the Multiple-ECU configuration of PDU as Overlay-PDU which contains optional signals in the master ECU-Extract.
• File version checking of the MECU schema version has been corrected
• During ARXML import the remember-option is now disabled on special import mode condition, if only new-mode is allowed
• RteEvent references will now correctly resolved if ECU-C uses short names with 32 chars but ECU-Extract uses short names with 128 characters
• DCF load aborted when the DCF AUTOSAR version was different from the ECU-C AUTOSAR version
• In some cases DEV requested an ECU-C lock although it was not the active application
• Bugfix in the placeholder replacement of $(GENDATAFOLDER) when the following character is a double quote
• ECU-Project consistency check crashed if several runnables exist which were triggered by an OnModeEntry event
• AUTOSAR Import/Export ignored the Communication-Specifications at the ECU delegation ports
• Missing popup menu entries at ECU-Project Connector-List editor for changing port prototypes
• Installation setup has defined wrong working directory entry in the DaVinci Developer desktop link
• ARXML import created Enum-Types without enumerator instead of Integer-Type if the scaling at the data type had defined an own range
• DCF workspace couldn't be saved if multiplexed communication was used
• DaVinci Difference analyzer stopped with error 0x800407D0 in XPath Expression at xsl:if "Too many items - string" if calibration parameter init values were defined
• In rare cases the ECU-C synchronization moves the ECU-Configuration tag in the ARXML file if a module configuration (e.g. of a 3rd Party module) in the ECU-C file exists, that has a Short-Name that comes in the alphabetical order before the 'ActiveECUC' Package.
• ARXML import aborts with E_FAIL error code when importing renamed record data-types referenced by record constants
• Wrong ComSignal handles in Rte because ARXML import didn't update the message to signal relation correctly in overwrite import mode.
• Main window could not be restored if it was minimized running on Windows 7
• Wrong Init-Value consistency check message was reported if obsolete communication specifications existed
• Wrong display of some dialog controls on Chinese Windows has been corrected
• Auto-Connect created a connection between C/S and S/R which resulted in a consistency error
• Auto-Mapping has created wrong or inconsistent signal group mapping if naming rules and compatibility of elements was ambiguously
• If NvM memory blocks were configured and the according NvM service component was imported the consistency check may have been crashed.
• Rte callbacks were missing if the same system signal was mapped on Rx and Tx port
• Response on GUI actions was very slow and had 1-2 seconds latency when using Vector USB Dongle license
• Setup threw an error message that product isn't installed when using the repair option
• Constraints and Limits properties of the data element prototype were ignored when importing
• In rare cases DCF load restored a wrong order index of the Task-Mapping
• Unintended message was shown if the ECU-Configuration file has been changed while closing DaVinci workspace
• Top-Level connections were not correctly removed during ECU-Extract update
• Obsolete ModeDisablingDependencies were not removed correctly during import
• Import of Multiple ECU Extract aborted with 'Item already in Set' error
• Save Workspace As failed, if the workspace was read-only because it was created with a newer DaVinci version.
• ARXML import of incorrect MODE-DEPENDENCY aborted with "Unknown error" instead of printing an error message
• Special import feature couldn't be executed if a Project Assistant file was referenced in the ECU-Project
• An update of an ECU-Project failed with the message "Invalid argument" if a mapped Per-Instance-Memory wasn't overwritten due to the Import-Mode-Preset attribute
• Import of incorrect EXCLUSIVE-AREA-ACCESS aborted with "Unknown error" if the references to the exclusive area was invalid
• If the P-Port was a delegation port of a SW-Composition it was unable to connect an R-Port because of wrong incompatible direction error message
• If multiplexed ECUs exists the DaVinci DEV added ComSignal callbacks to the ECU-Configuration but the functions are not generated by the Rte generator
• Rte generation failed with an internal error if an ARXML with multiple mapping of the same system signal has been imported in prior
• After loading a DCF workspace the data mapping was lost for delegation ports which received a subset of a signal group
• ARXML import crashed if LIN event triggered frames were imported
• Import-Mode-Preset attribute didn't work for Mode Disabling Dependencies and port related triggers in the 'keep' use-case
• Save workspace in DCF format didn't work if BSWMD files with command line macros are specified in the ECU-Project
• OS Application dialog crashed on editing an existing OS Application if more than one OS Application is defined for a task
• A signal was treated as received through a frame although no rx relation existed. This results in an incorrect ECU-C synchronization because the signal was actually not used on Com layer
• Rte generation was wrong because Rx signal relation was missing for Tx/Rx signals sent between two instances of a Multiple-ECU project
• Calibration port init values were not correctly updated on ARXML import of existing software components
• Graphic update was missing if 'complete delegation port' has been executed in a separate view
• Data mapping was not imported/updated correctly in ARXML import of a Multiple-Ecu configuration with complex data types
• Data mapping was lost on loading DCF workspace if not all data elements of a delegation port were connected to an atomic port prototype
• USB dongle access caused GUI freeze in some situations

(top)

DaVinci Developer Version 3.0 (SP2)

Tool features

• Support of AUROSAR 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 <SD GID="edve:ValRef"></SD> 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
• Record constants with invalid element order were created based on a Signal-Group
• In some cases the error message "Receivers of the data element prototype <SignalName> handle the Rx-Filter on a different way." was reported even if the Rx-Filter were correctly defined.
• Rte's Com-Callbacks for Signal-Groups use wrong Group-Signal identifiers if a Fan-In of Signal-Groups with mapping different frames of the same cluster exists
• Generated Rte contains several callback functions with the same name if a signal is mapped to one pdu which in turn is mapped to several frames and the Rte has to generate a callback function for this signal

(top)

DaVinci Developer Version 3.0 (SP1)

Tool features

• Support of LIN Signal-Groups defined LDF files with the naming convention <signal_group_name>__<signal_name>
• AliveTimeOut is now imported from DBC and can be propagated using a new function in the data mapping view
• The newly introduced automatic ECU-C synchronization during workspace load/save can be switched off in the global settings dialog
• Display of calibration objects in the graphic can be switched off in the workspace settings
• Support of ARXML import pre-configuration using generic attribute IMPORT_MODE_PRESET
• Constant property "Generate Symbol" can now be set in Library-Browser via multi-selection

Fixed issues

• Wrong workspace conversion that causes missing Signal Group references during ECU-C synchronization has been fixed
• Inconsistent connections (wrong sender/receiver direction) were not detected by a consistency check
• Error message in the GUI when changing R-Port's "Handle Invalid" property has been fixed
• Compatibility settings couldn't be set properly in the workspace settings dialog
• DCF Utility didn't show Activation Offsets in the ECU-Project binary file
• Missing check messages on inconsistent data mappings have been added
• Additional name information for "DEFINITION-REF" objects in difference view have been added
• Inconsistent structure of a complex constant compared to its data type have caused a generation error even if the constant was not actually generated.
• Out-of-memory error message occurred in DCF Utility when opening large dcb files
• Missing sorting of FIBEX-ELEMENT-REF in difference view has been fixed
• Crash in DaVinci DEV has been fixed when switching to the ModeDelarationGroups in the properties view
• Show in software design command for runnables in task mapping page didn't work.
• Error Handling for ModeQueueLength '0' has been corrected
• Within the data element prototype page the CreateNewDataType button didn't work
• During ARXML import the renaming a child object didn't always work if the names only differ in character case
• External tool command line parameters are changed back to default if no parameters are given in the dialog
• The consistency check for Calibration Ports has been weaken to allow compatible interfaces that are not identical
• ARXML import failed if existing objects only differ in character case from objects that were to be imported
• Tool crashed when saving new SwBlockNeeds with a mirror PIM that had no data type
• In read-only SWCs the implementation popup menus were not disabled and tool crashes if menu commands was executed
• Tool slowed down after running several hours because of GUI resource leaks
• Wrong setting of working folder in attached files dialog fixed that caused error message while opening generated attached SWC template file
• Generated OSAlarm and OSEvents didn't match because the setting 'use shortnames > 32' was not consistently communicated to the RTE
• Added multiple mapping of the same system signal on one frame to support the multiplexing use-case
• Extended support for Tx/Rx split and signal overlay in the Multiple-ECU use-case
• ARXML runnable import of Init-Trigger corrected if no other Trigger exists
• Fixed error while synchronize structure of a complex constant in AUTOSAR export if the structure of the complex data type has been changed
• Newly created graphic sheet names were not stored correctly in the workspace
• ECU-C file data wasn't fully loaded during opening DCF workspace if the AUTOSAR schema versions have been different
• Generic attribute definitions weren't loaded during opening DCF workspace if a corresponding generic attribute didn't exists at an AUTOSAR object
• Missing error message while opening incompatible workspace with RTE Generator fixed
• Generation of templates and contract headers is now allowed for service components
• Sorting of error/warning/info icons in the messages tab has been corrected
• The initial graphic scroll-bar position was often not correct
• Newly created Port-Prototypes are now automatically positioned near the original port
• Auto-mapping for wasn't working well with multi instance SWC
• Directory placeholders with workspace variables were not working correctly for DCF workspaces
• Service mapping was missing when exporting service layer components to ARXML or DCF
• Property dialog for NvM block needs threw an error when using read-only Component-Types
• Some issues in workspace merger functionality have been fixed concerning communication merge, generic attributes, and data-mapping
• The global attribute definition file in a DCF workspace can now be modified in the DCF-file to share it among DCF workspaces
• The Mode disabling dependencies for runnable triggers were doubled during the XML import
• Task attributes priority / description / schedule were incorrectly loaded from DCF workspaces
• Signal bit length was not updated from DBC file if the signal with data-type reverence already exists
• Service needs were deleted during special diagnostic import
• Bad performance while switching from structure design to port prototype view solved by specifiying the livst view as default editor for non-graphic use-cases
• ECU-C sychronize of Init Values produced unnecessary warning output
• Init value check for the Data Mapping didn't work
• Incorrect Exclusive Area Access after DCF loading if AR 2.1 SWC are used together with AR 3.0 ECU-C file
• Attribute definition inconsistencies weren't reported during DCF loading
• Inconsistent NvM block and PDAV order was not reported by a check
• Signal's unit was not imported via LDF file
• Crash has been fixed while opening ECU Project Software Design editor after large SWC was updated by importing new SWC definition
• Loading of global generic attribute definitions has been restructured to avoid overwriting with local attribute definition during DCF loading
• Wrong consistency message concerning maximum values was displayed due to rounding problems in physical value calculation
• Workspace settings were reset on saving a DCF workspace as DEV
• Read-only ECU-Projects were missing after loading a DEV workspace which was created out of an DCF workspace
• Crash during DCF save has been fixed if many read-only DCF files are about to be stored
• Signal length was set to null after a LDF file has been updated through the ECU-Project signal list
• Data mapping was missing after loading DCF workspace if atomic software components were multiply instantiated within an ECU-Project
• Update icon was not correctly displayed in Attached-Files dialog
• In rare cases DCF save aborted with COM Error 0x80070057 if the ECU-Project contains a large amount of Software Component Prototypes

(top)

DaVinci Developer Version 3.0

GUI rework

• New window concept for parallel editing in several views of an ECU project
• Modernized GUI style, icons and tool buttons
• Reworked library browser with additional folders for service related objects
• Reworked software design views to enable multi-editing of object properties
• Clear separation of global user settings and workspace specific settings
• Changed workspace file extension (.dev)

Improved cooperation with DaVinci Configurator Pro

• Project Assistant for convenient creation and update of ECU projects
• Overwrite protection against ECU-C editing conflicts by mutual blocking of the tools

Usability enhancements

• Drag&Drop of component types and port interfaces into structure graphics
• Direct invocation of template/header generation for individual component types from context menu
• More intuitive display of consistency check messages
• Optional display of calibration ports and connectors in structure graphics
• Display of additional info in data mapping editor for fan-in/fan-out signals
• Improved object selection dialogs (display of additional info, enhanced filter logic)

Graphic design improvement

• New layout function: Automatic positioning of delegation ports near the connected port
• New layout function: Vertical/horizontal alignment of components
• More intuitive zoom control via zoom-in/zoom-out buttons
• "Align spread/packed" function available for a selection of ports

Performance enhancements

• Speed-up of ECU-C synchronization
• Speed-up of general XML import/export and consistency check

Merging of design data

• Detailed merge control during import via difference view: overwrite workspace object or keep it
• Fine-grained merge control for complete library objects or individually for each sub-object, e.g. runnable entities and port prototypes
• Merge control setting persistently stored at each object - convenience for subsequent import

Tool features

• Definition of service needs of component types
• Support of complex device driver component types
• Support of LIN signal groups in imported ECU Extract
• Configurable symbol generation of constants
• Definition of limits for calibration element prototypes
• Support of unconnected R-ports and unconnected ports of calibration components
• Definition of alive timeout at delegation port prototypes
• Explicit trigger type "Init Runnable"
• Definition of task type (basic/extended/automatic)
• Definition of task role (application/BSW Scheduler/non-RTE)
• Disabling of automatic trigger generation in the OS
• Search function to find unused objects in the workspace
• Support of invalid values within the range of 0 ... 255 for boolean data-type
• Command line extension for DCF Utility to directly start a DCF workspace difference analyzing from the command line by specifying the 2 workspaces

Fixed issues

• Recent file list was too small
• Under rare circumstances copying of a software component caused a crash because of wrong graphic stream duplication
• Overlay of component prototypes in the Multiple-ECU use-case is now based on the component type reference
• During ECU-C synchronization the task activation value was not considered
• If the first ECU-C synchronization has been done with the direction from ECU-Project into ECU-C file existing COM-Signals were duplicated in the ECU-C file
• In some dialogs the display of the description contained non-printable line-feed characters
• When saving a DCF workspace as DVW all read-only objects were skipped and thus were missing in the resulting DVW workspace
• AUTOSAR export of NvRamAllocation was wrong when using AUTOSAR 2.1 format
• The AUTOSAR import didn't correctly update existing ModeDeclarationGroupPrototypes
• The minimal graphic canvas size couldn't be set using the specific dialog
• Missing GUI update after modification of NvM blocks corrected
• The description attribute of enumerators wasn't imported from the AUTOSAR XML
• In some cases the message output of external generators was truncated in the log window display
• Wrong command line parameter usage while starting external generators if a path parameter ends with a backslash
• Truncated display of constant names in record type combo-box fixed
• When using a constant to initialize a SWC local Calibration Parameter the according constant definition didn't appear within the exported AUTOSAR XML
• The check messages tab content was not cleared on closing the workspace
• Workspace was set to modified during ECU-C synchronization even if no modifications have been made
• Limitation in number of tabs in the software design window has been increased from 32 to 100
• Endlessly reappearing warning box when adding a calibration parameter with a name that already exists in the calibration parameter list fixed
• ECU-C difference dialog has displayed boolean values as 0/-1 instead of false/true
• Update of Task Mapping View was missing when a new runnable trigger with a so far unused cycle time was added

(top)

DaVinci Tool Suite Version 2.3 (SP7)

DaVinci Difference Analyzer

• Display of semantical differences between AUTOSAR XML files
• Supports System Description Files, SWC Description Files and ECU-C Files
• Integrated into Windows Explorer context menu for files with extension .arxml
• Integrated into DaVinci Developer: show differences before importing AUTOSAR XML files

DaVinci DCF Utility

• List the associated files of a DCF workspace
• Show the differences between two DCF workspaces
• Find missing files in DCF workspace
• View the content of DCB files

Usability enhancements

• Task mapping: improved trigger view
• Task Mapping: new view "Component View" to show the runnables per component
• Service Mapping: new views "Service Component View" and "Application Component View"

Tool features

• Design support for automatic creation of service ports and server runnables
• Automatic synchronization of ECU-C file when opening and closing an external configurator
• Detailed report of changed ECU-C settings during synchronization of ECU-C file
• Unified display of consistency errors and RTE generation errors
• Definition of scalings for enumeration types
• Definition semantical limits for data element prototypes
• Configuration of "switch only" and "ack only" access of mode P-ports

Fixed issues

• Wrong painting of property pages in runnable editor after resize
• Missing error message in case of invalid constants of complex data types
• Inter-Runnable-Variable Access-Mode was missing after ARXML import
• Misleading info message in case of missing INTERNAL-BEHAVIOR
• Sending the same signal on both FlexRay channels was falsely considered as signal Fan-Out
• Consistency check result for connected homopolar ports within service mapping was missing
• Missing reference on generic attribute table in DCF in case of adding attribute definitions without additional modifications
• System-Signal init value compatibility check reported wrong warning due to imprecise floating point calculation
• Frame-Node relations were not imported from ARXML for CAN and LIN Frames
• OS-Application property of tasks and description for ECU-Project got lost in DCF format
• Missing objects in AUTOSAR Export if started through multi-selection in Library Browser
• Problems occurred with DCF path definitions using slash '/'
• ECU-Project memory mapping view hasn't respected read-only attribute
• Incorrect update behavior of Port-Prototype dialog if a different Port-Interface was selected
• Ports are displayed overlapping when calling 'Arrange Ports | Align Packed'
• Ports were missing in port selection dialog because of filtering for non-strict compatible ports
• In the Properties views of port connectors, the source/destination data element prototypes were not sorted at all
• In the Properties views of port interfaces/prototypes, the data element prototypes were sorted in fixed descending order
• Moving a multi selection of input and output ports hasn't worked in the graphic display
• Tx-/Rx- evaluation during ECU-C Synchronization was wrong if the same signal was mapped to multiple messages received by different ECUs
• Faulty error message about incompatible data element to signal mapping in case of record data types
• During DCF loading the file name of currently processed ARXML file wasn't displayed
• Creeping performance of code generation and ECU-C Synchronization due to wrong evaluation of task mapping references fixed
• Wrong update of complex constants during ARXML import fixed if structure of the complex data type has been modified
• Wrong display of IOHWAbstraction in Service Mapping tab fixed
• COM-Error code while loading DCF workspace with parameter group generic attributes fixed
• Wrong Task-Priority value during ECU-C Synchronization on Asian Windows fixed
• Further performance enhancement during ECU-C Synchronization and Rte generation
• Missing consistency check for received Data-Elements
• AUTOSAR XML import containing a CompuMethod with Factor = 0 causes endless loop

(top)

DaVinci Tool Suite Version 2.3 (SP6)

Tool features

• Enhanced generator selection for ECU-Projects with support of RTE Generators in different versions
• Additional option whether string data types will use a terminating NULL-byte
• Support of open P-Ports
• Support of signal fan-in use case in ECU Configuration
• Enhanced auto-mapping rules for memory-mapping
• Support of AUTOSAR component type "ECU Abstraction" for desinging IoHwAbstraction
• Definition of communication specification at composition ports
• Various GUI round-ups and enhanced consistency checking

XML Import/Export

• Enhanced workflows:
  • Special overwrite of port prototypes incl. communication specification during import
  • Component implementation merge dialog during import
  • Optional export of top-level structure only
  • User notification in case the ECU-C file has been modified by another tool
• Enumeration constants are now stored with their numeric value as defined in AUTOSAR
• Import of communication data (e.g. signals) is now case-insensitive, i.e. signal names cannot be different in character case only
• Support of explicit rx/tx relation for FlexRay PDUs
• Opaque value can now be stored with byte representation as defined in AUTOSAR specification
• Enhanced sorting of elements within exported ARXML files
• MICROSAR standard service port interfaces are now available as AUTOSAR import file: <DaVinci>\Data\ServicePortInterfaces.arxml

Fixed issues

• Signal invalid values were not displayed as physical value
• Some FlexRay cluster attributes were missing in AUTOSAR export
• Invalid values for 32 bit opaque data types couldn't be defined
• Generic attributes were missing at the Calibration Parameter when stored in DCF format
• Crash in AUTOSAR import fixed if file contains a ModeDeclarationGroup without a valid reference to an initial mode
• Error during AUTOSAR export if both export options 'Export user-defined attributes' and 'Create data types/constants for signals if required' are checked
• Crash fixed when opening large amount (>70) of Component Type editors simultaneously
• Wrong import of extended CAN identifiers fixed
• Missing DCF update added to avoid that deleted objects re-appear after DCF loading
• Wrong renaming if new name only differs in character case
• Memory leak fixed when importing large amount of data
• Application blocking of DaVinci / MICROSAR RTE fixed when working on the same workspace

(top)

DaVinci Tool Suite Version 2.3 (SP5)

Support of Mode Management

• Design of Mode Declaration Groups and Mode Port Prototypes
• Runnable trigger on Mode Entry, Mode Exit, Mode Switch Acknowledge
• Definition of Mode Disabling Dependencies for all runnable triggers

Further port and runnable trigger enhancements

• Support of data element invalidation
• Support of Data Reception Error trigger in case of Rx Timeout

Tool features

• Enhanced GUI and consistency checking for mode / trigger / port access definition
• Automatic mapping of service ports according to naming conventions
• Enhanced automatic data mapping for complex data types
• New consistency check to report inter runnable variables using string data-types
• Support for recursive connections (connection between ports of the same component) within an ECU SW-Composition.
• Selective diagnostics import depending on PDM-ID attribute

XML Import/Export

• Support of AUTOSAR schema 3.0.2 with DCF import/export
• Support of FlexRay ISO TP in AUTOSAR System-Description
• Temporary workspace is no longer required for DCF import/export

Fixed issues

• Data type was missing in DCF export if referenced by a port defined argument value
• Unable to adapt the signal data type according to the data mapping if the init value was missing
• Predefined data types were missing in initially created DCF workspace
• ARXML import of cycle time causes a value overflow if the decimal precision exceeds 15 digits
• Existing service mapping is no longer overwritten on importing an ECU-Extract
• Incompatible Factor, Offset, Unit was not reported by data-mapping compatibility check
• Closing the application is no longer possible while DCF saving is in progress

(top)

DaVinci Tool Suite Version 2.3 (SP4)

Support of RTE Memory Protection in DaVinci DEV

• Definition of OS application (trusted/untrusted)
• Assignment of tasks to OS applications

Extended consistency check

• Allow split and merge of connectors in SW design
• Tolerant data mapping of complex data types
• Flexible data mapping for string types (signal length 1 byte smaller than the string type is now allowed)

Usability enhancements

• Signal Routing in DaVinci SAR: Automatic signal routing now possible for individual signals
• Signal Routing in DaVinci SAR: A correct routing path is now skipped by automatic signal routing
• No more reset of global tool settings after installing a new DaVinci version

XML Import/Export

• Improved handling of BSWMD files during ECU-C synchronization
• Import/Export of COM-PROCESSING-PERIOD
• For LIN import the cluster protocol version is used for the slaves if their protocol is not set

Fixed issues

• Missing data mapping in DCF format
• String constant values don't support full character set of ISO-8859-1
• P-/R-port connector list views display duplicate components
• Obsolete check messages in the output window
• Update problems in structure graphics
• Memory leak while saving DCF workspace removed
• Endless loop on data-mapping of complex data-types fixed
• Scaling of signal/data-types has not been considered correctly in data-mapping compatibility check
• LIN diagnostics frames will now be automatically created in DaVinci Network Designer if they are not available
• Port-Interfaces were always updated during DCF saving even if no modifications have been made
• ECU-C file path is now adapted on workspace Save-As and is only written on ECU-C relevant modifications
• Different generation check results were occurred depending on the generation start method by popup-menu or generator-list
• Endless loop while opening a read-only Component-Type graphic fixed

(top)

DaVinci Tool Suite Version 2.3 (SP3)

Port API options

• Option "Enable Indirect API"
• Option "Enable API usage by address"

Miscellaneous

• Consistency warning in case of runnable entities with period 0 (except for init runnables)
• User-defined attributes for Task and ECU-Project
• ARXML import: Support of FlexRay frames sent by different ECUs in the same slot
• ARXML export: Support of LIN2.0 specific communication properties in ARXML 3.0
• DVImEx.exe command line utility is now able to import/export ARXML files based on DCF workspace

Fixed issues

• Copy&paste by keyboard shortcuts not supported in "Implementation" page of Component Type Editor
• Data mapping displays signal groups, which don't belong to the ECU project
• Problems in "Data Mapping" and "Service Mapping" page in case of multi-instantiated components on different hierarchy levels
• ECU-C Sync: ComTimeoutNotificationCallback for AliveTimeout generated in wrong format (AR2.1 instead of AR3.0)
• Range check during XML import fails in case of 64 bit signals
• Constant- and Signal-Dialog displays wrong values in case of 64 bit data-types/signals
• Automatic data mapping ignores child elements of composite data types
• Consistency check does not report duplicated component prototype names
• ARXML export: T2 values from dbc ignored when generating IPDUTiming
• ARXML export: typo in generated XML file in case of infinite limit of real data types
• ARXML import: problems with upper/lower case of short names during import of service components
• Frame mapped signal group information can't be stored in DCF
• ECU-C synchronization fails if BSWMD files are specified with path information

(top)

DaVinci Tool Suite Version 2.3 (SP2)

Miscellaneous

• Multiple instantiation of atomic component types on the same ECU is possible now
• Specification of RTE Compatibility mode API at the software component
• Full AUTOSAR support of Signals with Data-Type definition and initial value constant; Legacy Signal-Type support has been removed from DaVinci SAR
• Auto-Data-Mapping now support complex data-types that will be mapped on signal groups
• Enhanced performance during workspace saving if many data-types or constants exists

AUTOSAR XML Import/Export

• Support of officially released new AUTOSAR schema version 3.0 rev. 3
• It is now allowed to work with ECU-C and BSWMD files having different AUTOSAR patch-versions
• ARXML export has duplicated the sender-receiver mapping on R-Ports
• ECU-C synchronization is now only done for elements if the ECU-C does contain a corresponding module configuration
• SwComponentInstances for Calprm-ComponentPrototypes are no longer exported in ECU-C file

Fixed issues

• Under some circumstances the data-mapping compatibility check was running into an endless loop for complex data types
• Wrong ranges are displayed for 64 bit data types / signals in DaVinci SAR/DEV
• Some memory leaks during ECU-C file synchronization have been fixed
• In the ECU-Project data-mapping the Tx-Signal Groups were missing for local ECU communication

Known issues

• AUTOSAR export will fail if the two options "Export user-define attributes" and "Create data types/constants for signals if required" are enabled both. Workaround: start the export two times with only one option enabled.

(top)

DaVinci Tool Suite Version 2.3 (SP1)

Miscellaneous

• List view for non-graphical display of compositions
• Support of range enumerators in enum types
• Configurable consistency check for initial value of data element and mapped signal

XML Import/Export

• Import/Export of FlexRay PDUs in AUTOSAR 3.0 XML

Fixed issues

• DCF storage
  • DCF read-only error response doesn't work for port interfaces
  • Saving DCF does overwrite read-only files
  • Sheet names not stored in DCF
  • ECU-Project local signal attributes were not stored in DCF
  • Storage of unmapped Network-Signals in DCF added
• ARXML Import/Export
  • Invalid value is not being imported with ARXML 3.0.1
  • Wrong import of signal unit attribute fixed
  • Fixed import for runnable wait points on asynchronous server calls where the runnable doesn't access the server itself
  • Import crashes if Data-Types doesn't contain min/max ranges
  • Import crashes if timeout of synchronous server call point is missing
  • Generic attributes were missing for Network-Signals
  • More detailed error-message if the AUTOSAR schema version is not supported
  • Fixed import of Network-Signal's init value if referenced constant is of type enumeration
  • Missing import of signal's min/max values / value-type added if a data-type is referenced
  • Some FlexRay node parameters were missing in import/export
  • ECU-C file is no longer re-sorted after export because element order has to be obtained
• DaVinci swaps min and max values for data types with huge range
• ECU-C synchronize for Os/Com/Nvm now possible even if Rte is in sync
• Signals and Data-Type scaling calculation fixed for negative factors greater than -1.0
• Automatic data-mapping has falsely used signals from signal-groups for primitive data elements
• Crash in creation of NVM-Blocks if the name was already used by another NVM-Block
• Incorrect signal-routing in DaVinci SAR fixed if signals are defined in more than one global signal group
• Check of array data-types hasn't report an array size 0 correctly

(top)

DaVinci Tool Suite Version 2.3

XML Import/Export

• Import/Export of component descriptions, communication descriptions, and ECU-C via AUTOSAR 3.0 XML (XSD rev. 0001 and rev. 0002)
• Preliminary FlexRay PDU support: conversion of PDUs into signal groups during import of AUTOSAR 3.0 XML (FIBEX 2.0 compatibility)

Calibration parameters for components

• New page "Calibration Parameters" in component type editor
• Assignment of parameter groups via user defined attribute (enum attribute definition "PAR_GROUP_CAL" with arbitrary group names as enum values)

Calibration component types

• Definition of calibration component types (new realization type "Calibration")
• Definition of calibration port interfaces and calibration port prototypes
• Referencing and connecting of calibration components within a composition type

Per-instance memory

• Definition of per-instance memory of a component type
• New page "Memory Mapping" in ECU project editor to map per-instance memory to NV memory blocks (DEV only)
• Manual and automatic definition of NV memory blocks (DEV only)
• Export and synchronization of NvM section in ECU-C file (DEV only; not available in AUTOSAR 3.0 XML)
• BSWMD file for NvM module configurable for an ECU project (DEV only)

MICROSAR RTE Configurator

• New exe in bin folder: DVRteConfig.exe
• Configures the MICROSAR RTE (Task Mapping, Memory Mapping, Generation Parameters)
• Operates directly on AUTOSAR XML (ECU Extract of System Description plus associated ECU-C)
• Same RTE configuration functionality as DaVinci DEV. Not required, if DaVinci DEV is used.

DaVinci Configuration Files (DCF)

• DCF: Alternative storage format for DaVinci workspaces
• Support for file-based configuration management of DaVinci design data
• New user manual: UserManual_Working_with_DCF.pdf

Miscellaneous

• Support of asynchronous C/S communication
• Support of string data types (data types larger than 8 bytes)
• Support of explicit gateway routing in DaVinci SAR: data mapping of connected data elements to different signals supported
• Import of user-defined attributes via DaVinci attribute XML format
• Selection of both FlexRay channels (redundant transmission) possible in the "Signal Routing" page of DaVinci SAR
• Performance enhancement of Data-Mapping editor in DaVinci SAR

Fixed issues

• Missing update of VFB Tracing page after calling ECU-C synchronization
• In rare cases RTE generation can't be initiated due to model inconsistencies even if ECU project check succeeds
• Usage of atomic component type as top-level component of a Vehicle-Project is now checked and reported

(top)

DaVinci Tool Suite Version 2.2 (SP4)

Usability enhancements in graphical editors

• Display of mapping info in Function Design page of Vehicle Project Editor (SAR only)
• Automatic creation of delegation ports
• Change of port prototype alignment by Drag&Drop
• Automatic arrangement of port prototypes: alphabetically, connected/unconnected
• Copy&paste of port prototypes
• Re-connecting of connector prototypes (change the start or end port)
• Better visibility of selected objects in graphical editors
• Zooming with <Ctrl> + mouse wheel or with +/- keys
• Object positioning with arrow keys

Miscellaneous usability enhancements

• List view in ECU mapping page (SAR only)
• Display of additional context info in ECU Pin Mapping (SAR only)
• Wildcards supported in Object Selection Dialog
• Display of connectors in Object Usage Dialog

Editable network topology graphics (SAR only)

• Manual layout mode and automatic layout mode selectable
• Manual placing of ECUs and networks
• Drawing of networks via line segments

Automatic data mapping

• Automatic selection of signals for unmapped data elements
• Selection based on best guess name matching
• Adaptation of automatically created data mappings possible

Miscellaneous

• Connector Tracing Dialog for function design (SAR only)
• Extended consistency check (open ports, unmapped components, incompatibility in case of queued/unqueued data elements)
• Support of XML schema of AUTOSAR Release 2.1.4 (XSD rev. 0018)
• Update of AUTOSAR Release 2.0 XML schema export: service mapping, scaled data types with shared base types
• Relative paths of BSWMD files supported (DEV only)
• XML export for AUTOSAR Release 1.0 DTD not supported any more

Fixed issues

• Error message when trying to open properties dialog of a C/S connector
• Crash when importing a "double" data type
• Wrong check message about multiple runnable triggers
• AUTOSAR XML Import/Export of C/S communication specification was not supported
• Consistency check for enum constant values was missing

(top)

DaVinci Tool Suite Version 2.2 (SP3)

RTE features

• Support of complex hierarchical data types like arrays-of-records
• Convenient configuration of VFB tracing by import of trace functions from Rte_Hook.h

XML Import/Export

• Support of short names with 128 characters (tool option)

Enhanced consistency checks

• Detailed consistency check and data re-synchronization now available in DaVinci SAR
• Messages page in output window now available in DaVinci SAR
• Consistency check for individual component types supported

Usability enhancement

• Automatic creation of delegation ports to support bottom-up design
• Smart template generator with update functionality now available in the attached file list of a component
• Definition of a global output path in DaVinci DEV

Miscellaneous

• AUTOSAR 1.0 XML format not supported any more

Fixed issues

• Import of TargetLink-generated XML files fails in some situations
• Crash in case of incomplete imported data (missing data type reference of data element prototype)
• Default values of Generation Parameters page do not appear correctly in ECU Configuration File
• Duplicate DATA-SEND-COMPLETED-EVENTs in XML export in some situations

Known issues

• Old tool versions until V2.2.44 (SP2) crash without error message when trying to open a workspace, which has been created with V2.2 SP3
• Task mapping of service components cannot be imported from ECU Configuration File

(top)

DaVinci Tool Suite Version 2.2 (SP2)

Support of AUTOSAR release 2.1

• XML Import/Export according to AUTOSAR 2.1 schema
• Adaptation of object properties according to AUTOSAR 2.1
• RTE generation according to AUTOSAR 2.1

Service mapping

Support of AUTOSAR 2.1 concept of service components and service connectors in DaVinci DEV

• List view in Component Type Editor for non-graphical defining of service ports
• Definition and import of service Component Types
• New page "Service Mapping" in ECU Project Editor to create service connectors

RTE features

• Generation of RTE memory usage report
• Adaptation of object properties according to AUTOSAR 2.1
• Support of activation offset for cyclic runnable entities
• Support of AUTOSAR compiler abstraction and memory abstraction mechanism
• Support of AUTOSAR makefile mechanism for the RTE
• Additional APIs supported: Rte_InitMemory, Rte_IWriteRef
• Smart template generator: Update of component implementation files after changing component description
• Summary of generated files displayed in output window

XML Import/Export

• Export of scalings into separate package
• Export of various additional tags to support Elektrobit Tresos
• Additional consistency checks during import

Miscellaneous

• Demo workspace "InteriorLight" extended by a ComManager service component
• Reload workspace functionality moved from view menu to file menu with (Ctrl+F5) shortcut

Fixed issues

• Rte_Feedback returns illegal error codes in some conditions
• Generation of multiple internal S/R buffers (unqueued communication) with identical name
• Rounding problems with 64 bit signals
• Multiple buffers generated for buffered Interrunnable Variables
• DaVinci SAR: Derivation of software architecture fails if function net contains empty connectors

(top)

DaVinci Tool Suite Version 2.2 (SP1)

RTE features

• Support of Port Defined Arguments (XML import and RTE generation)

Fixed issues

• Import of enumerator names with more than 32 characters not possible
• Data Mapping on FlexRay: Same signal displayed several times in selection dialog
• Application errors of C/S port interfaces not considered in consistency check
• Record constants missing in contract phase header

(top)

DaVinci Tool Suite Version 2.2

DaVinci DEV as standalone tool

• Full-featured design of application components possible with DaVinci DEV
• Setup of ECU projects without vehicle project possible
• Signal import via DBC, FIBEX or LDF files
• Separate command line generation tool for RTE generation: DVRTEGen.exe
• Detailed consistency check of ECU projects (Messages page in output window)

AUTOSAR compliant ECU configuration with DaVinci DEV

• Storage of RTE configuration as AUTOSAR ECU Configuration File
• Synchronization of DaVinci workspace with a given ECU Configuration file possible
• Configurable list of external configuration tools for cooperative editing of the ECU Configuration File
• Obsolete concept of DaVinci Target Packages eliminated. Automatic building of CANoe target DLLs suspended.

RTE features

• Support of array types and enumeration types
• Support of exclusive areas and inter-runnable variables
• Definition of data-send-completed trigger
• State request API for data send points
• Detailed configuration of VFB tracing
• Support of symbol attribute of runnable entities

XML Import/Export

• Merge functionality during XML import to support iterative development processes
• Support of XML schema of AUTOSAR Release 2.0 SP3

Fixed issues

• Task mapping in ECU Configuration file should base on RTE event references instead of runnable entity references
• Definition of communication specifications should be only possible at assembly port prototypes
• Derived port prototypes are not incrementally updated when changing the function network
• Some element issues in XML export (missing data type at operation arguments, wrong number format)
• Inconsistent event configuration when server and all client runnables are mapped to same task
• Missing read-modify-write protection for queue overflow flags

(top)

DaVinci Tool Suite Version 2.1 PRE (SP3)

Software Design

• Software design editor for ECU software architecture
• Redefinition of the top-level granularity of the ECU's software architecture
  see 'DaVinci_DEV_ECU_SW_Design.pdf' in DaVinci Documentation Browser for detailed description
• Support of user-defined ECU-Project local ComponentPrototypes
  see 'DaVinci_DEV_ECU_SW_Design.pdf' in DaVinci Documentation Browser for detailed description
• Definition of 'Not Valid Value' and 'Initial Value' (physical) at the signal added.
• Definition of 'Invalid Value' at the DataType added. The specification of an 'Invalid Value' creates a DataType with semantic
• Definition of a receive timeout value at the input function port added.

XML Import/Export

• Import/Export of INVALID_VALUE definition according to AUTOSAR 2.0 schema

Fixed issues

• Editors remain open after deletion of corresponding context item.
• Inconsistent display of data mapping connectivity information.
• Internal connections between multi-instantiated SWCs are not correctly detected in DaVinci DEV.
• Function Design editor view is not updated when adding a new function.
• Incorrect conversion of component graphic block.
• Incorrect alignment of Function-Net derived composition types.

(top)

DaVinci Tool Suite Version 2.1 PRE (SP2)

XML Export

• Additional export of user-defined attributes in a separate AUTOSAR XML file
  see 'TechnicalReference_UserDefinedAttributeExport.pdf' in DaVinci Documentation Browser

(top)

DaVinci Tool Suite Version 2.1 PRE (SP1)

Software Design

• Refinement of existing software architecture within DaVinci DEV
• Editable runnables and generic attributes in derived software architecture

Client/Server communication

• Support of serialized C/S communication with support of AUTOSAR attribute "Can be invoked concurrently"
• Trigger sorted view for operation invokation trigger in task mapping editor
• Derivation of operation invocation trigger from function trigger specification

ECU Configuration XML export (only DaVinci Developer)

• Export of RTE requirements to Com configuration (ComNotifications)
• Export of RTE requirements to Os configuration completed (OsAlarms, OsEvents)
• Configurable definitions for Com module and Os module in generated XML file

Fixed issues

• Crash when opening runnables properties dialog in task mapping editor
• Bad performance in large function net designs
• Wrong update of derived software architecture if function ports have been changed
• Automatic signal routing was not available for complex data types with signal groups

(top)

DaVinci Tool Suite Version 2.1 PRE

Client/Server communication

• Definition of C/S Port Interfaces and C/S Port Prototypes
• Selection of Operation Invoked trigger

XML Import

• Import of XML files according to AUTOSAR 2.0 schema
• Multi-file import context supported
• Workspace consistency guaranteed by pre-import check of XML files

Enhanced usability of graphical editors

• Component Type Editor for direct editing of component types without vehicle project
• Port alignment may be defined individually for each component prototype
• Direct editing of port prototypes within the structure view
• Function Editor for direct editing of functions without vehicle project

AUTOSAR 2.0 compatibility

• Multiple triggers per runnable entity supported
• XML export for AUTOSAR 2.0 schema available

XML Export of RTE configuration (only DaVinci Developer)

• Export of RTE configuration as AUTOSAR ECU Configuration Description file

Code Generation (only DaVinci Developer)

• Separate generation step for AUTOSAR RTE
• RTE generation possible without installation of a DaVinci Target Package

Fixed issues

• Navigation between sheets via cross reference symbols not possible
• Mapping view table not displayed any more in some situations
• Constants not considered in compatibility check of record data types
• Misc. issues in XML export (wrong TREFs, empty CONSTANTS tag)
• Port prototypes of a component type not displayed in Object Usage Dialog
• Connectivity status not correctly updated in GUI

(top)

DaVinci Tool Suite Version 2.0 PRE (SP3)

Graphical Topology Editor

• Network topology can be graphically displayed in the context of a vehicle project. The graphic is calculated on demand and can't be modified. The topology objects can be selected in the graphic and edited through the objects dialogs

Modeling of devices

• Devices with electrical properties can be globally defined in the Library-Browser and assigned to pins of an ECU.
• Device Accessors within a Function Net can be mapped to concrete devices connected to the ECU pins.
• The ECU Pin Topology is graphically displayed in the ECU Topology Editor accessible through the ECU in the Vehicle Project.

Support for complex data types

• Data types can be defined as record containing any number of non-record data types as record-elements
• Data mapping is done through signal groups where each record-element has to be mapped to a compatible signal within the signal group

Support for simple data semantics

• Simple data semantics consisting of scaling information (factor, offset, unit) can be specified at integer and real data types. This information is exported as PRIMITIVE-TYPE-WITH-SEMANTICS in the AUTOSAR XML Export
• Scaling is relevant for data mapping, i.e. a scaled data type requires a scaled signal to be compatible

Support for Waitpoints

• Additional "Data Access" tab page in the component type dialog to specify the access mode for Queued (Polling, Waiting) and Non-Queued (Direct, Buffered) communication

AUTOSAR Code-Generation (only DaVinci Developer)

• Basic Software Modules updated to AUTOSAR 2.0 API specification. Existent software component code based on previous AUTOSAR specification has to be adapted to new API.
• Support of V850 Real-Target with GreenHills 4.0.7
• Support of M32C Real-Target with IAR 3.10

Fixed issues

• Data-mapping calculates wrong bit-length for some data type ranges
• Deletion of component prototypes referencing multiple instantiated component types may corrupt task mapping
• Completion of Device Accessors within Function Net was sometimes wrong
• MATLAB/Simulink support of signal groups was not working correctly
• MATLAB/Simulink import does not attach the behavior model to the function

(top)

DaVinci Tool Suite Version 2.0 PRE (SP2)

AUTOSAR Code-Generation (only DaVinci Developer)

• Support of V850 Real-Target with GreenHills 3.51

Support for direct / buffered communication

• The access mode to the data element prototypes can be specified for each runnable entity.
  • None: The runnable doesn't access a specific data element prototype.
  • Direct: The runnable explicitly accesses a specific data element prototype. The RTE generation uses direct API calls without additional buffering.
  • Buffered: The runnable implicitly accesses a specific data element prototype. The RTE generation will use additional buffering to keep the state unchanged during runnable execution.

Performance enhancements

• Management of workspaces with huge amount of signals has been improved
• Faster display of tree objects in Project-Explorer and Library-Browser

Configuration management suspended

• Due to some internal restructuring issues the configuration management support has been temporarily disabled. It will be re-activated in one of next releases.

Fixed issues

• Various AUTOSR XML Export issues fixed
  • ENTRY-POINT is now generated for the IMPLEMENTATION
  • Ambiguous NUMERIC-CONSTANT if the same Data-Type is used in different ports at the Component-Type
  • Description for constants were missing
• Copy/Paste of Network within the same Vehicle-Project may crash
• Update of Signal-Routing was incorrect under some circumstances, e.g. deleting a Network
• Data-Type ranges for real-single and real-double corrected if -INF or +INF are used
• Data-mapping creates signals with wrong bit-length

(top)

DaVinci Tool Suite Version 2.0 PRE (SP1)

AUTOSAR Code-Generation (only DaVinci Developer)

• Integration of Vector AUTOSAR Evaluation Bundle with Code-Generation of AUTOSAR SW-Architecture for PC- and Real-Target
• Support of CANoe PC-Target with Microsoft Visual C++ 6.0 / 7.1
• Support of M32C Real-Target with Renesas 5.20

Task-Mapping extension for runnables

• Each runnable entity defined at the Component can now be mapped to a task
• Additional external tasks can be defined through attachment of OIL-Component files at the ECU-Project

Documentation

• Documentation of AUTOSAR XML Export: See "DaVinci AUTOSAR XML Cross Reference" in the Documentation Browser
• User manual of Tool concepts, AUTOSAR RTE and code-generation: See "Vector AUTOSAR Evaluation Bundle" in the Documentation Browser
• Online-Help for DaVinci Network Designer CAN is now available
• Online-Help for DaVinci System Architect and DaVinci Developer is currently not available

AUTOSAR XML Export

• Option in export dialog to generate full-qualified short names
• Export of IMPLEMENTATION with ENTRY-POINT

Fixed issues

• Various AUTOSR XML Export issues fixed
  • Wrong format of P-PORT-PROTOTYPE-REF and R-PORT-PROTOTYPE-REF
  • Short name of TIMING-EVENT missing
  • Definition of BOOLEAN-CONSTANT with BOOLEAN-TYPE-TREF corrected
  • Deleted signals may cause artifacts in the element <SYSTEM-SIGNAL>
  • In some cases a DATA-RECEIVE-POINT was exported where a DATA-SEND-POINT was expected
  • A reference to a DataElementPrototype lacks the ComponentType; a reference to a RunnableEntity lacks the InternalBehavior
  • The values created for the tags CYCLE-TIME, CYCLE-TIME-REPEAT, STARTING-TIME, and DEBOUNCE-TIME are not correctly scaled to unit second
  • Sensor/Actuator creates an internal behavior using an ATOMIC-SOFTWARE-COMPONENT-TYPE-REF instead of a SENSOR-ACTUATOR-SOFTWARE-COMPONENT-TYPE-REF
  • Constants defined in the scope of a Data-Type were not exported
  • Object references using a “*” for fully dereferencing of the current context are valid definitions according to the "Template Formalization Guide", but may be difficult to interpret for XML-Importer. The creation of references with stereotype <<instanceRef>> have been changed by adding the name of a Port-Prototype in front of the qualified name: "port_prototype_short_name*/Element1"
• Component-Prototype can only be created within Compositions. Trying to create it within other Component-Type was not inhibited and causes a crash.
• ECU specific signal choice dialog causes crash in data mapping
• Object can't be renamed to a name with different character case
• Wrong behavior of radio-buttons within Data-Type dialog
• Autorouting of signals doesn't recognize ambiguous receiver within one network correctly
• Mapping of runnables causes deletion of network signals
• Drag&Drop for Sensor/Actuator in mapping page was missing
• Runnable name and description was not stored correctly
• In some cases the function port update in function design structure graphic was missing
• Crash in interface editor if port interface of an exiting port prototype was deleted
• Wrong Tool-Tip behavior in trees consumes all mouse inputs on the subjacent item
• Deletion of a ECU-Project within the Vehicle-Configuration causes a fully deletion of the ECU-Projects itself and not of the link

(top)

DaVinci Tool Suite Version 2.0 PRE

Prerelease to introduce the new tool concept and the AUTOSAR design support. Comprised tools:

• DaVinci System Architect 2.0 PRE
• DaVinci Developer 2.0 PRE
• DaVinci Network Designer CAN 1.0 PRE

Support of Code Generation/Target Packages and ECU State Management is suspended.

New tool concept

Specialized tools for each design use case:

• DaVinci System Architect: Specialized tool for system design
• DaVinci Developer: Specialized tool for ECU code integration
• DaVinci Network Designer: Specialized tool for network design

New tool framework

• Common look-and-feel for all DaVinci tools
• Introduction of projects (vehicle project or ECU project) as "working context"
• New concept for editor windows

Function Design (only DaVinci System Architect)

• Definition of functions with signal interfaces
• Definition of device accessors for specifying signal interfaces of sensors and actuators
• Function-local specification of signal properties allowed to support preliminary integration of a function net
• Manual and automatic definition of function port connectors
• Graphical visualization of function net consistency
• Definition of hierarchical signal groups
• User-defined stereotypes for signals and functions
• Stereotypes are configurable through the STEREOTYPE.INI file located in the DaVinci Bin\Config directory
• Optional display of stereotypes within function graphic
• Function trigger definition (cyclic, spontaneous, on input signal)
• Definition of function execution sequence
• Derivation of a function net as an equivalent AUTOSAR SW architecture

AUTOSAR-compliant SW Design (only DaVinci System Architect)

• Definition of data types
• Definition of port interfaces with data element prototypes
• Graphical design of atomic software components types and composition types
• Definition of runnable entities
• Trigger types "periodically" and "data reception" supported
• Graphical design of SW structure by definition of component prototypes

Data Mapping (only DaVinci System Architect)

• Mapping of network signals to data elements
• Analysis of data element connectivity (internal vs. external communication)

ECU Mapping (only DaVinci System Architect)

• Mapping of functions or components to ECUs
• Definition of mapping constraints to ensure that all sub-functions/sub-components are located on the same ECU

Signal routing (only DaVinci System Architect)

• Definition of signal routing paths within the vehicle topology
• Signal routing across gateway ECUs supported

Export of AUTOSAR XML-files (only DaVinci System Architect)

Export of design data into the AUTOSAR XML-format (AUTOSAR 1.0, DTD revision 12342).

• Export of complete vehicle projects with all sub-objects
• Export of individual objects like data types, port interfaces or component types

User-defined stereotypes (only DaVinci System Architect)

• Stereotypes are configurable by a STEREOTYPE.INI file located in the DaVinci Bin\Config directory
• Stereotypes supported for functions, signals and signal groups

Import/Export of MATLAB/Simulink models (only DaVinci System Architect)

• Import of Simulink models as function hierachy
• Export of individual functions or complete function hierarchies as Simulink model
• Import/Export includes signal groups and stereotype annotation
• An example model "ImportExample.mdl" is available in the "Work"-Directory of the DaVinci installation
• An example workspace "ImportExample.dvw" having imported "ImportExample.mdl" is available in the "Data"-Directory
• Style guide for Simulink import is available in the DaVinci documentation browser

Network design (only DaVinci Network Designer)

• Explicit definition of CAN messages and network signals
• Definition of Tx- and Rx-relations
• Definition of message layout with various display schemes
• Manual or automatic definition of DLC
• Display of gateway tables
• Network timing analysis
• Import/Export of DBC
• Import of MDC files

Task mapping (only DaVinci Developer)

• View modes for displaying the components in a flat list or sorted by trigger types

Object Usage Dialog (only DaVinci System Architect and DaVinci Developer)

• Tracking of usage relations between objects in the workspace
• Two tracking directions:
  • Referencing objects: Upward tracking (which objects use me)
  • Referenced objects: Downward tracking (which objects do I use)

Search Function (only DaVinci System Architect and DaVinci Developer)

• Searching of objects by name
• Search for specific object types

Limitations

• Auto-mapper for network signals not available
• Multi-instantiation only supported for atomic software component types, not for composition types
• All runnable entities of a component are always mapped to the same task

(top)

DaVinci Tool Suite Version 1.0 (SP4)

Support of Microsoft Visual C++ 7.1

• PC-Target generation using CANoe OSEK library is now available for Visual C++ 7.1 compiler, which is part of Microsoft .NET 2003 release. Legacy Visual C++ 6.0 is still supported.

CANdesc Basic Diagnostics for DB-Kom

• Support for CANdesc Basic diagnostics using DBKOMgen Version 2.51
• Extension of initial firmware generation for application callbacks
• Attachment of generated diagnostic files
• Notes concerning the generated template file "AppDesc.c":
  An application diagnostic template file "AppDesc.c" will be generated in the ECU output directory at each code generation. This file has to be initially attached once at the ECU to fulfill the diagnostic functions. It is highly recommended to use an ECU specific name rather than the standard "AppDesc.c". After attachment the file may be modified to code application specific diagnostic functionality.

Event Triggered Execution

• In addition to the cyclic execution of software components, it is now possible to defined events to tigger execution of procedures at the behavior components.
• There may be multiple procedures with multiple trigger conditions defined at each behavior component.
• The DaVinci ECU-Callback object is superseded by the trigger concept and thus no longer available
• Possible triggers are: State changes, Timer, Signals
• The Simulink/TargetLink blocksets are enhanced by a procedure block

Task-Mapping

• Task-Mapping for software components is now defined in the mapping view of the Hardware & Mapping Editor
• See topic "Task mapping of software components" within the DaVinci online help for detailed information

Iterative OSEK Configuration

• Changes in the OSEK configuration made in the OIL-Configurator are now read back and stored into the DaVinci workspace.
• Storage is done for each ECU separately and can be modified through the OIL-Configurator without losing previous modifications
• Additional OIL-Files can be attached at the ECU or software component

TargetLink 2.0

• Implementation of behavior components can now be done with TargetLink 2.0 using MATLAB R13.
• An upgrade mechanism of DaVinci models from TargetLink 1.3 to 2.0 is supported
• A data dictionary is used for each behavior component with additional pool definitions for DaVinci
• The single XML-Files for pool definitions can be found in <DaVinci>\Generation\Behavior\Matlab\R13\TL20\config
• The previous implementation of TargetLink 1.3 using MATLAB R12 is still available.

Fixed issues

• Attached files are now stored with paths relatively to the working folder
• Linker problem with multiple RTW generated Stateflow files at the same ECU
• Under rare circumstances modifications at attached files may be lost if working on the same behavior component with both DaVinci tools in parallel
• Unhandled exception if output dir can't be created during code generation
• Wrong ESM procedure execution during startup of CANoe simulation
• Usage of ESM on ECUs without mapped software component leads in code generation errors

(top)

DaVinci Tool Suite Version 1.0 (SP3)

Parallel working with both DaVinci tools on the same workspace

• Convenient switching between the tools without closing the workspace
• Parallel editing of the objects without mutual blocking of the tools

Enhanced Target Package architecture and selection

• Selection of used Target Package at each ECU and Mapping-System
• Parallel installation of Target Packages in different versions supported

DaVinci Documentation Browser

• New convenience tool to display documents and help files of DaVinci tools and Target Packages

MATLAB/Simulink Import

• Recursive import of a Simulink subsystem as DaVinci software component structure

Internal Perl usage

• External Perl installation no longer required
• DaVinci installs Perl (build from CPAN sources Version 5.8.0) locally into the DaVinci generation directory
• Any other Perl installations may exists on the PC and will not affect DaVinci code generation

DBC file export

• Export of a mapping systems as dbc files

DBC Import

• Support of sub-signals
• Renaming of attached DBC-Files
• Some minor roundup features and fixed issues
  • Enhanced check of DBC import conflicts
  • Check on imported DBC message ID while creating DaVinci messages
  • No more inconsistencies when deleting a DBC-imported signal from a bus interface
  • Correct update of properties on DBC-imported signals
  • Interpretation of some signal attributes corrected: start bit, init value, timeout

Configuration Management

• Permanently disconnecting a workspace from a configuration management repository

Fixed issues

• Generation rebuild fails without warning if output files are locked by another application
• Attachment of large files via network was extremely slow
• Compiler parameter settings are not stored after closing/reopen workspace
• Opening a .dvw file through Windows Explorer doesn't work under some circumstances

(top)

DaVinci Tool Suite Version 1.0 (SP2)

Rework of target package settings

Please check and adapt your settings within the Mapping-Systems

• Communication system type is now specified the Bus and no longer at each ECU
• New generation parameter dialog at the Mapping-System and their ECUs available
• CANoe firmware generation is now specifiable at each ECU within the Mapping-System

New DBkom version 2.48

• Please adapt all workspaces using older DBKom versions at the ECU and Mapping-System

CAN Multi-Channel support

• Support for more than one CAN-Channel at an ECU with DBKom communication system

Software System Sheets

• Graphical grouping of components on several sheets
• Cross reference links to follow signal paths across sheets

MATLAB/Simulink Export

• Export of a Software System as one MATLAB/Simulink model containing all models attached to the used software components

MATLAB/Simulink/TargetLink functional interface

Please re-generate your existent, attached models with the enhanced blockset

• Enhanced signal blockset with additional parameter
• Additional blockset for ECU State Manager and Network Management

XML Import/Export

• Software Component exchanged (incl. attached files) via XML

New CPU-Variants available

• S12DG128
• HC12DG128

Attached files enhancements

• Additional attached files at the ECU within the Mapping-System
• Support for binary file types (OBJ, LIB)
• Additional file categories to specify file action within the generation make process

Fixed issues

• Objects names within the Mapping-System are not checked correctly on uniqueness
• Online help couldn't be started through adapter dialogs
• Messages without bus signals are deleted during Mapping-System update
• Missing explorer update after importing or selecting bus signals through a bus interface
• Crash in subseqently renaming of component procedures
• Missing connections when calling 'Complete Device Accessors' function
• Wrong model name in initial TargetLink model generation

(top)

DaVinci Tool Suite Version 1.0 (SP1)

Fixed issues

• After installation on a clean PC, an immediate Simulink generation will fail due to missing path settings
• Some ECU specific parameters of the communication system can't be saved
• Wrong Signal-Prefix (dvFwSim instead of dvFw) in template generation of Initial I/O Firmware for real ECUs
• Missing update in Hardware-System explorer after creating new ECUs or Buses
• Missing bus signals in Mapping-System after ECU exchange
• Renaming of configurations may corrupt workspace and configuration management interaction
• Component interface can't be removed in interface view under some circumstances
• The same Signal in different versions can be used within one component. This is inconsistent and must not be allowed.
• General error during code generation if the Mapping-System is read-only (i.e. checked in)
• Renaming of generic attributes is not possible
• Copy & Paste of diagnostic settings for an ECU is missing
• ECUs without bus-signals won't be generated correctly
• Missing check on unique sensor/actuator names
• Wrong Network Management ID generation in DBC file

(top)

DaVinci Tool Suite Version 1.0

Extra installation of ActivePerl required

It is required to install ActivePerl Version 5.6.1 build 631 or higher in a separate step. ActivePerl may be downloaded from ActiveState at http://www.activestate.com/Products/ActivePerl/

Workspace conversion

A conversion of older workspaces with DTD 1.x to DTD 2.0 has to be performed for loading with DaVinci 1.0. There are two possibilities to perform this step:

• Implicitly: Loading a workspace will automatically display a dialog for conversion.
  Please read the notes in this dialog carefully
• Explicitly: Use the DVCvt.exe console application to convert a workspace with parameter -d2.0
  The parameter -f is always active for conversions to DTD 2.0, i.e. the workspace will always be saved in the new version

New Interaction Layer Versions

Please adapt all workspaces using older target settings at the ECU and Mapping-System:

• DBKom 2.46
• GM-LAN 3.99
• Vector-IL 3.99

Configuration Management

• Integration of Microsoft Visual SourceSafe

Diagnostic Support

• Integration of CANdela and CANdesc for GM-LAN
• Automatic creation of diagnostic stubs

ECU State Manager

• Design of ECU State Machines
• Definition of procedures with conditional execution

MATLAB/Simulink import

• Import of a Simulink subsystem as DaVinci software component

Support of ECUs with predefined communication (DBC-Import)

• Import of messages and signal mapping when using the auto-mapper for bus signals

Support for PowerPC Target

• Target Package for MPC555 with DBKom 2.46 available

Signal states

• Specification of signal error conditions at design time
• Extensions of DaVinci Target API for accessing the signal state

(top)

DaVinci Tool Suite Version 0.9.8

Changes in the Target API

• Please replace the following function calls in the behavior code of the C-coded components:
  
  • "dvSetSignalRequest()" by "dvRequestSignal(DV_SIGREG_ALL)"
  • "dvClearSignalRequest()" by "dvReleaseSignal(DV_SIGREG_ALL)"
  • "dvSignalsAvailable()" by individual calls of "dvGetState<SignalName>()"
• Interface to CAN-Transceiver handling changed for systems using CCL (e.g. GM-LAN)
  see CodeGenerationManual.pdf and exemplary attached file HC12_Transceiver.c at the ECUs

SoftwareSystem Table Editor

• Tabular viewing and editing of SoftwareSystems without graphic

Display of realization type in component graphic

• Components will now have a visual distinction if they are included, structure or behavior components

Target Selection of attached files

• Firmware and component files get a new attribute to specify, if they are used in PC- and/or Real-Target

Support for Logical Networks (LN)

• Support for Logical Networks (LN)
  
  • LN Definition in Software-System
  • Integration with GM-LAN 3.97.00 Virtual Networks
  • Import of SAAB 3FD Models into DaVinci with LN

Performance Enhancements

• Opening Component Mapping

Fixed issues

• Unmapped signals won't be displayed within Mapping-System check
• Wrong display of open signal paths
• No Mapping-System check after assigning a signal to a sensor
• No status information text output for a missing Software- or Hardware-System

(top)

DaVinci Tool Suite Version 0.9.7 (SP1)

Fixed issues

• Linker error with multiple Simulink R13 models in one ECU
• Check-State of mapping system not displayed correctly
• Assertion, when activating a Mapping-System with attached DBC-File

(top)

DaVinci Tool Suite Version 0.9.7

GM-LAN Integration

• Support of GM-LAN for Canoe and HC12 Target without Virtual Networks

Workspace DTD Converter Tool (DVCvt.exe)

• Conversion of workspaces to a newer data model version

Sorting of Trees

• All Explorer Trees (Global, Favorites, Categories) are now sorted

Name length limitation of 32 characters

• All object names are now limited to a length of 32 characters to ensure proper usage in code generation and DBC-Files

Workspace Path checking

• Workspace naming and path length will now be checked to ensure a maximum path length of 260 characters

Performance Enhancements

• Loading Signals and Components
• Editing Signal Types

Fixed issues

• Disconnecting an ECU from a Bus causes an error
• In some situations, renaming of objects was impossible
• "New Workspace" command doesn't work in Hardware&Mapping Editor
• Creating a new object category with an existing name will crash

(top)

DaVinci Tool Suite Version 0.9.6 (SP1)

Support for MATLAB R13

• Adaptation of code generation for MATLAB R13 using RTW-GRT

(top)

DaVinci Tool Suite Version 0.9.6

Support of Large Systems

• Rework of object loading and tree display
• Enhancements in graphic display
• Smart update mechanisms in tools (Trees, Object-Viewer and Graphic)
• Rework of Mapping-System data update mechanisms

Object Categories

• User defined grouping of objects with categories
• Favorite Lists

Enhanced checking of attached files

• Hints on closing, saving and generating if attached files are not up-to-date

XML Import Tool (DVImEx.exe)

• Import of SAAB 3FD Models into DaVinci

Usability

• Stop-Button for Code Generation added
• Generate-All command added
• Save-Button won't be grayed if workspace is not modified

Perl Installation Check

• New script DVPerlCheck.pl to retrieve information about current Perl installation

Fixed issues

• Missing update on DBC-Signal import
• Mapping system consistency: Sensor signal specified as actuator is not detected as error
• Overlapping display of interface names
• Property windows of a message causes a crash
• Multiple Tx-nodes of Tx-messages crashes in DB-Kom
• Deleting a SWS corrupts the Mapping-System

(top)

Additional Information

Vector Informatik GmbH – Support

Our business hours are Monday to Friday from 9:00 am to 5:00 pm (CET)

Phone: +49.711.80670.200
Fax: +49.711.80670.111
E-Mail: support@vector.com
Online Report Form: http://vector.com/support

(top)