Modern simulation systems are complex. They often combine real-time physics models, hardware interfaces, high-speed data logging, and deterministic control loops. Building and managing that environment from scratch is difficult and error-prone.

SIMulation Workbench (SimWB) offers a unified solution. It is a simulation framework that helps engineers build, test, and execute models with deterministic timing. Whether you are simulating a flight controller, validating an automotive subsystem, or developing control logic for industrial machinery, SimWB provides the tools to make your models run with real-world fidelity.

SimWB is more than a modeling tool. It is a full runtime environment that manages the execution of simulation models alongside real-time I/O and scheduling. Built on top of RedHawk Linux, it ensures predictable execution with microsecond-level timing precision.

Developers can load models created in environments like MATLAB/Simulink, C/C++, or Python. These models are then compiled and executed within the SimWB framework, which handles:

  • Scheduling model steps in precise cycles
  • Synchronizing data between model and hardware
  • Managing real-time threads and I/O latency
  • Logging simulation data without disrupting execution

SimWB supports both Software-in-the-Loop (SiL) and Hardware-in-the-Loop (HiL) configurations, making it ideal for iterative development, integration testing, and full system validation.

SimWB includes a graphical interface that lets users manage simulations without needing to write scripts or edit configuration files. From the control panel, users can:

  • Load models and configure inputs and outputs
  • Start, stop, or pause simulation cycles
  • View live variable values
  • Set breakpoints or override inputs
  • Launch post-processing tools

Simulations often need to connect with the outside world. SimWB supports a wide range of hardware interfaces, including:

  • Analog and digital I/O
  • CAN, ARINC, and MIL-STD-1553 buses
  • Serial and Ethernet devices
  • FPGA-based expansion cards
  • Custom drivers via open APIs

SimWB is designed to grow with your project. Whether you’re running a single simulation on a desktop system or managing a network of synchronized nodes in a large-scale testbed, SimWB can scale accordingly.

It supports distributed execution, allowing components of a simulation to run on separate machines while remaining tightly synchronized. This is especially helpful in scenarios where I/O, compute, and model logic need to be separated for performance or architecture reasons.

  • SIMulation Workbench is used across industries that require real-time modeling, such as:
  • Aerospace: Flight control system simulation, pilot training environments
  • Defense: Weapon system simulation and sensor integration
  • Energy: Grid simulation and fault injection testing
  • Robotics: Real-time kinematic and path planning validation

Engineers rely on SimWB to run test scenarios with hardware in the loop, validate safety-critical logic, and ensure that simulated environments behave as close to reality as possible.

Related Articles

  • Diagram showing software staying the same while hardware changes: Guest OS + Application on RedHawk KVM-RT Host, with Hardware Gen 1 retired, Gen 2 in production, and Gen 3 planned refresh.

    Preserving Legacy Real-Time Applications Through Virtualization

    Preserving Legacy Real-Time Applications Through Virtualization Real-time applications often remain in service much longer than the hardware on which they were originally developed. Test systems, industrial controls, simulation environments, and data-acquisition platforms…

    Read more

  • Diagram comparing native RedHawk Linux (left) and RedHawk KVM-RT virtualization (right) with application layer and real-time workload on both sides.

    Native Real-Time Linux vs. Real-Time Virtualization: Which Architecture Fits Your Application?

    Native Real-Time Linux vs. Real-Time Virtualization: Which Architecture Fits Your Application? Virtualization is now common in enterprise computing, but timing-sensitive systems introduce requirements that conventional IT workloads do not share. An application may…

    Read more

  • Diagram of NUMA placement: keep Cores, Memory, and PCIe device in one node (local placement). Cross-node placement is discouraged (Node 0 and Node 1).

    How CPU Shielding, NUMA, and Interrupt Affinity Affect Real-Time Virtual Machines

    How CPU Shielding, NUMA, and Interrupt Affinity Affect Real-Time Virtual Machines Running a real-time operating system inside a virtual machine does not automatically create a deterministic environment. The virtual machine still depends…

    Read more