Sim racing
The whole cockpit through all six axes, for long back-to-back development sessions.
Portal Development Kit (PDK): this is a development kit.
Uses
The Portal Development Kit (PDK) is a development kit for developers, integrators and research partners: a six-axis motion simulator with an open interface for everyone who builds on it. 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.
Development Kit: early-access hardware, software in active development.
The twelve
Each page states what that field asks of a motion platform and — where it applies — what the PDK is not qualified to do.
The whole cockpit through all six axes, for long back-to-back development sessions.
Sustained attitude with airframe texture written over it — and a plain statement of what the PDK is not certified to be.
Physical motion that grounds virtual immersion, and the latency question that decides whether it helps or hurts.
Research and industry
Driver-in-the-loop for vehicle dynamics, ADAS and AV research, and HMI studies, at lab scale rather than proving-ground scale.
Published specifications and an open interface for motion research.
Vestibular, balance and postural work with pure-axis isolation a single-axis chair cannot deliver.
Applied
The hexapod architecture beneath certified simulators, at research-instrument scale. Your cueing algorithm stays in your stack.
A programmable 6DOF stage for motion R&D and hardware-in-the-loop work.
Full-body motion for active-gaming development.
Specialist
Sea-state motion for antenna, radar and navigation research.
A teaching instrument for parallel kinematics, real-time control and field-oriented motor control.
Development for attractions and location-based experiences.
Does it fit your work
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
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.
| 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
The interface is the same in every field: 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.57 m in diameter with the extension feet · 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 |
| Loop rates | Game to motion 1 kHz · control loop 3.3 kHz · drive loop 8 kHz per motor — none is a telemetry rate to your PC |
Envelope read from the T1 firmware boot banner, 7 July 2026 capture. A combined-axis “extended” envelope is not published. The PDK is supplied as a development kit, 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
Every one of these fields already has a toolchain. There is no proprietary layer you have to adopt.
Keep reading
Ten pages, one subject each — architecture, control, measurement and the numbers we will not publish yet.
What you actually receive, what it costs, and what you assemble yourself.
For a question a page cannot answer.