MicroAutoBox II

Software Getting Started

For all variants of MicroAutoBox II

Release 2024-A – May 2024

How to Contact dSPACE
Mail: dSPACE GmbH
Rathenaustraße 26
33102 Paderborn
Germany
Tel.: +49 5251 1638-0
E-mail: info@dspace.de
Web: https://www.dspace.com

How to Contact dSPACE Support

If you encounter a problem when using dSPACE products, contact your local dSPACE
representative:
§ Local dSPACE companies and distributors: https://www.dspace.com/go/locations
§ For countries not listed, contact dSPACE GmbH in Paderborn, Germany.
Tel.: +49 5251 1638-941 or e-mail: support@dspace.de

You can also use the support request form: https://www.dspace.com/go/supportrequest. If

you are logged on to mydSPACE, you are automatically identified and do not have to add
your contact details manually.

If possible, always provide the serial number of the hardware, the relevant dSPACE License
ID, or the serial number of the CmContainer in your support request.

Software Updates and Patches

dSPACE strongly recommends that you download and install the most recent patches
for your current dSPACE installation. Visit https://www.dspace.com/go/patches for the
software updates and patches themselves and for more information, such as how to
receive an automatic notification when an update or a patch is available for your dSPACE
software.

Important Notice
This publication contains proprietary information that is protected by copyright. All rights
are reserved. The publication may be printed for personal or internal use provided all the
proprietary markings are retained on all printed copies. In all other cases, the publication
must not be copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine-readable form, in whole or in part, without the prior written consent
of dSPACE GmbH.

© 2021 - 2024 by:

dSPACE GmbH
Rathenaustraße 26
33102 Paderborn
Germany

This publication and the contents hereof are subject to change without notice.

AURELION, AUTERA, ConfigurationDesk, ControlDesk, MicroAutoBox, MicroLabBox,

SCALEXIO, SIMPHERA, SYNECT, SystemDesk, TargetLink, and VEOS are registered
trademarks of dSPACE GmbH in the United States or other countries, or both. Other
brand names or product names are trademarks or registered trademarks of their respective
companies or organizations.
 Contents

Contents

About This Document 5

Quick Start for Working with a MicroAutoBox II 7

Required Software and Hardware Installation.................................... .............. 7
How to Create a Real-Time Application........................................................... 8
How to Experiment with a Real-Time Application in ControlDesk................... 13

Detailed Description for Working with a dSPACE System 21

Accessing the Hardware with ControlDesk................................................. ............ 22

Basic Steps When Accessing the Hardware......................................................... 22

Workflow for Accessing the Hardware.............................................. ............ 23
How to Start ControlDesk............................................................................. 23
How to Register a dSPACE System................................................................. 25

Checking the Configuration of the dSPACE Boards............................................ 28

How to Check the Configuration...................................................... ............ 29
How to View the Properties of a dSPACE System........................................... 30

Updating the Firmware...................................................................................... 30

Basics on Firmware........................................................................................ 31
How to Prepare the Firmware Update............................................................ 33
How to Update Firmware.............................................................................. 35

Implementing Models via Simulink/RTI or via Handcoding....................................... 37

How to Start RTI............................................................................................ 37
How to Implement a Model via Simulink and RTI........................................... 39
How to Implement a Model via Handcoding.................................................. 42

Handling Real-Time Applications with ControlDesk................................................. 44

How to Load an Application to the Program Memory and Start the
Real-Time Processor.......................................................................... ............ 44
How to Stop a Real-Time Application............................................................ 45
How to Reload a Real-Time Application......................................................... 46
How to Load an Application to the Flash Memory and Start the Real-
Time Processor.............................................................................................. 47
How to Clear an Application from the Flash Memory..................................... 48

Experimenting with ControlDesk............................................................................ 50

Demo Projects/Experiments and Related Files................................................. 50

3
May 2024 MicroAutoBox II Software Getting Started
 Contents

How to Measure Variable Values................................................................... 51

How to Change Parameter Values of a Running Application.......................... 58

Glossary 61

Index 71

4
MicroAutoBox II Software Getting Started May 2024
 About This Document

About This Document

Content This document shows how to get started with the MicroAutoBox II in connection
with RTI and ControlDesk.

Symbols dSPACE user documentation uses the following symbols:

Symbol Description
Indicates a hazardous situation that, if not avoided,
V DANGER
will result in death or serious injury.
Indicates a hazardous situation that, if not avoided,
V WARNING could result in death or serious injury.
Indicates a hazardous situation that, if not avoided,
V CAUTION could result in minor or moderate injury.
Indicates a hazard that, if not avoided, could result in
NOTICE
property damage.
Indicates important information that you should take
Note
into account to avoid malfunctions.
Indicates tips that can make your work easier.
Tip
Indicates a link that refers to a definition in the
glossary, which you can find at the end of the
document unless stated otherwise.
Follows the document title in a link that refers to
another document.

Naming conventions dSPACE user documentation uses the following naming conventions:

%name% Names enclosed in percent signs refer to environment variables for

file and path names.

<> Angle brackets contain wildcard characters or placeholders for variable

file and path names, etc.

5
May 2024 MicroAutoBox II Software Getting Started
 About This Document

Special Windows folders Windows‑based software products use the following special folders:

Common Program Data folder A standard folder for application-specific

program data that is used by all users.
%PROGRAMDATA%\dSPACE\<InstallationGUID>\<ProductName>
or
%PROGRAMDATA%\dSPACE\<ProductName>\<VersionNumber>

Documents folder A standard folder for application‑specific files that are

used by the current user.
%USERPROFILE%\Documents\dSPACE\<ProductName>\<VersionNumber>

Local Program Data folder A standard folder for application-specific

program data that is used by the current user.
%USERPROFILE%\AppData\Local\dSPACE\<InstallationGUID>\
<ProductName>

Accessing dSPACE Help and After you install and decrypt Windows‑based dSPACE software, the
PDF files documentation for the installed products is available in dSPACE Help and as PDF
files.

dSPACE Help (local) You can open your local installation of dSPACE Help:
§ On its home page via Windows Start Menu
§ On specific content using context-sensitive help via F1

PDF files You can access PDF files via the icon in dSPACE Help. The PDF
opens on the first page.

dSPACE Help (Web) Independently of the software installation, you can

access the Web version of dSPACE Help at https://www.dspace.com/go/help.
To access the Web version, you must have a mydSPACE account.
For more information on the mydSPACE registration process, refer to
https://www.dspace.com/faq?097.

6
MicroAutoBox II Software Getting Started May 2024
 Quick Start for Working with a MicroAutoBox II

Quick Start for Working with a MicroAutoBox II

Introduction After checking the preconditions, you can start work on typical use-cases.

Where to go from here Information in this section

Required Software and Hardware Installation............................................. 7

The MicroAutoBox II must be installed before you can perform the steps
described in this document.

How to Create a Real-Time Application..................................................... 8

First you generate a real-time application for your dSPACE system.

How to Experiment with a Real-Time Application in ControlDesk............. 13

To experiment with the real‑time application, you can open a
platform‑specific ControlDesk demo.

Required Software and Hardware Installation

Introduction The MicroAutoBox II must be installed before you can perform the steps
described in this document.

Required software installation To perform the first work steps, the installation of the following software is
required:
§ The MATLAB software must be installed with at least the following
components:
§ Simulink
§ Simulink® CoderTM
§ Necessary toolboxes, refer to
http://www.dspace.com/goto?toolboxes

7
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

The MATLAB version must match the available dSPACE Release. For
compatibility information, refer to http://www.dspace.com/goto?compatibility.
§ The following dSPACE software must be installed:
§ RTI (Real-Time Interface)
§ A C code cross compiler
§ ControlDesk
Refer to Installing dSPACE Software .

Required hardware To perform the first work steps, the MicroAutoBox II must be installed and
installation connected to the host PC via Ethernet.

For more information on the installation, refer to MicroAutoBox II Hardware

Installation and Configuration Guide .

How to Create a Real-Time Application

Objective First you generate a real-time application for your dSPACE system.

Workflow To generate a real-time application, you have to perform the following steps:

Step Description
Step 1: Creating a Simulink model You have to create a Simulink model using MATLAB and Simulink.
Instead of programming C code manually, you implement the algorithm
graphically using Simulink blocks. The models are saved as SLX files.
Step 2: Specifying RTI I/O interfaces To connect the simulation model to the physical world, you need to
introduce I/O interfaces into the model. These allow you to replace parts
of your simulated model with real hardware. dSPACE's RTI (Real-Time
Interface) blocks provide I/O interfaces for accessing dSPACE hardware.
Step 3: Generating C code You can build the model created with Simulink and RTI blocks using the
Simulink® CoderTM. The Simulink® CoderTM generates C code from the
model automatically.
Step 4: Compiling and linking the real- The cross compiler environment compiles the generated C code and
time application links the object files and libraries into an executable application for the
real-time processor.

Precondition Before you can start the build and download procedure, you have to ensure that
your dSPACE hardware is registered correctly in ControlDesk. Refer to How to
Register a dSPACE System on page 25.

Method To generate a real-time application

1 Start MATLAB.

8
MicroAutoBox II Software Getting Started May 2024
 How to Create a Real-Time Application

2 Choose your platform by clicking RTI1401 in the Select dSPACE RTI

Platform Support dialog.

Tip

If you select the Do not show this dialog again checkbox, MATLAB
will always start with the platform that was last active.
This option can be reset by clicking the Click here to re-enable RTI
platform selection for next MATLAB start link in the MATLAB Command
Window.

3 Select Set template file automatically in the displayed dialog to set the
dSPACE‑specific options in the configuration parameters and to provide the
model template for the MicroLabBox.

9
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

4 In the MATLAB Command Window, enter rti to open the corresponding

RTI library.

5 From the LIBRARY ribbon, select New – RTI1401 to open a new model
based on the board‑specific template. If this entry is not displayed, check the
activation of the dSPACE platform described in step 2.

10
MicroAutoBox II Software Getting Started May 2024
 How to Create a Real-Time Application

A new model opens.

6 From the SIMULATION ribbon in the model, select LIBRARY – Library

Browser.
The Simulink Library Browser opens.

11
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

7 Add blocks from the Simulink Library Browser to the model via drag and
drop.

8 Add RTI blocks from the RTI library to the model via drag and drop, and
connect the blocks as shown in the following illustration.

9 Save the model.

10 Press Ctrl + B.
The Simulink® CoderTM generates C code for the model. The RTI build
process compiles the generated C code, links the object files and libraries
into an executable application and downloads the application to the real-
time hardware directly after the compilation (build). The build status is
displayed in the MATLAB Command Window.

Result You have generated a real-time application consisting of the following files:

File Description
MAP Map file with address information of variables
PPC Real-time application to be downloaded to the dSPACE real-time hardware
SDF System description file to be used by ControlDesk. It contains references to the PPC, MAP, and TRC file.
TRC Variable description file
TRZ If real-time testing is enabled for the generated real-time application, the build process generates a TRZ file
containing the MAP file and the TRC file.

12
MicroAutoBox II Software Getting Started May 2024
 How to Experiment with a Real-Time Application in ControlDesk

Next step You can now experiment with the real-time application with ControlDesk. Refer
to How to Experiment with a Real-Time Application in ControlDesk on page 13.

How to Experiment with a Real-Time Application in ControlDesk

Objective To experiment with the real‑time application, you can open a platform‑specific
ControlDesk demo.

Experimenting with a real- The Real‑Time application demos provided by ControlDesk let you quickly start
time application experimenting with a real-time application. They also let you familiarize yourself
with the ControlDesk instruments for measuring signals and changing parameter
values.

Workflow To experiment with a real-time application in ControlDesk, perform the following

steps:
1. Register your dSPACE real-time hardware as shown in Part 1.
The registration process for other platforms may differ. In this case, perform
the steps described in How to Register a dSPACE System on page 25.
2. Open a demo and experiment with the real-time application as shown in
Part 2.

13
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

Part 1 To register a MicroAutoBox II

1 Start ControlDesk.

2 On the Platforms ribbon, click Register Platforms.

The Register Platforms dialog opens.
3 In the Register Platforms dialog, select MicroAutoBox II.

14
MicroAutoBox II Software Getting Started May 2024
 How to Experiment with a Real-Time Application in ControlDesk

4 Specify the IP address of the network client.

5 In the Register Platforms dialog, click Register. The MicroAutoBox II is now

registered as shown in the following illustration.

Close the Register Platforms dialog.

15
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

Interim result The following illustration shows the registered MicroAutoBox II in the
Platforms/Devices controlbar:

Part 2 To open a demo and experiment with the real-time application

1 If not already done, copy the demos to the Documents folder. In the File
menu, click Options and open the User Settings page. click Copy Demos
to copy the demos to your working folder with modify rights.

16
MicroAutoBox II Software Getting Started May 2024
 How to Experiment with a Real-Time Application in ControlDesk

2 On the File ribbon, click Open – Open Project + Experiment to open the
demo experiment for your platform.

17
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

ControlDesk opens the experiment and automatically assigns the platform

registered in Part 1 to the platform displayed in the Project Manager.

3 On the Home ribbon, click Status Control – Start Measuring.

ControlDesk automatically downloads the experiment's application to the
hardware.
4 Change to the throttle controller layout.

18
MicroAutoBox II Software Getting Started May 2024
 How to Experiment with a Real-Time Application in ControlDesk

5 Experiment with the real-time application, e.g., by changing parameter

values on the layouts.

Result You experimented with the real-time application in ControlDesk and finished the
quick start using dSPACE hardware. If you need a detailed description of how
to experiment with ControlDesk, refer to Experimenting with ControlDesk on
page 50.

Related topics Basics

Real-Time Application Demos (ControlDesk Introduction and Overview )

HowTos

How to Register a dSPACE System............................................................................................ 25

References

Open Project + Experiment (ControlDesk Project and Experiment Management )

Register Platforms (ControlDesk Platform Management )
Start Measuring (ControlDesk Measurement and Recording )

19
May 2024 MicroAutoBox II Software Getting Started
 Quick Start for Working with a MicroAutoBox II

20
MicroAutoBox II Software Getting Started May 2024
 Detailed Description for Working with a dSPACE System

Detailed Description for Working with a dSPACE

System

Introduction If the quick start instructions do not match your requirements, this document
also provides a detailed description for working with your dSPACE system.

Where to go from here Information in this section

Accessing the Hardware with ControlDesk............................................... 22

You can manage dSPACE real-time hardware with the ControlDesk
Platforms/Devices pane.

Implementing Models via Simulink/RTI or via Handcoding........................ 37

The first step is to implement your model. You can either embed the
blocks provided by dSPACE’s Real-Time Interface (RTI) in a Simulink
model or use RTLib’s functions to handcode your application directly in C.

Handling Real-Time Applications with ControlDesk.................................. 44

Learn how to handle applications on real-time processors (RTP).

Experimenting with ControlDesk............................................................. 50

To experiment with real-time applications, use ControlDesk.

21
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Accessing the Hardware with ControlDesk

Introduction You can manage dSPACE real-time hardware with the ControlDesk
Platforms/Devices pane.

Where to go from here Information in this section

Basic Steps When Accessing the Hardware.............................................. 22

Gives an overview of the workflow and an introduction to the graphical
user interface of ControlDesk.

Checking the Configuration of the dSPACE Boards.................................. 28

After registration, you can check the properties of the dSPACE system
with ControlDesk.

Updating the Firmware............................................................................ 30

Your board usually contains the latest firmware. If you install a new
dSPACE Release it may contain newer firmware. In this case the firmware
can be updated.

Basic Steps When Accessing the Hardware

Introduction An overview of the workflow and an introduction to the graphical user interface
of ControlDesk help you to access the hardware.

Where to go from here Information in this section

Workflow for Accessing the Hardware..................................................... 23

The configuration process varies according to the type of dSPACE board.

How to Start ControlDesk........................................................................ 23

ControlDesk lets you manage your dSPACE simulation platform.

How to Register a dSPACE System........................................................... 25

After installing dSPACE real‑time hardware, you have to make it known
to ControlDesk.

22
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

Workflow for Accessing the Hardware

Workflow steps To access dSPACE hardware, you can use ControlDesk, which lets you
experiment with dSPACE systems. For example, you can use it to register dSPACE
boards, download applications and manage experiments.

The first time you access dSPACE real-time hardware, you have to perform the
following workflow steps:
1. Starting ControlDesk
ControlDesk is installed on the host PC during software installation. Refer to
How to Start ControlDesk on page 23.
2. Registering dSPACE boards
ControlDesk provides the Platforms/Devices pane that lets you register
dSPACE real-time hardware. Refer to How to Register a dSPACE System on
page 25.
3. Checking the configuration of dSPACE boards
When the dSPACE board is registered you can check the board
configuration. Refer to Checking the Configuration of the dSPACE Boards
on page 28.
4. Updating the firmware
Your board usually contains the latest firmware. If you install a new dSPACE
Release it may contain newer firmware. In this case the firmware should be
updated. Refer to Updating the Firmware on page 30.

How to Start ControlDesk

Objective After installation of the dSPACE software, ControlDesk is available in the

Windows Start menu and as an icon on the desktop.

23
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

User interface The following illustration shows the user interface of ControlDesk.

Quick Access Toolbar Ribbon Main window Working area with pages Search field

Panes Status bar

Method To start ControlDesk

1 In the Windows Start menu, select Programs – dSPACE

ControlDesk 2024‑A.

24
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

ControlDesk starts, see the following illustration.

Result ControlDesk is ready to register your dSPACE simulation platform.

Related topics Basics

Introduction to ControlDesk (ControlDesk Introduction and Overview )

How to Register a dSPACE System

Objective After installing dSPACE real‑time hardware, you have to make it known to
ControlDesk.

Preconditions § To register a platform to access dSPACE real-time hardware, the hardware

must be connected to the host PC.

25
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

§ Before you register the MicroAutoBox II, configure it using

the DS1401ConfigGUI.exe utility, for example, to change
MicroAutoBox II's default IP address. The utility is located in
<RCP_HIL_InstallationPath>\Exe. For configuration details, refer to
Connecting the MicroAutoBox II to the Host PC (MicroAutoBox II Hardware
Installation and Configuration Guide ).

Tip

You can add the DS1401ConfigGUI.exe tool as a user function to

ControlDesk. Refer to How to Add External Programs or Scripts as User
Functions to ControlDesk (ControlDesk Customization ).

Method To register a dSPACE system

1 On the Platforms ribbon, click Platform Management - Register
Platforms.
The Register Platforms dialog opens.
2 From the Platforms list, select the type of the platform you want to register.
The registration settings vary according to the selected platform type. The
following illustration shows an example for the SCALEXIO platform type.

26
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

3 Specify the registration settings for the dSPACE hardware you want to
register. The number and kinds of properties depend on the selected
platform type.

Property Description / Refer to

Common Properties
Platform name Lets you specify a unique name for the selected platform. After registration, the name is displayed in the
ControlDesk Platforms/Devices pane.
The valid characters are 'a ... z', 'A ... Z', '0 ... 9', '_', '-' and ' '. The name must not start or end with an
underline, hyphen or blank.
If you do not specify a platform name, ControlDesk displays a default name in the
Platforms/Devices pane.
Platform type Common Properties (ControlDesk Platform Management )

Connection Settings Properties

Alias name Assignment Properties (ControlDesk Platform Management )
Board name Assignment Properties (ControlDesk Platform Management )
Connection parameter Lets you select one of the following connection parameters for registration:
§ Alias name
§ Board name
§ IP address
§ MAC address
The selected parameter is used to register the member processing units/processor boards (SCALEXIO),
member platforms (DS1202 MicroLabBox, MicroAutoBox III; MicroLabBox II), or simulator (VEOS).
Connection type Assignment Properties (ControlDesk Platform Management )
IP address Assignment Properties (ControlDesk Platform Management )
MAC address Assignment Properties (ControlDesk Platform Management )
Network client Assignment Properties (ControlDesk Platform Management )
Platform Lets you specify the platform belonging to the DS1202 MicroLabBox, MicroAutoBox III, or MicroLabBox II
platform, or the simulator (local host PC or remote PC) for the VEOS platform.
The platform has an edit field to specify its connection parameter value.
Processing units
Lets you specify the processing units or processor boards belonging to the SCALEXIO platform. Click
to add a processing unit or processor board, or click to delete the selected processing unit or processor
board.

Note

You cannot subsequently add processing units or processor boards to a SCALEXIO system that is
already registered.

Each processing unit or processor board has an edit field to specify its connection parameter value and
an edit field to specify a unique name for it. After registration, the name is displayed in the ControlDesk
Platforms/Devices pane.
The valid characters are 'a ... z', 'A ... Z', '0 ... 9', '_', '-' and ' '. The name must not start or end with an
underline, hyphen or blank. If you do not specify a custom name for a processing unit or processor board,
ControlDesk displays a default name for it in the Platforms/Devices pane.
Scan for available Lets you scan the local network for connected platform hardware or simulators (VEOS). Depending on
processor boards/ the platform type to be registered, ControlDesk opens the Scan Local Network for Processor Boards,
processing units/ the Scan Local Network for Processing Units, or the Scan Local Network for Platforms dialog and
platforms displays all the platform hardware found in the network. Refer to Scan Local Network for Processor
Boards/ Processing Units /Platforms dialog (ControlDesk Platform Management ).

27
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Property Description / Refer to

MAPort Implementation Properties

MAPort Lets you select the MAPort implementation for the XIL API MAPort platform.
Implementation The list displays all the supported XIL API MAPort implementations. The XIL API MAPort platform analyzes
the IMF files in the standard XIL API folder (ProgramData\ASAM\XIL\Implementation) to determine
the installed XIL API MAPort implementations.
Product name MAPort Implementation Properties (ControlDesk Platform Management )
Product version MAPort Implementation Properties (ControlDesk Platform Management )
Vendor name MAPort Implementation Properties (ControlDesk Platform Management )
XIL API version MAPort Implementation Properties (ControlDesk Platform Management )

4 Click Register to complete the registration.

The registered platform is displayed with its registration settings in the
Registered platforms list.

Tip

If you register a platform with corrupted boot firmware or with

hardware components containing different firmware versions, a
message box containing warning messages about the detected
firmware problem is displayed. The warning messages are also displayed
in the Message Viewer. In the Platforms/Devices pane, the affected
hardware components are marked with the symbol. Its tooltip also
provides information on the detected firmware problem. You should
check the entries and perform firmware updates, if necessary. Refer to
Update Firmware (ControlDesk Platform Management ).

5 Click Close to close the Register Platforms dialog.

Result You have registered a dSPACE system.

Related topics References

Register Platforms (ControlDesk Platform Management )

Checking the Configuration of the dSPACE Boards

Introduction After registration, you can check the properties of the dSPACE system with
ControlDesk.

28
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

Where to go from here Information in this section

How to Check the Configuration............................................................. 29

To check whether the system is ready to experiment with real-time
applications.

How to View the Properties of a dSPACE System..................................... 30

After registration, you can view the properties of the dSPACE system.

How to Check the Configuration

Objective To check whether the system is ready to experiment with real-time applications.

Check application and related To check whether your dSPACE system works correctly, it is recommended that
ControlDesk experiment you load the check application. There is a ZIP file with a backup of a ControlDesk
experiment referencing the check application. To check the configuration of
your system, open the ZIP file in ControlDesk and load the contained real‑time
application to the system.

For the MicroAutoBox II, the smd_1401_ch.zip is located in the

\Demos\DS1401\Check\ folder (relative to the folder of the RCP and HIL
installation).

Method To check the configuration

1 Start ControlDesk.
2 On the File ribbon, click Open ‑ Project + Experiment from Backup.
ControlDesk opens a standard Open dialog.
3 In the Open dialog, specify the ZIP file that matches your system type and
click Open. For the location of the ZIP file, see the table above (refer to
Check application and related ControlDesk experiment).
ControlDesk opens the project and experiment that belong to the check
application.
4 From the context menu of the experiment's platform, select Configure
Platform/Device to configure the platform according to the dSPACE real-
time hardware connected to the host PC. For example, you have to specify
the IP address of the hardware.
5 Press F5 to start a measurement.
6 If no error message is displayed in the Message Viewer, the board is
installed correctly.

Result You have checked the configuration.

29
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Related topics References

Configure Platform/Device (ControlDesk Platform Management )

How to View the Properties of a dSPACE System

Objective After registration, you can view the properties of the dSPACE system.

Preconditions The dSPACE system is registered.

Method To view the properties of a dSPACE system

1 On the View ribbon, click Pane - Show Panes - Properties to open the
Properties pane.
2 In the Project Manager, select the corresponding system.
The platform information is displayed in the Properties pane.

Result You have viewed the properties of your dSPACE system. For a detailed
description of the properties, refer to Platform/Device-Related Properties
(ControlDesk Platform Management ).

Related topics References

Platform/Device-Related Properties (ControlDesk Platform Management )

Updating the Firmware

Introduction Usually your board contains the latest firmware. If you install a new dSPACE
Release it may contain newer firmware. In this case the firmware can be
updated.

30
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

Where to go from here Information in this section

Basics on Firmware.................................................................................. 31
Gives you information on the different kinds of firmware.

How to Prepare the Firmware Update...................................................... 33

Before you start an update or repair process, some preparations have to
be made.

How to Update Firmware........................................................................ 35

Gives you the instructions for the firmware update mode.

Basics on Firmware

Introduction You can execute a real‑time application on dSPACE real‑time hardware only if
the different kinds of firmware are available. The loaded firmware version has to
provide the functionality implemented in the real‑time application.

Firmware features The firmware for a hardware component provides basic functionality that is
stored in a nonvolatile memory. For example, it includes functions for the
communication between the host PC and the hardware, and can also provide
I/O functions such as CAN or LIN protocol support, or complex I/O functions for
an FPGA component.

The firmware archives provides all the relevant firmware components that are
required for your hardware.

Details on the firmware The following firmware archives are available.

archives
MABXFwArchive.arc (for MicroAutoBox II) The firmware archive for
MicroAutoBox II contains the following firmware components:
§ DS1401 boot firmware
§ DS1401 System PLD firmware
§ DS1401 Host IF PLD firmware
§ DS1401 Host IF firmware
§ ADC TYPE 4 PLD firmware
§ DIO TYPE 3 PLD firmware
§ DIO TYPE 4 PLD firmware
§ FPGA TYPE 1 PLD firmware
§ AIO TYPE 1 PLD firmware
§ CAN TYPE 1 firmware
§ DS4342 firmware

31
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Note

To program the firmware that supports the RTI DS1552 I/O Extension
blockset for the DS1552 Multi‑I/O module, you have to use the
DS1401UpdateExtIO command, which is described in the MicroAutoBox II
RTLib Reference .

Special firmware The firmware archives installed with your dSPACE software provide the standard
firmware type. There might be other firmware types to be managed with the
Firmware Manager.

Custom firmware The Firmware Manager allows you to install custom

firmware that dSPACE provides for solutions or engineering projects.

User firmware User firmware is a firmware that is based on dSPACE

firmware but extended with your own functionality. The Firmware Manager does
not support loading user firmware.

Note

dSPACE accepts no liability for incorrect operation or property damage

when using user firmware with dSPACE hardware.

Default factory firmware MicroAutoBox II, MicroAutoBox III, MicroLabBox,

MicroLabBox II, and SCALEXIO are providing a secured mode for using the
default factory firmware. If firmware is corrupted, the hardware, automatically
reboots, if necessary, and loads the default factory firmware that lets you access
the board and retry the firmware update.
For further information, refer to:
§ Using MicroAutoBox II: How to Start MicroAutoBox II to Secured Mode
(MicroAutoBox II Hardware Installation and Configuration )

Note

Note the following restriction if you use MicroAutoBox II or MicroLabBox.

In secured mode, for example, caused by an interrupted firmware repair
or update process, you cannot repair or update the firmware components
of the I/O components of the board (internal I/O modules or the I/O
FPGA). You firstly have to repair or update the firmware components of
the base board and then reboot the board to leave the secured mode. Error
messages regarding to the repair or update process of the I/O components
can be ignored. After reboot, you can continue the repair or update process
for the firmware of the I/O components.

If your real‑time hardware does not provide a secured mode for using the default
factory firmware, you have to repair the board's boot firmware. You can do this
via the command line interface of the firmware management or via the Platform
Manager. To repair the corrupted boot firmware via the command line interface,
refer to Examples of Script‑Based Firmware Management (Firmware Manager
Manual ).

32
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

Related topics Basics

Basics on the Firmware Manager (Firmware Manager Manual )

How to Prepare the Firmware Update

Objective The preparation of a firmware update consists of specifying some general

firmware settings.

Preconditions The following preconditions must be fulfilled for configuring the general
firmware settings:
§ The real‑time hardware must be connected to the host PC.
§ The real‑time hardware must be switched on.
§ The required firmware archive must be available.
You can find the latest firmware archives on the dSPACE website at
https://www.dspace.com/go/firmware.
§ If a real‑time application is loaded to the board's flash memory, it is
recommended to clear the flash before starting the update process to avoid
unpredictable output signals.
If a real‑time application is running, it is stopped by the firmware
management.
§ If you have registered a multicore system with additional I/O boards, you have
to select the core to which the I/O boards are connected for the update of the
entire system. The other cores will be updated, too.

Method To prepare the firmware update

1 Open the Platform Manager.
2 If no real‑time hardware is displayed in the Platform Manager, register the
real‑time hardware that you want to update.

3 Choose Update Firmware in the platform's context menu to open the

Update Firmware Wizard.

33
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

The wizard starts with the Select Mode dialog.

4 Select the firmware update mode.

By default, the Update mode is set to update all firmware components
of your real‑time hardware with later firmware. With the Repair mode
enabled, you can select the firmware components to be repaired.
To switch to the repair mode, select Firmware repair mode in the Select
Mode dialog.
5 Click Next to continue with the Select Firmware Archive dialog.

The latest firmware archive for the selected platform is automatically set.
Optionally, browse for another firmware archive. This might be useful if
you want to update to a firmware version other than the latest or repair
user firmware, for example. You find the installed firmware archives in
C:\Program Files\Common Files\dSPACE\Firmware Archives.
6 Click Next to continue with the Select Firmware Components dialog.

Result You have configured the settings which are required for a firmware update
process in update or repair mode.

34
MicroAutoBox II Software Getting Started May 2024
 Accessing the Hardware with ControlDesk

Related topics HowTos

How to Repair Firmware (Firmware Manager Manual )

How to Update Firmware......................................................................................................... 35

How to Update Firmware

Objective Gives you the instructions for the firmware update mode.

Preconditions The firmware update process has to be prepared with the Update Mode
specified as described in How to Prepare the Firmware Update on page 33.

Safety precautions V WARNING

Risk of injury and/or material damage

Updating the firmware can cause uncontrolled movements of connected
devices.
§ Disconnect actuators and sensors from the associated real‑time hardware
before you start the update process.

NOTICE

Interrupting the update process disables the hardware

If the firmware update is interrupted, for example, by switching off the
power, you have to restart the update process.

Note

Follow the instructions of the firmware management tool to correctly finish

the firmware update process. For example, in some cases the hardware has
to be rebooted to complete the firmware update.

Method To update firmware

1 In the Select Firmware Components dialog, click Update to start the
firmware update process.
In the Update column, the firmware components to be updated are marked
and red. The components are not marked for update if the version of the
currently installed firmware is identical to or later than the firmware available
in the specified firmware archive.

35
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

If there are updatable firmware components, the update process starts. You
can see the progress in the Status column. The initial '--' entry is replaced by
a percentage. If the progress information cannot be detected continuously,
only the states 50% and 100% are displayed. If the process successfully
finished, an OK is shown, otherwise an error message is displayed.
If the firmware update will require more than 40 minutes, an estimate of
the time is displayed. Then you can decide whether to start the process.
Interrupting a running firmware update process is not possible.

Note

You must not switch off the hardware during the firmware update
process. This will cause a corrupted firmware.

Follow the given instructions to complete the firmware update. For example,
some firmware components require a hardware restart.

Result You have updated the firmware components of your hardware.

Related topics HowTos

How to Prepare the Firmware Update....................................................................................... 33

How to Repair Firmware (Firmware Manager Manual )

36
MicroAutoBox II Software Getting Started May 2024
 Implementing Models via Simulink/RTI or via Handcoding

Implementing Models via Simulink/RTI or via Handcoding

Introduction The first step is to implement your model. You can either embed the blocks
provided by dSPACE’s Real-Time Interface (RTI) in a Simulink model or use RTLib’s
functions to handcode your application directly in C.

Where to go from here Information in this section

How to Start RTI...................................................................................... 37

Real-Time Interface (RTI) is the interface between Simulink and the
dSPACE systems.

How to Implement a Model via Simulink and RTI..................................... 39

A demo model is used to show you how to work with a Simulink model.

How to Implement a Model via Handcoding............................................ 42

An algorithm can also be handcoded in C. The dSPACE software includes
the necessary compilers and tools required to generate the real-time
application.

How to Start RTI

Objective dSPACE Real-Time Interface (RTI) is the interface between Simulink and
the dSPACE systems: In connection with MATLAB®/Simulink®, the C code
for the real‑time model for a specific dSPACE system is generated by the
Simulink® CoderTM.

Preconditions § Ensure that MATLAB, Simulink, Simulink® CoderTM, and Real-Time Interface
(RTI) for your dSPACE system are properly installed.
§ The required licenses must be available and activated. For information on
handling the license mechanism, refer to Installing dSPACE Software .

Method To start RTI

1 Start MATLAB.

37
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

2 Choose your platform.

Tip

If you select the Do not show this dialog again checkbox, MATLAB
will always start with the platform that was last active.
This option can be reset by clicking the Click here to re-enable RTI
platform selection for next MATLAB start link in the MATLAB Command
Window.

3 In the MATLAB Command Window, enter rti to open the RTI block library
of your dSPACE system.

38
MicroAutoBox II Software Getting Started May 2024
 Implementing Models via Simulink/RTI or via Handcoding

Result You started RTI and opened the RTI block library of your dSPACE system.

To switch to another platform such as MicroLabBox, enter rti1202.

Next step Now you can work with a Simulink model. Refer to How to Implement a Model
via Simulink and RTI on page 39.

Related topics HowTos

How to Implement a Model via Simulink and RTI...................................................................... 39

How to Implement a Model via Simulink and RTI

Objective A demo shows you how to work with a Simulink model.

Demo model The smd_1401_sl demo model is an example of how to use the RTI library.
The demo simulates a damped spring‑mass system stimulated by a square-wave
signal. It is a ready-to-use example that does not require any I/O hardware.

39
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Precondition Before you can start the build and download procedure, you have to ensure that
your dSPACE hardware is registered correctly in ControlDesk. Refer to How to
Register a dSPACE System on page 25.

Method To implement a model via Simulink and RTI

1 In the Library: rtilib1401 window, double-click Demos.
2 Double-click Spring ‑ Mass ‑ Damper in the Library: rti1401demolib
window.
The Get demo with ControlDesk experiment dialog opens.
3 In the Get demo with ControlDesk experiment dialog, click Yes to copy
the demo model and the experiment files to your current MATLAB working
directory.

The Simulink model is then opened.

4 To examine the model, double-click its blocks.

40
MicroAutoBox II Software Getting Started May 2024
 Implementing Models via Simulink/RTI or via Handcoding

5 Press Ctrl + E.
The Configuration Parameters dialog opens.

6 On the Code Generation page, check that the system target file
(rti1401.tlc) and the template makefile (rti1401.tmf) match your
dSPACE system, and that the make command make_rti is specified. If
necessary, change the entries.
7 Press Ctrl + B to build the real-time application and download it to the
dSPACE system.
The smd_1401_sl.sdf system description file and the real-time application
are generated. The real-time application is loaded to your dSPACE system
and started automatically.
If the real‑time application — stored in the current MATLAB working folder
— is stopped, you can reload it to the dSPACE system using ControlDesk. No
new build process is needed if you do not change the Simulink model in the
meantime.

Result The real-time application is built and loaded to the dSPACE system.

Next steps You can use ControlDesk to stop and restart the real-time application. Refer to
Handling Real-Time Applications with ControlDesk on page 44.

The smd_1401_sl.zip file contains a ControlDesk demo experiment for

experimenting with the MATLAB/Simulink-based demo application. The ZIP file
is located in the \Demos\DS1401\GettingStarted\Simulink folder in your
RCP and HIL installation.

41
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Related topics HowTos

How to Implement a Model via Handcoding............................................................................. 42

How to Start RTI....................................................................................................................... 37

How to Implement a Model via Handcoding

Objective A demo model shows you how to work with a C‑coded model.

C-coded demo model The C‑coded example model smd_1401_hc.c demonstrates how to proceed
without MATLAB and Simulink. This model does not require any I/O hardware. It
simulates a damped spring-mass system stimulated by a square‑wave signal. The
parameters are spring, mass and damper.

down1401 utility To compile and link the real-time application for your dSPACE system, you can
use the down1401 utility in a Command Prompt window. The utility downloads,
starts and checks the application as well.

Method To implement a model via handcoding

1 Extract the file
<RCP_HIL_InstallationPath>\Demos\DS1401\GettingStarted\Hand
Code\smd_1401_hc.zip to a folder for which you have write permission.
2 Open the file .\smd_1401_hc\Source Files\smd_1401_hc.c in a text
editor of your choice to inspect the code.
3 Open the Command Prompt for dSPACE RCP and HIL in the dSPACE
RCP and HIL start menu folder.
4 In the Command Prompt for dSPACE RCP and HIL, change to the folder
you extracted the ZIP file to.
5 Enter the following command: down1401 smd_1401_hc.
The smd_1401_hc.ppc real-time application file is generated.

Result The smd_1401_hc real-time application is generated, downloaded and started.

Next step You can use ControlDesk to stop and restart the real-time application, refer to
Handling Real-Time Applications with ControlDesk on page 44.

The smd_1401_hc.zip file contains a ControlDesk demo experiment for

experimenting with the MATLAB/Simulink-based demo application. The ZIP file

42
MicroAutoBox II Software Getting Started May 2024
 Implementing Models via Simulink/RTI or via Handcoding

is located in the \Demos\DS1401\GettingStarted\HandCode\ folder in your

RCP and HIL installation.

Related topics HowTos

How to Implement a Model via Simulink and RTI...................................................................... 39

How to Start RTI....................................................................................................................... 37

43
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Handling Real-Time Applications with ControlDesk

Introduction This section describes how to handle applications on real-time processors (RTP).

Where to go from here Information in this section

How to Load an Application to the Program Memory and Start

the Real-Time Processor........................................................................... 44
To execute the application, it must be downloaded to the program
memory.

How to Stop a Real-Time Application............................................ .......... 45

You can use the ControlDesk Platforms/Devices pane to stop an
application running on a real-time processor.

How to Reload a Real-Time Application................................................... 46

You can use the ControlDesk Platforms/Devices pane to reload an
application running on a real-time processor.

How to Load an Application to the Flash Memory and Start the

Real-Time Processor................................................................................. 47
To load and start a real-time application automatically after power-up of
your dSPACE system, load the application to its flash memory. This allows
you to use the dSPACE system stand-alone, without a connection to the
host PC.

How to Clear an Application from the Flash Memory............................... 48

If an application is loaded to the flash memory, the dSPACE board starts
the application automatically after reboot. If you want to avoid this, you
have to clear the flash memory.

Information in other sections

Implementing Models via Simulink/RTI or via Handcoding........................ 37

The first step is to implement your model. You can either embed the
blocks provided by dSPACE’s Real-Time Interface (RTI) in a Simulink
model or use RTLib’s functions to handcode your application directly in C.

How to Load an Application to the Program Memory and Start the Real-Time
Processor

Objective You can load real-time applications to the program memory and start the real-
time processor in the ControlDesk Platforms/Devices pane.

44
MicroAutoBox II Software Getting Started May 2024
 Handling Real-Time Applications with ControlDesk

Method To download an application to the program memory and start the Real-
Time Processor
1 In the Platforms/Devices pane, open the context menu of your platform
icon (or multiprocessor icon) and select Real-Time Application - Load.
The Select Real-Time Application dialog opens.
2 In the Select Real-Time Application dialog, select an SDF file, or a PPC,
RTA, or x86 file (depending on the hardware type).
3 If a previously loaded application is still running on your system, a dialog
similar to the following opens:

If you click Yes, the running application is stopped before the new
application is downloaded and started.

Result You have downloaded an application to the program memory and started the
real-time processor.

Related topics HowTos

How to Load an Application to the Flash Memory and Start the Real-Time Processor................ 47

References

Real-Time Application - Load (ControlDesk Platform Management )

Registering Platforms and Handling Applications via cmdloader (ControlDesk
Platform Management )

How to Stop a Real-Time Application

Objective You can use the ControlDesk Platforms/Devices pane to stop an application
running on a real-time processor.

Method To stop a real-time application

1 In the Platforms/Devices pane, open the context menu of your platform.
Depending on your platform, select Stop or Stop RTP.

45
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Result You have stopped the real-time application.

Related topics HowTos

How to Reload a Real-Time Application.................................................................................... 46

References

Registering Platforms and Handling Applications via cmdloader (ControlDesk

Platform Management )

How to Reload a Real-Time Application

Objective You can use the ControlDesk Platforms/Devices pane to reload an application
running on a real-time processor.

Restrictions § You cannot reload a multiprocessor application. You have to download it

again. Refer to How to Load an Application to the Program Memory and Start
the Real-Time Processor on page 44.
§ You cannot reload an application for a modular system containing DS230x
boards. You have to download it again. Refer to How to Load an Application
to the Program Memory and Start the Real-Time Processor on page 44.

Method To reload a real-time application

1 In the Platforms/Devices pane, open the context menu of your board icon
and select Real Time Application - Reload.

Tip

For some platforms, the command is available in the context menu of

the application to be reloaded.

Result You have reloaded a real-time application.

Related topics HowTos

How to Stop a Real-Time Application........................................................................................ 45

46
MicroAutoBox II Software Getting Started May 2024
 Handling Real-Time Applications with ControlDesk

References

Registering Platforms and Handling Applications via cmdloader (ControlDesk

Platform Management )

How to Load an Application to the Flash Memory and Start the Real-Time
Processor

Objective To load and start a real-time application automatically after power-up of your
dSPACE system, load the application to its flash memory. This allows you to use
the dSPACE system stand-alone, without a connection to the host PC.

Flash memory The MicroAutoBox II is equipped with a flash memory for real-time applications.

Loading the application on power up On power-up, the dSPACE board

always starts executing the bootstrap loader contained in the flash memory. The
loader checks for an application program currently stored in the flash memory. If
it finds one, the application is started. If it does not detect an application in the
flash memory, the loader enters the idle state and waits for commands from the
connected host PC.

Method To load a real-time application to the flash memory and start the real-
time processor
1 In the Platforms/Devices pane, open the context menu of your
platform and select Real-Time Application - Load to Flash
(DS1104/MicroAutoBox II Only).
The Select Real-Time Application dialog opens.
2 In the Select Real-Time Application dialog, select an SDF file, or a PPC,
RTA, or x86 file (depending on the hardware type).
3 If a previously loaded application is still running on your system, a dialog
similar to the following opens:

If you click Yes, the running application is stopped before the new
application is loaded and started.

47
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Result You have loaded an application to the flash memory and started the
real-time processor. The F next to the real-time application icon in the
Platforms/Devices pane indicates that the running application is loaded from
the flash memory.

Related topics HowTos

How to Load an Application to the Program Memory and Start the Real-Time
Processor.................................................................................................................................. 44

References

Real-Time Application - Load to Flash (DS1104/MicroAutoBox II Only) (ControlDesk

Platform Management )
Registering Platforms and Handling Applications via cmdloader (ControlDesk
Platform Management )

How to Clear an Application from the Flash Memory

Objective If you want to prevent the system from booting a flash application, you have to
clear the application from the flash memory.

Method To clear an application from the flash memory

1 In the Platforms/Devices pane, open the context menu of your platform
icon and select Clear Flash Options.

2 Select one of the following commands to clear the memory (the available
options depend on the selected platform type):
§ Clear Complete Flash Memory to clear the whole flash memory.
§ Clear Flash Application to clear only the loaded application from the
application flash memory.
§ Clear Flight Recorder Data to clear the flight recorder data.
§ Clear Nonvolatile Data to clear only data that is stored as nonvolatile.

48
MicroAutoBox II Software Getting Started May 2024
 Handling Real-Time Applications with ControlDesk

3 Click OK in the related confirmation dialog to clear the flash memory

according to your selection.

Result You have cleared the specified data from the flash memory.

Related topics HowTos

How to Load an Application to the Flash Memory and Start the Real-Time Processor................ 47

References

Registering Platforms and Handling Applications via cmdloader (ControlDesk

Platform Management )

49
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

Experimenting with ControlDesk

Introduction To experiment with real-time applications, use ControlDesk.

Where to go from here Information in this section

Demo Projects/Experiments and Related Files........................................... 50

To help you begin using ControlDesk, there is a demo experiment for
each platform.

How to Measure Variable Values.............................................................. 51

To measure the variable values of a running real‑time application, you
have to connect an instrument to the variables.

How to Change Parameter Values of a Running Application.................... 58

Use ControlDesk to change the parameters of a running application.

Demo Projects/Experiments and Related Files

Introduction You can use demo projects/experiments for your platform to experiment with
ControlDesk features. The Real‑Time application demo projects allow you to
work with ControlDesk and use all of its features with dSPACE real-time
hardware connected to the host PC.

Accessing the demo ControlDesk provides a demo project/experiment and related files for each
projects/experiments platform.

For instructions on opening demo projects, refer to Copying and opening a

demo project (ControlDesk Introduction and Overview ).

Related files Demo projects/experiments contain the following files:

PPC/x86/RTA file The real-time application file to be downloaded to the

hardware.

TRC file Provides information on available variables and how they are
grouped. Trace files are either generated by RTI/Simulink or hand-coded.

MAP file Maps names of variables to addresses of the physical memory. It is

generated by the C compiler.

SDF file The system description (SDF) file specifies which executable is
downloaded to which processor.

50
MicroAutoBox II Software Getting Started May 2024
 Experimenting with ControlDesk

Related topics Basics

Real-Time Application Demos (ControlDesk Introduction and Overview )

How to Measure Variable Values

Objective To measure the variable values of a running real‑time application, you have to
connect an instrument to the variables.

Tip

A successful measurement also confirms that your ControlDesk installation

is working correctly.

Working without the demo To show you how to set up a project/experiment and perform a measurement,
project/experiment the instructions below show all the steps from defining a project/experiment to
starting a measurement. For this reason, the instructions do not use the prepared
demo project/experiment, but only the variable description file contained in the
demo.

Preconditions The board must be registered. Refer to How to Register a dSPACE System on
page 25.

Method To measure variable values

1 Start ControlDesk.
2 On the File ribbon, click New - Project + Experiment to define a new
project/experiment.
The Define a Project dialog opens.
3 In the Define a Project dialog, enter a name for the new project.
Click Next > to open the Define an Experiment dialog.
4 In the Define an Experiment dialog, enter a name for the new experiment
and click Next > to open the Add Platform / Device dialog.

51
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

5 In the Add Platform / Device dialog, add the desired platform or device
and click Next > to open the Select Variable Description dialog.

6 In the Select Variable Description dialog, click Import from file to

navigate to the installation folder of your ControlDesk installation, select the
<platform>_demo.sdf variable description file for your real-time hardware
from the \Demos\RTApplications\<platform> folder and click Open.
For example,
select ..\Demos\RTApplications\DS1401\ds1401_demo.sdf for a
MicroautoBox II.

7 Click Finish.
The new project/experiment opens.

52
MicroAutoBox II Software Getting Started May 2024
 Experimenting with ControlDesk

8 In the tree view of the

Variables pane, navigate to <platform>_demo.sdf/Model
Root/SignalGenerator/SignalGenerator.

9 In the Variable list, select the SignalGenOutput variable and drag it to the
new layout.
10 In the Instrument Type list, click Time Plotter.

The Time Plotter opens. You have connected the SignalGenOutput

variable to the Time Plotter.

53
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

11 To display or change the properties of the Time Plotter, click the

instrument. The Properties pane shows the plotter properties.

12 Press F5 to measure the variable values.

The illustration below shows a running measurement.

13 To add another variable to your measurement, change to the Throttle

Controller variable group in the tree view of the Variables pane and select
the throttle valve position [%] variable in the Variable list.
14 Drag it to the Time Plotter.
15 The Restart Measuring dialog opens and asks you either to keep the
current measurement or to stop it and start a new one, because the added
variable cannot be measured until a restart is performed.

54
MicroAutoBox II Software Getting Started May 2024
 Experimenting with ControlDesk

Click Restart to perform the measurement again.

You have added another variable to your measurement.

With ControlDesk, you can perform triggered measurements on dSPACE

real‑time hardware. Triggered measurement means that data capture with a
measurement raster is not continuous, but started and stopped by triggers.
In the following steps, you will specify a start trigger (indicated by a
symbol), and a stop trigger (indicated by a symbol) for the measurement
raster.
16 In the Measurement Configuration pane, click Platform - 1ms - Platform
Trigger 1. The trigger currently is grayed.

55
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

17 Expand the Time Plotter to get a list of all plotted variables by clicking the
expand button in the lower right corner.

18 Drag the SignalGenOutput variable to the expanded Variable mappings

field as shown below.

56
MicroAutoBox II Software Getting Started May 2024
 Experimenting with ControlDesk

19 Make the specifications as shown in the following illustration:

Setting Value
Platform Trigger 1 checkbox Selected
Reference Value edit field 65
Delay [s] edit field (click the expand button if hidden) 0.1
20 In the Measurement Configuration pane, click Platform - 1ms -
Duration Trigger 1.
21 Make the specifications as shown in the following illustration:

Setting Value
Duration Trigger 1 checkbox Selected
Duration edit field 0.1 s

The plotter now displays the data stream of the variable values when
triggered.

57
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

22 On the File ribbon, click Save Project or press Ctrl + Shift + S to save the
project/experiment.

Result You have measured the values of the variables.

Next steps For instructions on changing the parameters of a running application with
ControlDesk, refer to How to Change Parameter Values of a Running Application
on page 58.

Related topics Basics

Demo Projects/Experiments and Related Files............................................................................ 50

HowTos

How to Change Parameter Values of a Running Application..................................................... 58

How to Change Parameter Values of a Running Application

Objective You can change the parameter values of a running application with ControlDesk.

Demo project/experiment For a short description of the demo project/experiment, refer to Demo
Projects/Experiments and Related Files on page 50.

58
MicroAutoBox II Software Getting Started May 2024
 Experimenting with ControlDesk

Preconditions The board must be registered. Refer to How to Register a dSPACE System on
page 25.

Method To change parameter values of a running application

1 Start ControlDesk.
2 On the File ribbon, click Open – Open Project + Experiment to open the
demo project/experiment.
ControlDesk opens the project/experiment together with all the related files
including the SDF file.
3 On the Home ribbon, click Status Control – Start Measuring.
4 Change to the throttle controller layout.

5 To change a parameter value while measuring, enter a new variable value:

In the value field of the f_Kd_1 variable, change the value from 0.001 to
0.002.
You can see that the plotter display changes slightly.

59
May 2024 MicroAutoBox II Software Getting Started
 Detailed Description for Working with a dSPACE System

You have changed the parameter values during the measurement.

Result You have changed parameter values of a running application.

Related topics Basics

Demo Projects/Experiments and Related Files............................................................................ 50

HowTos

How to Measure Variable Values............................................................................................... 51

60
MicroAutoBox II Software Getting Started May 2024
 Glossary

Glossary

Introduction Briefly explains the most important expressions and naming conventions used
when you get started with dSPACE systems in connection with ControlDesk.

Where to go from here Information in this section

A............................................................................................................. 62

B............................................................................................................. 62

C............................................................................................................. 62

D............................................................................................................. 63

E............................................................................................................. 64

F.............................................................................................................. 64

G............................................................................................................. 64

I.............................................................................................................. 64

L.............................................................................................................. 65

M............................................................................................................ 65

O............................................................................................................. 66

P............................................................................................................. 66

R............................................................................................................. 66

S............................................................................................................. 67

T............................................................................................................. 67

U............................................................................................................. 68

V............................................................................................................. 69

W............................................................................................................ 69

61
May 2024 MicroAutoBox II Software Getting Started
 Glossary

Acquisition An object in the Measurement Configuration pane in

ControlDesk that specifies the variables to be measured and their measurement
configuration.

Automatic Reconnect Feature for automatically reconnecting to

platform/device hardware, for example, when the ignition is turned off and on,
or when the physical connection between the ControlDesk PC and the ECU is
temporarily interrupted.
If the feature is enabled for a platform/device and if the platform/device is in the
'unplugged' state, ControlDesk tries to re-establish the logical connection to
the platform/device hardware. After the logical connection is re-established, the
platform/device has the same state as before the unplugged state was detected.
A measurement started before the unplugged state was detected is resumed.

Bus connection A mode for connecting dSPACE real-time hardware to the

host PC via bus. Bus connections can be used for dSPACE real-time hardware
installed directly in the host PC.

Calibration Changing the parameter values of real-time application s,

ECU applications, or VPUs.

cmdloader A command line tool for registering platforms and handling

applications without using the user interface of an experiment software.

Connected A platform/device state defined by the following characteristics:

§ A continuous logical connection is established between ControlDesk and the
platform/device hardware.
§ A platform/device must be in the 'connected' state before it can change to the
'measuring/recording' or 'online calibration started' state.
§ Online calibration is impossible. ControlDesk did not yet adjust the memory
segments containing calibration data in the platform/device and on the
corresponding hardware. Offline calibration is possible.
§ Platform/device configuration is not possible. However, you can invoke
platform/device configuration for a platform/device that is in the connected
state. ControlDesk temporarily sets the platform/device to the disconnected
state.
The 'connected' platform/device state is indicated by the icon.

62
MicroAutoBox II Software Getting Started May 2024
 D

Connection mode dSPACE real‑time systems can be installed within the host
PC or connected to the host via a bus interface and/or via Ethernet. When the
Ethernet is being used, different network clients might exist. The connection
type being used and, in the case of Ethernet, the network client being used,
determine the dSPACE systems that can be accessed.

Controller board Single‑board hardware computing the real-time

application. Contains a real-time processor for fast calculation of the model and
I/O interfaces for carrying out the control developments.

Disabled A platform/device state defined by the following characteristics:

§ No logical connection is established between ControlDesk and the
platform/device hardware.
§ When a platform/device is disabled, ControlDesk does not try to establish the
logical connection for that platform/device. Any communication between the
platform/device hardware and ControlDesk is rejected.
§ Online calibration is impossible. Offline calibration is possible.
§ Platform/device configuration is possible.
The 'disabled' platform/device state is indicated by the icon.

Disconnected A platform/device state defined by the following

characteristics:
§ No logical connection is established between ControlDesk and the
platform/device hardware.
§ When a platform/device is in the disconnected state, ControlDesk does not try
to re-establish the logical connection for that platform/device.
§ Online calibration is impossible. Offline calibration is possible.
§ Platform/device configuration is possible.
The 'disconnected' platform/device state is indicated by the icon.

Display An instrument (or a value cell type of the Variable Array ) for
displaying the value of a scalar variable or the text content of an ASCII variable.

Documents folder A standard folder for application‑specific files that are

used by the current user.
%USERPROFILE%\Documents\dSPACE\<ProductName>\<VersionNumber>

dSPACE system A hardware system such as MicroAutoBox II or MicroLabBox

on which a real-time application runs.

Duration trigger A trigger that defines a duration. Using a duration

trigger, you can, for example, specify the duration of data acquisition for a
measurement raster . A duration trigger can be used as a stop trigger only.

63
May 2024 MicroAutoBox II Software Getting Started
 Glossary

Environment model A model that represents a part or all of the ECU's

environment in a simulation scenario.

Ethernet connection A mode for connecting dSPACE real-time hardware

to the host PC via Ethernet. Ethernet connections are possible with
MicroAutoBox II/III and MicroLabBox/MicroLabBox II.

Expansion box A box that hosts dSPACE boards. It can be connected to the
host PC via bus connection or via network.

Experiment A container for collecting and managing information and files

required for a parameter calibration and/or measurement task. A number of
experiments can be collected in a project but only one of them can be active.

Firmware update An update for the firmware installed in the board’s flash
memory. Firmware should be updated if it is older than required by the real-time
application to be downloaded.

Flight recording The recording of data on dSPACE real-time hardware that

does not require a physical connection between the host PC and the real-time
hardware. In contrast to data logging, flight recording is not configured in
ControlDesk but via RTI and RTLib.

Gigalink module A dSPACE board for connecting several processor boards in

a multiprocessor system. The board allows high-speed serial data transmission via
fiber-optic cable.

Instrument An on-screen representation that is designed to monitor and/or

control simulator variables interactively and to display data captures. Instruments
can be arranged freely on layouts .

Instrument Navigator A pane that displays a tree with all the

instruments of the active layout and all the variables that are connected to

64
MicroAutoBox II Software Getting Started May 2024
 L

them. The Instrument Navigator's main function is easy selection of instruments

in complex layouts.

Instrument Selector A pane in ControlDesk that provides access to

instruments . The instruments can be placed on a layout via double-click
or drag & drop.

Interpreter pane A pane that can be used to execute line-based

commands. It is used by the Internal Interpreter to print out Python standard
error messages and standard output during the execution or import of Python
scripts.

Layout A page with instruments for visualizing, measuring, and

calibrating variables interactively.

Layout Navigator A pane that displays all opened layouts . It can be

used for switching between layouts.

Measurement Viewing and analyzing the time traces of variable s, for

example, to observe the effects of ECU parameter changes.
ControlDesk provides various instrument s for measuring variables.

Measurement Configuration A pane in ControlDesk that allows you to

configure measurement and recording.

Measurement raster Specification of how often a value of a variable is

updated during a measurement . A measurement raster is derived from a
measurement service.

Messages pane A pane displaying a history of all error and warning

messages that occur during work with ControlDesk.

MicroAutoBox platform A platform that provides access to a

MicroAutoBox II connected to the host PC for function prototyping purposes
such as bypassing.

65
May 2024 MicroAutoBox II Software Getting Started
 Glossary

Offline State in which the parameter values of hardware or a VPU in the

current experiment cannot be changed. This applies regardless of whether or not
the host PC is physically connected to the hardware.

Page An area in the ControlDesk working area to display and edit a

document, such as a layout , a Python script, or a signal description set .

Pane A separate area of the ControlDesk user interface that provides access
to a specific component, such as the Bus Navigator.

Parameter Any variable type that can be calibrated.

Platform A software component representing a simulator where a simulation

application is computed in real-time (on dSPACE real-time hardware) or in non-
real-time (on VEOS).

Platform trigger A trigger that is available for a platform and that is

evaluated on the related dSPACE real-time hardware or VEOS.

Platforms/Devices pane A pane that provides functions to handle devices,

platforms , and the applications assigned to the platforms.

Processor board A board that computes real-time applications. It has an

operating system that controls all calculations and communication to other
boards.

Project A container for collecting and managing the information and

files required for experiment/calibration/modification tasks in a number of
experiments . A project collects the experiments and manages their common
data.

Project pane A pane that provides access to projects and experiments

and all the files they contain.

Properties pane A pane providing access to the properties of, for

example, platforms/devices, layouts/instruments, and measurement/recording
configurations.

Real-time application An application that can be executed in real time on

dSPACE real‑time hardware. A real-time application can be built from a Simulink
model containing RTI blocks, for example.

66
MicroAutoBox II Software Getting Started May 2024
 S

Recorder An object in the Measurement Configuration pane in

ControlDesk that specifies and executes the recording of variables according to
a specific measurement configuration.

Recording Saving the time traces of variables to a file. Both measurement

variables and parameters can be recorded. Recorded data can be postprocessed
directly in ControlDesk.
A recording can be started and stopped immediately or via a trigger:
§ Immediate recording
The recording is started and stopped without delay, without having to meet a
trigger condition.
§ Triggered recording
The recording is not started or stopped until certain trigger conditions are met.
These conditions can be defined and edited in ControlDesk.

SDF file A file that describes a dSPACE simulation application, including the
contained parameters and measurement variables. SDF files are created during
the build process.

Signal description set A group of one or more signals.

A signal description set and its signals can be edited in the working area by
means of the Signal Editor. Each signal description set is stored as an STZ file
either in the Signal Description Sets folder or in the Signal Generators folder.

Single-processor system A system that is based on one dSPACE processor or

controller board.

Slave application An application assigned to the slave DSP of a controller

or I/O board. It is usually loaded and started together with the real-time
application running on the corresponding main board.

Slave DSP A DSP subsystem installed on a controller or I/O board. Its

slave application can be loaded together with the real-time application or
separately.

Stop trigger A trigger that is used, for example, to stop a measurement

raster .

Time Plotter A plotter instrument for displaying signals that are measured in
a time-based raster (time plots).

67
May 2024 MicroAutoBox II Software Getting Started
 Glossary

Topology A description of the processor boards belonging to a

multiprocessor system and their interconnections via Gigalinks. The topology
also contains information on which Gigalink port of each processor board is
connected to the Gigalink ports of other processor boards in the multiprocessor
system.
Topology information is contained in the real-time application (PPC/x86/RTA) files
of the multiprocessor system's processor boards.

TRC file A variable description file with information on the variables available
in an environment model running on a dSPACE platform .

Trigger A condition for executing an action such as starting and stopping a

measurement raster or a recorder .
The generic term for the following services:
§ Duration trigger
§ Platform trigger

Unplugged A platform/device state defined by the following characteristics:

§ The logical connection between ControlDesk and the hardware was
interrupted, for example, because the ignition was turned off or the
ControlDesk PC and the hardware were disconnected.
§ Before the state of a platform/device changes to 'unplugged', the
platform/device was in one of the following states:
§ 'Connected'
§ 'Online calibration started'
§ 'Measuring' / 'Recording'

Tip

A device for which the connection between ControlDesk and the device
hardware currently is interrupted is also set to the 'unplugged' state when
you start online calibration if both the following conditions are fulfilled:
§ The device's Start unplugged property is enabled.
§ The Start online calibration behavior property is set to 'Ignore
differences'.
This is possible for CCP and XCP devices. For details on the two properties
listed above, refer to General Settings Properties (ControlDesk Platform
Management ).

§ If the Automatic Reconnect feature is enabled for a platform/device and if the

platform/device is in the 'unplugged' state, ControlDesk periodically tries to
re-establish the logical connection for that platform/device.
§ Online calibration is impossible. Offline calibration is possible.
§ Platform/device configuration is possible.

68
MicroAutoBox II Software Getting Started May 2024
 V

The 'unplugged' platform/device state is indicated by the icon.

Variable Any parameter or measurement variable defined in a variable

description . ControlDesk provides various instrument s to visualize variables.

Variable Array An instrument for calibrating parameters and displaying

measurement variable values.
The Variable Array can be used for the following variable types:
§ Measurement ( )
§ Measurement array ( )
§ String ( )
§ Struct ( )
§ Struct array ( )
§ Value ( )
§ Value block ( )

Variable description A file describing the variables in a simulation

application, which are available for measurement, calibration, and stimulation.

Variables pane A pane that provides access to all the variable

descriptions and calculated variables of the currently open experiment .

Working area An area of the user interface of ControlDesk where you can
edit documents, such as layouts , Python scripts, or signal description sets .
Each document is displayed on a separate page .

69
May 2024 MicroAutoBox II Software Getting Started
 Glossary

70
MicroAutoBox II Software Getting Started May 2024
 Index
Index
Properties pane 66
C
C-coded models 42 R
clearing application from flash memory 48 real-time application
Common Program Data folder 6 clearing from flash memory 48
CompactFlash card CompactFlash card 47
handling applications 47 flash memory 47
ControlDesk program memory 44
overview 23 registering
starting 23 dSPACE system 25
custom firmware 32 reloading application to global memory 46

D S
default factory firmware 32 SDF file 50
Documents folder 6, 63 Simulink model
down1401 42 handling 39
downloading starting
to global memory 44 ControlDesk 23
dSPACE system starting ControlDesk 23
registering 25 stopping application 45

E T
experimenting TRC file 50
with ControlDesk 50
U
F user firmware 32
firmware using ControlDesk 51
updating in secured mode 32
flash memory V
clearing application 48
viewing
handling applications 47
system properties 30
loading and starting application 47

G
global memory
reloading an application 46
stopping an application 45

I
implementing C models 42
Instrument Selector 65

L
loading
to flash memory 47
Local Program Data folder 6

M
MABXFwArchive 31
MAP file 50
Messages pane 65

P
Platforms/Devices pane 66
program memory
downloading and starting application 44
handling applications 44
Project pane 66

71
May 2024 MicroAutoBox II Software Getting Started
 Index

72
MicroAutoBox II Software Getting Started May 2024