SDK built and documented by the engineers who designed the platform.
ForceSeatMI is the application-level SDK for telemetry streaming. ForceSeatDI is the direct-control interface for embedded systems, Linux and Raspberry Pi. C, C++, C#, Python, Unity, Unreal Engine. One API across the Qubic and Professional Series lineup, kept stable across hardware generations, with docs open to read before any order and engineering support for both layers.
Flexible Control Integration
Choose the level of abstraction that fits. ForceSeatMI is recommended for nearly all integrations; ForceSeatDI is for the few cases needing direct, below-the-manager control.
Telemetry Data Mode
Send vehicle telemetry through ForceSeatMI; ForceSeatPM and the motion controller turn it into coordinated motion across up to six axes (Pitch, Roll, Yaw, Heave, Surge, Sway), with inverse kinematics and work-envelope limits applied automatically.
FSMI_TelemetryACE t;t.structSize = sizeof(t);t.bodyLinearAcceleration; // m/s²t.bodyAngularVelocity; // rad/sBest for: simulation integrators, game developers
Direct Interface (DI)
Talk straight to the controller with ForceSeatDI, below the ForceSeatPM layer. Best for embedded systems, Linux and Raspberry Pi, and applications that need direct low-latency hardware control.
FSDI_TopTablePositionPhysical p;p.structSize = sizeof(p);p.roll = deg2rad(10); // radp.heave = 50; // mmBest for: embedded targets, direct hardware control
A minimal telemetry loop
in about ten lines.
The motion API takes a few calls to wire up: one call to connect, one struct to fill, and frames are flowing. Most integrations reach a moving platform within the first few days.
// C++ SDK Initialization#include "ForceSeatMI_Functions.h" FSMI_Handle api = ForceSeatMI_Create();ForceSeatMI_ActivateProfile(api, "SDK - Vehicle Telemetry ACE");ForceSeatMI_BeginMotionControl(api); FSMI_TelemetryACE t = {0};t.structSize = sizeof(t);t.bodyLinearAcceleration.forward = 2.0f; // m/s² ForceSeatMI_SendTelemetryACE(api, &t);ForceSeatMI_EndMotionControl(api);ForceSeatMI_Delete(api);// C# (Unity) - ForceSeatMI_Unity + ForceSeatMI_Vehiclepublic class VehicleController : MonoBehaviour { Rigidbody m_Rigidbody; ForceSeatMI_Unity m_Api; ForceSeatMI_Vehicle m_vehicle; void Start() { m_Api = new ForceSeatMI_Unity(); m_vehicle = new ForceSeatMI_Vehicle(m_Rigidbody); m_Api.ActivateProfile("SDK - Vehicle Telemetry ACE"); m_Api.SetTelemetryObject(m_vehicle); m_Api.Begin(); } // After Begin(), the API pulls telemetry from the Vehicle automatically void OnDestroy() { m_Api.End(); }}# Pythonfrom ForceSeatMI import * fsmi = ForceSeatMI()fsmi.activate_profile("SDK - Vehicle Telemetry ACE")fsmi.begin_motion_control() t = FSMI_TelemetryACE()t.structSize = sizeof(FSMI_TelemetryACE)t.bodyLinearAcceleration.forward = 2.0 # m/s² fsmi.send_telemetry_ace(t)fsmi.end_motion_control()Motion Platform SDK Documentation
From a first "Hello World" build to a running motion deployment.
Designed for
Advanced R&D
The platform is fully programmable and reports its own motion state. Research institutes and universities use the SDK for MATLAB®/Simulink® integration, pilot training validation, and haptics research. Korea University of Technology and Education runs Driver-in-the-Loop studies with the ForceSeatMI/DI SDK; NTU Singapore uses a PS-3TM-350 for 5G teleoperation research.
Control & Readout Programmatic motion control and platform-state readout that researchers correlate offline with the external measurement systems in their lab.
Position & Diagnostics Turn off the washout filters and command exact platform positions. Capture the actuator positions reported by the controller for mechanical-response analysis.
TIME_S ROLL_RAD PITCH_RAD YAW_RAD HEAVE_MM SWAY_MM SURGE_MM0.000 0.008 0.010 0.003 11.2 2.4 4.10.004 0.011 0.018 0.005 12.5 3.1 5.00.008 0.015 0.025 0.007 13.8 3.8 5.90.012 0.019 0.033 0.009 15.1 4.5 6.80.016 0.022 0.040 0.011 16.4 5.2 7.70.020 0.026 0.048 0.013 17.7 5.9 8.60.024 0.029 0.055 0.015 19.0 6.6 9.5Features comparison
ForceSeatMI covers the vast majority of integrations. Reach for ForceSeatDI when the project needs Linux, a Raspberry Pi, Ethernet-controlled platforms, or direct control without ForceSeatPM in the loop.
| Feature | ForceSeatMI | ForceSeatDI |
|---|---|---|
| C/C++ | ||
| C# | ||
| Python | ||
| Unity 3D | only Windows PC target platform | only Windows PC target platform |
| Unreal Engine | only Windows PC target platform | only Windows PC target platform |
| Matlab® / Simulink® | ||
| Microsoft Windows | ||
| LinuxUbuntu 24.04.4 LTS Desktop x64 | ||
| Raspberry Pi 3armv7l 4.9.35 | ||
| Raspberry Pi 4 64-bitARMv8-A 6.1.5 | ||
| Gear VR platformse.g. Oculus Go, Samsung Gear VR | ||
| Multiple platforms from a single PCover USB | same data sent to all platforms | separated control of each platform |
| Multiple platforms from a single PCover Ethernet | ||
| Easy error handling | by ForceSeatPM | by the application |
| Diagnostic features | by ForceSeatPM | by the application |
| Requires ForceSeatPM | ||
| Telemetry mode & scripting engine | ||
| Motion profile selection by the user | ||
| Inverse kinematics | ||
| Forward kinematics | ||
| Motion compensation for VR | by VR HeadWay in ForceSeatPM | by the application, e.g. camera position correction |
| Licensing | per motion platform (license stored on PC) | per motion platform (license stored on motion controller) |
Describe the project being built.
Quick question or a full simulator project - the team reads everything.
What happens next?
Confirmation & initial review
A dedicated account manager reads the message directly.
Technical assessment
The team analyzes feasibility and prepares questions or an initial concept.
Proposal delivery
Detailed technical proposal with a platform recommendation, transparent pricing, lead time, and integration timeline.
Team support
Ongoing support from the team behind the recommended platform - for the life of the project.