(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-NKB5KB'); DaVinci Developer 3.10.40 SP4 | Vector

DaVinci Developer 3.10.40 SP4

Contains the complete installation of DaVinci Developer 3.10.40 (SP4). For the operation a license of version 3.10 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.

With Service Pack 4 (Update to 3.10 Build 40) the following changes become effective:

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


Categoria : Service Pack
Tamanho : 175.03 MB
MD5 hash : 1f309b9c41912e87be8eb061f4eb1111
Transferir agora página anterior