For a better experience on, enable JavaScript in your browser. Thank you!


Configuration and implementation software for dSPACE SCALEXIO® hardware

ConfigurationDesk is an intuitive, graphical configuration and implementation tool, ideal for handling large HIL real-time applications based on SCALEXIO hardware, and for implementing behavior models and I/O function code on SCALEXIO hardware. ConfigurationDesk provides a clearly arranged overview of the external devices (e.g., ECUs), configured SCALEXIO channels, and the connected behavior models. 

  • Support of Simulink Implementation Containers

    ConfigurationDesk supports two approaches for working with Simulink models. Besides the direct import of MDL files, now Simulink implementation containers (SICs) can be generated. SICs contain the model C code and other artefacts, such as precompiled libraries and a model interface description.

    Read more

  • Support for Functional Mock-up Units

    ConfigurationDesk supports the open Functional Mock-up Interface (FMI) standard. This enables the users to use different modeling approaches (e.g., based on physical modeling with Modelica) by using Functional Mock-up Units (FMUs). In HIL projects, FMUs can be integrated together with V-ECUs and Simulink® models.

    The user workflow for importing and connecting FMUs to other model interfaces and to I/O is identical to the workflow for V-ECUs and Simulink® models.

  • Importing Virtual ECUs

    In ConfigurationDesk, you can integrate virtual ECUs (V-ECUs) into a real-time application just like any other behavior model. With the SCALEXIO real-time hardware, V-ECUs can be simulated alone or in combination with real ECUs. The V-ECUs can contain CAN or LIN controllers to simulate CAN or LIN bus communication between the ECUs.

  • ConfigurationDesk for Virtual Validation

    Product demonstration of how to integrate virtual ECUs on the HIL simulation system SCALEXIO® by using ConfigurationDesk.

    Read more

  • Example Workflow for FMI

    Product demonstration of how to integrate Functional Mock-up Units into an existing model by using ConfigurationDesk.

Application Fields

ConfigurationDesk is an intuitive, graphical configuration and implementation tool. It is ideal for handling HIL real-time applications based on dSPACE SCALEXIO hardware, and for implementing behavior models and I/O function code on dSPACE SCALEXIO hardware. You can define and document external devices such as ECUs and loads, including their signal properties (descriptions, electrical properties, failure simulation settings, load settings). ConfigurationDesk displays user-defined views of the signal path between the ECU pins/load pins and the behavior model interfaces.


With ConfigurationDesk, it is easy to implement the behavior model code (from MATLAB®/Simulink®/Simulink Coder™ or other modeling tools via FMUs or V-ECUs) and the I/O function code (from ConfigurationDesk) on the dSPACE SCALEXIO hardware. ConfigurationDesk handles the entire build process for a real-time application. Comprehensive documentation options and graphical displays give you high project transparency – a great advantage, especially with large-scale HIL project. You can assemble and configure the project-specific hardware as a virtual system, in other words, as a purely software-based configuration. A real-time application can be executed for test runs even if parts of the necessary (and configured) I/O hardware are not physically available. In addition, you can generate a Microsoft® Excel® file with information on the cable harness and external devices.

Functionality Description
I/O configuration and documentation
  • I/O configuration for connecting a MATLAB®/Simulink® behavior model to dSPACE SCALEXIO hardware:
    • External device topologies (properties of ECU pins and load pins)
    • Device port mapping (connections between the ECU/load pins and the signal ports of an I/O function)
    • I/O functions (describe the functionality between a set of external device ports and a set of model ports independently of the hardware topology)
    • Model port mapping (connections between function ports and model ports)
    • Model topology (model ports used for the ConfigurationDesk application)
    • Hardware resource assignment (mapping I/O functions to hardware resources)
    • Hardware topology (hardware resources used by I/O functions)


    • External device topologies (properties of ECU pins/load pins)
    • Model topology (describes the interface to the MATLAB/Simulink model)
    • Hardware topology (describes the simulator hardware: boards, internal wiring, internal loads, board locations, ...)
    • Microsoft® Excel® file with pin information for external wiring harnesses
    • CAN and LIN signals are configured with the RTI CAN MultiMessage Blockset and the RTI LIN MultiMessage Blockset. FlexRay nodes are configured with the dSPACE FlexRay Configuration Package.
Real-time code generation
  • Complete build process for I/O functions (ConfigurationDesk) and the behavior model (MATLAB/Simulink/Simulink Coder)




Large, complex models can be distributed across multiple processing units and processor cores to ensure the simulation runs in real time. Two different workflows are possible for this. The first is to use separate Simulink® models for each core and import them into ConfigurationDesk. Intermodel communication in this workflow is configured in ConfigurationDesk.

In the second workflow, there is one overall Simulink® model for the whole application, and a special Simulink block is used to specify which of its subsystems should be computed together on one core. The overall model is then automatically split into separate model files. Intermodel communication in this workflow is transferred from Simulink® to ConfigurationDesk.
One processor core executes one model. Several models are combined to processing-unit applications. These can be assigned to processing units in ConfigurationDesk, which automatically performs the core-to-model assignment within each unit.
One processing unit consists of several processor cores. One processor core in each processing unit is always reserved for communication with the host PC. The other cores can be used for behavior model calculation.