Connection Modes

The SDK reaches the robot in one of three connection modes. The Robot object and every verb are the same in all three; the mode decides what the connection carries and where it works from.

A saved robot carries a mode, so Robot().connect() needs no argument. Pass one to override it for a session: connect("udp").

connect.py builds the connection in code. Set MODE at the top of the file to "udp", "hybrid" or "livekit"; the three ConnectionConfig shapes sit side by side:

The other example scripts call Robot() with no config and read the environment or a saved robot instead; see How the SDK Picks a Connection.

Commands go to the robot on UDP port 8850 and state comes back on port 8851. There is no media and no sign-in: anyone on the robot's network who can reach port 8850 can command it, so trust the network before you turn it on.

The robot sends UDP state to one host. In Asimov Manager, set the Asimov Edge parameters udp-control to on and udp-state-host to your computer's address (Asimov Manager).

One client per state port: a second script on the same computer binds UdpConfig(state_bind=("0.0.0.0", <port>)) and the robot's udp-state-port matches it.

Control and state travel as in udp, so a velocity command does not cross the internet. The camera, microphone and speaker travel over the robot's LiveKit room, which the SDK joins with an SDK credential from Asimov Manager. Use hybrid on the robot's network when a script needs the camera or sound.

It needs the robot's address, its Asimov Manager URL and an SDK credential. Issue the credential on the Developer page of Asimov Manager (Get an SDK Credential). The credential's role applies to the LiveKit room: a Control credential can talk through the speaker, an Observe credential watches and listens only. Commands in hybrid travel over UDP, which has no sign-in, so the role does not limit driving.

Everything, commands included, goes through the robot's LiveKit room. Commands travel on the data topic commands and state on the data track state, at about 10 Hz. Use livekit away from the robot's network, or when an agent framework joins the same room and the SDK is one more participant in it.

It needs the Asimov Manager URL and an SDK credential (Get an SDK Credential). The SDK asks Asimov Manager for a room token, joins, and reports robot.info.endpoint as room@url as <identity>. The credential's role applies: a Control credential drives, an Observe credential watches and listens, and the robot drops its commands.

The Asimov Manager URL is the one you open in the browser: http://192.168.22.32, http://asimov.local:8080 or a bare host name. The LiveKit URL Asimov Manager hands out is the one the robot itself uses; when it says localhost, the SDK substitutes the manager's host. A manager that redirects is reported as a ConnectError, not followed.

Every SDK session joins the room as its own participant, sdk-<credential id>-<host>-<6 hex>. ManagerConfig(label="...") fixes the suffix so a restarted script replaces its previous session instead of joining beside it. To join with a token you minted yourself, pass LiveKitConfig(url, room, token) instead of ManagerConfig; one token is one participant. To use the room without the SDK at all, see Without the SDK.

Robot() with no argument builds its connection from the environment or a saved robot, in this order:

MENLO_MODE sets the mode connect() uses with no argument and MENLO_LIMITS the velocity limits, whichever source supplied the connection. MENLO_HOME moves the store directory.

A saved robot holds everything one mode needs, and can hold more than one mode's fields:

udp needs udp_host; hybrid needs udp_host, manager_url and credential; livekit needs manager_url and credential. A mode whose field is missing raises ConnectError naming the field and the menlo robots add command that fills it. Save and change robots with the command line; the file is created with mode 0600 because it holds SDK credentials.

connect() returns once the robot has reported state, so robot.get_state() is valid on the next line. It raises ConnectError after timeout (5 s by default) without state. On hybrid and livekit the media tracks are awaited for media_timeout (3 s); the capabilities the SDK claims are the tracks that arrived.

connect(require_state=False) opens the room without waiting for the firmware: camera, microphone and speaker work at once, and state and the motion verbs unlock when the first state frame arrives.

A protocol version other than the one the SDK speaks raises ProtocolMismatchError. allow_version_skew=True connects anyway, and the robot may misread the commands the SDK sends. Update the SDK or the robot instead.