Organize host and robot streaming releases

This commit is contained in:
Mike Mi
2026-08-09 15:56:20 +08:00
commit decff19daf
532 changed files with 127054 additions and 0 deletions

21
robot/README.md Normal file
View File

@@ -0,0 +1,21 @@
# Robot releases
There are two camera acquisition releases. Choose one for a run:
## `v4l2`
`robot/v4l2/OmniSocketGo_robot` opens `/dev/video*` directly. It is the
2026-08-08 robot package extracted from the deployment bundle. Use it when
testing direct MJPEG/V4L2 access and make sure no Orbbec/proc_manager camera
process owns the selected device.
## `ros2`
`robot/ros2/OmniSocketGo_robot_ros` subscribes to the Orbbec ROS 2 RGB topics
through `omnisocket_camera_bridge`. The bridge keeps the existing KCP payload
format while avoiding a second V4L2 opener. It is the path to use when local
RGB/depth consumers and `proc_manager` must continue running.
The two releases use the same transport peer IDs and daemon entry points; do
not run both simultaneously on one robot. See each release README and the
root `NETWORK_LINK_STARTUP_GUIDE.md` for startup and network configuration.