olixSense™ X2 Ultra | ROS 2 Native IMU | Olive Robotics

olixSense™ · Inertial motion intelligence

X2 Ultra

Embedded Inertial Sensing For Physical AI Native to your robot

Multi-Redundant MEMS. Onboard olixAI™ fusion. Native ROS 2. Relative or magnetometer-aided orientation, angular velocity and acceleration—connected and powered through one Ethernet cable.

100 Mb/s Ethernet · IEEE 802.3af PoE · olixOS™

olixSense X2 Ultra metal enclosure with Ethernet and PoE connector
1,000 HzMaximum publish-rate setting¹
100 Hz nominal default
66 × 57 × 42 mmNominal overall envelope
Includes mounting tabs and sensor-side connector
IMU + AHRSRelative or magnetometer-aided orientation
One virtual measurement frame
ROS 2 nativeStandard messages over DDS
TCP / UDP JSON export

ROS 2, at the source

Native ROS 2.
From the first message.

Connect motion sensing directly to your robotics stack. X2 Ultra publishes standard ROS 2 messages from the device, with timestamps, frame identifiers and covariance fields.

Build around familiar topics for orientation, inertial measurements, magnetic field, temperature and diagnostics. Use TCP or UDP JSON when your application runs outside ROS 2.

ROS 2 / DDSROS 2 HumbleTCP + UDPJSON
Sensing → Your applicationROS inside
01

Sense and fuse onboard

Multi-Redundant MEMS with Advanced Skew-Redundant Geometry Mounting. olixAI™ combines calibration, filtering and sensing into one output.

02

Publish through olixOS™

Configure motion streams, coordinate frames and publication settings over the Ethernet connection.

03

Integrate in your robot

Receive standard ROS 2 topics or timestamped JSON in your estimator, logger or application.

X2 Ultra connected to a PoE Ethernet cable with an RJ45 host end
Power and Ethernet data through one cable. Accessory configuration follows the quotation.

Ethernet + isolated PoE

One cable.
A direct connection.

Connect X2 Ultra to an IEEE 802.3af PoE switch or injector. Power the sensor, reach olixOS™ in your browser and stream motion data over the same Ethernet connection.

  • 100 Mb/s EthernetMotion data, configuration and diagnostics on your robot’s network.
  • Isolated PoEIEEE 802.3af input, 37–57 V DC. End-span and mid-span power-feed support.
  • Defined installationApproved M12-to-RJ45 mating cable, with strain relief and clearance for the coupling and bend radius.
Reference M12-to-RJ45 Ethernet accessory cable
Ethernet + PoE

The connection, considered.

Your cable.
Your configuration.

A simple connection starts with the right fit. Specify the cable length and connector arrangement for your robot.

01 Cable length
From the sensor to your PoE source.
02 Connector arrangement
Approved M12-to-RJ45 mating cable.
03 Installation
Room for the coupling, cable bend and strain relief.

Cable appearance and supplied configuration follow your quotation.

Plan your connection

olixAI™

Intelligence inside the sensor

From motion.
To useful data.

olixAI™ combines redundant sensing, calibration corrections and filtering into a unified motion output. olixOS™ brings configuration, calibration and diagnostics together on the device.

OrientationQuaternion x, y, z, w
Angular velocityRadians per second
Accelerationm/s² · gravity-compensated stream
Auxiliary dataMagnetic field, temperature, status
Top view of X2 Ultra showing the engraved enclosure axes and product identification

olixAI™ · Time-series sensor fusion

A sequence of motion.
One coherent output.

Explore how successive inertial measurements can inform a unified motion state.

01 / Sensor sequences

Accelerationax · ay · az
Angular velocitygx · gy · gz
Magnetic fieldmx · my · mz

AHRS mode input

02 / Temporal fusion concept

olixAI™Conceptual temporal neural fusionSuccessive sensor samples are represented as connected nodes. Highlighted paths illustrate a unified information flow, not the product’s actual neural-network topology.
Earlier samplesNow

03 / Unified motion

OrientationQuaternion · x, y, z, w
Angular velocityrad/s
Accelerationm/s²

One virtual measurement frame

IMU mode · relative orientation from acceleration and angular velocity. Magnetic-field data is excluded from this orientation solution.

Conceptual neural-fusion illustration. Waveforms, nodes and connections are illustrative; they do not disclose the internal network architecture or show measured data.

AI-enhanced sensor fusion

Keep the movement.
Refine the signal.

Illustrative concept

See the fusion objective in a moving robot frame: follow changing orientation while limiting vibration and short disturbances. The traces below show the same scene as motion data.

olixAI™ conceptTraditional fusion conceptReference
Motion, made visible.Illustrative attitude response
Traditional fusion conceptIllustrated residual interference
olixAI™ conceptIllustrated refined motion output

Dashed outlines show the reference movement.

Follow the movement.

Conceptual relative-motion signal · the same scene, shown as data.

During motion: illustrative sensor-fusion comparison Synthetic conceptual traces. A gray conventional-output curve contains more noise than a green olixAI™ concept curve, compared with a dashed reference. These are not measured product outputs.

Changing orientation · preserve the movement needed by your state estimator.

Synthetic, normalized illustration of the fusion concept, not measured X2 Ultra outputs or a benchmark against a specific traditional algorithm. Robot frames and traces share one scripted motion sequence. Product specifications and their basis follow below.

Two modes. One virtual measurement frame. IMU mode provides relative orientation from acceleration and angular rate. AHRS mode adds magnetometer data for magnetic heading aiding. Fused output uses a virtual origin at the board centre. Calibrate the magnetic field in the installed configuration and apply the sensor-to-robot transform.

Fused motion output

Precision.
In the details.

A closer look at orientation, noise and stability.
Explore the X2 Ultra specification estimates.

Relative orientation · estimated

A precise view
of movement.

<0.4°

Roll & pitch · IMU mode · estimated RMSE

Settled relative rotation

Conservatively rounded engineering estimate for aggregate relative-angle error after motion has stopped.

Gyroscope

Fused noise density

<0.01°/s/√Hz

Estimated bound · stationary three-axis mean

Accelerometer

Fused noise density

<200µg/√Hz

Estimated bound · stationary three-axis mean

Engineering estimates from the product datasheet, rounded conservatively. Model-specific performance validation is pending; these figures are not measured X2 acceptance limits or production guarantees.

Orientation specificationsIMU & AHRS · estimated settled-angle RMSE

Relative orientation · estimated RMSE bounds

Estimated X2 Ultra relative-orientation RMSE bounds
ConditionModeRollPitchYaw
Settled rotationAHRS<0.4°<0.6°<0.5°
IMU<0.4°<0.4°<0.2°
Moving platform
Between settled poses
AHRS<1.1°<1.2°<1.7°
IMU<1.1°<1.2°<1.3°

Specification basis

Settled relative rotation. Estimated aggregate RMSE for settled single-axis rotations. This describes relative angular displacement after motion has stopped.

Moving platform. Estimated relative-angle error between settled poses on a moving platform. These values do not specify continuous tracking error or absolute magnetic-heading accuracy.

Reading the bounds. The < notation denotes an estimated aggregate bound, not a maximum sample error or a production guarantee. Performance depends on mode, calibration, temperature, range, bandwidth and installation. Compare configurations with matching filter and publication settings.

Noise & stabilityFused output · engineering estimates
Estimated fused inertial noise and stability bounds
ParameterGyroscopeAccelerometer
Noise density<0.01 °/s/√Hz<200 µg/√Hz
Random walkAngle: <0.6 °/√hVelocity: <0.11 m/s/√h
Bias instability<7 °/h<0.001 m/s²

Engineering estimates for three-axis means during stationary operation at room temperature. Allan-derived white-noise coefficients and bias instability are distinct from absolute bias and thermal drift. Model-specific validation is pending.

olixOS™ · Browser configuration

Configure in a browser.
Build in your stack.

Set up the sensor in your browser. Choose the output frame, profile, measurement range and stream settings, then bring the data into your application.

01 / CONNECT

Power and network

Mount the sensor on a rigid surface. Secure the approved Ethernet cable and connect its RJ45 end to a compatible IEEE 802.3af PoE switch or injector.

02 / CONFIGURE

Your sensor. Your frame.

Default device IP: 192.168.7.100. Example host IP: 192.168.7.1/24. Open the device address in a browser; configure mode, frame, publication rate and calibration.

03 / INTEGRATE

Receive motion data

Subscribe to ROS 2 topics with matching QoS, or enable JSON export. TCP uses newline-delimited samples; UDP begins after an initial client registration packet.

ROS 2 · example subscription
ros2 topic echo /olive/olixSense/x2/id001/imu \
  --qos-reliability best_effort

Use the commissioned device address and configured namespace. Place the host on the sensor subnet with a unique IP address. Match subscriber reliability to publisher QoS; give each sensor a unique IP address and ROS namespace.

ROS 2 output topics and message types
Topic suffixROS 2 message typeAvailable data
imusensor_msgs/msg/ImuQuaternion, angular velocity, acceleration, covariance
accelerationgeometry_msgs/msg/AccelStampedGravity-compensated acceleration
velocitygeometry_msgs/msg/TwistStampedIntegrated velocity estimate; external aiding for sustained use
magneticfieldsensor_msgs/msg/MagneticFieldAuxiliary magnetic field, in tesla
temperaturesensor_msgs/msg/TemperatureInternal temperature, in °C
statusdiagnostic_msgs/msg/DiagnosticStatusSystem diagnostics

Topic availability follows the selected mode; optional /tf publication is supported. TCP / UDP export uses the olive_imu.v1 JSON schema, with timestamps, frame ID, quaternion and motion data; default port 5600. The host integration reference uses ROS 2 Humble; match topic names and QoS to your configured device.

Designed to fit your system

Compact by design.
Detailed where it matters.

A 48 × 48 mm housing footprint, integrated mounting base and a single network connector. Integrate X2 Ultra with a defined mechanical pose and virtual measurement reference.

X2 Ultra mechanical drawing: 66 mm width, 57 mm nominal depth, 42 mm height; four 4.1 mm mounting holes on 58 by 28 mm centres
Nominal dimensions in mm. Overall depth includes the 8.96 mm connector projection, rounded to 57 mm. Use the controlled drawing for production tolerances.

Mechanical & electrical

Mechanical and electrical specifications
Overall envelope66 × 57 × 42 mm, including mounting tabs and sensor-side connector
Housing footprint48 × 48 mm
Mounting base66 × 48 × 4 mm
Mounting holes4 × Ø4.1 mm; 58 × 28 mm centres
Network100 Mb/s Ethernet
Power inputIEEE 802.3af PoE · 37–57 V DC
PoE power stage12.95 W capacity; 1.5 kV input-to-output isolation
InstallationApproved mating cable; provide connector and cable-bend clearance

Sensing & configuration

Sensing and configuration specifications
Acceleration ranges±2 / ±4 / ±8 / ±16 g in IMU mode; ±4 g in AHRS
Angular-rate front end±125 / ±250 / ±500 / ±1,000 / ±2,000 °/s; available settings depend on configuration
Publication setting0–1,000 Hz; 100 Hz default¹
Output conventionsFLU / FRD
Application profilesDrone / Mobile Robot / Humanoid / Raw
PlatformolixOS™ with olixAI™
Processing resources8-core 64-bit CPU, up to 2.2 GHz; up to 6 TOPS peak²
Memory / storage4 GB memory / 64 GB eMMC, nominal
Ambient operation−20 to +60 °C design envelope³

¹ Publication rate is a configurable setting; effective throughput depends on configuration and network. Measurement bandwidth and publication rate are separate. ² Peak platform capability; sustained performance depends on workload and thermal conditions. ³ Subsystem-based environmental design envelope; complete-assembly qualification is pending. Storage: −20 to +70 °C; humidity: 10–90% RH, non-condensing, on the same basis. PoE capacity and isolation ratings apply to the power stage; capacity is distinct from device consumption. Confirm assembled mass, measured operating power, connection drawing and applicable conformity documentation with the quotation.

Applications · Physical AI

Different robots.
A common sense of motion.

From a robot’s next step to a vehicle’s next turn. Bring orientation, angular velocity and acceleration into the systems that move.

Humanoid robot walking through a laboratory with a tiny embedded torso IMU and lime-green conceptual motion overlays

Humanoid robotics

Every step.
In perspective.

Give your state estimator a body-motion reference. Combine X2 Ultra’s fused orientation, angular velocity and acceleration with joint encoders, contact information and external perception.

Humanoid profileBody orientationROS 2 integration

Define the body frame.Mount on a rigid torso or pelvis reference and apply the sensor-to-robot transform.

Configure the response.Select the Humanoid profile, output convention and publication settings in olixOS™.

Build the estimator.Combine inertial observations with the robot’s other measurements for gait and balance estimation.

Explore the applications

AMR moving through a warehouse with conceptual motion overlays

Autonomous mobile robots

Motion for the next turn.

Bring orientation and inertial data into localization alongside wheel odometry and vision.

Warehouse forklift with conceptual orientation overlays

Automated forklifts

A reference for vehicle motion.

Add body-motion observations to a warehouse vehicle’s localization and navigation stack.

Quadruped robot with conceptual body attitude and ground contact overlays

Legged robots

Understand body attitude.

Provide body orientation and angular rate to the estimator alongside joint and contact measurements.

Excavator with conceptual inertial motion overlays

Construction equipment

Measure platform movement.

Observe chassis orientation and angular motion during equipment development and integration.

Industrial tow train with conceptual trajectory overlays

Industrial tow trains

Follow the platform.

Combine inertial observations with vehicle odometry along changing factory routes.

Agricultural tractor with conceptual orientation overlays

Agricultural robotics

Motion across changing terrain.

Combine body-motion measurements with GNSS, vision and vehicle odometry in field-robot development.

Autonomous shuttle with conceptual motion overlays

Autonomous shuttles

An inertial view of the route.

Provide timestamped body-motion data to a vehicle’s externally aided state estimator.

Mining haul truck with conceptual chassis motion overlays

Heavy mobile equipment

Observe chassis attitude.

Explore orientation and vibration observations on large mobile platforms.

Indoor service robot with conceptual trajectory overlays

Service robots

A consistent sense of motion.

Integrate orientation and inertial data with perception and localization in indoor mobile systems.

Mobile manipulator with conceptual inertial reference frames

Mobile manipulation

Connect base and robot frames.

Observe mobile-base motion and maintain a defined sensor-to-robot installation transform.

Application illustrations show integration concepts, not customer deployments or certified use cases. Platform suitability, mounting and environmental requirements must be assessed for the complete installation. Inertial data complements the robot’s other sensors; it does not by itself provide position, safety functions or closed-loop balance control.

Integration, explained

The details.
Made clear.

What is the difference between IMU and AHRS mode?

IMU mode provides relative orientation using inertial acceleration and angular-rate measurements; magnetometer data is excluded from that orientation solution. AHRS mode includes magnetometer data for magnetic heading aiding. Local orientation zero is configurable in both modes.

For AHRS operation, perform magnetic calibration in the installed configuration and maintain separation from magnets, high-current wiring and ferromagnetic structures. The relative-angle specifications do not define absolute magnetic-heading accuracy.

Does X2 Ultra publish at 1,000 Hz?

The main IMU publish-rate setting extends to 1,000 Hz, with a 100 Hz default. Effective throughput depends on configuration and network. Verify the received rate in your application and select compatible filter settings. Publication rate and measurement bandwidth are configured separately.

Where is the measurement origin?

Fused and filtered data is published at a virtual origin at the board centre, aligned with the central inertial reference frame. Use the configured output convention and apply the installation transform from this sensor frame to your robot frame.

How are bias calibration and orientation zero different?

Bias calibration estimates sensor bias while the device is stationary in its normal mounting pose. Run the olixOS™ bias action or setBias service. Orientation zero uses setZeroQuaternion to define the present orientation as the local reference.

For AHRS mode, magnetic calibration is a separate operation. Choose FLU or FRD consistently and confirm the active settings after any requested service restart.

Can I use the sensor without ROS 2?

Yes. Enable TCP or UDP JSON export in olixOS™. The sensor acts as the server, using a configurable port with 5600 as the default. TCP provides newline-delimited JSON samples; UDP requires an initial client registration packet. Both include timestamps and the configured frame ID.

How do I integrate multiple X2 Ultra sensors?

Connect the sensors to a compatible PoE network. Assign each device a unique IP address and ROS namespace, and confirm that the switch or injector has the per-port capacity and total power budget for your configuration. Use a shared time reference when correlating data from multiple devices.

Which cable and mounting accessories should I order?

Specify an approved M12-to-RJ45 Ethernet cable, its length and connector arrangement. Connect to an IEEE 802.3af PoE switch or injector. Use the order-specific connection drawing and provide strain relief and clearance for the coupling and cable bend.

The mounting base has four Ø4.1 mm holes on 58 × 28 mm centres. Confirm delivery contents, assembled mass and measured operating power with the quotation.

Documentation & next steps

Documentation.
And direct support.

Technical reference

X2 Ultra datasheet

The complete technical reference. Performance, interfaces, installation drawings and integration details in one PDF.

Download PDF
Developers

Documentation

Explore the Olive documentation for configuration, ROS 2 integration, device services and application setup.

Open documentation
Engineering support

Plan your setup

Discuss installation, output configuration, cable options and the documentation your application requires.

Contact support

olixSense™ X2 Ultra

Build your next move.

Tell us about your robot, required quantities and connection needs. We’ll help define the sensor and accessory configuration.

Request a quote

Specification basis. This page follows the olixSense™ X2 Ultra Datasheet, OLV-X2U-DS-0001, Rev. 3.7, 19 October 2026. Performance figures are engineering estimates; model-specific validation is pending. Environmental figures are a subsystem-based design envelope pending complete-assembly qualification. Dimensions are nominal. Accessory appearance and delivery contents follow the accepted quotation.

Product information. Information is provided for product evaluation and integration planning, subject to revision. Assess suitability for the intended application and validate the complete installed system. Commercial and licensing terms apply. The complete product disclaimer is included in the downloadable datasheet.

  1. Scope; contractual precedence. This website is published by Olive Robotics GmbH for informational and commercial purposes. Unless expressly agreed otherwise, descriptions, specifications, availability and roadmaps do not constitute a binding offer, independent guarantee or commitment to future functionality. The applicable agreement, including the validly incorporated Terms & Conditions, governs the supply; individual agreements and mandatory statutory information requirements take precedence. Website updates do not amend an existing contract.

  2. Technical data; performance representations. Published measurements apply to the stated product revision, configuration, methodology and operating conditions. Performance may vary with calibration, mounting, firmware, filtering, network conditions and integration. Typical, nominal and illustrative values are not guaranteed limits unless expressly designated and agreed as such. Renderings, application scenes, simulations and AI visualizations are illustrative unless expressly identified as measured results; they do not establish product certification, delivery scope or third-party endorsement.

  3. Intended use; system integration. Products shall be used within their documented intended use and operating limits. The integrator shall assess application suitability and validate the complete system, including timing, interfaces, installation and applicable safety requirements. Component-level declarations do not certify a complete machine or safety function. These provisions do not transfer or exclude duties imposed on Olive Robotics by mandatory law. Refer to the applicable technical documentation and compliance documentation.

  4. Liability; reserved rights. Nothing in these notices excludes or restricts liability for intent or gross negligence, culpably caused injury to life, body or health, fraudulent concealment, an expressly assumed guarantee, or mandatory statutory product liability. Mandatory consumer protections and statutory remedies remain unaffected. Any further allocation or limitation of liability is governed solely by a valid agreement and applicable law; this notice does not establish a blanket exclusion of liability.

  5. Intellectual property; software; external content. Olive Robotics names, marks and proprietary materials remain protected. olive® and OLVX® are registered trademarks of Olive Robotics GmbH. Third-party marks and materials belong to their respective rights holders. No licence is granted beyond rights expressly granted or required by law; applicable open-source licences remain unaffected. Software and AI services are subject to their applicable licence terms. External content is provided by the relevant operator; statutory duties concerning unlawful content remain unaffected. Website access is governed by the applicable Terms of Use.

  6. Data protection; cookies; provider identification. Personal-data processing and the use of cookies or similar technologies are described in the Privacy Policy. Where legally required, consent must be obtained separately before the relevant processing or terminal-equipment access; continued browsing does not constitute consent. These notices neither replace a required consent mechanism nor restrict data-subject rights. Statutory provider information and contact channels are set out in the Imprint.

Olive Robotics icon

Olive Robotics GmbH

Embedded Intelligence for Physical AI

Let’s talk robotics.

Contact our team
Daimlerstraße 7 · 85521 Ottobrunn
Germany

Intelligence in every move.

Copyright © 2022–2026 Olive Robotics GmbH.All rights reserved.

English / International