Quest Teleoperation

Fix any potential issues with your Quest headset and controllers

Quest headset asleep

If Quest teleoperation isn't working, one simple cause may be that the headset fell asleep. There is a light on the headset that indicates when it's awake; if it's off, one short-press of the button on the side will wake it up, and then it should be ready for action.

The Anvil Devbox is configured to keep the headset awake, so it's advised to keep the headset plugged in even when not actively operating, since this will help it stay awake indefinitely.

Quest controllers asleep

Sometimes, especially after placing them down on a table, the quest controllers themselves can enter sleep mode. Simply holding them close to the headset (within 0.5m) and pressing any button (not moving the joystick) should wake them back up, and allow you to continue controlling your robots.

Quest not detected

Occasionally, the system will report that no ADB devices are detected, meaning it can't tell that the Quest headset is plugged in. This is very rare, but can be fixed by rebooting the Anvil Devbox, and ensuring that the headset is plugged in before the machine boots up.