update dataflow-gamepad to drive the arm instead of the bench

It now runs joy, teleop and dora-ulite6 with the probe declared and the
console shut, so a pad can be checked against the arm that will actually
move. ROBOT_IP in both arm dataflows points at the bench arm.

The run recipe drops dora up + dora start: dora 1.0.1 refuses to start a
dataflow holding git: nodes from a coordinator, reporting that no build was
run straight after one that succeeded. That costs the file dora topic, which
needs a coordinator to read the wire.
This commit is contained in:
2026-09-16 18:06:12 -03:00
parent 7a0847893c
commit eede2e5774
3 changed files with 63 additions and 31 deletions
+3 -2
View File
@@ -5,8 +5,9 @@
# manifest from `path:` and CI needs no gamepad, no robot and no sibling clones.
#
# There is **no gamepad here**, because the pad is another node and wiring it in
# by `git:` would cost this file the one property it has. For a real pad on a
# real bench, use `dataflow-gamepad.yml`.
# by `git:` would cost this file the one property it has. For a real pad, use
# `dataflow-robot.yml`, or `dataflow-gamepad.yml` to check the pad with the
# probe — both of which drive a real arm.
#
# This is **not** the real stack. The bench answers services and publishes
# telemetry but never moves anything. README.md carries the four-node wiring a