SunSpec Model 806 — Flow Battery Model
SunSpec Model 806 is the Flow Battery Bank Model, part of the SunSpec Alliance Energy Storage specification for distributed energy resources. It represents a bank of flow battery strings connected in parallel, covering technologies such as vanadium redox, zinc-bromine, and iron-chromium cells. This Modbus TCP template exposes the model identifier, model length, and the battery bank descriptor register, giving your monitoring system a standardized entry point into the bank-level data layer. Integrating SunSpec Model 806 via ModbusCloud lets asset managers verify bank configuration and detect structural anomalies across multi-string flow battery installations.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 3, read only
- Brand
- SunSpec
- Last updated
Registers (3)
3 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| id | Read | ||||
| l | Read | ||||
| battbd | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Verify the SunSpec Model 806 identifier register to confirm correct bank-model discovery during commissioning.
- Track the model length register to validate that the full bank descriptor block is present and correctly sized.
- Monitor the battery bank descriptor to detect unexpected configuration changes between maintenance intervals.
- Alert on missing or not-implemented values in the bank descriptor to flag incomplete device implementations.
- Compare bank descriptor readings across multiple sites to ensure consistent flow battery bank configurations.
Installation
Enable Modbus TCP on the flow battery system's BMS or gateway under the communication or Modbus section, and note the assigned IP address and port (default 502).
Connect the flow battery system to the same LAN segment as the ModbusCloud Gateway, ensuring no firewall rules block TCP port 502.
In the ModbusCloud portal, add the ModbusCloud Gateway, import the SunSpec Model 806 template, and set the correct unit ID matching your device's Modbus slave address.
Read register address 0 and confirm the returned value is 806, verifying the correct SunSpec Flow Battery Bank model block has been located.
Things to watch for
Register 0 returns an unexpected value instead of 806. Why?
The template uses relative model-offset addressing, so address 0 is the start of the model block, not the absolute Modbus map base. Ensure the ModbusCloud Gateway is pointed at the correct base address for the Model 806 block within the device's full SunSpec map, which follows the Common Model block.
The model length register returns a not-implemented value. What does this mean?
Some devices ship with SunSpec Model 806 partially implemented. A not-implemented value (0xFFFF for uint16) on the length register indicates the bank model block is present in the map header but not populated. Check the device firmware version against the manufacturer's SunSpec implementation notes.
No data appears after importing the template, even though the device is reachable. What should I check?
Confirm the unit ID in the portal matches the Modbus slave address configured on the device. SunSpec devices often use unit ID 1 by default, but some energy storage systems use a higher address. Also verify Modbus TCP is explicitly enabled in the device's communication settings, as it is frequently disabled by default.
The battery bank descriptor register reads zero on every poll. Is this normal?
A persistent zero on the bank descriptor can indicate the field is not implemented by the device, which is permitted under the SunSpec specification. Unsupported data points within a storage model should be set to the not-implemented value. Cross-reference the device's SunSpec compliance documentation to confirm whether this field is populated.
Knowledge base articles for this device
SunSpec Modbus: one register map for many inverters
SunSpec Modbus is the open register map SMA, Fronius, SolarEdge and Kostal share. The layout, int+SF vs float, the TCP port per brand and reading a mixed fleet.
Fronius Modbus: read a Symo GEN24 over Modbus TCP
Fronius Modbus explained: enable Modbus TCP on the Symo GEN24 on port 502, choose between int+SF and float, read the right SunSpec registers and scale them correctly. Practical guide for solar installers.
SMA Modbus: reading a Sunny Boy over Modbus TCP (installers)
SMA Modbus explained: enable the Modbus TCP server on port 502, choose between the SMA profile (unit ID 3) and SunSpec (unit ID 126), read the right registers, and handle the NaN values at night. Practical guide for installers.
Want to see how it works?
