Vector: DYNA4

Legacy/internal identifier: DYNA4

Vendor information

Vendor

Web page

Product name

Version

Vector Informatik GmbH

https://www.vector.com/

DYNA4

From R5 to R8.

Categories

MDL 🛈

APL 🛈

BAN 🛈

BMA 🛈

SVC 🛈

DGN 🛈

FIU 🛈

EES 🛈

FCT 🛈

DBG 🛈

IMG 🛈

AUDIO 🛈

ENVSIM 🛈

ENVCOM 🛈

Signal recordings 🛈

File format

Comment

*.mf4

Platform

Operating system

Support

Windows

✓

Linux

Specifics

The DYNA4 tool connection with its tooljobs allows loading, parameterizing and starting of Tasks as well as retrieving signal recordings of a simulation.

Setup

When starting the TBC, DYNA4 will be started automatically; however, in order to ensure this, some options in the TBC must be set correctly:

  • The Path to DYNA4 Python API option must point to the dyna4_api.py file or dyna4.py file for DYNA4 versions < 8. It is usually located in the directory DYNAwareProductsRemoteAPI in the Dyna4 installation directory. Instead of the supplied file you can also use your own, possibly modified, file.

  • The option XMLRPC-API-Port must point to the port of the DYNA4-XMLRPC-API (default: 10895).

  • The option Project must point to the name of an existing DYNA4 project. They are available in DYNA4 in the workspace under Project Navigator. This project will be loaded by ecu.test after the start of DYNA4.

Usage

Job sequence

The following should be considered regarding the order of the tool jobs:

  • Before the simulation can be started with RunTask, a Model Configuration and a Task must be loaded with LoadModelConfiguration and LoadTask.

  • Before signal recordings can be retrieved with GetSimulationResults, a simulation must have been run with RunTask.

  • The job LoadTask resets all Task Parameters previously set with SetTaskParameter.

Names of Model Configurations and Tasks

For the LoadModelConfiguration and LoadTask jobs, the file path of the artifact to be loaded must be specified. This is the path relative to the artifact specific directory in the Database within the project. For example, when loading the Task MyVehicleProject/Database/Tasks/MyVehicleTasks/MyTask1.task, it would be referenced with “MyVehicleTasks/MyTask1.task”.

Parameterization of Tasks

The SetTaskParameter job can be used to change one parameter of the loaded Task. If the Task is selected in the GUI of DYNA4, the specified input fields indicate, which parameters can be varied for the Task. It is important that not only the parameterName is correct, but also that the value of ParameterValue has the right datatype.

Different simulation targets

The option Simulation-Target in the TBC sets the platform of the simulation. Depending on the platform, compilation and download might be necessary. The download is implicitly executed during RunTask, while the compilation can be invoked with the Job BuildSimulationTarget.

Limitations

Due to a limitation of the DYNA4 interface, it is currently not possible to load new tasks from the project directory. If a task is selected with the tool job LoadTask, this task must have been previously loaded in the currently selected project.