Skip to content

Overview

This chapter introduces how to establish a closed-loop safety workflow for officially released control pathways across the dual arms, head, and waist, while clarifying reference guidelines and functional constraints for the chassis, grippers, voice modules, and power management systems.

  • Applicable Hardware & Version Baseline:

    • Device Model: RealBot01_RX75
    • Software Version: V1.1.1-dl / V1.2.9
    • Hardware Version: HW 1.2
    • Pathway Constraints: Strictly utilize control pathways designated as officially released within the Capability Matrix.
  • Risk Levels:

    • Controlled Risk: Standard operational tasks.
    • High Risk: Modifying mechanical software/hardware limits, power management states, or core service configurations.
  • Content Scope:

    • Read real-time device telemetry alongside software and hardware limits, issue low-speed and small-amplitude motion commands, and validate position reset and state recovery upon task completion.
    • Although vendor protocol definitions are included in this documentation, message structures without completed motion closed-loop verification serve purely as "Reference Information." Replicating or executing these payloads directly as automated steps is strictly PROHIBITED, and issuing malformed payloads for trial-and-error testing is strictly PROHIBITED.