Technology
No safety MCU at the edge.
Battery functions plug and play at the edge, and the logic runs in your controller.
The problem, and the answer
Every battery function carries its own computer.
In a typical battery architecture, each isolated function has its own safety MCU, SBC and firmware. We leave them out: the functions plug into one edge interface, and the logic runs in your zonal or central controller.
Plug and play
Plug in the functions. Configure in software.
With no computer inside, a function becomes a part you plug in.
- Plug in what each battery needs. Add a function, or swap one as needs change.
- Configured in software. Your controller is set up for each battery's functions, with software from us.
Every battery
Different batteries, made simpler to build.
Each application decides its battery, and the battery decides its functions. With plug-in functions, that's a choice of parts.
- Its own battery. Its cells, size and voltage, from a 400 V car to 1500 V grid storage.
- Its own functions. The mix it needs, with parts rated for its voltage.
- Not a new BMS. No BMS electronics to design and no edge firmware to write for it.
At scale
The benefits grow as you scale.
The hardware savings come with every pack, and the design savings with every new battery. All of it is managed from one place.
- A truck runs six Edge battery packs on one zonal controller.
- A grid rack runs eight on one Central BMS.
- A 1 GWh site is 20,000 packs at 50 kWh each, with 0 MCUs at the edge.