DaVinci Developer 3.13.50 SP5

Categoria : Service Pack
Dimensioni : 169.47 MB
Hash MD5 : c01c258ec7582a20334760f2c1f8cd99

Contains the complete installation of DaVinci Developer 3.13.50 (SP5). For the operation a license of version 3.13 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.

Tool features

  • 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

  • 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

  • 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


Scarica ora pagina precedente