- Home
- Modbus register maps
- Studer Innotec
- 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
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
Integration notes: Studer Innotec Xcom-CAN in BMS mode (lithium battery link, 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 122 | Charge voltage limit {7061} | FLOAT32 ABCD | BMS charge voltage limit | Read |
| IR 126 | Charge current limit {7063} | FLOAT32 ABCD | BMS charge current limit | 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 Xcom-CAN BMS; 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 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.
| 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 | 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 | 44 | Minigrid State of Charge {7022} | FLOAT32 | ABCD | 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 | 94 | Manufacturer State of Charge {7047} | FLOAT32 | ABCD | % | Read | |||
| IR | 106 | Battery Type {7053} | FLOAT32 | ABCD | Read | ||||
| IR | 108 | BMS Version {7054} | FLOAT32 | ABCD | Read | ||||
| IR | 110 | Nominal or remaining battery capacity (see battery documentation) {7055} | FLOAT32 | ABCD | Ah | Read | |||
| IR | 112 | Reserved Manufacturer ID {7056} | FLOAT32 | ABCD | Read | ||||
| IR | 114 | State Of Health {7057} | FLOAT32 | ABCD | Read | ||||
| IR | 116 | High resolution manufacturer State of Charge {7058} | FLOAT32 | ABCD | Read | ||||
| IR | 118 | Local daily communication error counter (CAN) {7059} | FLOAT32 | ABCD | Read | ||||
| IR | 122 | Charge voltage limit {7061} | FLOAT32 | ABCD | V | Read | |||
| IR | 124 | Discharge voltage limit {7062} | FLOAT32 | ABCD | V | Read | |||
| IR | 126 | Charge current limit {7063} | FLOAT32 | ABCD | A | Read | |||
| IR | 128 | Discharge current limit {7064} | FLOAT32 | ABCD | A | Read | |||
| IR | 130 | Recommended charge current {7065} | FLOAT32 | ABCD | A | Read | |||
| IR | 132 | Recommended discharge current {7066} | FLOAT32 | ABCD | A | Read | |||
| IR | 134 | Manufacturer name {7067} | Enumerated state, sent as a float (1.0 = code 1). | FLOAT32 | ABCD | Read | 0 = OTHERS; 1 = BYD; 2 = PYLON; 3 = WECO | ||
| IR | 136 | State of Charge status {7068} | Enumerated state, sent as a float (1.0 = code 1). | FLOAT32 | ABCD | Read | 0 = 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 | ||
| IR | 138 | State of Charge for backup {7069} | FLOAT32 | ABCD | Read | ||||
| IR | 140 | State of Charge for grid-feeding {7070} | FLOAT32 | ABCD | Read | ||||
| IR | 142 | State of Charge for end of charge {7071} | FLOAT32 | ABCD | Read | ||||
| 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 | 124 | SOC level for backup {6062} | Expert level. Range 0 to 100, default 30. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 126 | SOC level for grid feeding {6063} | Expert level. Range 0 to 100, default 98. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 128 | Use battery current limits instead of recommended values {6064} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 132 | Manufacturer SOC for 0% displayed {6066} | Expert level. Range 0 to 60, default 0. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 134 | Manufacturer SOC for 100% displayed {6067} | Expert level. Range 80 to 100, default 100. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 136 | Allow user to define the maximum charge current of the battery {6068} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 138 | Maximum charge current defined by user {6069} | Expert level. Range 0 to 10000, default 10. | FLOAT32 | ABCD | A | Read/write | ||
| HR | 140 | SOC level under which battery discharge is stopped {6070} | Expert level. Range 0 to 100, default 15. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 142 | Use battery priority as energy source when SOC >= SOC for backup (not recommended in parallel) {6071} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 144 | Solar Inverter connected on AC-Out {6072} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 146 | Delta from user frequency to start derating of solar inverter {6073} | Expert level. Range 0 to 5, default 1. | FLOAT32 | ABCD | Hz | Read/write | ||
| HR | 148 | Delta from user frequency to reach 100% derating of solar inverter {6074} | Expert level. Range 0 to 5, default 2.7. | FLOAT32 | ABCD | Hz | Read/write | ||
| HR | 150 | SOC level for end of charge {6075} | Expert level. Range 80 to 100, default 100. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 152 | Allow user to define the maximum discharge current of the battery {6076} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 154 | Maximum discharge current defined by user {6077} | Expert level. Range 0 to 10000, default 10. | FLOAT32 | ABCD | A | Read/write | ||
| HR | 156 | Charge current limit ratio {6078} | Expert level. Range 80 to 95, default 90. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 158 | Allow periodic full charging {6079} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 160 | Waiting time between two periodic full charges {6080} | Expert level. Range 1 to 1000, default 168. | FLOAT32 | ABCD | h | Read/write | ||
| HR | 162 | Time fully charged before resetting periodical full charge {6081} | Expert level. Range 1 to 60, default 5. | FLOAT32 | ABCD | min | Read/write | ||
| HR | 164 | Ki current regulation {6082} | Qualified service level. Range 1 to 100, default 15. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 172 | AC-Coupling priority {6086} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 174 | SOC level to start end of charge derating {6087} | Expert level. Range 80 to 100, default 90. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 176 | Charge current rate at end of charge {6088} | Expert level. Range 0 to 100, default 20. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 178 | Allow adaptative SOC for backup {6089} | Expert level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 180 | Time before reseting adaptative SOC for Backup {6090} | Expert level. Range 1 to 60, default 5. | FLOAT32 | ABCD | min | Read/write | ||
| HR | 182 | SOC in percent to reset adaptative SOC for Backup {6091} | Expert level. Range 80 to 100, default 99. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 184 | SOC in percent to increase adaptative SOC for Backup {6092} | Expert level. Range 20 to 100, default 98. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 186 | Discharge current limit ratio {6093} | Expert level. Range 80 to 95, default 95. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 188 | Enable minigrid {6094} | Installer level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 190 | Enable minigrid as central {6095} | Installer level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 194 | Frequency offset when minigrid energy is low {6097} | Installer level. Range -5 to 0, default -3. | FLOAT32 | ABCD | Hz | Read/write | ||
| HR | 196 | Frequency offset when minigrid energy is full {6098} | Installer level. Range 0 to 5, default 3. | FLOAT32 | ABCD | Hz | Read/write | ||
| HR | 198 | Forced activation of the minigrid genset {6099} | Installer level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 200 | Delays for forcing activation of the minigrid genset {6100} | Installer level. Minutes after midnight as a float (0-1440). | FLOAT32 | ABCD | min | Read/write | ||
| HR | 202 | SoC to start forcing activation of the minigrid genset {6101} | Installer level. Range 0 to 100, default 20. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 204 | SoC to end forcing activation of the minigrid genset {6102} | Installer level. Range 0 to 100, default 50. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 208 | SOC in percent to reset periodical full charge {6104} | Expert level. Range 90 to 100, default 100. | FLOAT32 | ABCD | % | Read/write | ||
| HR | 210 | Enable overcharge security with transfer {6105} | Installer level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes | ||
| HR | 212 | Use target voltage max. for limit {6106} | Installer level. Float 0.0 = no, 1.0 = yes. | FLOAT32 | ABCD | Read/write | 0 = No; 1 = Yes |
Notes on this map
- The Xcom-CAN BMS uses the same unit IDs (60/61) as the BSP; only one of the two can be in an installation.
- 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 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
- Sensor (battery monitor for Studer systems)
Studer Innotec BSP battery status processor (via Xcom-485i)
Studer BSP-500 and BSP-1200 battery status processors read through an Xcom-485i Modbus RTU gateway, system release R706.
Also known as: BSP-500, BSP-1200, BSP500, BSP1200, Xcom-485i - 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 (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 Tauro 50-3 (SunSpec int+SF)
Fronius Tauro 50-3-P / 50-3-D commercial inverters (rest-of-world map, 3 MPPT), SunSpec Model Type int+SF.
Also known as: Fronius Tauro, Tauro 50-3-P, Tauro 50-3-D - Solar charge controller (PWM, dual battery)
Morningstar SunSaver Duo dual-battery PWM charge controller (Modbus RTU via MeterBus)
Morningstar SunSaver Duo through the MSC MeterBus-to-RS-232 adapter; Modbus specification V04 (19 March 2019). 16-bit registers only.
Also known as: SunSaver Duo, SSDuo - Solar inverter gateway (PV plant data logger)
SMA Sunny WebBox Modbus gateway (plant and gateway unit IDs 1-2)
Sunny WebBox firmware 1.52 or later with Modbus enabled, SMA Modbus profile as documented in WEBBOX_MODBUS-TB-US-EN-19 v1.9 (legacy product).
Also known as: Sunny WebBox, WebBox, SWEBBOX, Sunny WebBox with Bluetooth - Solar inverter
Fronius Tauro ECO 50-100 (SunSpec int+SF)
Fronius Tauro ECO 50-100 kW commercial inverters (rest-of-world map, single MPPT), SunSpec Model Type int+SF.
Also known as: Fronius Tauro ECO, Tauro ECO 50-3-P, Tauro ECO 99-3-D, Tauro ECO 100-3-P, Tauro ECO 100-3-D - Solar charge controller (MPPT, battery charger)
Morningstar SunSaver MPPT solar charge controller (Modbus RTU via MeterBus)
Morningstar SunSaver MPPT through the MSC MeterBus-to-RS-232 adapter; Modbus specification v11.
Also known as: SunSaver MPPT, SS-MPPT - Solar inverter (via Sunny WebBox gateway)
SMA Sunny WebBox Modbus profile - common addresses of SMA devices (unit IDs 3-247)
SMA devices reached through a Sunny WebBox (fw 1.52+) on unit IDs 3-247 whose family uses the common address set; SB n000US and SB nn000TL-US-12 families use their own tables instead.
Also known as: Sunny WebBox device profile, SMA Modbus profile WebBox, Sunny Central via WebBox, Sunny Tripower STP nn000TL-10 via WebBox, Sunny Mini Central via WebBox
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.