olixSense™ X1 Pro | ROS 2 Native IMU | Olive Robotics

olixSense™ · Inertial motion intelligence

X1 Pro

Embedded Inertial Sensing For Physical AI Native to your robot

Multi-Redundant MEMS. Onboard olixAI™ fusion. Native ROS 2. Orientation, angular velocity and acceleration from a compact sensor—connected and powered by one USB cable.

Ethernet-over-USB · olixOS™ · USB-C power

olixSense X1 Pro metal enclosure, three-quarter view showing the USB-C port and mounting points
1,000 HzMaximum publish-rate setting¹
100 Hz nominal default
40 × 40 × 10 mmNominal enclosure dimensions
32 g nominal bare-unit mass
0.9 WTypical operating power
1.8 W supply-design allowance
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. X1 Pro 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 / DDSHumble + Jazzy / Fast DDSTCP + UDPJSON
Sensing → Your applicationROS inside
01

Sense and fuse onboard

Multi-Redundant MEMS measurements are calibrated, filtered and combined by olixAI™.

02

Publish through olixOS™

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

03

Integrate in your robot

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

X1 Pro connected to a screw-retained USB data cable, showing the sensor and host connectors
One connection for power and IP data. Cable configuration follows the quotation.

Ethernet-over-USB

One cable.
A familiar network.

A USB-C connection supplies power and creates an IP network interface. Reach the sensor through your browser, subscribe to ROS 2 topics, or connect a custom data client.

  • USB networkUSB 2.0 Ethernet-over-USB with ECM / RNDIS profiles. Verify the selected profile on your host.
  • Secure connectionDual screw-retention positions for the approved locking USB cable.
  • Simple power4.6–5.5 V DC input; 0.9 W typical operation. Provide a 1.8 W supply allowance.
X1 Pro and approved locking USB cable with host connector
USB-C power + IP data

The connection, considered.

Your cable.
Your configuration.

A simple connection starts with the right fit. Specify a data-capable USB cable with the length, host connector and retention hardware your robot needs.

01 Cable length
From the sensor to your USB host or powered hub.
02 Host connection
USB Type-C at the sensor; specify the host connector and matching retention hardware.
03 Installation
Allow connector clearance, 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 X1 Pro with 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

Separate auxiliary stream

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 profile · relative orientation from acceleration and angular velocity. Magnetic-field data is available separately.

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 X1 Pro outputs or a benchmark against a specific traditional algorithm. The robot frames and traces share one scripted motion sequence. Measured specifications follow below.

Two profiles. A consistent reference. Select IMU or AHRS mode for the application. Both characterized profiles provide relative orientation using inertial fusion. Magnetic-field data is available separately; absolute magnetic-north accuracy is not specified.

Motion, measured

Precision.
In the details.

A closer look at orientation, noise and stability.
Explore the measured figures behind the X1 Pro.

Relative orientation

A precise view
of movement.

<0.4°

Roll & pitch · IMU mode

Settled relative rotation

Pooled RMSE at 200 Hz, referenced to the fixture encoder. Rounded bound across the tested rotations.

Gyroscope

Fused noise density

<0.01°/s/√Hz

Three-axis mean characterization bound

Accelerometer

Fused noise density

<200µg/√Hz

Three-axis mean characterization bound

Rounded characterization bounds under defined test conditions. Scope, configurations and measurement methods are available below.

Orientation resultsIMU & AHRS · three test conditions

Relative orientation · rounded RMSE bounds

Measured X1 Pro relative-orientation RMSE bounds under three test conditions
Test conditionModeRollPitchYaw
Settled rotationAHRS<0.4°<0.6°<0.5°
IMU<0.4°<0.4°<0.2°
Moving platform
Settled-angle change
AHRS<1.1°<1.2°<1.8°
IMU<1.1°<1.3°<1.4°
Continuous trackingAHRS<1.2°²<3.5°<3.5°³
IMU<2.5°<3.0°<2.5°³

Measurement conditions

Settled relative rotation. Single-axis ±45° and ±90° rotations, using settled 2 s windows starting 0.5 s after each stop. Results pool the tested angles and are not limits at every pose. At −90° pitch, AHRS per-angle RMSE was <1.1°.

Moving platform · settled-angle change. Fixture on a moving robot, with ±45° and ±90° rotations referenced to optical motion capture. One relative-angle error per movement is calculated between settled windows. These figures describe the change between holds, rather than tracking throughout rotation.

Continuous relative-orientation tracking. Evaluated at host receipt against optical orientation, without removing orientation delay. ² AHRS roll is the off-axis result in pitch-driven runs, within ±60° pitch. ³ Yaw removes heading wander using a 10 s moving average; it is not absolute-heading accuracy.

Each “<” value is a conservative rounded upper bound on the applicable aggregate RMSE reported in the available tests. It is not a maximum individual-sample error or a guaranteed production limit. Results depend on mode, filtering, motion and reference quality. IMU-mode figures use manufacturer recordings and their independent recalculation.

Noise & stabilityFused output · Allan analysis
Fused inertial noise and stability characterization bounds
ParameterGyroscopeAccelerometer
Noise density<0.01 °/s/√Hz<200 µg/√Hz
Random walkAngle: <0.6 °/√hVelocity: <0.12 m/s/√h
Bias instability<7 °/h<0.001 m/s²

Noise and stability: stationary room-temperature AHRS recordings at 200 Hz and 1 kHz, including a >23 h independent recording with filters disabled. Bounds apply to three-axis means; individual axes can be higher. White-noise coefficients use Allan analysis around 1 s; bias instability uses the Allan minimum divided by 0.664. Results depend on configuration and analysis window.

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, connect a data-capable USB cable and allow the USB network interface to enumerate. Set the host USB adapter to the sensor subnet.

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/x1/id001/imu \
  --qos-reliability best_effort

Use the commissioned device address and configured namespace. Match subscriber reliability to publisher QoS. Verify host ECM / RNDIS support; use unique addresses, subnets and namespaces when integrating multiple sensors.

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/TemperatureMean MEMS temperature, in °C
statusdiagnostic_msgs/msg/DiagnosticStatusDevice diagnostics, including CPU temperature

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. ROS 2 host reception was verified with Humble and Jazzy using Fast DDS.

Designed to fit your system

Compact by design.
Detailed where it matters.

A 40 mm footprint, base and side mounting options, and a screw-retained USB-C connection. Integrate the sensor with a defined mechanical and coordinate reference.

X1 Pro engineering drawing: 40 by 40 by 10 mm enclosure, 28 mm mounting centres, M3 mounting threads and 15 mm USB retention spacing
Nominal dimensions in mm. Use the controlled drawing for production tolerances and screw engagement.

Mechanical & electrical

Mechanical and electrical specifications
Envelope40 × 40 × 10 mm, excluding cable
Bare-unit mass32 g nominal
Base mounting4 × M3 × 0.5, 6H; 28 × 28 mm centres
Side mounting2 × M3 × 0.5, 6H; 28 mm spacing
Cable retention2 × M2 × 0.4, 6H; 15 mm spacing
Data / powerUSB Type-C · Ethernet-over-USB 2.0
Input voltage4.6–5.5 V DC
Power0.9 W typical; 1.8 W supply allowance

Sensing & configuration

Sensing and configuration specifications
Acceleration ranges±2 / ±4 / ±8 / ±16 g
Angular-rate ranges±125 / ±250 / ±500 / ±1,000 / ±2,000 °/s
Inertial resolution16 bit nominal front end
Publication setting1–1,000 Hz configurable¹
Output framesFLU / FRD / legacy compatibility
Application profilesDrone / Mobile Robot / Humanoid / Raw
PlatformolixOS™ with olixAI™ · 512 MB memory / 32 GB eMMC nominal
Ambient operation−20 to +80 °C⁴

¹ Publication rate is a configurable setting; achieved throughput depends on mode, filtering, host and system load. Measurement bandwidth and publication rate are configured separately. ⁴ Temperature qualification here is functional publication across an approximately 4 h ambient ramp-and-soak test; it does not specify orientation accuracy across temperature. Internal MEMS temperature is reported separately.

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 X1 Pro’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 and AHRS are the device’s mode names. IMU mode uses inertial acceleration and angular-rate measurements for relative orientation. AHRS mode adds onboard bias estimation and filtering. In the characterized configuration, neither orientation solution uses magnetometer aiding; yaw is relative rather than a magnetic-north heading.

Auxiliary magnetic-field data is available separately. Apply external heading aiding when the application requires an absolute heading reference.

Does X1 Pro publish at 1,000 Hz?

The publication-rate setting is configurable from 1 to 1,000 Hz, with a 100 Hz nominal default. Effective throughput depends on the selected mode, filtering, enabled streams, host configuration and system load. Verify the received rate in your application. The output setting is separate from measurement bandwidth.

What does “timestamp-to-callback below 2 ms” mean?

The datasheet reports a median timestamp-to-host-callback interval below 2 ms at 200 Hz, 400 Hz and 1 kHz. It measures the age of the message’s header timestamp when the host callback runs. It is not a worst-case motion-to-message latency.

Signal filtering contributes separate delay. Reported alignment estimates give rounded bounds of <10 ms for angular rate and <40 ms for orientation at 1 kHz, and <10 ms / <100 ms respectively at 200 Hz on the tested settings. These are recording-level estimates, not guaranteed motion-to-host maxima. Account for signal delay in the host estimator.

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 make the present orientation the local reference; it does not replace bias calibration.

Choose FLU or FRD consistently, apply the installed sensor-to-robot transform and confirm stable output after configuration changes or a 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 configurable ports 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 X1 Pro sensors?

Assign unique device IP addresses and ROS namespaces. Configure USB subnets and host routes to prevent addressing conflicts, and provide a sufficient host power budget for each unit. Confirm the selected ECM / RNDIS profile, discovery configuration and subscriber QoS on the intended host.

Which cable and mounting accessories should I order?

Specify the USB cable length, host connector and matching screw-retention hardware. Confirm sensor and accessory quantities in the quotation. Leave clearance for the mating connector, cable bend and strain relief; choose mounting screw engagement using the controlled drawing.

Documentation & next steps

Documentation.
And direct support.

Technical reference

X1 Pro 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™ X1 Pro

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™ X1 Pro Datasheet, Technical Document 1790616122, Rev. 0.8, 19 October 2026. Rounded characterization figures apply under the stated test conditions and are not guaranteed production limits. Dimensions and mass 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.

¹ Scope and Precedence. This notice governs all statements, specifications, images, performance figures, CAD/STEP drawings, SDKs, binaries, and downloadable materials referring to any olixSense™ unit (including but not limited to X1, X1 Pro, and X1 Ultra). In the event of inconsistency, the latest signed commercial agreement or Olive Robotics GmbH (“Olive”) published technical bulletin shall prevail. Materials may be revised, replaced, or withdrawn at Olive’s discretion without prior notice.

² Informational Nature; No Warranted Characteristics. Datasheets, user guides, ROS 2 topic maps, latency/jitter figures, accuracy tables, and benchmark graphics are provided solely for orientation and planning. They do not constitute an assurance of properties, a guarantee, or a durability warranty, and are expressly subject to deviation under field conditions, including but not limited to host design, mounting geometry, EMI/EMC exposure, thermal cycling, supply quality, and middleware stack variation. See also Olive’s technical document series for X1 Pro (rev. V0.1) which characterizes features and publishes a non-warranty disclaimer. 

³ Validation Regime. Unless stated otherwise, all performance claims (e.g., output-data-rate ranges, fusion ODR ceilings, sub-ms time-sync, orientation RMS) are measured on internal rigs under controlled conditions using standardized robotics workloads (e.g., UAV stabilization, AMR trajectory tracking). Replication by third parties requires equivalent instrumentation, calibration procedures, excitation profiles, and environmental controls; otherwise, divergence is expected.

⁴ Series Variants and Configuration Dependence. Capabilities may differ among X1, X1 Pro, and X1 Ultra (e.g., number of redundant MEMS arrays, magnetometer inclusion, thermal envelope, power draw, maximum filtered ODR, or olixAI™ model class). Any feature labeling “typical,” “up to,” “~,” or “<” denotes indicative, configuration-dependent values and shall not be interpreted as a unilateral promise of performance.

⁵ Software Stack; Licensing. olixOS™ (real-time Linux kernel adaptations), olixAI™ embedded fusion models, bootloaders, and control-panel software are licensed, not sold. They may include FOSS components subject to their respective licenses; compliance with such licenses is the integrator’s responsibility. Reverse engineering, decompilation, or circumvention of signature checks or secure-boot policies is prohibited except to the extent mandatorily permitted by law. Olive may condition feature access (including advanced fusion modes) on version alignment and/or license activation.

⁶ Firmware, Models, and Updates. OTA or tethered updates (e.g., over Ethernet-over-USB) may modify timing, fusion strategies, security posture, or driver interfaces and can enable/disable features for integrity or safety reasons. Olive reserves rollback rights and may impose cryptographic verification as a precondition to boot or update acceptance. Use of non-authorized binaries voids support and may disable the device.

⁷ Interoperability and Middleware. ROS 2/DDS interoperability (e.g., Fast DDS, Cyclone DDS) is validated only for enumerated versions and default QoS profiles; other versions, custom QoS, or alternate middlewares may require adaptation bridges and are outside conformance unless expressly certified in writing. Topic schemas are subject to evolution with semantic versioning; backward compatibility is a goal, not a guarantee.

⁸ SDKs and Reference Code. SDKs, examples, and reference drivers (including browser-based GUIs) are provided “as is,” for development and integration assistance only. They are not production commitments, and Olive assumes no duty to maintain API stability, ABI compatibility, or indefinite repository availability. Integrators must conduct independent cybersecurity review, static/dynamic analysis, and functional safety assessment.

⁹ IP and Confidentiality. All patents, patent applications, copyrights, design rights, trade secrets, trademarks, and mask works related to olixSense™ enclosures, PCBs, fusion algorithms, timing schemes, calibration processes, and manufacturing workflows are reserved. De-labeling, logo removal, or misrepresentation of origin is prohibited. Any non-public artifacts (e.g., private datasheets, test vectors, or beta firmware) are confidential information.

¹⁰ Safety-Critical Exclusions. Unless explicitly certified for a particular standard (e.g., IEC 61508, ISO 26262, DO-178/254), olixSense™ units are not designed for life-support, human-rated aerospace, or other safety-critical contexts where failure may cause personal injury, death, or catastrophic loss. The integrator bears sole responsibility for system-level hazard analysis, FMEA, functional safety architecture, and certification.

¹¹ Export Controls and Sanctions. Hardware, software, technical data, and cryptographic functionalities may be subject to EU, German, and—where applicable—U.S. export/sanctions regimes. Customer warrants compliance, including classification, licensing, end-use and end-user screening, and record retention. Olive disclaims responsibility for a buyer’s regulatory posture and may suspend deliveries for compliance reasons.

¹² Measurements, Tolerances, and BOM Variability. Physical dimensions, weights, torque specs, connector pinouts, and bill-of-materials line items are subject to normal manufacturing tolerances and supply-chain substitutions of equivalent form/fit/function components. Integrators must design mounting and harnessing with appropriate allowances and verify assemblies during incoming quality control.

¹³ Power, EMI/EMC, and Environment. Published power figures assume regulated inputs and compliant ground strategy. Ripple, ground loops, conducted emissions, or cable ingress can degrade timing and fusion accuracy. Environmental limits (temperature, vibration, humidity, dust, ingress) apply at the device boundary; external housings may be required to meet application-specific IP ratings or EMC directives.

¹⁴ Data, Logs, and Privacy. Diagnostic streams, timestamps, and calibration/state logs may be generated and stored locally for service, safety, and quality purposes. Customer is responsible for ensuring lawful processing of any personal or operational data captured in adjacent systems when using such logs for analytics, remote support, or fleet management.

¹⁵ Third-Party Dependencies and Marks. References to ROS, DDS, Linux, Arm®, TrustZone®, USB Type-C®, or other third-party technologies are descriptive only and imply no sponsorship, endorsement, or affiliation beyond documented licenses. All third-party marks are the property of their respective owners.

¹⁶ Commercial Terms; Availability. Quotations, lead times, and service-level statements are indicative and not binding until accepted by Olive in writing. Ship-dates are subject to component supply, regulatory screening, and force-majeure events. Olive may allocate constrained inventory across customers at its reasonable discretion.

¹⁷ Field Returns and Forensics. RMA acceptance is conditioned on adherence to Olive’s diagnostic triage, firmware provenance verification, and physical inspection protocols. Devices showing unauthorized modification, tampering, or operation outside published limits may be returned unrepaired or subject to fee-based service.

¹⁸ Limited Warranty; Exclusive Remedies. Subject to Olive’s standard Terms of Sale, Olive warrants only that new olixSense™ units will be free from defects in materials and workmanship under normal use for the stated warranty period. THE SOLE AND EXCLUSIVE REMEDY SHALL BE REPAIR, REPLACEMENT, OR REFUND (AT OLIVE’S ELECTION). TO THE MAXIMUM EXTENT PERMITTED BY LAW, ALL OTHER WARRANTIES—EXPRESS, IMPLIED, OR STATUTORY (INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT)—ARE DISCLAIMED.

¹⁹ Damage Limitation. EXCEPT FOR LIABILITY THAT CANNOT BE LIMITED BY LAW (E.G., PERSONAL INJURY CAUSED BY OLIVE’S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT), OLIVE SHALL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS, BUSINESS INTERRUPTION, OR DATA LOSS), NOR FOR COSTS OF SUBSTITUTE GOODS OR SERVICES, ARISING FROM OR RELATED TO THE PURCHASE, USE, INTEGRATION, OR INABILITY TO USE OLIXSENSE™ PRODUCTS, SOFTWARE, OR DOCUMENTATION.

²⁰ Governing Law and Venue. All disputes arising out of or in connection with olixSense™ products or related materials shall be governed by the laws of the Federal Republic of Germany, without regard to conflict-of-laws principles. Exclusive venue shall be the courts of Munich, Germany; Olive reserves the right to seek injunctive or equitable relief in any competent jurisdiction to protect its intellectual property.

²¹ Updates to this Notice. Olive may amend this series-specific notice at any time. Continued access to materials, SDKs, or shipments following publication of revisions constitutes acceptance of the amended terms.

Legal notice

  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. 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 Physical AI for sensors & robots.

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