For vehicle makers

Make the battery part of your software-defined vehicle.

Manage every pack from your zonal controller, update it over the air with the rest of the car, and launch new variants in configuration.

The battery, on your zonal network.

One EBJB1500 per pack. Everything else in the pack plugs into it, and only its edge interface talks to your zonal controller.

  • High voltage on one board. Pack voltage, current and isolation, and the contactors.
  • Module boards on a daisy chain. Cell voltages and module temperatures, module by module.
  • Thermal event detection on its I/O. Wired to the EBJB1500 and reported to your controller.

Every programme from one platform.

Each programme’s pack has its own cells, size and voltage, and takes the functions it needs.

  • Its own functions. Plug in what the pack needs, and leave out what it doesn’t.
  • Configured, not redesigned. Each programme’s zonal controller is set up for its pack.
  • No computer at the edge. No BMS electronics to design and no edge firmware to write for a new pack.

Trucks multiply the savings.

A truck carries many packs, and none of them brings a computer to the edge. The more packs, the more you save, and all of them answer to one controller.

  • At least eight packs on one Ethernet line.
  • No safety MCUs in the packs. A typical BMS architecture puts three in each pack, in its BMS, its current sensor and its thermal event detection, each with its own firmware.
  • On the truck’s 24 V. The EBJB1500 runs from a 12 V to 24 V supply.

Battery management, in your software.

The battery logic runs in your zonal controller, with the rest of your vehicle software, so the battery improves with every release.

  • Over the air, wherever your zonal controllers are updated that way.
  • Nothing in the pack to flash. The edge functions run no firmware of their own.