DaVinci Developer 4.1.32 SP2

Categoria : Service Pack
Tamanho : 229.03 MB
MD5 hash : 72994f60f2da8f753943139af3cf7df2

Contains the complete installation of DaVinci Developer 4.1.32 (SP2). For the operation a license of version 4.1 or higher is necessary. In case an according license is already activated on your PC no further renewal of this activation is necessary. This release is only relevant for AUTOSAR 4. AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.


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

This release will upgrade existing DaVinci DEV 3.x workspaces to a newer format. For creating/updating projects with DaVinci Configurator, the latest Service-Pack of the according DaVinci Configurator 5 version is required.
DaVinci Developer 4.1 is only available as a 64-bit executable, i.e. Windows 32-bit is no longer supported.

Tool features

  • Variant clusters with different cluster-names are now supported

Usability enhancements

  • Missing referenced files are now reported with full path and referencing .dcf in the Action Log and a popup

Fixed issues

  • Create port from SignalGroup hadn't considered the variant assignment of PostBuild-Selectable projects
  • The consistency check result of deleted objects was still visible in the messages tab
  • ComplexDeviceDriver and EcuAbstraction Component Types were occidentally moved to the service layer on ARXML import
  • DataTransformation wasn't overwritten correctly on ARXML import
  • Incorrect command routing for the Copy&Paste(Ctrl+C) in the "Properties" window caused another active view to act as source
  • Internal record references where not correctly updated if the referenced record data type was changed from implementation to application data type
  • Error message "Object reference not set to an instance of an object. (code 0x80004003)" was shown if a new compu scale was created in the dialog
  • DVImEx command line import throws wrong error message when trying to import files into a DaVinci DEV 3.x workspace
  • ComponentPrototypes appeared unexpectedly in the Library Browser's Package view if a new ComponentPrototype was created
  • Axis couldn't be created in the characteristic table properties dialog because the "New" button's context menu entries were disabled
  • ARXML import failed with message "An item with the same key has already been added. (code 0x80070057)" when trying to update read-only elements with e.g. new structure and service-flag
  • "Unhandled InvalidOperationException" or "FormatException" occurs when a file priority wasn't numeric
  • Confusing message appeared when trying to open a dcf workspace without DPA file reference from the Windows Explorer
  • BaseType fixed size wasn't stored correctly if the size attribute differed from the default
  • Invalid open limits with value 0 were created when importing the compu-method the second time (update)
  • Obsolete DataMappings weren't cleaned up correctly
  • Invalid Admin-Data was written if a new SpecialDataGroup was created without specifying a value
  • Sometimes the tool crashed when trying to edit pre-mappings in the auto-data mapping dialog
  • Child items of unlocked parent items were not editable
  • When using the tree filter in the Object Browser a 'select All' selected also elements that are not visible
  • Names of deleted items couldn't be re-used
  • CreatePortFromSignal didn't add the correct native declarations for boolean data types
  • ScalingRanges were duplicated on ARXML import if the same CompuScales are defined in multiple files
  • Consistency Error 40321: "Invalid limit specification on a compu-scale" was reported if an INF upper limit was defined
  • Consistency Error 20001 "Unresolved link(s) of type port prototype detected in context of data mapping" was reported if obsolete data mappings existed
  • Invalid component links of End-to-End protections couldn't be reset
  • RoleBaseDataAssignment's Role property was incorrectly handled in the ARXML file
  • Import option "default package" didn't work
  • Loading ARXML and DCF with identical priority incorrectly overwrote elements
  • Init-Value of PR-ComSpecs were not stored correctly
  • Consistency check 40333 "Check delegation connector communication specifications" couldn't be disabled anymore
  • End-to-End Connection check didn't handle variant data mappings correctly
  • Platform functions filter didn't work in search functionality
  • Loading a workspace with communication elements aborted with error message "Object reference not set to an instance of an object" if a reference existed but didn't contain an actual reference path
  • ServiceNeeds couldn't be copied with the context menu functions
  • Consistency Error 40065 "Invalid object name" was reported for port defined argument values without short-labels
  • Complex constants were not updated correctly if the type of nested value-specifications changed
  • CompuScale limits changed unintentionally when opening the Compu-Method dialog
  • ObjectBrowser wasn't updated when a new TriggerInterface was created
  • When creating an implementation data type of category record, the attribute "dynamic array size profile" wasn't persisted
  • Connection select dialog showed Strict and Extended compatibility options which were no longer used
  • ARXML project update didn't handle the empty Components with keep
  • CreatePortFromSignal didn't handle dynamicSize signals correctly
  • DataType and constant references were not written correctly for characteristic tables or com axis
  • Wrong DEST attribute was written for SW-COMPONENT-PROTOTYPE type references
  • DaVinci Configurator reported error RTE51017 "Missing port interface reference for P-Port prototype" if the input file contained elements which are already included in the DaVinci Developer workspace as external elements
  • Wrong bit position of the activation reason was saved when editing activation reasons
  • It wasn't possible to define PR-Ports as Client/Server or Calibration
  • Port-Interface-Mappings couldn't be distinguished when using different package paths
  • The type reference wasn't set correctly when creating a new complex data type
  • Port-Group list wasn't updated when renaming a port-group
  • It wasn't possible to create a new data type from the NV block descriptor page
  • Init values couldn't be set with multi select
  • ServiceNeed consistency check didn't consider the parameter active status
  • The zoom factor control wasn't updated if the graphic zoom was changed using the mouse wheel


Transferir agora página anterior