device library

Seplos 48V BMS (RS485)

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

pointaddress (0-based)typescaleunit
cell_1_voltage1U160.001
cell_2_voltage2U160.001
cell_3_voltage3U160.001
cell_4_voltage4U160.001
cell_5_voltage5U160.001
cell_6_voltage6U160.001
cell_7_voltage7U160.001
cell_8_voltage8U160.001
cell_9_voltage9U160.001
cell_10_voltage10U160.001
cell_11_voltage11U160.001
cell_12_voltage12U160.001
cell_13_voltage13U160.001
cell_14_voltage14U160.001
cell_15_voltage15U160.001
cell_16_voltage16U160.001
cell_1_temperature18U160.1
cell_2_temperature19U160.1
cell_3_temperature20U160.1
cell_4_temperature21U160.1
ambient_temperature22U160.1
components_temperature23U160.1
pack_current24I160.01
pack_voltage25U160.01
remaining_capacity26U160.01
battery_capacity27U160.01
soc28U160.1
rated_capacity29U160.01
cycle_life30U161
soh31U160.1
port_voltage32U160.01

link settings as documented (unverified): ASCII; Uses YD/T1363.3 standard-based ASCII protocol (referred to as MODBUS-ASCII in document) with SOI (~), VER, ADR, CID1, CID2, LENGTH, INFO, CHKSUM, EOI.

bench facts as documented (unverified)
terminalsRS232 and RS485
termination120Ω
wiring notesAsynchronous serial communication interface with 1 start bit, 8 data bits, 1 stop bit, and no parity.
broadcastsupported
protocol notesSU sends control messages to SM through broadcast addresses. SM sends feedback to SU.
field reports — community-sourced, unverified (checked 2026-06-11)
  • Baud rate confusion: Users often struggle to connect because some firmware versions default to 19200 baud instead of 9600 baud. [source]
  • RS485 lockup issue: The BMS RS485 interface can stop responding entirely after some time due to electromagnetic interference (EMI) or bus disturbance, requiring a physical reboot of the BMS to recover. [source]
  • CAN/RS485 conflict: If the master battery is communicating with an inverter via CAN, the master's RS485 port becomes unreadable because it is occupied managing intra-pack communication with slave batteries. [source]
  • Physical pinout surprise: On some hardware revisions, RS485 is routed through the CAN socket on RJ45 pins 1 and 2 (A and B), with ground disconnected. [source]
  • confirmed: Uses YD/T1363.3 standard-based ASCII protocol with SOI (~), VER, ADR, CID1, CID2, LENGTH, INFO, CHKSUM, EOI — confirmed by Seplos BMS Communication Protocol V2.0 PDF and GitHub implementations
  • confirmed: Asynchronous serial communication interface with 1 start bit, 8 data bits, 1 stop bit, and no parity — confirmed by Seplos BMS Communication Protocol V2.0 PDF
  • confirmed: Broadcast supported where SU sends control messages to SM through broadcast addresses — confirmed by Seplos BMS MODBUS-ASCII Protocol Guide

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.