Live controller
The TQC policy runs on the chip's second core every control tick. Arm it, pick a target pose, and watch the network think. Esc disarms from any tab.
- —control rate
- —loop load
- —misses / min
- —telemetry
Inside the network
Swipe sideways to see the whole network.
Each square is one neuron, violet when positive and green when negative. Your browser downloads the device's own weights and runs the same forward pass on every observation the controller streams. In delta mode the output is a force rate (N/s) that the controller integrates into the force command; it drives the cart only when the device is armed in AI mode, otherwise it is a dimmed preview.
Health
Loop timing, the two cores and their tasks, memory, and the link to this page.
Control loop
—- policy
- —
- estimator
- —
- exec max
- —
- deadline misses
- —
- real-time factor
- —
Cores & tasks
—| task | core | prio | cpu | stack free |
|---|---|---|---|---|
| waiting for the device… | ||||
Memory & link
—- internal free
- —
Telemetry is what this page receives: frames per second against the device's rate, and gaps in the tick count (frames lost on Wi-Fi).
Sensors & drive
—Waiting for the device…
Event log
—- Waiting for the device…
Faults, arming, uploads, Wi-Fi and calibration; local time once the device's clock is set over the internet, else time since that boot (hover for both). The device keeps the latest 40 through crashes, watchdog resets and reboots (not a power-off), so the entries before a reset explain it.
Record
Log every control tick, with optional excitation, for system identification.
Record
—- samples
- —
Settings
Network, firmware and model updates, and the device itself.