9 Boundaries & Disclaimer for Secondary Development

Warning

  1. Do not modify the system environment on the ORIN module (such as OS, drivers, and dependency libraries), as this may affect the robot’s stability and compatibility.

  2. Taking Motion Control Computing Unit (PC1, 10.0.1.40) as build & run environment for secondary development is strictly prohibited to avoid safety risks

  3. Do not alter system configurations or built-in algorithm parameters (such as DDS configuration files, kernel settings, and algorithm-related configurations).

  4. Unauthorized modifications or access to hardware interfaces, power systems, or communication buses are strictly prohibited to avoid hardware damage or safety risks.

  5. If integrating third-party software or libraries during secondary development, use the containerized development mode and ensure compliance with relevant open-source licenses and regulations. If the container mode does not meet your requirements, consult AgiBot technical support in advance to evaluate potential library conflicts.

  6. All custom features and extension modules should preferably be implemented as plugins or independent processes, rather than replacing or overriding official core components.

  7. If you encounter system abnormalities, functional issues, or safety warnings, refer to the robot operation guide or contact official technical support. Do not perform high-risk operations on your own.

  8. Launching ROS nodes in rapid bulk while the robot is in Stable Standing Mode or Locomotion Mode is strictly prohibited (no more than 2 nodes per second is recommended). A large number of nodes joining DDS discovery within a short period causes communication congestion, which degrades motion control real-time performance and may cause the robot to lose balance and fall. When multiple nodes are needed, launch them in batches, or finish launching them in Zero-Torque Mode or Damping Mode before switching to a motion mode.

AgiBot will not provide support or warranty for any software/hardware damage or interface call failures resulting from violating the above boundaries.