- Home
- Modbus register maps
- Studer Innotec
- 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
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
Integration notes: Studer Innotec BSP battery status processor (via Xcom-485i)
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.
| Register | Name | Type | Why | Access |
|---|---|---|---|---|
| IR 0 | Battery voltage {7000} | FLOAT32 ABCD | Battery voltage | Read |
| IR 2 | Battery current {7001} | FLOAT32 ABCD | Battery current | Read |
| IR 4 | State of Charge {7002} | FLOAT32 ABCD | State of charge | Read |
| IR 6 | Power {7003} | FLOAT32 ABCD | Battery power | Read |
| IR 8 | Remaining autonomy {7004} | FLOAT32 ABCD | Remaining autonomy | Read |
| IR 58 | Battery temperature {7029} | FLOAT32 ABCD | Battery temperature | Read |
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
- Unit 61 addresses the first BSP; multicast unit 60 reads the first such device and writes to all of them at once.
- Values are floats even for on/off and enumerated items: 1.0 = 0x3F800000.
Network setup
- With DIP 1-2 off: unit 1 = Xcom-485i gateway, 2 = system, 10 = all Xtenders, 11-19 = single Xtenders, 20 = all VarioTracks, 21-35 = single VarioTracks, 40 = all VarioStrings, 41-55 = single VarioStrings, 60 = all BSP/Xcom-CAN BMS, 61 = the single BSP or Xcom-CAN BMS. Add the DIP offset to each.
- Single devices are numbered in the order shown on the RCC remote's device list.
- Allow up to 1 s for a reply and send one request at a time; the gateway is slower when the Studer bus is busy.
Watch out for
- Writing a parameter at its base register stores it in flash; cyclic writes should use base + 6000 (RAM only).
- Some parameters restart an internal timer or algorithm when changed while running.
- Parameter levels (Basic/Expert/Installer/QSP) are the RCC access levels printed in the appendix.
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.
| Table | Address | Name | Description | Type | Order | Scale | Units | Access | Values / bits |
|---|---|---|---|---|---|---|---|---|---|
| IR | 0 | Battery voltage {7000} | FLOAT32 | ABCD | V | Read | |||
| IR | 2 | Battery current {7001} | FLOAT32 | ABCD | Adc | Read | |||
| IR | 4 | State of Charge {7002} | FLOAT32 | ABCD | % | Read | |||
| IR | 6 | Power {7003} | FLOAT32 | ABCD | W | Read | |||
| IR | 8 | Remaining autonomy {7004} | FLOAT32 | ABCD | minutes | Read | |||
| IR | 10 | BSP Temperature {7005} | FLOAT32 | ABCD | °C | Read | |||
| IR | 12 | Relative capacity {7006} | FLOAT32 | ABCD | % | Read | |||
| IR | 14 | Ah charged today {7007} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 16 | Ah discharged today {7008} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 18 | Ah charged yesterday {7009} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 20 | Ah discharged yesterday {7010} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 22 | Total Ah charged {7011} | FLOAT32 | ABCD | kAh | Read | |||
| IR | 24 | Total Ah discharged {7012} | FLOAT32 | ABCD | kAh | Read | |||
| IR | 26 | Total time {7013} | FLOAT32 | ABCD | days | Read | |||
| IR | 34 | Custom charge Ah counter {7017} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 36 | Custom discharge Ah counter {7018} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 38 | Custom counter duration {7019} | FLOAT32 | ABCD | h | Read | |||
| IR | 58 | Battery temperature {7029} | FLOAT32 | ABCD | °C | Read | |||
| IR | 60 | Battery voltage (minute avg) {7030} | FLOAT32 | ABCD | V | Read | |||
| IR | 62 | Battery current (minute avg) {7031} | FLOAT32 | ABCD | Adc | Read | |||
| IR | 64 | State of Charge (minute avg) {7032} | FLOAT32 | ABCD | % | Read | |||
| IR | 66 | Battery temperature (minute avg) {7033} | FLOAT32 | ABCD | °C | Read | |||
| IR | 68 | ID type {7034} | FLOAT32 | ABCD | Read | ||||
| IR | 70 | ID batt voltage {7035} | FLOAT32 | ABCD | V | Read | |||
| IR | 72 | ID HW {7036} | FLOAT32 | ABCD | Read | ||||
| IR | 74 | ID SOFT msb {7037} | Software version word, encoded as in the protocol spec's version section. | FLOAT32 | ABCD | Read | |||
| IR | 76 | ID SOFT lsb {7038} | Software version word, encoded as in the protocol spec's version section. | FLOAT32 | ABCD | Read | |||
| IR | 78 | Parameter number (in code) {7039} | FLOAT32 | ABCD | Read | ||||
| IR | 80 | Info user number {7040} | FLOAT32 | ABCD | Read | ||||
| IR | 82 | ID SID {7041} | FLOAT32 | ABCD | Read | ||||
| IR | 94 | Manufacturer State of Charge {7047} | FLOAT32 | ABCD | % | Read | |||
| IR | 96 | ID FID msb {7048} | Half of the unit's unique FID number. | FLOAT32 | ABCD | Read | |||
| IR | 98 | ID FID lsb {7049} | Half of the unit's unique FID number. | FLOAT32 | ABCD | Read | |||
| IR | 118 | Local daily communication error counter (CAN) {7059} | FLOAT32 | ABCD | Read | ||||
| IR | 120 | Number of parameters (in flash) {7060} | FLOAT32 | ABCD | Read | ||||
| HR | 2 | Nominal capacity {6001} | Basic level. Range 20 to 20000, default 110. | FLOAT32 | ABCD | Ah | Read/write | ||
| HR | 4 | Nominal discharge duration (C-rating) {6002} | Basic level. Range 1 to 100, default 20. | FLOAT32 | ABCD | h | Read/write | ||
| HR | 6 | Reset of battery history {6003} | Expert level. Write 1.0 to trigger. | FLOAT32 | ABCD | Write | |||
| HR | 8 | Restore default settings {6004} | Basic level. Write 1.0 to trigger. | FLOAT32 | ABCD | Write | |||
| HR | 10 | Restore factory settings {6005} | Installer level. Write 1.0 to trigger. | FLOAT32 | ABCD | Write | |||
| HR | 34 | Nominal shunt current {6017} | Basic level. Range 10 to 10000, default 500. | FLOAT32 | ABCD | A | Read/write | ||
| HR | 36 | Nominal shunt voltage {6018} | Basic level. Range 10 to 200, default 50. | FLOAT32 | ABCD | mV | Read/write | ||
| HR | 38 | Self-discharge rate {6019} | Expert level. Range 0 to 25, default 3. | FLOAT32 | ABCD | %/month | Read/write | ||
| HR | 40 | Nominal temperature {6020} | Expert level. Range 0 to 40, default 20. | FLOAT32 | ABCD | °C | Read/write | ||
| HR | 42 | Temperature coefficient {6021} | Expert level. Range 0 to 3, default 0.5. | FLOAT32 | ABCD | %cap/°C | Read/write | ||
| HR | 44 | Charge efficiency factor {6022} | Expert level. Range 50 to 100, default 90. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 46 | Peukert's exponent {6023} | Expert level. Range 1 to 1.5, default 1.2. | FLOAT32 | ABCD | Read/write | |||
| HR | 48 | End of charge voltage level {6024} | Expert level. Range 31.9 to 70.1, default 52.8. | FLOAT32 | ABCD | V | Read/write | ||
| HR | 50 | End of charge current level {6025} | Expert level. Range 0 to 500, default 2. | FLOAT32 | ABCD | %cap | Read/write | ||
| HR | 62 | Reset of user counters {6031} | Expert level. Write 1.0 to trigger. | FLOAT32 | ABCD | Write | |||
| HR | 84 | Activate the end of charge synchronization {6042} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 88 | Activate the state of charge correction by the open circuit voltage {6044} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 96 | Temperature correction of the end of charge voltage {6048} | Expert level. Range -8 to 0, default 0. | FLOAT32 | ABCD | mV/°C/cell | Read/write | ||
| HR | 98 | Use C20 Capacity as reference value {6049} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 110 | Manufacturer SOC for 0% displayed {6055} | Expert level. Range 0 to 60, default 30. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 112 | Manufacturer SOC for 100% displayed {6056} | Expert level. Range 80 to 100, default 100. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 114 | Voltage of the system {6057} | Basic level. Option code as a float; one option at a time. | FLOAT32 | ABCD | Read/write | 1 = Automatic; 2 = 12V; 4 = 24V; 8 = 48V | ||
| HR | 116 | Battery charge current centralized regulation activated {6058} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 118 | Max battery charge current {6059} | Expert level. Range 0 to 10000, default 60. | FLOAT32 | ABCD | A | Read/write | ||
| HR | 130 | Minimum duration before end of charge {6065} | Expert level. Range 5 to 300, default 5. | FLOAT32 | ABCD | min | Read/write |
Notes on this map
- Info 7004 'Remaining autonomy' counts minutes to 0 % while discharging (between -60000 and 0) and reads NaN while charging.
- Info 7006 'Relative capacity' is deprecated and reads 100 % from BSP software 1.5.6 on. Info 7034 'ID type' reads 10241 (0x2801) for BSP500 and BSP1200.
- Every info and parameter is an IEEE 754 single-precision float in two registers, high word first. The protocol spec's example reads Xtender info 3001 as 0x41D3 0x3333 = 26.4 °C, and parameter 1107 as 0x4170 0x0000 = 15.0 A.
- Each request must read or write exactly 2 registers (one value); asking for more returns an exception. Infos use function 04, parameters function 03 to read and 16 to write.
- Parameter registers have three more views at fixed offsets: +2000 = minimum allowed value, +4000 = maximum allowed value (read only), +6000 = write to RAM only. Use the RAM-only offset for anything written repeatedly; flash is only guaranteed for about 1000 writes per parameter.
- Enumerated infos count 0, 1, 2 ...; enumerated parameters use one bit per option (1, 2, 4, 8), still sent as a float. Codes shown as '---' in the appendix are unused and left out of the value lists.
- Register names keep the Studer info/parameter number in braces, e.g. {3000}. The register is 2 x (number - base) for that device family.
- Parameters whose appendix format is MENU are menu headings, not values, and are left out. The appendix's per-row remarks column is not reproduced.
- The gateway's own input registers (pending messages at 0-4, device counts at 5-9, gateway identity at 10-14, on unit 1) and the system clock (holding registers 0-7 on unit 2) are described in the protocol spec but live at other unit IDs, so they are not in this register list.
- The protocol spec's first read example prints the value as 0x4170 in the PDU table but 0x41F0 in the serial-line frame; 0x4170 matches the stated 15.0 A.
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
- Solar inverter (MPPT solar charge controller)
Studer Innotec VarioString MPPT solar charge controller (via Xcom-485i)
Studer VarioString VS-70 and VS-120 MPPT chargers read through an Xcom-485i Modbus RTU gateway, system release R706.
Also known as: VS-70, VS-120, VarioString VS-120, Xcom-485i - Solar inverter (MPPT solar charge controller)
Studer Innotec VarioTrack MPPT solar charge controller (via Xcom-485i)
Studer VarioTrack VT-40/65/80/HV MPPT chargers read through an Xcom-485i Modbus RTU gateway, system release R706.
Also known as: VT-40, VT-65, VT-80, VT-HV, VarioTrack VT-65, Xcom-485i - Battery inverter system (lithium battery BMS interface)
Studer Innotec Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i)
Studer Xcom-CAN set to BMS mode (CAN link to a lithium battery BMS), read through an Xcom-485i Modbus RTU gateway, system release R706.
Also known as: Xcom-CAN, Xcom-CAN BMS, Xcom-485i - Battery inverter (off-grid inverter-charger)
Studer Innotec Xtender XTH / XTM / XTS inverter-charger (via Xcom-485i)
Studer Xtender XTH, XTM and XTS inverter-chargers read through an Xcom-485i Modbus RTU gateway, system release R706.
Also known as: XTH, XTM, XTS, Xtender XTH, Xtender XTM, Xtender XTS, Xcom-485i
Other solar & battery inverters register maps
- Solar inverter
Fronius Primo GEN24 / Symo GEN24 (Plus) SunSpec int+SF
Fronius Primo/Symo GEN24 (Plus) rest-of-world variants with a battery configured, SunSpec Model Type int+SF; without a battery the MPPT model has 2 inputs and model 124 is absent.
Also known as: Primo GEN24 Plus, Symo GEN24 Plus, Primo GEN24, Symo GEN24, Symo GEN24 10.0 Plus, Primo GEN24 6.0 Plus - Solar inverter gateway (smart dongle)
Huawei SDongleA smart dongle (Modbus TCP)
Huawei SDongleA WLAN/WLAN-FE/4G dongles with firmware V100R001C00SPC100 or later, per MODBUS Interface Definitions issue 05.
Also known as: SDongleA-01, SDongleA-02-CN, SDongleA-03-EU, SDongleA-03-AU, SDongleA-03-KR, SDongleA-03-JP, SDongleA-03-CN - Solar inverter
Schneider Electric Conext CL three-phase PV inverter 18/20/25 kVA
Conext CL (IEC, PVSCL20E/25E) and Conext CL-NA (PVSCL18NA/25NA) three-phase string inverters, map revision 1.5.
Also known as: Conext CL-NA, Conext CL-E, PVSCL18NA, PVSCL20E, PVSCL25E, PVSCL25NA - Solar inverter
Fronius Primo GEN24 Plus / Symo GEN24 Plus US (SunSpec int+SF with 700-series models)
Fronius Primo/Symo GEN24 (Plus) US variants with a battery configured, SunSpec Model Type int+SF; the US map appends IEEE 1547 models 701-713 after storage model 124.
Also known as: Primo GEN24 Plus US, Symo GEN24 Plus US, Primo GEN24 10.0 208-240, Primo GEN24 3.8 208-240, Primo GEN24 6.0 208-240 - Solar inverter gateway (plant data logger)
Huawei SmartLogger plant data logger (Modbus TCP)
Huawei SmartLogger (V100R001C00 to V300R001C00 firmware families) per ModBus Interface Definitions issue 35; the document names only 'SmartLogger', so check the issue that matches your hardware and firmware.
Also known as: Huawei SmartLogger - Solar inverter
Schneider Electric Conext Core XC Series grid-tie PV inverter (0G-XC-BB)
Conext Core XC Series grid-tied PV inverters (540/630/680 kW ratings, 0G-XC-BB) with firmware v1.07 and later; some registers need newer firmware as noted.
Also known as: 0G-XC-BB, XC-AIC15P
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.