DaVinci Developer
AUTOSARソフトウェアコンポーネントの設計

DaVinci Developerの概要

DaVinci DeveloperはAUTOSAR ECUのソフトウェアコンポーネント(SWC)アーキテクチャーを設計するためのツールです。

 

特長

  • ユーザーフレンドリーな操作で簡単にAUTOSAR SWCを設計
  • グラフィカルな編集機能を多数装備
  • SWCのAUTOSAR適合性をチェック
  • モデルベース開発ツールとARXML経由でリンク
  • AUTOSAR 3.xおよび4.xに対応

適用分野

SWCアーキテクチャーを設計

  • さまざまなレイアウト補助機能も備えた、ソフトウェアコンポーネントのグラフィカルな定義
  • ポートインターフェイスとデータタイプの定義
  • サービスニーズや、初期値、タイムアウトなどの通信仕様を含む、各種ポートプロトタイプの定義
  • コンポジションの作成
  • 手動および自動によるSWCのリンク
さらに表示
  • ランナブルエンティティー(runnable entity)と、そのアクティベーションイベントやポートアクセスの定義
  • 排他エリアの記述
  • インターランナブル変数、Per-Instanceメモリー、およびキャリブレーションパラメーターの定義
  • NVメモリーへのアクセスなどを想定したサービスニーズの定義
  • SWCの手動および自動接続
さらに表示
  • SWCポートとネットワークシグナルの間のデータマッピングを表示
  • シグナルおよびポート指向の表示
  • データマッピングの手動作成
  • 名前に基づくデータマッピングの自動作成
  • ネットワークシグナルに適合するポートプロトタイプの生成
  • データトランスフォーマーをサポートし、エンドツーエンド保護とSOME/IPに対応
さらに表示
  • 包括的なSWCの整合性チェック
  • SWCテンプレートとRTEに対し、AUTOSAR仕様への整合性規則を考慮
さらに表示

ユースケースにおける必要となるDaVinci製品の概略

スタンダードユーザーグループ

 

 

エクスパートユーザーグループ

さらに表示

バージョン4.2の新機能

新しいアシスタント機能によりNV Block SWCの設定が省力化

  • NvBlock SWCのポートにマッチするNvBlockDescriptorの作成
  • データ型を継承し、NvBlockDataMappingを自動的に作成
  • 標準的な診断ユースケースに最適(DcmによるNVメモリー内の診断データ識別子へのアクセスなど)

AUTOSARリリース4.3.1のサポート

  • AUTOSAR 4.3.1スキーマと整合するARXMLファイルの作成

機能

  • 自動車メーカーからの入力データの変更後、専用のインポート機能でSWCアーキテクチャーを更新
さらに表示
  • SWC間のコネクターを自動生成
  • SWCとネットワークシグナルの間のデータマッピングを自動生成
  • 自動車メーカーでの一般的な命名規則を踏まえた、名前に基づく検索アルゴリズム
さらに表示
  • SWCアーキテクチャーの解析により、ECU内でのデータ交換の詳細を表示
  • 個々の通信関係をデータ要素やネットワークシグナルのレベルで詳しく解析表示
さらに表示
  • 共有ARXMLファイルをDCFライブラリーに移動可能
  • 書込み保護されたDCFライブラリーを読み込むメカニズムを装備

DaVinci DeveloperはMathWorksパートナープログラムの一部です。

 

 

 

 

 

 

さらに表示

オプション

オプションCPG: RTEコントラクトフェーズの生成

  • C言語ベースのアプリケーションに対応したヘッダーファイルと実装テンプレートファイルを、素早く簡単に生成
  • SWC Descriptionの変更後、SWC実装を更新
  • 注: オプションCPGを使用することにより、MICROSAR RTEジェネレーターを別途使用せずにコントラクトフェーズ生成を実行可能

関連情報

ファクトシート:

 

 

さらに表示
要素 推奨 最小要件
CPU Quad-Core Dual-Core
メモリー (RAM) 16 GB 2 GB
画像解像度 1280 × 1024 1024 × 768
オペレーティングシステム Windows 7, 8.1, 10 (64Bit) Windows 7 (32または64Bit)
ディスク
SSD HDD
さらに表示

ベクターのKnowlegdeBaseでは、グローバルのお客様FAQを掲載しています。
 

 

さらに表示

ダウンロード

ニュース/イベント

さらに表示
さらに表示

トレーニング

ベクター・ジャパンでは、ベクターのソフトウェアツール、ソフトウェアコンポーネント、最新のバステクノロジーやプロトコルに関する日本語のトレーニングを多数開催しております。トレーニングの概要につきましては、トレーニングポータルにてご紹介しておりますので、是非ご覧ください。

バージョン履歴

Released: 2017-04-06

 

NOTE

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

Due to an architectural enhancement in the ARXML processing the performance and memory usage differs from the previous Service-Pack.

Depending on the use-case and data structures this can also result in a slower loading and saving performance or an increased memory usage, this will be optimized again with upcoming versions


Tool features

  • AUTOSAR 4.3.0 is now supported.
  • Calibration element prototype mappings are now supported
  • SwcToECUMapping is now exported as part of the SystemElement
  • Category Tag for ApplicationValueSpecifications is now exported
  • Top-down definition of DTCStatusChangedNotification service need is now supported
  • The parameter 'TransformationErrorHandling' is now supported in the Port-API options of Port-Prototypes

Usability enhancements

  • 'Graphic settings' are now accessible via the context menu
  • To reduce the memory consumption of signals not actually received/sent by the ECU Instance are now ignored during ARXML import
  • The specific Transformer Type is now displayed in the data mapping view and signal selection dialog
  • CompuMethod consistency check has been improved to check for unique identifiers and multiple identical ranges
  • Compatibility check for constants has been extended for to show more detailed information
  • Additional check was implemented to ensure that an axis, that is referenced by a characteristic table (CT), is used elsewhere within the corresponding software component
  • When changing the CompuMethod Category in the GUI to a non-TextTable the tool now queries if the defined enumerators should be removed

Fixed issues

  • Depending on the FlexNet environment the application may hanged-up at startup during license query
  • Create Port Prototypes created a Base-Type with invalid Native Declaration 'int16' instead of 'sint16'
  • End-to-End Transformer settings at receiver ComSpec were not editable when using in modal properties dialog
  • 'Generate Contract Phase / Component Implementation Templates' aborted if there are model consistency warnings
  • Existing wait-points were not removed when changing the port access to none
  • When creating an implementation data type of category array, the attribute 'size handling' was not persisted
  • Compu-Scales were not correctly updated if they didn't specify symbol, label or constant
  • Import of Variant Clusters is now rejected with a specific error message since this is not supported
  • Consistency message #40405 'CompuScale without label' was falsely shown if the Compu-Scale defined a symbol and/or constant but not a label
  • NvM Port Assignment disappeared from the list after renaming but it still existed
  • Create Port from Signal didn't consider CompuMethod to create arrays and records
  • Assignment of a NvMBlockNeed to a PIM didn't remove existing assignments when using the PIM-page
  • When the NvBlockNeed-Page was opened within a standalone dialog, the action bitmap-buttons didn't appear
  • Exporting a NVMBlockNeed had duplicated the port assignment
  • Changing the service need attribute 'Cycling writing period' is only saved if another attribute had been changed too
  • Wrong service need type had been created for DcmDiagIOControlNeed, DcmDiagSecurityNeed, DltUserNeed
  • Multiply used RecordLayout-Annotations were not detected by the consistency check
  • Existing service needs were falsely reset to default during ARXML import of a Nv software component
  • Since AUTOSAR version 4.2.2 double underscores can be used in Short-Names but DaVinci DEV didn't accepted this in GUI and ARXML import/export

 

さらに表示

Released: 2016-11-29

 

NOTE

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

Tool features

  • Preparation for upcoming AUTOSAR 4.3.0 schema version files. Currently no new features are supported.
  • Support for 64 bit COM signals according to AUTOSAR 4.2.2 has been added

Usability enhancements

  • Additional consistency check has been implemented to ensure that different ranges of a Compu-Method don't overlap
  • Additionally merged usability enhancements from service packs of previous releases:

    • Create port with data-type from signal now suppresses transformed signals
    • Delete of End-to-End connections with multi-select is now supported
    • ArrayElement-ReferenceName is now configurable

Fixed issues

  • Data type mapping check didn't support integer data types which require more than 32 bit
  • DaVinci CFG5 threw "unsupported merge/communication scenario" error message if data mapping was done in CFG5 at atomic ports and the same signal was mapped to the same port for different variants
  • Consistency check for application data types that references compu methods of type "BitfieldTextTable" was wrong
  • Bitfield dialog showed "out of range" on correctly defined bitfield values
  • Rte code generation failed with error 40170 "Multiple mappings for network signal" if the same data mapping was done in DaVinci CFG5 at atomic ports of different component prototypes
  • References to record elements stored in external files were not resolved when loading a workspace
  • Compu method could be deleted but was used within the ISignal network representation
  • Project update aborted if an E2E protection with same name is defined in different E2E protection sets and the E2E protection specifies an E2E ISignal IPDU
  • Additionally merged issues from service packs of previous releases:
    • Consistency check 40454 didn't consider array element mapping according to AUTOSAR Constr_1004
    • Delegation ports with several data mappings for different variants weren't supported
    • Communication and data mapping was lost after import of an ECU-Extract having several clusters with the same name
    • "Adapt structure of record type" function created non-matching init value for nested complex data-types
    • AR3 to AR4 workspace conversion showed the error message 40338 inconsistent data type mappings when using real data-types
    • Loading a workspace with external DCF references failed with message "Item with name is read-only" if the loaded DCF referenced another DCF with custom generic attributes
    • Existing Type-Reference couldn't be selected as Inter-Runnable-Variable data-type
    • ARXML export duplicated the data mapping if the signal was mapped and the signal was part of a signal group
    • Constant reference wasn't imported correctly for calibration parameters with 'per instance' scope
    • Create port from signal group didn't consider the variant assignment
    • The separate variant assignment for group signal mappings wasn't deactivated if the signal group is already mapped

さらに表示

Released 2016-09-26

 

NOTE

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

Tool features

  • Various Diff/Merge extensions to support sub-elements e.g. internal behavior
  • Software Component Prototypes are now allowed to have the same name in different compositions
  • Variant I-Signal groups with the same triggering and System-Signal group are now supported

Usability enhancements

  • DaVinciDEV.exe command line parameters can now be displayed using /help switch
  • Additionally merged usability enhancements from service packs of previous releases:

    • Tool version check is now skipped for workspaces without having a ECU-Project
    • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
    • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

  • The "Uses Tx Acknowledge" check box value couldn't be changed
  • Additionally merged issues from service packs of previous releases:

    • Signal's init/invalid value was always "" in the properties dialog
    • Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
    • Data-Mapping couldn't handle mapped ports without port-interfaces
    • Connections were deleted during ARXML import even if the import mode preset should avoid that
    • The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
    • Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
    • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
    • Create port from signal didn't create correct init values in all cases
    • Init value constant contained duplicate record elements after merge
    • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)

さらに表示

Release: 2016-11-07

 

NOTE

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

With Service Pack 3 (Update to 3.12 Build 30), the following changes become effective:

Tool features

  • Various Diff/Merge extensions to support sub-elements e.g. internal behavior
  • Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

  • Create port with data-type from signal now suppresses transformed signals
  • Delete of End-to-End connections with multi-select is now supported
  • ArrayElement-ReferenceName is now configurable
  • Additionally merged usability enhancements from service packs of previous releases:

    • Tool version check is now skipped for workspaces without having a ECU-Project
    • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
    • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

  • Consistency check 40454 didn't consider array element mapping according to AUTOSAR Constr_1004
  • Delegation ports with several data mappings for different variants weren't supported
  • Communication and data mapping was lost after import of an ECU-Extract having several clusters with the same name
  • "Adapt structure of record type" function created non-matching init value for nested complex data-types
  • AR3 to AR4 workspace conversion showed the error message 40338 inconsistent data type mappings when using real data-types
  • Loading a workspace with external DCF references failed with message "Item with name is read-only" if the loaded DCF referenced another DCF with custom generic attributes
  • Existing Type-Reference couldn't be selected as Inter-Runnable-Variable data-type
  • ARXML export duplicated the data mapping if the signal was mapped and the signal was part of a signal group
  • Constant reference wasn't imported correctly for calibration parameters with 'per instance' scope
  • Create port from signal group didn't consider the variant assignment
  • The separate variant assignment for group signal mappings wasn't deactivated if the signal group is already mapped
  • Additionally merged issues from service packs of previous releases:

    • Signal's init/invalid value was always "" in the properties dialog
    • Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
    • Data-Mapping couldn't handle mapped ports without port-interfaces
    • Connections were deleted during ARXML import even if the import mode preset should avoid that
    • The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
    • Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
    • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
    • Contract phase generation couldn't be used at the ECU-Project
    • Crash during SWC check on runnable data accesses by value has been fixed
    • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
    • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
    • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
    • Create port from signal didn't create correct init values in all cases
    • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
    • A component type DCF file accidently contained data constr elements
    • Init value constant contained duplicate record elements after merge
    • GUI crashed when calling "Show in other views" on a found object
    • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
    • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
    • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
    • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

さらに表示

NOTE

 

This release is only relevant for AUTOSAR 4.

AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

  • Various Diff/Merge extensions to support sub-elements e.g. internal behavior
  • Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

  • Tool version check is now skipped for workspaces without having a ECU-Project
  • Additionally merged usability enhancements from service packs of previous releases:

    • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
    • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

  • Signal's init/invalid value was always "" in the properties dialog
  • Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
  • Data-Mapping couldn't handle mapped ports without port-interfaces
  • Connections were deleted during ARXML import even if the import mode preset should avoid that
  • The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
  • Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
  • Additionally merged issues from service packs of previous releases:

    • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
    • Contract phase generation couldn't be used at the ECU-Project
    • Crash during SWC check on runnable data accesses by value has been fixed
    • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
    • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
    • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
    • Create port from signal didn't create correct init values in all cases
    • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
    • A component type DCF file accidently contained data constr elements
    • Init value constant contained duplicate record elements after merge
    • GUI crashed when calling "Show in other views" on a found object
    • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
    • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
    • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
    • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

さらに表示

Released: 2016-08-09

 

NOTE

This release is only relevant for AUTOSAR 4.

AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

With Service Pack 5 (Update to 3.10 Build 50) the following changes become effective:

Tool features

  • Additionally merged tool features from service packs of previous releases:

    • Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

  • Additionally merged usability enhancements from service packs of previous releases:

    • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
    • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

  • Additionally merged issues from service packs of previous releases:

    • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
    • Contract phase generation couldn't be used at the ECU-Project
    • Crash during SWC check on runnable data accesses by value has been fixed
    • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
    • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
    • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
    • Create port from signal didn't create correct init values in all cases
    • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
    • A component type DCF file accidently contained data constr elements
    • Init value constant contained duplicate record elements after merge
    • GUI crashed when calling "Show in other views" on a found object
    • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
    • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
    • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
    • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

さらに表示

Released: 2016-08-09

 

Tool features

  • AUTOSAR 3 ECU-C synchronization now supports application refs of OS resources if the OS applications use exclusive areas as interruption mechanism
  • Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

  • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
  • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

  • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
  • Contract phase generation couldn't be used at the ECU-Project
  • Crash during SWC check on runnable data accesses by value has been fixed
  • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
  • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
  • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
  • Create port from signal didn't create correct init values in all cases
  • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
  • A component type DCF file accidently contained data constr elements
  • Init value constant contained duplicate record elements after merge
  • GUI crashed when calling "Show in other views" on a found object
  • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
  • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
  • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
  • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component
さらに表示