Easy Modbus
  1. Home
  2. Modbus register maps
  3. Studer Innotec
  4. Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i)

Battery inverter system (lithium battery BMS interface) · Modbus register map

Studer Innotec Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i) Modbus register map

Updated 17 November 2026

Short answer

In BMS mode the Studer Xcom-CAN links a lithium battery's BMS to the Xtender system and reports the battery's own values. An Xcom-485i on the Studer bus answers Modbus RTU for it. This map lists the Xcom-CAN BMS user infos (voltage, current, state of charge, BMS limits) as input registers and its parameters as holding registers.

This page lists 74 Modbus registers for the Studer Innotec Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i) — 41 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
Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i)
Equipment type
Battery inverter system (lithium battery BMS interface)
Registers
74 (41 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
Xcom-CAN, Xcom-CAN BMS, 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 Xcom-CAN in BMS mode (lithium battery link, 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 122Charge voltage limit {7061}FLOAT32 ABCDBMS charge voltage limitRead
IR 126Charge current limit {7063}FLOAT32 ABCDBMS charge current limitRead

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 Xcom-CAN in BMS mode (lithium battery link, 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.

74 of 74 shown
Studer Innotec Xcom-CAN in BMS mode (lithium battery link, 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
IR14Ah charged today {7007}FLOAT32ABCDAhRead
IR16Ah discharged today {7008}FLOAT32ABCDAhRead
IR18Ah charged yesterday {7009}FLOAT32ABCDAhRead
IR20Ah discharged yesterday {7010}FLOAT32ABCDAhRead
IR44Minigrid State of Charge {7022}FLOAT32ABCDRead
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
IR94Manufacturer State of Charge {7047}FLOAT32ABCD%Read
IR106Battery Type {7053}FLOAT32ABCDRead
IR108BMS Version {7054}FLOAT32ABCDRead
IR110Nominal or remaining battery capacity (see battery documentation) {7055}FLOAT32ABCDAhRead
IR112Reserved Manufacturer ID {7056}FLOAT32ABCDRead
IR114State Of Health {7057}FLOAT32ABCDRead
IR116High resolution manufacturer State of Charge {7058}FLOAT32ABCDRead
IR118Local daily communication error counter (CAN) {7059}FLOAT32ABCDRead
IR122Charge voltage limit {7061}FLOAT32ABCDVRead
IR124Discharge voltage limit {7062}FLOAT32ABCDVRead
IR126Charge current limit {7063}FLOAT32ABCDARead
IR128Discharge current limit {7064}FLOAT32ABCDARead
IR130Recommended charge current {7065}FLOAT32ABCDARead
IR132Recommended discharge current {7066}FLOAT32ABCDARead
IR134Manufacturer name {7067}Enumerated state, sent as a float (1.0 = code 1).FLOAT32ABCDRead0 = OTHERS; 1 = BYD; 2 = PYLON; 3 = WECO
IR136State of Charge status {7068}Enumerated state, sent as a float (1.0 = code 1).FLOAT32ABCDRead0 = UNK. SOC; 1 = OVER GRID; 2 = AT GRID; 3 = UNDER GRID; 4 = UNDER ADA; 5 = AT BACKUP; 6 = UNDER BACK; 7 = END OF CH; 8 = OVER ENDC; 9 = FULL; 10 = NORMAL
IR138State of Charge for backup {7069}FLOAT32ABCDRead
IR140State of Charge for grid-feeding {7070}FLOAT32ABCDRead
IR142State of Charge for end of charge {7071}FLOAT32ABCDRead
HR8Restore default settings {6004}Basic level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR10Restore factory settings {6005}Installer level. Write 1.0 to trigger.FLOAT32ABCDWrite
HR124SOC level for backup {6062}Expert level. Range 0 to 100, default 30.FLOAT32ABCD%Read/write
HR126SOC level for grid feeding {6063}Expert level. Range 0 to 100, default 98.FLOAT32ABCD%Read/write
HR128Use battery current limits instead of recommended values {6064}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR132Manufacturer SOC for 0% displayed {6066}Expert level. Range 0 to 60, default 0.FLOAT32ABCD%Read/write
HR134Manufacturer SOC for 100% displayed {6067}Expert level. Range 80 to 100, default 100.FLOAT32ABCD%Read/write
HR136Allow user to define the maximum charge current of the battery {6068}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR138Maximum charge current defined by user {6069}Expert level. Range 0 to 10000, default 10.FLOAT32ABCDARead/write
HR140SOC level under which battery discharge is stopped {6070}Expert level. Range 0 to 100, default 15.FLOAT32ABCD%Read/write
HR142Use battery priority as energy source when SOC >= SOC for backup (not recommended in parallel) {6071}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR144Solar Inverter connected on AC-Out {6072}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR146Delta from user frequency to start derating of solar inverter {6073}Expert level. Range 0 to 5, default 1.FLOAT32ABCDHzRead/write
HR148Delta from user frequency to reach 100% derating of solar inverter {6074}Expert level. Range 0 to 5, default 2.7.FLOAT32ABCDHzRead/write
HR150SOC level for end of charge {6075}Expert level. Range 80 to 100, default 100.FLOAT32ABCD%Read/write
HR152Allow user to define the maximum discharge current of the battery {6076}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR154Maximum discharge current defined by user {6077}Expert level. Range 0 to 10000, default 10.FLOAT32ABCDARead/write
HR156Charge current limit ratio {6078}Expert level. Range 80 to 95, default 90.FLOAT32ABCD%Read/write
HR158Allow periodic full charging {6079}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR160Waiting time between two periodic full charges {6080}Expert level. Range 1 to 1000, default 168.FLOAT32ABCDhRead/write
HR162Time fully charged before resetting periodical full charge {6081}Expert level. Range 1 to 60, default 5.FLOAT32ABCDminRead/write
HR164Ki current regulation {6082}Qualified service level. Range 1 to 100, default 15.FLOAT32ABCD%Read/write
HR172AC-Coupling priority {6086}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR174SOC level to start end of charge derating {6087}Expert level. Range 80 to 100, default 90.FLOAT32ABCD%Read/write
HR176Charge current rate at end of charge {6088}Expert level. Range 0 to 100, default 20.FLOAT32ABCD%Read/write
HR178Allow adaptative SOC for backup {6089}Expert level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR180Time before reseting adaptative SOC for Backup {6090}Expert level. Range 1 to 60, default 5.FLOAT32ABCDminRead/write
HR182SOC in percent to reset adaptative SOC for Backup {6091}Expert level. Range 80 to 100, default 99.FLOAT32ABCD%Read/write
HR184SOC in percent to increase adaptative SOC for Backup {6092}Expert level. Range 20 to 100, default 98.FLOAT32ABCD%Read/write
HR186Discharge current limit ratio {6093}Expert level. Range 80 to 95, default 95.FLOAT32ABCD%Read/write
HR188Enable minigrid {6094}Installer level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR190Enable minigrid as central {6095}Installer level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR194Frequency offset when minigrid energy is low {6097}Installer level. Range -5 to 0, default -3.FLOAT32ABCDHzRead/write
HR196Frequency offset when minigrid energy is full {6098}Installer level. Range 0 to 5, default 3.FLOAT32ABCDHzRead/write
HR198Forced activation of the minigrid genset {6099}Installer level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR200Delays for forcing activation of the minigrid genset {6100}Installer level. Minutes after midnight as a float (0-1440).FLOAT32ABCDminRead/write
HR202SoC to start forcing activation of the minigrid genset {6101}Installer level. Range 0 to 100, default 20.FLOAT32ABCD%Read/write
HR204SoC to end forcing activation of the minigrid genset {6102}Installer level. Range 0 to 100, default 50.FLOAT32ABCD%Read/write
HR208SOC in percent to reset periodical full charge {6104}Expert level. Range 90 to 100, default 100.FLOAT32ABCD%Read/write
HR210Enable overcharge security with transfer {6105}Installer level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes
HR212Use target voltage max. for limit {6106}Installer level. Float 0.0 = no, 1.0 = yes.FLOAT32ABCDRead/write0 = No; 1 = Yes

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 Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i)

What Modbus registers does the Studer Innotec Xcom-CAN in BMS mode (lithium battery link, via Xcom-485i) have?

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

Are the Studer Innotec Xcom-CAN in BMS mode (lithium battery link, 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 Xcom-CAN in BMS mode (lithium battery link, 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 Xcom-CAN in BMS mode (lithium battery link, 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 122 Charge voltage limit {7061} (BMS charge voltage limit); IR 126 Charge current limit {7063} (BMS charge current limit).

How do I enable Modbus control of the Studer Innotec Xcom-CAN in BMS mode (lithium battery link, 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 Xcom-CAN in BMS mode (lithium battery link, 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.