镜像自地址
https://github.com/MINT-SJTU/Evo-RL.git
已同步 2026-11-20 18:17:06 +00:00
docs(piper): clarify leader/follower mode guidance for HIL flows
- document MasterSlaveConfig linkage_config semantics (0xFA/0xFC) in README - update piper leader startup role command from 0xFA to 0xFC - add inline note on commandability and power-cycle requirement after role switch - align piper leader config comment with 0xFC startup role
这个提交包含在:
@ -32,7 +32,7 @@ class PiperLeaderConfigBase:
|
||||
log_level: str = "WARNING"
|
||||
startup_sleep_s: float = 0.1
|
||||
|
||||
# Optional role command on startup (0xFA = teaching input arm)
|
||||
# Optional role command on startup (0xFC = motion output arm)
|
||||
set_leader_mode_on_connect: bool = False
|
||||
|
||||
# Manual backdrivable mode for human teleop
|
||||
|
||||
@ -79,7 +79,12 @@ class PiperLeader(Teleoperator):
|
||||
self._is_connected = True
|
||||
try:
|
||||
if self.config.set_leader_mode_on_connect:
|
||||
self.arm.MasterSlaveConfig(0xFA, 0x00, 0x00, 0x00)
|
||||
# NOTE:
|
||||
# - Piper teaching-input mode (0xFA) does not accept external JointCtrl/GripperCtrl commands.
|
||||
# - For policy-sync and human-in-the-loop switching, the leader must remain commandable,
|
||||
# so we configure it as motion-output mode (0xFC), same as the follower side.
|
||||
# - Mode-role changes (e.g., 0xFA <-> 0xFC) may require a full power-cycle to take effect.
|
||||
self.arm.MasterSlaveConfig(0xFC, 0x00, 0x00, 0x00)
|
||||
time.sleep(0.05)
|
||||
self.configure()
|
||||
except Exception:
|
||||
|
||||
在新工单中引用
屏蔽一个用户