Magni

The default repository snapshot is a different software route

The primary collected repository snapshot contains ROS 2 description and simulation launch files, and its README explicitly says other portions still need porting from ROS 1. The separately preserved Noetic branch includes the bring-up, teleoperation and navigation configuration discussed here. That branch selection is deliberate: the manufacturer's Noetic image instructions start ROS core and Magni services and cannot be treated as instructions for the incomplete ROS 2 snapshot. [S001] [S005] [S006] [S011]

The image guide calls for a Raspberry Pi and an SD card of at least 16 GB. Images include ROS and Magni packages, while Conveyorbot and EZ-Map images are supplied separately. The source archives inspected here do not include a validated copy of those images or establish the terms of every installed application. No image was flashed or booted for this review. [S011]

Configuration overrides can change the running robot

The Noetic bring-up documentation explains that the magni-base service launches base nodes and generates a configuration-dependent launch file. Motor settings come first from /etc/ubiquity/robot.yaml; missing values fall back individually to package defaults. A partially populated override can therefore produce a mixture of local and default settings. Inspect the effective configuration when moving an SD card or software checkout between robots. [S006]

Camera and lidar extrinsics also have override locations. The chosen sensor and position in the robot configuration determine which calibration file is used, with user files taking priority over packaged files. A sensor mount change should trigger a review of the selected extrinsics rather than an assumption that the package defaults still describe the robot. These are editorial setup recommendations based on the documented precedence rules. [S006]

The motor interface subscribes to velocity commands and publishes odometry, firmware identification and motor state. Those outputs are useful for checking what is running, but a ROS topic name alone does not establish correct wheel calibration, sensor placement or an independently tested stop function. This publication performed no driving or controller validation. [S008]

Hardware revisions constrain replacement parts

The manufacturer's revision history records changes to the main controller board and its paired switch board. In particular, it says MCB revision 5.0 requires the newer revision 2.0 switch board with four resistors and will not power up with the older three-resistor board. It also records firmware changes that required corresponding host-side updates. These historical tables are evidence that revisions matter, not a recommendation to install whichever firmware number appears last in an old guide. [S012]

The setup requirements include two 12 V lead-acid batteries because the robot ships without them, plus a CR2032 clock battery. A purchased-base price would therefore not automatically be a complete operational budget. Current delivered cost, battery sourcing and a full build-specific bill of materials remain unverified. [S010]

Record the complete configuration

For a configuration record, preserve the following together. This checklist is an editorial synthesis of the source and setup requirements:

• The reviewed magni_robot Noetic commit dfaee639044f81ce5ec46473408a02b6dc452114 and ubiquity_motor commit 52a35ba5b2f46113e48c0524a6d9b72a446c28e2. [S005] [S008]
• The installed image identifier and ROS environment, plus the physical MCB and switch-board revisions. [S011] [S012]
• The firmware version and date code reported by the controller interface. [S008] [S012]
• /etc/ubiquity/robot.yaml, the package defaults it falls back to, and the selected camera/lidar extrinsic files. [S006]

Only the named source snapshots and documentation were preserved by this review. The installed image, board and firmware combination remains unverified.

Host source availability does not include controller firmware

The selected Noetic README explicitly says the motor-controller firmware is not to be released. Its public host packages and the separately inspected motor-interface repository carry BSD-3-Clause license text, but that does not establish firmware source availability or a fully reproducible controller build. The profile records this as partial source availability. [S005] [S007] [S009]

Mechanical dimensions and board information are available in the manufacturer's documentation, but this review did not establish a complete editable fabrication package or matching electronics design. No assembly, image installation, calibration, payload test or navigation result is claimed. [S012] [S013]