Open Source RoboticsRobots, software & learning

MicroStrain inertial ROS2 driver

Software

This repository provides ROS 2 interface packages for MicroStrain inertial devices, including a driver, messages, examples and separate RQT status tools. [1] [2] [3] [4] [5] [6] [7]

Installation & first result →Official websiteGetting started

For
Robotics developers selecting a concrete sensor, interface or simulation workflow [1] [2] [3] [4] [5] [6] [7]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

This repository provides ROS 2 interface packages for MicroStrain inertial devices, including a driver, messages, examples and separate RQT status tools. The README identifies the MicroStrain Inertial Protocol SDK underneath the interface. The released contribution is sensor-integration software, not an open inertial sensor design or a validated navigation solution. [1]

Is this for you?

Known limitations
  • Submodule checkout/update is separate from top-level revision; no complete matcheddevice build tested.
  • Differentdriver/RQT licenses and externalSDK/hardware terms remain separate.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] [6] [7] · Editorial assessment

What you need

Dependencies
  • ROS2 branch and matchingROSdistribution; recursive submodules and MIP SDK dependencies
  • Deviceport/permissions and nodeconfiguration; RQTstatus tool installed separately

[1] [2] [3] [4] [5] [6] [7]

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4] [5] [6] [7]

  • Select the named hardware/model and corresponding source configuration before installation.
  • Follow the cited starting route while keeping package, device and firmware versions matched; no operation reproduced here.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] [6] [7] · Editorial assessment

Installation

ROS 2 recursive clone of branch `ros2`, submodule initialization/update, rosdep and colcon workspace build/source; binary driver/RQT packages and udev rules are a separate route.

Upstream documented requirement/configuration only, not independently tested installation or compatibility.

[1] [4]

Project notes

A top-level checkout is only one part of the source setup

The README says this branch contains ROS 2 code and directs ROS 1 users elsewhere. Its source route uses a recursive ros2-branch clone, rosdep, colcon and sourcing the resulting workspace. Submodules share code between versions: the README explicitly warns that automatically checking out a missing submodule does not keep it updated. The common submodules are microstrain_inertial_driver_common, microstrain_inertial_msgs_common and microstrain_inertial_rqt_common, each nested under its corresponding package. The documented initialization is git submodule update --init --recursive; after pulling, use git submodule update --recursive. The reviewed wrapper revision is 77271ba3f80d73b9d03be613df944ab7d29b7f4b. Preserve it alongside selected submodule revisions; this packet does not supply those individual submodule commit IDs. A wrapper checkout alone is not a complete tested dependency set. [1] [4]

For packaged installation, the README separates driver and RQT packages and uses ROS_DISTRO as a distribution placeholder. Replace that placeholder and verify package availability for the chosen environment. Buildfarm installation installs udev rules automatically. For multiple devices, use serial-specific /dev/microstrain_main_{serial} and /dev/microstrain_aux_{serial} paths rather than the shared aliases that get overwritten. For ROS 2 overrides, start from empty.yml and select it with params_file; the linked ROS-format params.yml cannot be passed directly to ROS 2. No binary package, submodule build or sensor port was tested here. [1] [6]

The inspected driver/lifecycle-node source gives a concrete ROS execution boundary to investigate alongside the underlying SDK. A started ROS process or a status panel is not evidence of correct output frames, timing, calibration or a particular device configuration. Select those settings before treating the published measurements as robot state. No device data or lifecycle transition was exercised. [5] [7]

What we checked

Pinned documentation/selected source review only; no build, installation, live device/network, simulator, calibration or performance test.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
77271ba

Source files and licenses

Distinct robot-facing source implementation/interface; no purchased hardware design or untested performance claim.

LayerAvailability / license
softwareavailable · MIT driver; BSD-2-Clause RQT plugin notice
Scoped source declaration; purchased hardware, firmware, binaries, assets and external dependencies require separate terms. [1] [2] [3] [4] [5] [6] [7]
documentationavailable · MIT driver; BSD-2-Clause RQT plugin notice
Scoped source declaration; purchased hardware, firmware, binaries, assets and external dependencies require separate terms. [1] [2] [3] [4] [5] [6] [7]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

Preserve the component licenses

The driver notice is MIT for the identified contribution. The RQT plugin has a separate two-condition BSD-style notice. Neither declaration establishes the rights of every submodule, firmware image or purchased sensor. This review did not test orientation accuracy, timing, recovery, sensor calibration or physical navigation. [2] [3]

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history