Skip to content

IN DEVELOPMENT · NO CHIP HAS BEEN TAPED OUT

BUILD USE CASES

Intended jobs, not delivered ones. BramHA is in development and no chip exists yet.

CONTROL

Close the loop on the machine.

A machine that moves has a loop it cannot be late for: read where it is, decide the next command, drive the motor, and read again. BramHA is being designed to run that loop on the machine itself, on a controller built for predictable timing instead of raw throughput.

That is the job a mature process node is good at. The loop needs the same answer at the same moment every time, for the life of the machine. The heavier work, such as perception and planning, is served from the pool in the building and arrives as a goal; the loop that reaches it stays where it is.

WHAT THAT IS FOR

A control loop that is intended to keep its timing whether or not the network is there.

MOTION

Put the controller at the joint.

A robot is a chain of joints, and each one is a small control problem of its own. BramHA is being designed to sit at the joint: to drive the motor there and to read what the joint is doing, so the wiring between a central box and every motor gets shorter.

The intent is one part, repeated. A robot maker would place the same chip at each joint and let the joints talk to each other over the machine's own bus. A small first design fits that shape: it does one job, and a machine uses several.

WHAT THAT IS FOR

One part a robot maker could repeat along a machine, instead of a different board for each axis.

SENSING

Read the sensors where they are.

A controller is only as good as what it is told. BramHA is being designed to read position, current, and force at the point where they are measured, and to hand the control loop a clean number on time.

Reading at the source keeps a small signal off a long wire, and keeps the timing of the reading tied to the timing of the loop. What the chip will measure, and how finely, belongs in the specification, which is not published yet.

WHAT THAT IS FOR

Measurements that are intended to arrive at the loop on the loop's own schedule.

IDENTITY

Let the machine prove what it is.

A facility that serves many machines from one pool has to know which machine is asking. BramHA is being designed with a hardware root of trust, so a machine can prove what it is and what it is running before a site lets it onto the network.

The appliance in the building already attests itself. A root of trust on the machine is the other half of that conversation: the pool proves what it is to the site, and the machine proves what it is to the pool. No security evaluation of BramHA exists, because no chip exists yet.

WHAT THAT IS FOR

A machine that is intended to answer one question before it is served: what are you, and what are you running?

FOR ROBOT MAKERS

A part for the people who build the machine.

BramHA is for the people who build robots: makers and integrators, not the facilities that run them. It is Element 31's own chip, designed and owned by Element 31, and it is intended to come from the same company that builds the pool the machine talks to.

The machine stays the maker's. Its safety case, its stops, and its motion are the maker's design and the maker's responsibility; BramHA would be a part inside it. Nothing can be ordered today, and how a robot maker would obtain the chip has not been decided.

WHAT THAT IS FOR

A part for the machine from the company that also builds the pool in the building.

BramHA is a part a robot maker may build into a machine. It is not a safety system and carries no certification; safety, stops and motion stay on the machine as its maker built them.