How Outputs Work

An output is the final step in the motion processing chain — it takes the actuator positions calculated by the Sim Config and transmits them to your physical motion controller hardware. This page explains how the output system works and the different types available.

What Is an Output?

An output is a communication bridge between DR Sim Manager and a motion controller (or other device). After the motion cues produce desired platform motion and the Sim Config calculates individual actuator positions, outputs deliver those positions to your hardware in the format it expects.

Each output type uses a different communication method (serial, UDP, shared memory, etc.) and data format matched to the target controller.

Output Types

Serial Outputs

Serial outputs send actuator positions over a USB serial (COM port) connection. This is the most common output type for motion controllers. DRSM supports several controller-specific serial formats:

Thanos Controller — For Thanos AMC and 4U motion controllers
M4S Controller — For Motion4Sim controllers
DMover Controller — For DMover motion platforms (4 or 6 actuators)
SMC3 Serial — For SMC3-based DIY controllers
VNM Controller — For VNM motion platforms (up to 9 channels)
Generic Serial Output — A fully configurable serial output for custom or DIY controllers. You define the data format, baud rate, prefix/suffix bytes, and axis mapping.

UDP Outputs

UDP outputs send actuator positions over a network connection as UDP packets. These are useful for:

Wireless controller setups
Controllers on a separate PC
Custom hardware that accepts network input
YawVR simulators (which use a network protocol)

The generic UDP output offers the same level of configurability as the generic serial output — you define the data format, destination address, port, and axis mapping.

Memory-Mapped File (MMF)

Memory-mapped file outputs share actuator data through a shared memory region on the local PC. This is used for software-to-software integrations where another application running on the same machine needs to read DRSM’s motion output.

Virtual Tracker

The Virtual Tracker output generates VR motion compensation data. It communicates the platform’s current position and orientation to OXRMC (OpenXR Motion Compensation) or OVRMC (OpenVR Motion Compensation), which adjust the VR headset’s tracking to cancel out the real-world motion of the simulator. This keeps the virtual world stable even as your platform moves.

Teleplot

The Teleplot output streams real-time motion data to Teleplot, an open-source data visualization tool. This is invaluable for debugging and tuning — you can see live graphs of actuator positions, telemetry values, and cue outputs to understand exactly what DRSM is doing at any moment.

Axis Mapping

Each output has an axis mapping configuration that connects sim component actuators to output channels. For example, if your Thanos controller expects actuator 1 on channel 1 and actuator 2 on channel 2, you map them accordingly in the output settings.

Axis mapping lets you:

Match actuator numbering between DRSM and your controller
Select which sim component each channel reads from (important when you have multiple sim components)
Invert axes if an actuator is mounted in the opposite direction
Rearrange channels without rewiring physical connections

Update Rate

Outputs send position updates at the configured refresh rate — up to 500 times per second (500 Hz). The update rate is set globally in Settings and applies to all active outputs.

Higher update rates produce smoother motion but require your controller hardware to accept data at that speed. Most modern controllers (Thanos, M4S) handle 500 Hz without issues. Older or DIY controllers may need a lower rate.

Some output types also have their own configurable output rate (in milliseconds) for fine-tuning the transmission frequency to match controller requirements.

Multiple Simultaneous Outputs

You can run multiple outputs at the same time. Common combinations include:

Serial output for the motion platform + Virtual Tracker for VR motion compensation
Serial output for the platform + UDP output for a remote visualization
Serial output for motion + Teleplot for real-time debugging
Multiple serial outputs for different controllers (e.g., one for the hexapod, one for bass shakers)

Each output operates independently and can be connected to different sim components. Add outputs by clicking the + tab on the Outputs page.

Connection Lifecycle

DRSM handles output connections automatically:

Auto-detection: Serial outputs scan available COM ports and can auto-detect your controller
Auto-reconnect: If a connection is lost (cable unplugged, controller reset), DRSM will attempt to reconnect automatically
Error handling: Connection errors are logged and displayed in the status bar. The motion system continues running on remaining outputs if one output fails
Startup/Shutdown strings: Serial and UDP outputs support optional byte strings sent when the connection opens or closes — useful for initializing or parking your controller hardware

Configuring an Output

Navigate to the Outputs tab
Click the + tab and select the output type from the list
Configure connection settings (COM port, baud rate, IP address, etc.)
Set up axis mapping to connect sim component actuators to output channels
Click Start Motion on the Sources tab to begin sending data

For detailed setup instructions for each output type, see the individual output pages under Outputs.