DaVinci Developer 4.1.23 SP1

Categoria : Service Pack
Tamanho : 228.74 MB
MD5 hash : 51eefd34d3cb4e333049744ebc9f600c

Contains the complete installation of DaVinci Developer 4.1.23 (SP1). 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 PNC mappings are now supported in ECU-Project import/export
  • Modelling of SWC external triggers with TriggerInterfaces, ExternalTriggerOccurredEvents, and TriggerConnections is now possible
  • Definition of SwIntendedResolution has been added to the application data-types
  • Connections between PR-Ports are now allowed at Service-Components
  • Connections between NV-ports of non-NV component types are now allowed

Usability enhancements

  • In addition to the reference tree view the legacy Object Usage dialog can now be opened as well
  • Additional consistency check to detect an unsupported sub-element mapping between record-elements and primitive data-types
  • Propagate AliveTimeout now also works for SignalGroups
  • If the workspace path exceeds the maximum Windows path length a dedicated error message is now shown instead of simply throwing a generic 'Workspace is not open' error
  • Analogue to the import dialog the command line importer now accepts a file list containing the ARXML files to be imported

Fixed issues

  • Unresolved References from Service Components were shown which should not be reported
  • The export option 'Export AUTOSAR package' wasn't available in the export dialog any more
  • Graphic sheets got the default name even if they were renamed
  • The default package for the SwAddrMethod wasn't persisted and may blocked the application functions
  • Exception was thrown when creating a copy of a root package in a child package
  • Runnable external trigger events and accesses were not removed if any of their referenced elements were deleted
  • Constants were not correctly imported if an Application Value Specification of category "Boolean" and a Compu Method was defined
  • Copy/Paste unintentionally moved the original item to another package
  • The tool crashed when working in the graphic for a longer time and moving a scrollbar
  • In some cases, the save button remained active after saving the workspace
  • Exception was thrown when trying to open the import dialog and a previously imported file has been deleted
  • Tool crashed when trying to create "On Transition" triggers
  • Report generation failed error 'invalid pointer (code 0x80004003)' if a data constraint wasn't referenced
  • The "Find Unused Objects" dialog falsely showed referenced objects if the referencing object hadn't been accessed before
  • Nv block data mappings were lost when leaving the editor unsaved
  • PortGroup port-prototype references were not deleted when the port was deleted
  • In rare cases saving a workspace failed with an exception and message 'hexadecimal value 0x00, is an invalid character'
  • Nv-Data Mapping wasn't imported correctly if it's expressed by one mapping element for both directions
  • 'Internal exception occurred: Object reference not set to an instance of an object' was shown if a referenced port interface was missing
  • 'Internal exception occurred: Unable to cast object' was shown during template generation if the workspace contained data mappings or an E2E protection configuration
  • DataTypeMapping dialog froze if no TypeMappingSet was set as default
  • Invalid Admin Data content was written into ARXML file if the Admin Data was edited and no DocRevision existed yet.
  • Variant Data Mapping couldn't be created for trigger interfaces
  • When using drag&drop, objects with same names could appear in a package
  • Copy/Paste of internal behavior objects threw an exception in the component type editor
  • Some tree updates were missing in the package view
  • Proprietary internal attributes were visible and editable in Admin Data GUI
  • FirstToSecondDataTransformation of DataPrototypeMapping wasn't persistent
  • End-To-End protections were not visible after loading a workspace if they were modeled with I-SIGNAL-I-PDUs or DEP-REFs.
  • Interrunnable Variable Access couldn't be changed on ARXML import
  • Generated Contract Phase data type file didn't include all data types
  • Comparison mode couldn't be started if End-To-End protections existed
  • Consistency Check #40195 'Component type with differing mode switch acknowledgement modes' was thrown and couldn't be resolved
  • SwAddrMethods were always exported to the default package "SwAddrMethods"
  • The file 'ProfileSettings.xml' didn't exist after workspace creation
  • The FileBrowser displayed many records for the same file
  • Trying to close the application had no response on the first time
  • Runnable Data Access was removed if the Variable Data Prototype referenced by the Data Access was renamed in the imported ARXML file
  • ARXML import didn't work properly in case of file browser modifications
  • DataPrototype-Mapping for Trigger-PortInterfaces were not saved
  • ECU communication wasn't updated correctly if the SYSTEM's short name paths in the old and new ECU-Extract were different.
  • Duplicate implementation names were reported after importing an ARXML SWC file
  • Consistency check #40250 'Unconnected port prototype' wasn't reported for trigger ports
  • Additionally merged issues from service packs of previous releases:

    • ARXML import with 'Substitute missing objects' didn't support CDD and EcuAbstraction
    • PortInterfaceMappingSets could falsely be deleted even if their Mapping was referenced by a connection
    • Reference to a PortInterfaceMappingSet couldn't be removed at the connection
    • 'Invalid Argument..' exception was thrown when using a port interface mapping on a delegation connector at a composition
    • The last single element couldn't be deleted in the Find Unused objects dialog
    • The ARXML files of consecutive exports differed, i.e. the XML element order was different.
    • Obsolete AUTOSAR3 port interface Constraints/Limits were displayed at the port prototype
    • ARXML merge aborted with 'Item with name is read-only. (code 0xC0500022)' if the imported ARXML and the workspace contained an identical element which was loaded from a read-only file
    • 'Create Port from Signal' now ignores invalid CompuMethods to avoid wrong data-type creation
    • ARXML import crashed when using an ECU extract with unresolved Component-Prototype references
    • ARXML import didn't change the realization of an existing Complex Device Driver if the imported component type was of a different type
    • CreatePortPrototype didn't create a valid record constant for the init value
    • ARXML import didn't import an WINDOWS-1512 encoding correctly
    • Project update failed with several errors if the project contained more than one Data-Transformation-Set and any Data-Transformation of the first Data-Transformation was referenced
    • ARXML export falsely wrote the DynamicArraySizeProfile 'None' into the ARXML file
    • Consistency check #40246 was reported on compatible port-connections if the same init value was defined as numeric and as constant
    • Consistency check threw an 'Invalid pointer' error if an application data types of category Map, Curve, Cuboid used SwAxisGroup to reference an Axis but the actual SharedAxisType reference was missing
    • In some cases, constants were reported as incompatible even though they should be compatible
    • Variant annotation of a new data mapping that was based on signal variance wasn't correct


Transferir agora página anterior