Sim racing
The whole cockpit through all six axes, plus the duty cycle of an esports venue or a lounge running back-to-back sessions.
Industries
One platform.
Twelve contexts.
The PDK is a six-axis motion platform with an open interface. What changes between a racing cockpit, a vestibular laboratory and a driver-in-the-loop rig is not the hardware — it is what you mount on it, what drives it, and which of its properties you actually care about.
The twelve
Pick the one that matches your work.
Each page states what that field needs, how the platform meets it, and — where it applies — what it is not qualified to do.
Flight simulation
Sustained attitude with airframe texture written over it — and a plain statement of what the PDK is not certified to be.
Aerospace and defence
The hexapod architecture beneath certified simulators, at research-instrument scale. Your cueing algorithm stays in your stack.
Research and industry
Laboratories, programmes and production.
Automotive
Driver-in-the-loop for vehicle dynamics, ADAS and AV validation, and HMI studies, at lab scale rather than proving-ground scale.
Academic research
Citable specifications, reproducible motion delivery, and an open interface — a platform that survives a methods section.
Medical and vestibular
Vestibular, balance and postural work with pure-axis isolation a single-axis chair cannot deliver.
Applied
Where motion is the product.
XR and VR
Physical motion that grounds virtual immersion, and the latency question that decides whether it helps or hurts.
Robotics and industrial
A programmable 6-DOF stage for operator training, motion R&D and hardware-in-the-loop work.
Active gaming
Full-body motion as the thing that gets people off the couch, and what a venue needs from it.
Specialist
Narrower fields, same platform.
Maritime
Sea-state motion for antenna, radar and navigation research, and for crew familiarisation.
Education
A teaching instrument for parallel kinematics, real-time control and field-oriented motor control.
Entertainment
Attractions and location-based experiences, where throughput and uptime decide the economics.
Does it fit your work
The same numbers, whichever field you came from.
Twelve pages describe twelve contexts, but the instrument underneath them does not change. These are the figures that decide whether it suits your study before you read any of them — what it moves, what it carries, and what it accepts as a command.
Motion
Nominal envelope
Single-axis limits with every other axis at neutral. Parallel kinematics means the axes trade against one another, so no axis reaches its maximum while the others are working — a combined pose is always smaller than the table suggests.
| Axis | Range | Total span |
|---|---|---|
| Surge | −75.49 … +82.74 mm | 158.23 mm |
| Sway | ± 71.92 mm | 143.85 mm |
| Heave | ± 58.68 mm | 117.35 mm |
| Pitch | −7.98° … +8.09° | 16.07° |
| Roll | ± 8.68° | 17.36° |
| Yaw | ± 9.80° | 19.60° |
Load and command
What it carries, what it accepts
The interface is the reason one platform serves twelve fields: a six-axis pose arrives over UDP and the platform executes it. Your cueing algorithm, vehicle model or experimental-control software stays where it is.
| Payload | up to 250 kg |
|---|---|
| Platform mass | 115 kg |
| Footprint | 1.00 × 1.00 m platform · 1.20 × 1.00 m for the PDK Racer (the chassis extends one face by 200 mm) · retracted height 0.50 m |
| Command interface | Six-axis pose over UDP · FlyPT Mover (third-party) or your own code |
| Feedback | 6 × 21-bit magnetic encoders · 0.000171661° per count |
| Internal rates | Drive loop 8 kHz per motor · position commands 1 kHz — internal to the platform, not a telemetry promise to your PC |
Envelope read from the T1 firmware boot banner, 2026-07-07 capture. A combined-axis “extended” envelope is larger, and it is published when it is measured. The platform is a research-grade instrument at lab scale: it is not a certified simulator, not a proving-ground rig, and no page here claims a qualification it does not hold. How the figures were derived ›
What they share
An open interface,
and no vendor
in the middle.
Every one of these fields already has a toolchain. The PDK takes a six-axis pose over UDP and executes it, which means your cueing algorithm, your vehicle model or your experimental-control software stays where it is. There is no proprietary layer you have to adopt, and nothing between your command and the platform that we will not describe.
Keep reading
The engineering
Ten pages, one subject each — architecture, control, measurement and the numbers we will not publish yet.
The Ecosystem
What you actually receive, what it costs, and what you assemble yourself.
Talk to us
For a deployment, a programme, or an integration question a page cannot answer.