3 Commits

Include renames

Author	SHA1	Message	Date
cristhian	8a7bfb02e0	add a probe that shows what the gamepad is doing ... The axis and button indices in mapping.py are SDL's documented layout rather than an observed one, and until now the only way to find a pad that numbers things differently was to watch a real arm move the wrong way. `dora-teleop-probe` prints the raw axes, the buttons it sees and the velocity that would be sent, live, with no dataflow and no arm — it cannot move anything. It goes through the same Gamepad and velocity() the node runs, so what it prints is what the arm would get; that is the whole reason it is worth having, and the reason it must not grow its own copy of the mapping. Every axis is listed, including ones the layout does not use, because an axis marked unused that moves when a stick is pushed is exactly the finding this is for. The centred bar makes a worn stick that does not return to zero obvious.	2026-09-15 15:47:36 -05:00
cristhian	7250396a1f	add the node manifest, dataflow, CI and docs ... dora-node.yml is the typed contract a consumer wires against, and the only one they get: no source package is shared between node repositories. The jog, request and ui ports stay untyped, because dora treats a port carrying request_id as pattern-correlated and several Arrow schemas legitimately flow over each — one per service, one per console message. dataflow.yml runs the whole operator stack from checkouts: this node, the WebSocket bridge and the arm. web/ holds a placeholder page, not the real console. It exists so the dataflow has something to serve and so the node can be checked end to end before the Control section is ported across from the monolithic repo. It reads telemetry and can take, release and stop; nothing else.	2026-09-15 15:43:12 -05:00
cristhian	bde8582de3	add the gamepad reader and the node's settings ... The reader owns the pad on a thread of its own, and nothing outside that file may touch pygame: everything else sees a plain immutable Sample. That is what lets the rest of the node be tested with no hardware, and what keeps SDL's quirks out of the arm logic. Sample.present is the field that matters. A pad that has been unplugged reads as absent rather than as centred, so "the operator let go" and "the pad fell off the desk" stay distinguishable — they call for the same stop, but only one of them is worth logging. Only the display and joystick subsystems are initialised. pygame.init() also opens audio, which on a headless robot fills stderr with ALSA errors for a device this node never uses; the display is needed despite there being no window, because SDL refreshes joystick state during the event pump. Settings are parsed once at startup so a deadzone that would silently make the pad inert stops the node before it joins the dataflow.	2026-09-15 15:42:48 -05:00