Command center hub
Live surgeon target
Delayed robot end-effector
⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.
A single command center rarely runs one telesurgery link at a time — it manages several simultaneous robotic procedures across sites at very different distances, all sharing one finite uplink. This simulator models three such links as a real queueing-theory and fiber-propagation problem: you set the total bandwidth budget, how the traffic shaper prioritizes each site, the jitter buffer size, and background network load, and watch the resulting round-trip latency drive each robotic arm's ability to track its surgeon's live motion. Push a link's latency past the safety threshold and its controller stops executing stale commands and enters autonomous hold — the same fail-safe behavior real telesurgery systems use when the network can no longer guarantee a safe control loop.