Decode

What it is

A raw frame is bytes on a wire. A decoder knows what those bytes mean for one battery protocol and turns them into readings such as voltage, current and state of charge.

There is one decoder library for every customer. When a decoder is added, every customer's gateways can use it.

You tell Adaptr which protocol a battery speaks when you register it. Nothing is guessed from the bytes.

Who it is for

• Fleet operators with batteries that speak CAN or RS-485 and no cloud of their own.
• Integrators who need to know whether a given BMS is read.

How it works

1. Name the protocol. Each battery is registered with the wire it uses (CAN or RS-485) and its protocol.
2. Match the decoder. Ingest picks the decoder for that pair. A pair with no decoder is left unread and recorded as such, not guessed.
3. Store the readings. Decoded values become readings in the battery's history, each marked with its source.

What it does not do yet

• Today the decoders are: CAN, Nissan Leaf (passive broadcasts only, so no temperature and no health) and Egret GT; RS-485, Daly, a SunSpec battery bank (model 802) over Modbus RTU, and JK PB over Modbus RTU.
• The JK PB decoder has been tested against software only, not yet against a real unit.
• Other protocols are not decoded yet.
• There is no page to paste a frame into and try a decoder.

Related services

• Ingest — The door that device data comes in through. Frames from your gateways arrive over MQTT and are kept as received before they are read.
• Gateway — Register the devices that report for your batteries. Each gets its own credentials and can publish only on its own topics.
• Monitor — Live readings for your batteries, and rules that alert you by webhook, email or Slack when one needs attention. See pricing for the charge.