Enthält das vollständige Setup von DaVinci Developer 3.11.30 (SP2). Zum Betrieb ist eine Lizenz der Version 3.11 oder höher notwendig. Falls Sie die Lizenz auf Ihrem PC bereits aktiviert haben, ist keine erneute Aktivierung der Lizenz notwendig. Diese Version ist nur für AUTOSAR 4 relevant. AUTOSAR 3 wird vom DaVinci Developer Version 3.7 oder früheren Versionen unterstützt.
With Service Pack 2 (Update to 3.11 Build 30), the following changes become effective:
This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.
Find function for objects with duplicate UUIDs has been added
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
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