DaVinci Developer 4.3.29 SP2

Enthält das vollständige Setup von DaVinci Developer 4.3.24 (SP1). Zum Betrieb ist eine Lizenz der Version 4.x 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.


Mit dieser Version werden bestehende DaVinci DEV 3.x Workspaces auf ein neueres Format aktualisiert.
Für die Erstellung/Aktualisierung von Projekten mit DaVinci Configurator wird das neueste Service Pack der entsprechenden DaVinci Configurator 5 Version benötigt.

Mit Service Pack 2 (Update auf 4.3.29 SP2) werden die folgenden Änderungen wirksam:

Usability Enhancements

  • The performance of solving many differences in comparison mode has been significantly improved
  • Ambiguous mode declaration group mappings of several TypeMappingSets can now be distinguished in consistency check messages and the mapping dialog

Fixed Issues

  • Ports and related elements were not imported if a component type referenced at least one constant mapping set
  • Existing External-Trigger-Occurred events were accidentally renamed if updated during an ARXML import
  • Unhandled exception occurred after multi-editing of Mode P-Port attribute 'MdSwAckTimeout'
  • Nv block descriptor properties changed unintentionally when editing another Nv block descriptor
  • Exception was thrown when trying to open a .dpa file with many DaVinci CFG5 consistency messages set to 'accepted' which resulted in a large 'accepted' string in the .dpa file
  • Deleted NVM Block Need couldn't be re-created with the same name
  • Delegation port wasn't displayed in the graphic view when connected by a connector with invalid references
  • Obsolete port connectors were reported when the ECU-Composition was read-only and contained further invalid elements, e.g. data mappings
  • Check message #40265 wasn't displayed in the messages view if the ECU-Composition contained E2E-Connections without a valid port prototype reference
  • Importing an already loaded arxml file appended _1, _2, _3, ... postfixes to short names
  • Deleting an NvBlock service need left obsolete tags in the arxml file
  • Processing differences in comparison mode failed when comparing variant workspaces
  • Mode disablings were not deleted when deleting a port prototype
  • Importing an Axis data type created two calibration axis elements instead of one
  • Unspecified error (code 0x80004005) occurred when deleting a calibration port using the SWC editor list
  • CompuScale of type TextTable accidentally contained CompuRationalCoeffs in the saved ARXML file
  • Admin Data Template Editor: Modifications were not recognized and couldn't be saved when deleting the last template
  • Admin Data Template Editor: Exception occurred when applying a new template before closing the dialog
  • Element creation was indeterministic when CreatePortPrototype was called on a Signal-Group
  • External trigger data mapping wasn't imported correctly
  • Duplicated data mappings were not reported in the workspace consistency check
  • Not all duplicate file references in the .dcf file were reported during the consistency check
  • Checking a workspace automatically after ARXML import was much slower than checking the workspace afterwards with a separate call
  • The File Browser showed files as being part of a referenced .dcf workspace although the files were part of the referencing workspace
  • When adapting the structure of a constant to a record data type cyclic references within the data type structure caused a stack overflow crash
  • ImportMode-Preset wasn't correctly set when duplicating imported elements, e.g. when using the 'Complete Port' function
  • Attributes of NvDataElementComSpec and SRComSpec were missing in the multi-edit dialog
  • Internal references unexpectedly pointed to the modified element if element was copied or moved into another package and renamed to the original element
Bitte beachten:
Dieses Software-Paket enthält eine ältere Version von WIBU CodeMeter, die eine kritische Sicherheitslücke enthält.
Bitte stellen Sie sicher, dass Sie den neuesten Vector License Client installiert haben, der diese Schwachstelle behebt. Weitere Details finden Sie im Vector Security Advisory.

Größe : 240.56 MB
MD5-Hash : 5a9e972594cfc1748abfb9262fbd044c
Jetzt herunterladen Zurück