Menlo
System Tour

Electrical

Asimov 1 battery, power, control electronics, actuator communications, sensors, and media hardware.

Overall Architecture

The Compute Module comprises two connected stacks: the Head Compute Unit in the head and the Robot Processing Unit (RPU) in the torso.

SubsystemRole
Head Compute UnitProvides media, networking, edge services, and the buzzer
RPURuns locomotion and actuator control, handles IMU feedback and actuator CAN communications, and distributes power
Actuator networkCarries battery power and CAN communication through the robot
Sensors and mediaProvide inertial state, video, audio input, and audio output
Battery systemSupplies energy for actuators, compute, sensing, and peripherals

Compute Module

Compute Module

In the head

Head Compute Unit

  1. Top

    Media HAT Board

    Buzzer and Pi 5 brownout protection

  2. Raspberry Pi 5

    Media, networking, and edge services

  3. Head Board

    Head power and peripheral connections

    Base

In the torso

Robot Processing Unit (RPU)

  1. Top

    Power Distribution Board (PDB)

    Distributes power to connected hardware

  2. Radxa CM5

    Runs motion-control firmware and locomotion

  3. Radxa Carrier Board

    Hosts the CM5 and connects to the actuator network

    Base

Data link: to via the 1000 mm Ethernet cable.

Head power: to via the 1000 mm XT30-Male to XT30-Female power cable.

Mounts, fan, camera, and other peripherals are omitted.

Head Compute Unit

The head stack contains three boards. The sits at the base, the mounts above it on standoffs, and the mounts on the header. The provides the buzzer and helps prevent brownouts on the .

The Head Compute Unit is the electronics stack, not the entire mechanical head assembly. Its camera, mounts, covers, and neck hardware are identified separately in the build instructions.

Robot Processing Unit (RPU)

The torso stack also contains three boards. The mounts on the , forming the Motion Control Board (MCB). The (PDB) then fits above the . Together, the MCB and PDB form the Robot Processing Unit (RPU).

The handles high-frequency, low-latency workloads, including locomotion, actuator control, and IMU feedback. The provides the interfaces for communication with all 25 actuators. The distributes power to connected hardware.

Connecting the Two Assemblies

A 1000 mm Ethernet cable links the to the . A separate 1000 mm XT30-Male to XT30-Female power cable connects the to the . The Head Compute Unit and RPU work together while remaining in separate locations on the robot.

Keeping media, external networking, and application services on the separates those workloads from the 's time-sensitive control loop.

Actuator Power and Communication

The published system specification identifies five CAN interfaces at 1 Mbps and one at 500 kbps. The actuator network distributes battery power and CAN communication from the body outward through six physical branches.

Daisy-Chain Architecture

Each actuator has two electrically equivalent XT30 (2+2) ports. Each port carries BATT+, BATT-, CAN_H, and CAN_L, allowing power and communication to continue from one actuator to the next.

There is no fixed electrical input or output port. Use the port and orientation shown in the applicable assembly step so the cable follows the intended mechanical path.

The six branches enter the body at left hip pitch, right hip pitch, waist yaw, left shoulder pitch, right shoulder pitch, and neck yaw. Within each branch, actuators form a chain from the central body toward the distal joint.

At each branch entry, CAN_H and CAN_L route toward the RPU while BATT+ and BATT- route toward the robot power bus.

For example, each leg follows:

  • hip pitch -> hip roll -> hip yaw -> knee -> ankle A -> ankle B

This topology keeps the number of body-entry connections small while allowing each limb to carry power and CAN through the same connector system.

Keep the robot unpowered

Keep the battery disconnected and its output protected. Do not connect, disconnect, route, strip, or join conductors while any part of the robot is energized.

Wire-to-actuator visualization coming soon

An interactive visualization will be added here to show how every wire connects through the actuator network.

CAN mapping under confirmation

The public sources do not yet reconcile the six physical branch-entry paths with the controller specification of five 1 Mbps CAN interfaces plus one 500 kbps interface. Treat the physical topology and controller-interface count as separate facts until the release-specific bus assignment is confirmed.

Sensors and Media Hardware

DeviceCurrent specificationPrimary role
IMU6-axisBody orientation and angular-motion sensing
Camera2 MP monocular cameraRobot video and visual input
MicrophoneStereo microphone arrayAudio capture
Speaker10 W, 4 ohmRobot audio output

The is the currently supported edge computer for camera, audio, networking, and edge services. Other Raspberry Pi models are not validated for Asimov 1.

Battery

The current pack design is a 13-series, 4-parallel lithium-ion battery.

ParameterCurrent specification
Battery typeLithium-ion
Cell modelINR18650
Pack configuration13S4P
Nominal voltage46.8 V
Typical capacity10.5 Ah
Minimum capacity10.05 Ah
Energy491.4 Wh
Charge voltage54.6 V
Discharge cut-off35.75 V
Standard charge current2.1 A
Maximum charge current15 A
Standard discharge current2.1 A
Maximum discharge current30 A
Storage voltage45.5 to 48.1 V
Battery massApproximately 2 kg

Operating Temperature

ConditionTemperature range
Charging0°C to 45°C
Discharging-20°C to 60°C
Storage, less than 1 month-10°C to 45°C
Long-term storage, less than 3 months-10°C to 35°C

Protection Circuit

The pack includes a protection circuit module for over-charge, over-discharge, and over-current protection.

Protection itemThreshold
Over-charge protection4.25 V per cell
Over-discharge protection2.75 V per cell
Over-current protection30 A or less

How is this guide?

On this page