Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
workbenchthis machine
TOP: the hosted app connects to the real arm and camera - it still serves the simulation with ARM_SERVER set and both addresses granted #40
Sign in to join this conversation.
new above
offline
Probe 2026-10-20 20:25Z, everything outside the app is in place:
curl 127.0.0.1:8101/status→ shoulder_pan position 2017, 23 °C, torque true.Yet: the public
/statusreturns the simulation (every joint position 2048, torque false, temperature 0), and on the Pissshows NO connection from the forge (100.84.55.62) to :8101 or :8080 - only the owner's Mac. Before the grants the deploy log saidegress refused: 100.89.95.68:8101 ...; after, nothing.Find why and fix, smallest change first. Likely places: the production entry (forge.json app.run = Software/so101/bench/fake-serve.ts) may never read ARM_SERVER, or it reads it only at a different path; the WebSocket/MJPEG client may not go through the cell's egress (check how Bun fetch/WebSocket reach the outside inside a cell - an egress proxy env such as HTTP(S)_PROXY, or a direct connect); or it falls back to the simulation silently. Make the fallback loud: /status says
"source":"live <host>"or"simulated: <why>", and the UI shows it. Done: the public /status shows the real joints (not 2048s), the camera tab shows the Pi's stream, andsson the Pi shows the forge connected. The crew may use the Pi over SSH once trevato/forge#3470 lands ([email protected]).