Reachy 2023 Camera Focal Length: Why It’s Missing and How to Get It
Pollen Robotics doesn’t publish a focal length for Reachy 2023’s Kurokesu C2 cameras — here’s why, and how to get the intrinsic matrix you actually need for stereo depth estimation.
Pollen Robotics doesn’t publish a focal length for Reachy 2023’s Kurokesu C2 cameras — here’s why, and how to get the intrinsic matrix you actually need for stereo depth estimation.
Reachy 2023’s official docs skip audio entirely. Here are three working approaches — ReachyAudio, direct SSH with Linux tools, and the Reachy 2 SDK — to get sound playing through the robot’s speakers.
Reachy 2023’s reachy-sdk has no built-in audio module. Here’s how to play sound through the robot’s speaker using direct Linux audio tools and Python, plus how the newer Reachy 2 SDK compares.
Camera missing from lsusb and /dev/video* on Reachy robot 1? This guide walks every diagnostic step from USB enumeration errors to confirming hardware failure.
If your Reachy 2021 head won’t move even with the power off, the Orbita parallel mechanism likely has a mechanical jam. Here’s how to diagnose it and what to open up.
If your Reachy 1’s cameras are invisible to lsusb and /dev/video*, here’s how to distinguish a physical failure from a driver problem and what to check before opening the head.
When lsusb shows nothing for your Reachy 1 cameras, it’s not a driver issue. Here’s how to properly diagnose a CSI camera failure on the onboard Raspberry Pi and fix it.
Reachy 1 cameras missing from lsusb and /dev/video*? Learn how to read the diagnostics correctly and fix the problem from physical connections up to the ROS 2 layer.
Step-by-step guide to running three Reachy2 robot simulations in separate Docker containers, each on its own gRPC port, with a working docker-compose example and Python SDK connection code.
If your Reachy robot 1 cameras don’t appear in lsusb or /dev/video*, here’s how to tell whether it’s a physical connection failure or a missing driver — and how to fix each.