Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

dSPACE SCALEXIO Architecture

ComponentSpecificationNotes
Processing Unit (PU)Intel Xeon E5-2600; 8 cores; QNX RTOSRuns Simulink-generated C code; 1 us step achievable
FPGA board (DS6001)Xilinx Kintex UltraScale; 250 MHzPWM capture/gen, encoder, VRS, crank/cam at 4 ns resolution
DS2680 I/O module48x analog I/O (16-bit); 64x digital I/OGeneral-purpose; +/-16V range; 1 MS/s
DS2655M FPGA moduleXilinx FPGA + 64x flexible I/O channelsConfigurable: PWM, encoder, freq, serial per channel
DS4340 bus board8x CAN FD, 4x LIN, 2x FlexRayReal-time bus simulation; tight timing synchronisation
DS5640 Ethernet2x 1GbE, 2x 100BASE-T1SOME/IP, DoIP, Ethernet/IP real-time simulation
ConfigurationDeskGUI: hardware configuration, I/O mappingGenerates RTLib variables from hardware configuration
ControlDeskGUI: instrument panels, data logging, scriptingRuns on host PC; connects to PU via XCP

ControlDesk Python Automation

Pythoncontroldesk_automation.py
#!/usr/bin/env python3
# dSPACE ControlDesk automation via COM API
# Requires ControlDesk 7.x on Windows

import win32com.client as win32
import time

def run_hil_test_sequence(test_scenarios):
    cd  = win32.Dispatch("ControlDesk.Application")
    app = cd.ActiveExperiment.Platforms[0].Applications[0]

    results = []
    for scenario in test_scenarios:
        print(f"Running: {scenario['name']}")

        # Set plant parameters
        for path, value in scenario.get("parameters", {}).items():
            app.Variables[path].Value = value

        # Start and wait
        cd.ActiveExperiment.Platforms[0].Start()
        time.sleep(scenario.get("duration_s", 10))

        # Check outputs
        result = {"name": scenario["name"], "pass": True}
        for name, (path, expected, tol) in scenario.get("checks", {}).items():
            actual = app.Variables[path].Value
            ok = abs(actual - expected) <= tol
            if not ok:
                result["pass"] = False
                print(f"  FAIL: {name}={actual:.3f} (exp {expected} +/-{tol})")

        cd.ActiveExperiment.Platforms[0].Stop()
        results.append(result)

    return results

Summary

dSPACE SCALEXIO is the most common enterprise HIL platform in automotive OEM and Tier-1 development. Its key differentiator is the tight integration between Simulink, Embedded Coder, Real-Time Interface (RTI), and ControlDesk. The ControlDesk Python automation API enables fully scripted test execution - essential for CI/CD pipeline integration. The FPGA board handles all time-critical I/O (crank/cam, PWM, encoder) with 4 ns resolution, independent of the main CPU model execution timing.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

  • Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
  • Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
  • Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

  • Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
  • Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
  • Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

  1. Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
  2. Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
  3. Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
  4. Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.

← PreviousHands-On: Engine Plant ModelNext →ETAS LABCAR Configuration