- Home
- Technology
- How a 6DOF Motion Platform Works
Motion platform technology · Working principle
How a 6DOF Motion Platform Works
Most explanations stop at six arrows on a diagram. That tells you what a platform may move, not how it moves — or why two platforms with the same six arrows behave nothing alike under the same payload. This guide follows one commanded pose through the mechanism, the mathematics and the controller, then shows you how to read a 6DOF spec sheet without being misled by it.
Technical guide · Reviewed by the CSCmotion Motion Control Engineering Team · Updated October 4, 2026 · Reading time ~17 min
Fig. 1 · One pose, six lengths. The controller never commands a leg directly. It commands a platform pose; geometry decides what each of the six legs must do.
6
Controlled degrees of freedom
The complete set for one rigid body.
6
Coupled actuators
No leg owns an axis; no axis can be sized alone.
1
Answer per pose
Inverse kinematics: pose in, six lengths out.
0
General closed-form formulas
Forward kinematics must be solved numerically.
Start with three separate ideas
What Is a 6DOF Motion Platform
A six-degree-of-freedom motion platform is a mechatronic system that controls the position and orientation of a moving rigid body. That is the definition. The correction most buyers need is the next sentence: 6DOF describes a motion capability, not a machine. It says nothing about the mechanism, the actuators, the controller or how the motion was verified.
Direct answer
A complete 6DOF motion platform combines a load-bearing parallel mechanism, six actuators with their drives, a motion controller running kinematics in real time, position feedback, software limits, a host interface and an agreed verification method. The mechanism produces useful motion only when all of those layers behave as one system.
01
6DOF describes motion
X, Y and Z define translation; roll, pitch and yaw define orientation. Together they fully describe the pose of a rigid body.
02
Stewart describes a mechanism
Six variable-length limbs connect a moving platform to a fixed base in parallel. The most common route to 6DOF, not the only one.
03
Motion platform describes a system
Structure, actuators, controller, interface, limits, feedback and the acceptance method. Buy the system, not the arrow diagram.
Two distinctions worth keeping. Serial robot arms also reach six axes, so not every 6DOF mechanism is a Stewart platform. And precision positioning hexapods use the Stewart architecture without being simulators. This guide explains the parallel architecture in CSCmotion 6DOF motion platforms and Stewart platforms.
One honest limitation of the term: six axes describes completeness, not suitability. If your test only needs pitch, roll and heave, a 3DOF platform is usually cheaper and simpler to integrate — and we will say so in the first technical reply.
Not sure your task needs all six axes? Decide from the motion task, not from the budget or the brochure. Compare 3DOF vs 6DOF by motion task →
Platform pose coordinates
Surge, Sway, Heave, Roll, Pitch and Yaw
The 6-Axis Interface Convention Sheet
The axis names are shared across simulation and test engineering, but they mean something only once the frame, positive direction, rotation order and reference point are stated. Host systems disagree on all four — hence the last column.
The 6-Axis Interface Convention Sheet Agree every row in writing before integration, not at first power-on. Rotation order matters most: roll 10° then pitch 10° is a different pose from pitch 10° then roll 10°.
| Coordinate | Physical motion | What to fix in your interface document |
|---|---|---|
| X Surge | Translation forward and backward along the longitudinal axis | Which direction is +X, and the origin the offset is measured from |
| Y Sway | Translation left and right along the lateral axis | Whether the frame is right-handed, so +Y points the way both teams expect |
| Z Heave | Translation up and down along the vertical axis | Whether +Z points up or down — many aerospace frames point Z down |
| Rx Roll | Rotation about the longitudinal axis | Degrees or radians, and the sign of a positive rotation |
| Ry Pitch | Rotation about the lateral axis | Whether positive pitch means nose-up or nose-down |
| Rz Yaw | Rotation about the vertical axis | Rotation order (Z-Y-X or X-Y-Z) and the pivot point all three rotations act about |
Why exactly six?
A free rigid body has exactly six independent ways to move: three translations and three rotations. Any motion decomposes into these six, which is why 6DOF is the complete case.
Integrating with an existing host? Send its axis convention and update rate, and we map both before the first power-on. Send your interface convention →
The mechanism underneath
The Parallel Mechanism: Six Limbs Carrying One Platform
and Why We Build It With Cardan Joints
Picture six people lifting a tabletop by its edge. Nobody carries a corner alone, and if one person stands up while the others stay still, the whole top tilts rather than one corner simply rising. That is a parallel mechanism: every limb connects the fixed base directly to the moving platform, and the load is shared across six paths instead of passing down a chain of joints.
A serial robot arm stacks joints in a chain, so each motor carries everything downstream and errors add up along the way. In a parallel mechanism the limbs share the load and their errors average. That is why a hexapod is stiff and repeatable for its mass — and why its mathematics is harder and its workspace small for its footprint. All three come from the same geometry. You cannot have the first without the other two.
Almost every published explanation assumes spherical (ball) joints at both ends of each limb. That is the textbook form, and it keeps the equations clean. It is not what we build.
CSCmotion 6DOF platforms use Cardan (universal) joints. Combined with the sliding and turning freedom of the rod inside each servo electric cylinder, each limb keeps the freedom a Stewart limb needs. The choice changes three things a buyer cares about: the load path, the stiffness under alternating load and the edge of the usable workspace.
Fig. 2 · One rotation removed. Blocking spin about the limb axis is what gives the Cardan joint a determinate load path.
The Spherical-vs-Cardan Joint Crosswalk Same mechanism family, different trade-offs at the joint.
| Property | Spherical (ball) joint | Cardan (universal) joint | What it means for your project |
|---|---|---|---|
| Rotational freedom | Three axes, including spin about the limb's own axis | Two axes; spin about the limb axis is constrained | One less free motion for the limb to wander in under load |
| Load path | Cannot resist torsion about the limb | Determinate | Joint and rod loads are calculated, not estimated |
| Stiffness under alternating load | Lower for a given size; stiff ball joints at high load become large and costly | Higher | Alternating load is what governs fatigue life in a motion base |
| Articulation range | Wide cone | More restricted | Large combined tilt has to be checked joint by joint before quoting |
One honest limitation: a Cardan joint gives up articulation range. If your profile asks for unusually large combined tilt, we check every joint angle along the trajectory before quoting, and we will tell you if the geometry has to grow to keep the joints inside their range.
“We chose the joint for the load case, not for the textbook diagram. A motion base sees alternating load all day, and that is exactly the condition the Cardan joint handles better.”
— — CSCmotion Motion Control Engineering Team
Specifying geometry for a new platform? Joint circles, limb angles and platform ratio decide the trade between workspace and stiffness. Read the Stewart Platform Design guide →
Follow one pose through the system
How a 6DOF Motion Platform Works, Step by Step
The 7-Step Command-to-Motion Chain
The clearest way to understand a 6DOF platform is to follow a single target pose from the host to a measured result. Who owns each step varies between projects. The order never does.
host pose → command validation → inverse kinematics → axis trajectories → servo drives and cylinders → feedback correction → measured platform motion
01
Define the target pose
A host or test controller requests X, Y, Z, roll, pitch and yaw over time.
02
Validate the command
Units, frame, state, pose and rate limits are checked first.
03
Solve inverse kinematics
The pose becomes six target lengths, using calibrated geometry.
04
Generate axis references
Interpolation within velocity, acceleration and jerk limits.
05
Move the actuators
Servo drives move the six electric cylinders.
06
Correct with feedback
Each servo loop closes its position error every cycle.
07
Verify platform motion
Measured at an agreed reference point, under the approved load.
Step 01 · the command source
The host is not always doing the same job
A test rig replays a trajectory, a research model generates motion live, a simulator inserts motion cueing. Settle four questions early: who owns the command and at what update rate, which units and frame, who enforces each limit, and what happens on a fault or a lost connection.
Step 07 · verification
"The platform moved" is not an acceptance criterion
Useful evidence compares commanded with measured motion for a stated payload, reference point, trajectory, instrument and tolerance. A fast no-load video proves only that the mechanism can move.
Have a trajectory already? Send one representative combined trajectory and your payload. We run it through the real geometry and tell you where it runs out of stroke, force or joint angle. Get a reachability check on your trajectory →
Joint space is not platform space
Why Six Actuators Do Not Equal Six Platform Axes
The Limb Coupling Map
Surge, sway, heave, roll, pitch and yaw describe the moving platform. Limb length describes the mechanism. The two are related through geometry, never by a one-to-one assignment — and the clearest way to see that is to run the numbers.
The map below uses an illustrative symmetric hexapod: base joint circle 1.0 m radius, platform joint circle 0.6 m, neutral height 0.9 m, every limb 1,118 mm at neutral. A teaching geometry, not a CSCmotion model — but the pattern holds for every Stewart platform.
The Limb Coupling Map Change in each limb length, in mm, for one small move from the neutral pose.
| Requested platform motion | L1 | L2 | L3 | L4 | L5 | L6 | What it tells you |
|---|---|---|---|---|---|---|---|
| Heave +50 mm | +40.6 | +40.6 | +40.6 | +40.6 | +40.6 | +40.6 | All six extend equally here, and by less than the heave itself. Actuator stroke is not platform travel. |
| Surge +50 mm | −26.0 | −26.0 | +25.3 | +3.4 | +3.4 | +25.3 | One pure translation shortens two limbs, lengthens two and barely moves two. |
| Sway +50 mm | −11.7 | +13.8 | −15.8 | −28.8 | +30.3 | +17.8 | No two limbs move alike. The pattern comes from the joint layout, not from the axis name. |
| Roll +3° | −19.4 | +19.3 | +24.1 | +4.5 | −4.3 | −23.3 | Opposite sides work against each other to tilt the top. |
| Pitch +3° | −15.9 | −15.9 | −8.8 | +25.1 | +25.1 | −8.8 | Four limbs shorten so that two can lengthen more. |
| Yaw +3° | −17.6 | +18.5 | −17.6 | +18.5 | −17.6 | +18.5 | Every limb moves. There is no "yaw actuator." |
| Surge +50 mm with pitch +3° | −42.3 | −42.3 | +16.7 | +28.5 | +28.5 | +16.7 | L1 and L2 now carry most of both demands. This is where stroke runs out first. |
Illustrative geometry · computed with the inverse kinematics equation below · rotations about the platform centre at neutral height · Z-Y-X rotation order
The consequence: the platform has to be controlled as one coupled mechanism. Treat it as six unrelated linear axes and you get incorrect motion, unplanned joint loads and unsafe transitions between poses. No axis can be sized on its own either — the limb that runs out of stroke in a combined move is rarely the one the axis name suggests.
Want to see this map for a real configuration? Our 6DOF platform page lists the configurations we build around. Explore 6DOF motion platform configurations →
Pose in, six lengths out
How Inverse Kinematics Converts a Target Pose Into Actuator Lengths
Inverse kinematics answers the real-time control question: given the required position and orientation of the platform, what length must each limb have? For a parallel platform this is the easy direction. It is a direct geometric calculation with one answer, and it runs every control cycle.
Principle equation · limb i
li = t + R · pi − bi
Li = ‖li‖
| bi | base attachment point, in the base frame |
| pi | platform attachment point, in the moving frame |
| t | target translation vector |
| R | target rotation matrix |
| li | limb vector in the base frame |
| Li | required limb length |
Read plainly: rotate the platform attachment point into the commanded orientation, shift it by the commanded translation, subtract the base point. The magnitude of what remains is the length the actuator must reach. Repeat six times.
Worked example · the limb-inclination check Two limbs, the same 100 mm of heave, simplified to a vertical plane.
| Limb geometry | Length at neutral | Length after +100 mm heave | Limb extension | Axial force per unit of vertical load | What it means for your project |
|---|---|---|---|---|---|
| Steep limb · 0.30 m across, 0.80 m up | 854.4 mm | 948.7 mm | 94.3 mm | 1.07× | The more a limb leans, the less it extends for the same heave and the more force it carries for the same load. Stroke and force are traded in the geometry, before any motor is chosen. |
| Inclined limb · 0.60 m across, 0.80 m up | 1,000.0 mm | 1,081.7 mm | 81.7 mm | 1.25× | The more a limb leans, the less it extends for the same heave and the more force it carries for the same load. Stroke and force are traded in the geometry, before any motor is chosen. |
Why this direction is easy
Each limb is solved on its own. Six subtractions, six magnitudes, one answer in a fixed number of operations — fast enough for every control cycle.
What the controller does next
Lengths alone are not executable. Each axis still needs a trajectory within velocity, acceleration and jerk limits, all six kept in sync.
Calibration beats the formula
The equation assumes attachment points sit where the drawing says. They never do exactly. Loading the as-built geometry is what makes a correct equation accurate.
Already have a joint layout? Send base and platform joint coordinates with your trajectory, and get the limb-length range it demands. Request a limb-length check →
The half most guides skip
The Forward Problem: Six Lengths Back to One Pose
The Inverse-vs-Forward Kinematics Ledger
Run the question backwards. You have six measured limb lengths from the encoders. Where is the platform? Most introductions move straight past this point. It deserves attention, because it is the harder half, and it decides what a platform can honestly claim about its own position.
The Inverse-vs-Forward Kinematics Ledger The same mechanism, solved in opposite directions.
| Question | Inverse · pose → lengths | Forward · lengths → pose | What it means for you |
|---|---|---|---|
| Formula | Closed form; each limb solved on its own | No general closed form; six coupled non-linear equations solved together | Inverse is cheap enough for every control cycle. Forward needs a numerical solver. |
| Number of answers | One | Up to 40 mathematical solutions for a general Stewart geometry, most of them assemblies the mechanism could never reach | A solver started in the wrong place can converge to the wrong root. |
| Where it runs | The real-time control loop | Pose estimation, monitoring and limit checks | The "platform pose" a controller reports is usually a forward-kinematics result. |
| Failure mode | A requested length outside the stroke — caught and rejected | Slow convergence, a wrong root or no convergence near singular poses | Software limits should keep the platform away from those regions. |
A robot arm has the opposite problem: its forward direction is trivial and its inverse is hard. For a hexapod, the forward problem is solved numerically, and numerical solvers need a good starting estimate — without one they converge slowly, to the wrong root, or not at all.
Three different claims hide behind the word “pose.” A stated pose is either the pose that was commanded, a pose calculated from a mechanism model, or a pose measured by an external instrument. Only the third is independent of the model’s assumptions. Ask which one you are looking at.
One caveat: no solver is well-behaved next to a singular configuration, ours included. We do not claim otherwise; we set the software limits so the platform never operates there.
Evaluating how a supplier reports pose? Ask which of the three claims their number is — then ask us the same question. Ask how pose is estimated on your geometry →
Three different kinds of proof
How Closed-Loop Control Keeps Six Actuators Synchronized
The 3-Layer Pose Evidence Stack
Closed-loop control is often described as if one feedback value proved the whole platform pose. It does not. Actuator feedback, the calculated platform pose and an independent measurement are three evidence layers that answer three different questions — and each one is blind to something.
The 3-Layer Pose Evidence Stack If one layer misses something, the next one is there to catch it.
| Evidence layer | Proves | Blind to | When we use it |
|---|---|---|---|
|
01 · Actuator feedback encoder or linear position sensor in each servo loop | Actuator-side position; the six limbs staying synchronized with each other | Structural deflection, joint compliance, payload dynamics | Every control cycle, in operation |
|
02 · Calculated platform pose forward kinematics on the calibrated geometry | Model-based platform state; the input for limit checks | Geometry error the calibration did not capture; compliance the model leaves out | Continuously, inside the controller |
|
03 · Independent measurement external instrument at the payload reference point | Measured platform response under the approved load and trajectory | Everything that was not tested — other loads, trajectories and reference points stay unproven | During factory acceptance testing, with the instrument agreed in the specification |
Deflection, joint compliance, mounting flex and geometry error open a gap between the three layers. On a well-built platform it is small — but small is a measured result, not an assumption.
How the working principle gets built into a CSCmotion platform
We write the kinematics, build the controller and assemble the servo electric cylinders ourselves, so the geometry our controller calculates with is the geometry we identified on the platform you receive, not a drawing value copied into a parameter file:
The 6-Station Build-and-Verify Line Each station protects one assumption the equations make.
| Station | What happens | Which assumption it protects |
|---|---|---|
| ST 01 · Cylinder single-axis test | Each servo electric cylinder runs alone for stroke, thrust and backlash. | Every limb can hold the length the controller asks for |
| ST 02 · Joint preload record | Every joint preloaded to a recorded value, logged against the serial number. | Joint play adds no motion the model does not know about |
| ST 03 · Frame assembly | Upper and lower frames assembled, joint mounts fixed. | Attachment points exist where the geometry says |
| ST 04 · As-built geometry identification | Real attachment-point positions identified and loaded into the controller. | The kinematics run on this platform, not on the drawing |
| ST 05 · Loaded dynamic test | Representative payload, combined trajectories, temperature rise, limit behaviour. | Workspace and force limits hold under load, not just empty |
| ST 06 · Factory acceptance test | Your trajectory, payload, reference point and instrument; your team or a third party welcome to witness. | Layer 03 of the evidence stack, before shipment |
Why ST 02 gets its own record: joint preload is where a Stewart platform’s repeatability is won or lost. A few hundredths of a millimetre of play at each of twelve joints stacks into visible jitter at the payload, and it cannot be tuned out in software after assembly. It has to be built in, not calibrated in.
Writing an acceptance specification? Send the payload, reference point and instrument you expect, and we propose the FAT test items before you order. Get proposed FAT test items →
Reachable is not the same as usable
What Limits the Usable 6DOF Workspace
The 8-Constraint Workspace Gate
A parallel platform cannot offer maximum translation and maximum rotation on every axis at once. The usable workspace is a coupled volume, and a pose is usable only if it passes all eight gates below at the same time.
01
Limb length
Minimum and maximum actuator lengths set part of the reachable boundary.
02
Joint articulation
Every Cardan or spherical joint must stay inside its permitted angle at every pose along the path.
03
Mechanical clearance
Limbs, joints, platform, base, payload and surrounding equipment must never touch.
04
Force and speed
A pose can be geometrically reachable and still exceed actuator force, velocity or acceleration.
05
Payload and centre of gravity
Mass distribution and inertia change limb loads and dynamic response across the workspace.
06
Conditioning
Near singular configurations, force transmission degrades and control authority is effectively lost.
07
Cables and utilities
Routing, bend radius, drag and strain relief shrink the practical motion envelope.
08
Safety margin
Software limits keep a margin from every mechanical, joint, load and control boundary.
Do not add isolated maxima — the coupling map shows why
In the surge-with-pitch row above, limbs L1 and L2 shorten by 42.3 mm, where surge alone asked for 26.0 mm and pitch alone for 15.9 mm. Combined demand lands on the same two limbs, so stroke runs out there first. Check a representative combined trajectory before agreeing any specification.
USABLE WORKSPACE ≠ MAX X + MAX Y + MAX Z + MAX ROLL + MAX PITCH + MAX YAW
Sizing a platform from a load case? Payload, centre of gravity, stroke and acceleration have to be read together, not one at a time. Read the Payload, Stroke & Acceleration guide →
Before you compare two quotes
How to Read Any 6DOF Spec Sheet, Including Ours
The 6-Line Spec-Sheet Decoder
Engineers don’t want adjectives; they want limits. Every number on a 6DOF spec sheet is true under some condition. The trouble starts when the condition is missing, because two sheets that look comparable are then measuring different things.
The 6-Line Spec-Sheet Decoder Six lines, six questions, and what a complete answer looks like.
| Line on the sheet | Ask this | Why the bare number misleads | A complete answer includes |
|---|---|---|---|
| 1 · Payload | Gross moving mass or useful payload? At what centre-of-gravity height? | A tall payload adds tilting moment; the same mass with a higher centre of gravity can exceed joint and actuator limits. | Mass, centre-of-gravity height and offset, and inertia where known |
| 2 · Travel and rotation | Single-axis with the others at neutral, or combined? | Per-axis maxima are not available at the same time. | Single-axis values plus a check of your combined trajectory |
| 3 · Velocity and acceleration | Single-axis peak or combined? At what payload, and for how long? | An empty-platform peak says little about a loaded, sustained profile. | Values with the payload, the axis and the duration stated |
| 4 · Latency, update rate, "cycle time" | Is it the controller's interpolation period or the platform's end-to-end response? Loaded or empty? Does it include host communication? | A controller's interpolation period is not the platform's closed-loop response. | The measurement start and end points, the payload and the instrument |
| 5 · Accuracy and repeatability | Commanded, calculated or measured? Design value or test result? Which instrument? | A design value and a measured value can share the same digits. | The evidence layer, the instrument and the test condition |
| 6 · Frequency response | At what amplitude, on which axis, with what payload? | Small-amplitude bandwidth hides force and stroke limits at larger amplitude. | Amplitude, axis and payload for every bandwidth figure |
Missing conditions, not wrong numbers, are what make two quotes impossible to compare.
Why this page carries no millisecond figure: we do not publish a closed-loop latency number here. A figure in milliseconds means nothing without the payload, the measurement points and the instrument, and we will not print one until we have it on record with those conditions attached. The same rule applies to repeatability: when we quote it, we say whether it is a design value or a measured result.
Comparing quotes right now? Run this decoder on any spec sheet, including ours. Send it over and an engineer marks which conditions are missing. Send a spec sheet for decoding →
An optional application layer
Where Motion Cueing Fits, and Where Our Scope Ends
Motion cueing is not inverse kinematics, and it is not servo control. A cueing algorithm turns vehicle or flight-model dynamics into bounded motion that feels convincing inside a small workspace. It sits above everything in this guide: cueing decides what pose to request; kinematics and the controller execute it.
Many platforms never use it. Industrial test systems command a physical trajectory directly, because the goal is to reproduce a motion, not the perception of one.
Industrial testing · usually no cueing
The motion is the goal
test profile → pose command → inverse kinematics → servo motion
Research · project-dependent
The motion is the experiment
experiment model or recorded data → optional processing → pose command
Simulation · cueing normally present
The motion is a perception
vehicle model → motion cueing → bounded pose command → platform
Here is the honest version of our scope: we build the motion platform, its controller and its host interface. The cockpit, the visual system, the vehicle or flight model, the training content and any training-device qualification stay with the simulator integrator or with you. We work alongside integrators; we are not one.
Integrating a platform into a simulator? See how interface, safety and commissioning are split between platform supplier and integrator. Read the motion platform integration guide →
From principle to platform
Where the Working Principle Meets a CSCmotion Platform
Choose by what you are moving and how it has to move, not by the number of axes.
Six coupled limbs
6DOF Motion Platform
The full principle on this page: six servo electric cylinders, inverse kinematics every cycle.
- Fits research labs, industrial motion testing, simulator integrators who need all six axes
- Not for tasks that only ever need pitch, roll and heave
Hexapod by geometry
Stewart Platform
The same hexapod, specified around joint layout, stiffness and positioning duty.
- Fits precision positioning, test fixtures, alignment and calibration benches
- Not for large-amplitude motion where workspace matters more than stiffness
Three axes, fewer parts
3DOF Motion Platform
Three actuators for pitch, roll and heave — the same coupled idea, a simpler mechanism.
- Fits tilt and heave testing, compact simulators, budget-sensitive research rigs
- Not for anything that needs surge, sway or yaw
None of these fits your load case? Custom builds start from your payload, centre of gravity and trajectory, not from a catalogue. See custom motion platform engineering →
Frequently asked
6DOF Motion Platform — FAQ
Short answers to the questions engineers ask most — including the sceptical ones.
What is a 6DOF motion platform?
A system that controls the position and orientation of a moving rigid body in six degrees of freedom: three translations (surge, sway, heave) and three rotations (roll, pitch, yaw). In the common parallel form, six actuators connect a moving platform to a fixed base, and a controller converts each commanded pose into six actuator lengths.
How does a 6DOF motion platform work?
A host requests a pose. The controller checks it against limits, solves inverse kinematics for six limb lengths and drives six synchronized servo axes. Feedback closes each loop, and platform motion is verified against the command with an approved load and instrument.
Does each actuator control one degree of freedom?
No. The actuators are coupled: even pure yaw changes all six limb lengths. Treating the platform as six independent axes produces incorrect motion and can overload joints.
Is a 6DOF platform always better than a 3DOF platform?
No. If a task needs only pitch, roll and heave, a 3DOF platform is usually cheaper, simpler to integrate and easier to maintain. Choose 6DOF when the task needs surge, sway or yaw, or when the motion has to be reproduced as a full rigid-body pose. See 3DOF vs 6DOF.
Why do you use Cardan joints when most Stewart platforms use ball joints?
For the load path. A Cardan joint blocks spin about the limb axis, which gives a determinate load path and higher stiffness under alternating load — the condition that governs fatigue life in a motion base. The trade-off is a narrower articulation range, so we check every joint angle along your trajectory before quoting.
Why don't you publish a latency or millisecond figure?
Because a bare number would mislead you. A controller's interpolation period, an empty-platform response and a loaded end-to-end response are three different figures often printed as one. We quote one only with the payload, measurement points and instrument stated.
Do you build the kinematics and controller yourselves, or buy them in?
In-house. We write the kinematics, build the controller and assemble the servo electric cylinders and the complete platform ourselves. That is why we can explain how the forward problem is solved on your platform instead of pointing you to a third-party manual.
Continue in the Technology section
Related Motion Platform Engineering Guides
Selection, architecture, sizing and drive technology each have their own guide.
Selection
How to Choose a Motion Platform
Selection in the order engineers actually decide it.
Drive technology
Electric vs Hydraulic
How drive technology changes installation, maintenance and control.
From principle to specification
Send Your Load Case, Get an Engineer's Answer
Understanding the principle is step one. A configuration can be reviewed once the real moving assembly, the combined motion profile and the integration boundary are defined. Send those, and an engineer tells you what is missing before anyone discusses a model number.
An engineer, not a sales inbox, replies within 24 hours — weekends included. Lead time is confirmed at quotation. Every platform carries a 12-month warranty. +86 152 5530 5272