Easy Modbus
  1. Home
  2. Modbus register maps
  3. Studer Innotec
  4. BSP battery status processor (via Xcom-485i)

Sensor (battery monitor for Studer systems) · Modbus register map

Studer Innotec BSP battery status processor (via Xcom-485i) Modbus register map

Updated 17 November 2026

Short answer

The BSP is Studer's shunt-based battery monitor for Xtender systems. An Xcom-485i on the Studer bus answers Modbus RTU for it. This map lists the BSP user infos (voltage, current, state of charge, power, Ah counters, temperature) as input registers and the BSP parameters as holding registers.

This page lists 60 Modbus registers for the Studer Innotec BSP battery status processor (via Xcom-485i) — 25 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Studer Innotec’s own free documentation (linked below) and checked against it.

Manufacturer
Studer Innotec
Model
BSP battery status processor (via Xcom-485i)
Equipment type
Sensor (battery monitor for Studer systems)
Registers
60 (25 writable)
Transport
Modbus RTU
Default unit ID
61
Default serial
8E1
Documented addressing
0-based (the number printed is the address on the wire)
32-bit word order
ABCD high word first (big-endian)
Firmware
Studer system release R706 (appendix V1.6.44); Xcom-485i protocol V1.1.3
Also known as
BSP-500, BSP-1200, BSP500, BSP1200, Xcom-485i
Source document
Technical specification Studer Modbus RTU Appendix V1.6.44 (with Technical specification Studer Modbus RTU Protocol V1.1.3) · Appendix V1.6.44 (R706); Protocol V1.1.3 · rev. 2025-09-03
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Studer Innotec BSP battery status processor (via Xcom-485i)

Integration in brief

Fit an Xcom-485i on the Studer communication bus and poll it as a Modbus RTU slave. Each Studer device answers at its own unit ID (offset set by DIP switches 1-2); read infos with function 04 and parameters with 03, always 2 registers at a time, and decode as big-endian float.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
IR 0Battery voltage {7000}FLOAT32 ABCDBattery voltageRead
IR 2Battery current {7001}FLOAT32 ABCDBattery currentRead
IR 4State of Charge {7002}FLOAT32 ABCDState of chargeRead
IR 6Power {7003}FLOAT32 ABCDBattery powerRead
IR 8Remaining autonomy {7004}FLOAT32 ABCDRemaining autonomyRead
IR 58Battery temperature {7029}FLOAT32 ABCDBattery temperatureRead

Enable Modbus control & writes

Install the Xcom-485i on the Studer bus. DIP switches 1-2 set the unit-ID offset (0, 32, 64 or 128) and switches 7-8 set the baud rate (9600, 19200, 38400 or 115200). Frames are 8 data bits, even parity, 1 stop bit.

Byte order & addressing

Network setup

Watch out for

Studer Innotec BSP battery status processor (via Xcom-485i) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

60 of 60 shown
Studer Innotec BSP battery status processor (via Xcom-485i) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
IR0Battery voltage {7000}FLOAT32ABCDVRead
IR2Battery current {7001}FLOAT32ABCDAdcRead
IR4State of Charge {7002}FLOAT32ABCD%Read
IR6Power {7003}FLOAT32ABCDWRead
IR8Remaining autonomy {7004}FLOAT32ABCDminutesRead
IR10BSP Temperature {7005}FLOAT32ABCD°CRead
IR12Relative capacity {7006}FLOAT32ABCD%Read
IR14Ah charged today {7007}FLOAT32ABCDAhRead
IR16Ah discharged today {7008}FLOAT32ABCDAhRead
IR18Ah charged yesterday {7009}FLOAT32ABCDAhRead
IR20Ah discharged yesterday {7010}FLOAT32ABCDAhRead
IR22Total Ah charged {7011}FLOAT32ABCDkAhRead
IR24Total Ah discharged {7012}FLOAT32ABCDkAhRead
IR26Total time {7013}FLOAT32ABCDdaysRead
IR34Custom charge Ah counter {7017}FLOAT32ABCDAhRead
IR36Custom discharge Ah counter {7018}FLOAT32ABCDAhRead
IR38Custom counter duration {7019}FLOAT32ABCDhRead
IR58Battery temperature {7029}FLOAT32ABCD°CRead
IR60Battery voltage (minute avg) {7030}FLOAT32ABCDVRead
IR62Battery current (minute avg) {7031}FLOAT32ABCDAdcRead
IR64State of Charge (minute avg) {7032}FLOAT32ABCD%Read
IR66Battery temperature (minute avg) {7033}FLOAT32ABCD°CRead
IR68ID type {7034}FLOAT32ABCDRead
IR70ID batt voltage {7035}FLOAT32ABCDVRead
IR72ID HW {7036}FLOAT32ABCDRead
IR74ID SOFT msb {7037}Software version word, encoded as in the protocol spec's version section.FLOAT32ABCDRead
IR76ID SOFT lsb {7038}Software version word, encoded as in the protocol spec's version section.FLOAT32ABCDRead
IR78Parameter number (in code) {7039}FLOAT32ABCDRead
IR80Info user number {7040}FLOAT32ABCDRead
IR82ID SID {7041}FLOAT32ABCDRead
IR94Manufacturer State of Charge {7047}FLOAT32ABCD%Read
IR96ID FID msb {7048}Half of the unit's unique FID number.FLOAT32ABCDRead
IR98ID FID lsb {7049}Half of the unit's unique FID number.FLOAT32ABCDRead
IR118Local daily communication error counter (CAN) {7059}FLOAT32ABCDRead
IR120Number of parameters (in flash) {7060}FLOAT32ABCDRead
HR2Nominal capacity {6001}Basic level. Range 20 to 20000, default 110.FLOAT32ABCDAhRead/write
HR4Nominal discharge duration (C-rating) {6002}Basic level. Range 1 to 100, default 20.FLOAT32ABCDhRead/write
HR6Reset of battery history {6003}Expert level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR8Restore default settings {6004}Basic level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR10Restore factory settings {6005}Installer level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR34Nominal shunt current {6017}Basic level. Range 10 to 10000, default 500.FLOAT32ABCDARead/write
HR36Nominal shunt voltage {6018}Basic level. Range 10 to 200, default 50.FLOAT32ABCDmVRead/write
HR38Self-discharge rate {6019}Expert level. Range 0 to 25, default 3.FLOAT32ABCD%/monthRead/write
HR40Nominal temperature {6020}Expert level. Range 0 to 40, default 20.FLOAT32ABCD°CRead/write
HR42Temperature coefficient {6021}Expert level. Range 0 to 3, default 0.5.FLOAT32ABCD%cap/°CRead/write
HR44Charge efficiency factor {6022}Expert level. Range 50 to 100, default 90.FLOAT32ABCD%Read/write
HR46Peukert's exponent {6023}Expert level. Range 1 to 1.5, default 1.2.FLOAT32ABCDRead/write
HR48End of charge voltage level {6024}Expert level. Range 31.9 to 70.1, default 52.8.FLOAT32ABCDVRead/write
HR50End of charge current level {6025}Expert level. Range 0 to 500, default 2.FLOAT32ABCD%capRead/write
HR62Reset of user counters {6031}Expert level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR84Activate the end of charge synchronization {6042}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR88Activate the state of charge correction by the open circuit voltage {6044}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR96Temperature correction of the end of charge voltage {6048}Expert level. Range -8 to 0, default 0.FLOAT32ABCDmV/°C/cellRead/write
HR98Use C20 Capacity as reference value {6049}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR110Manufacturer SOC for 0% displayed {6055}Expert level. Range 0 to 60, default 30.FLOAT32ABCD%Read/write
HR112Manufacturer SOC for 100% displayed {6056}Expert level. Range 80 to 100, default 100.FLOAT32ABCD%Read/write
HR114Voltage of the system {6057}Basic level. Option code as a float; one option at a time.FLOAT32ABCDRead/write1 = Automatic; 2 = 12V; 4 = 24V; 8 = 48V
HR116Battery charge current centralized regulation activated {6058}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR118Max battery charge current {6059}Expert level. Range 0 to 10000, default 60.FLOAT32ABCDARead/write
HR130Minimum duration before end of charge {6065}Expert level. Range 5 to 300, default 5.FLOAT32ABCDminRead/write

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the Studer Innotec BSP battery status processor (via Xcom-485i)

What Modbus registers does the Studer Innotec BSP battery status processor (via Xcom-485i) have?

This map lists 60 registers: 35 input registers, 25 holding registers. 25 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the Studer Innotec BSP battery status processor (via Xcom-485i) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers 0-based (the number printed is the address on the wire). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. The appendix lists the register exactly as it goes in the request. The protocol spec's example reads info 3001 from register 2 with start address 0x0002 in the frame, and parameter 1107 from register 14 (0x000E).

What byte order does the Studer Innotec BSP battery status processor (via Xcom-485i) use for 32-bit values?

Multi-register values in this map use ABCD (high word first (big-endian)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the Studer Innotec BSP battery status processor (via Xcom-485i)?

Start with IR 0 Battery voltage {7000} (Battery voltage); IR 2 Battery current {7001} (Battery current); IR 4 State of Charge {7002} (State of charge); IR 6 Power {7003} (Battery power); IR 8 Remaining autonomy {7004} (Remaining autonomy); IR 58 Battery temperature {7029} (Battery temperature).

How do I enable Modbus control of the Studer Innotec BSP battery status processor (via Xcom-485i)?

Install the Xcom-485i on the Studer bus. DIP switches 1-2 set the unit-ID offset (0, 32, 64 or 128) and switches 7-8 set the baud rate (9600, 19200, 38400 or 115200). Frames are 8 data bits, even parity, 1 stop bit.

Where is the official Studer Innotec BSP battery status processor (via Xcom-485i) Modbus documentation?

The source is Technical specification Studer Modbus RTU Appendix V1.6.44 (with Technical specification Studer Modbus RTU Protocol V1.1.3) (Appendix V1.6.44 (R706); Protocol V1.1.3), revision 2025-09-03, published free by Studer Innotec at https://studer-innotec.com/wp-content/uploads/2025/09/Manuel-xcom-485i-technical-specification.zip.

More Studer Innotec Modbus register maps

Other solar & battery inverters register maps

All solar & battery inverters Modbus register maps →

Source: Technical specification Studer Modbus RTU Appendix V1.6.44 (with Technical specification Studer Modbus RTU Protocol V1.1.3) · Appendix V1.6.44 (R706); Protocol V1.1.3 · rev. 2025-09-03. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.