Hardware & Calibration
The model identified by the platform does not match the physical hardware
At startup the platform scans the serial device list; detection of an OpenRB-150 control board results in identification as OpenMANIPULATOR-X, and absence of detection defaults to SO-101.
Where the identification does not match the physical hardware, specify the model manually at Data Tools → Hardware Settings → Select Robot and click "Save Settings". Prior to saving, the "Reset Arm" and "Arm Calibration" buttons remain hidden or disabled.
Moving the Leader arm produces no corresponding response on the Follower
The most common cause is that the wrong arm was disconnected during serial port detection, resulting in the two arms' roles being interchanged. The system cannot determine operator intent and registers the vanished port as the role designated at that time.
The remedy is to execute serial port detection again; the existing configuration is overwritten and no files require manual removal. See Serial Port Detection.
Serial port detection reports "No difference in the port list"
This indicates that the port lists from the two scans are identical, which may result from no cable having been disconnected, or from an unrelated device having been disconnected.
Both USB cables must be reconnected to the host before retrying, so that the comparison baseline is the complete port list.
Which joint is most commonly omitted during calibration
The gripper (gripper). The gripper is also a motor, and if it is not included in the scan, grasping cannot be learned.
During the range-of-motion scan, the live table on screen is the sole acceptance criterion: if a joint's minimum and maximum values are approximately equal, the motor in question was not actually rotated. See Arm Calibration.
Does closing the calibration wizard partway produce an incomplete configuration
No. The system reports "Calibration cancelled or aborted; no calibration data was written". An interruption does not leave an incomplete configuration, and the procedure may be repeated.
The difference between "Arm Calibration" and "Offset Calculation"
The two are distinct operations:
- Arm calibration (Data Tools → Hardware Settings): aligns the physical arm's readings with physical reality.
- Offset calculation (a tab within Simulation Environment Settings): aligns the virtual Follower with the physical Leader.
"Offset Calculation" need not be performed when using the physical hardware workflow.
Camera management reports "No cameras detected"
It must be confirmed that ROS is connected and that the camera devices are correctly mounted. Under containerised deployment, a camera that is physically connected but not correctly mounted into the container is a common cause of this condition.
Entry to the recording page is blocked by "Hardware not ready"
The notification lists the undetected items. Selecting "Detect and connect" permits remediation in place: SO-101 hardware is routed to the serial port detection wizard, while OpenMANIPULATOR-X hardware performs an arm reset.
Note that the items checked vary by page: the simulation page checks neither cameras nor the Follower Arm, and the inference page does not check the Leader Arm. See the hardware readiness check.