Frequently asked questions about the X1, HIL testing and UAV QC

It is laboratory infrastructure for evaluating real control hardware, sensors and physical rotational motion in one test workflow. X1 produces roll, pitch and yaw motion while measurement and simulation layers support control-response analysis.

Fixture, mechanical envelope, axis torque and instrumentation are selected for vehicle geometry, mass, inertia and test profile. The datasheet specifies up to 600 mm rotor-to-rotor for the reference mounting arrangement and up to 25 kg in a suitable configuration; these two figures alone do not establish compatibility.

Slip-ring power and signal transfer enables continuous 360° rotation on each rotational axis without cable-wrap travel limits. Combined-axis motion remains dependent on geometry, motion profile and the selected configuration.

Suitable fixtures and mechanical configurations can support attitude-control, avionics and sensor studies. Wing/rotor envelope, centre of mass and motion clearance are assessed per project; full-flight or aerodynamic performance is not assumed within the same scope.

Yes. Alongside UAV applications, we design custom machines, test systems and simulation infrastructure for different industries. Mechanical, electronic, sensing, control and software scope is defined around test objectives, product requirements and budget.

Software simulation evaluates control and environment models numerically. HIL includes real control hardware in the loop; X1 also provides physical attitude motion. Sensor and integration effects can be assessed within that physical scope.

Laboratory testing enables repeatable evaluation of control and sensor behaviour before field testing. It does not reproduce every aerodynamic, translational and operational condition; it complements flight testing within the validation process.

Integration depends on the control software, sensor path and data interface. Tests using physical attitude motion and closed-loop scenarios requiring simulated data have different connection requirements; modification-free operation is not assumed for every controller.

Many sensor and orientation tests can use platform-driven motion without running propellers. Scenarios involving thrust or load effects require a separate test design, including fixture, guarding and operating limits.

The reference architecture includes UDP telemetry over Ethernet, serial communication over USB and real-time monitoring software. Data fields, recording format, external-software integration and production-system interfaces are configured for the application.

X1 can be configured for defined orientation sequences, sensor-data records and unit-level evaluation. Automation level, data interfaces and acceptance logic are defined around the customer’s production and quality-assurance processes.

Cycle time depends on mounting, communication, selected orientations, motion profile and acceptance criteria. Test sequences and automation are defined around the intended production workflow rather than a universal duration.

The centre of mass relative to the rotation centre affects axis loads and measured behaviour. Fixture design and balancing account for vehicle geometry and test objectives; mass alone does not determine compatibility.

Axes in a nested three-axis gimbal can align at certain orientations. Motion profiles, coordinate representation and control are designed with this geometry in mind. Continuous rotation does not imply singularity-free operation at every orientation.

X1’s three degrees of freedom are roll, pitch and yaw rotations. A six-degree-of-freedom motion system adds three translational axes. Multi-axis sensors or force/torque measurements do not make X1 a six-axis motion platform.

The choice depends on test scope, instrumentation, integration effort and overall project budget. X1 provides a shared architecture with custom fixture, sensor and software options. Requirements for a different motion or machine architecture can be addressed through a dedicated design.