Asimov Manager

Reference for the robot's on-board console: its pages, the Overview panels, account and access, and the command line.

Asimov Manager is the console that runs on the robot's Raspberry Pi 5 — think of it as the robot's router login page. You use it to set up, start, drive, update and troubleshoot Asimov 1 from a browser. There is no app to install and no cloud account.

Open it at http://<name>.local, where <name> is the hostname you set when flashing the Pi 5. The console serves plain HTTP on port 80. Until you set a password, the login is pre-filled, so the first sign-in is one click — see Connect & Sign In.

In the console, RPU means the Robot Processing Unit in the torso, whose Radxa CM5 runs the motion-control firmware.

Pages

Group	Page	What it's for
—	Overview	The robot's vital signs and its main action — see Overview
—	Cockpit	Drive the robot — see Stand Up and Walk
Robot	Actuators	Assign IDs, check and calibrate actuators — see Calibrate Actuators
Robot	Firmware	Confirm assembly, start and stop the firmware, Start on boot and the RPU link — see First Start
Connections	Wi-Fi	Join and forget networks — see Connect & Sign In
Connections	Controller	Pair a Bluetooth gamepad — see Gamepad
System	Updates	Install a software update — see Software Updates
System	Developer	Issue credentials for the SDK — see Developer Credentials
System	Advanced Settings	Every setting on the robot, raw. Prefer the dedicated pages where they exist
System	Troubleshoot	Health checks, service restarts and logs — see Troubleshooting
User menu	Account	Password, appearance, version and settings reset — see Account and Access

On a phone, the sidebar becomes a menu behind Open Menu in the top bar.

The sidebar's device card shows the hostname, overall health, battery and any connected gamepad on every page. The E-Stop is in the page header of Overview, Firmware, Wi-Fi, Controller, Account and Troubleshoot on a desktop, and in the top bar of every page on a phone — see Stopping the Robot.

Overview

Overview has one main action, which depends on the robot's state:

Firmware	Main action
Stopped	Start Robot
Running	Drive Robot, plus Turn Off Robot
RPU unreachable or not controllable	None — fix the link first

Its panels:

Panel	What to look for
Battery	A percentage, amber below 50% and red below 20%. A blank reading means Asimov Edge isn't running
Subsystem strip	Firmware (Running, No RPU control or RPU unreachable), Controller (the paired gamepad, or Not connected) and Wi-Fi (your network's name)
Actuator roster	Each joint's result from the last actuator check, such as 25 of 25 responding · checked and when. not current means the result is old, not that anything failed
Software & services	The installed release, and Video streaming — whether the robot's video service (LiveKit) is running. The Cockpit doesn't show video in this release
Logs	The newest lines across services, with View logs for the full viewer

The Setup Checklist

Until the robot is fully set up, the sidebar shows a Finish setting up checklist. The Setup Checklist explains each row.

Account and Access

Password

Change it on Account, from the user menu — see Set a Password.

Forgotten Password

Asimov Manager has no reset link. Over SSH, clear the stored password:

sudo asimovctl config reset manager.password_hash

The login goes back to the pre-filled default. Sign in and set a new password straight away.

Reset All Settings

Reset All Settings, under Advanced on the Account page, returns the robot's RPU, video (LiveKit) and Asimov Edge settings to factory defaults. Asimov Edge's parameters, including the robot's serial, go back to their defaults too.

It keeps your login, saved Wi-Fi networks, SDK credentials, the assembly confirmation, and actuator IDs and calibration.

Developer Credentials

A developer credential lets a computer running the Python SDK join the robot's LiveKit room. You need one to connect the SDK in its hybrid or livekit connection mode, which is also how the SDK sees the camera and hears the microphone. The Cockpit needs no credential, and neither does the SDK's udp mode.

The robot runs its own LiveKit server and is set up to use it from the first boot, so there is nothing to configure before you issue a credential.

Issue a Credential

Open Developer in the sidebar. Under Issue a credential, name the computer that will use it, choose Observe or Control, and select Issue credential. The credential is shown once, so copy it then; if you lose it, revoke it under Issued credentials and issue another. Drive from Python walks through the page step by step and connects the SDK with menlo setup.

Observe and Control

Role	What it allows in the LiveKit room
Observe (default)	Watch the camera and listen to the microphone. The LiveKit server refuses its commands, whatever program holds it
Control	Everything Observe allows, plus sending commands and talking through the speaker. Commands still pass through the robot's safety layer, and the Cockpit keeps priority

The role limits driving only in the livekit mode. In hybrid, commands travel over UDP on the robot's network, which has no sign-in, so an Observe credential still gets the camera and microphone and the SDK can still drive. Hybrid also needs the robot to accept UDP commands and send state to your computer; see Hybrid.

Revoke a Credential

Under Issued credentials, select Revoke next to the credential and confirm. The computer holding it can no longer connect. A session that is already running keeps working until its current LiveKit token expires, at most 12 hours.

Reset All Settings keeps issued credentials.

The LiveKit Secret Stays on the Robot

The credential is not the LiveKit key or secret. Each time the SDK connects, it trades the credential for a short-lived LiveKit token from Asimov Manager, so the key and secret never leave the robot and you never need them.

To use a LiveKit server other than the robot's own, set LiveKit URL, LiveKit key and LiveKit secret under Asimov Edge in Advanced Settings, and select Save & Restart Asimov Edge. Saving checks that the server accepts the key and secret first. If the LiveKit URL row on the Developer page reads not set, the robot publishes no video or audio until you set it here.

Command Line

Everything the console does is also available over SSH on the Pi 5. Sign in with the username and password you set in Raspberry Pi Imager when flashing it, then use asimovctl with sudo:

asimovctl status                        # services, RPU link and setup state
asimovctl start|stop|restart <service>  # asimov-edge, asimov-firmware or livekit-server
asimovctl enable|disable <service>      # start on boot
asimovctl config show                   # every setting, secrets masked
asimovctl config set <key> <value>
asimovctl config reset <key|section>
asimovctl apply                         # write settings to the services
asimovctl reset-setup --yes             # undo Confirm assembly; stops the firmware
asimovctl update status                 # the current software update

The browser and the command line control the same services, so anything you start from one you can stop from the other.

What It Manages

Asimov Manager and Asimov Edge run on the Pi 5. Asimov Edge carries commands and telemetry between the console and the RPU, whose Radxa CM5 runs the motion-control firmware. The Pi 5 and RPU share a private Ethernet link, which the console reports as two checks: Network (the RPU answers on the wire) and Control (the console can manage it). An unplugged cable and a stopped service never look the same.

What It Doesn't Do

Run the control loop. The firmware on the CM5 does; the console starts it, stops it and relays your drive input.

Command actuators while the firmware runs. The Actuators page works only with the firmware stopped.

Show video. The Cockpit's camera panel reads No video in this release.

Restart or shut down the robot's computers.

Manage more than one robot. There is no fleet view.

Flash boards. It is installed and updated as part of the robot's software.

On this page