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.
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.
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 Simulink® models.
Product demonstration of how to integrate virtual ECUs on the HIL simulation system SCALEXIO® by using ConfigurationDesk.
Product demonstration of how to integrate Functional Mock-up Units into an existing model by using ConfigurationDesk.
ConfigurationDesk is an intuitive, graphical configuration and implementation tool. It is ideal for handling HIL real-time applications, 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 (e.g., from MATLAB®/Simulink®/Simulink Coder™) and the I/O function code (from ConfigurationDesk) on the dSPACE SCALEXIO hardware. The entire build process for a real-time application is handled by ConfigurationDesk. Comprehensive documentation options and graphical displays give you great project transparency – a great advantage with large-scale HIL projects especially. You can assemble and configure the project-specific hardware offline 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 wiring harness and on external devices.
ConfigurationDesk provides two approaches for integrating Simulink® models:
SICs are ZIP containers including the C code and other artifacts, such as precompiled libraries and a model interface description.
With the two ways of importing Simulink models, ConfigurationDesk always provides the best solution for your project needs and requirement.
To make exchanging simulation models easy, dSPACE offers a Model Interface Package for Simulink® (MIPS) for generating Simulink implementation container (SIC) files.
With the free-of-charge MIPS, modeling experts can generate the (C code) SIC file with Simulink Coder, without needing a VEOS or ConfigurationDesk license. Out of their Simulink models and together with dSPACE Run-Time Target, they can generate code and create ZIP files that contain all the necessary code and artifacts for executing the models on different simulation platforms, such as VEOS and SCALEXIO®.
Model integrators using SIC files do not have to generate code again for building the simulation. Using SICs therefore significantly reduces the amount of time needed for reusing the SICs in different projects.
|I/O configuration and documentation||
|Real-time code generation||
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.