- Home
- Modbus register maps
- Bender
- COM461MT BMS-to-Modbus/TCP gateway
Gateway for Bender BMS-bus devices (insulation monitors, RCMs, changeover modules) - sensor/alarm data · Modbus register map
Bender COM461MT BMS-to-Modbus/TCP gateway Modbus register map
Updated 17 November 2026
The COM461MT sits on a Bender internal BMS bus (RS-485) and republishes the data of up to 150 BMS devices (ISOMETER, RCMS, EDS, MK800, PRC changeover modules) as Modbus/TCP input registers. Each BMS address gets its own 256-register block: device name, timestamp, alarm flags, then 4 registers per channel (float value, alarm/unit byte pair, text code). This map shows the block for BMS address 1 (channels 1-12), the test record at address 0 and the command interface.
This page lists 50 Modbus registers for the Bender COM461MT BMS-to-Modbus/TCP gateway — 4 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Bender’s own free documentation (linked below) and checked against it.
- Manufacturer
- Bender
- Model
- COM461MT BMS-to-Modbus/TCP gateway
- Equipment type
- Gateway for Bender BMS-bus devices (insulation monitors, RCMs, changeover modules) - sensor/alarm data
- Registers
- 50 (4 writable)
- Transport
- Modbus TCP
- Default unit ID
- Not stated
- Documented addressing
- hexadecimal, 0-based
- 32-bit word order
- ABCD high word first (big-endian)
- Firmware
- D402 V1.0x
- Also known as
- COM461MT, B95061021
Integration notes: Bender COM461MT BMS-to-Modbus/TCP gateway
Read input registers (FC4) at BMS address x 0x100: register +0x0E tells you if the device has an alarm or has dropped off the bus, and each channel's float value sits at +0x10 + 4 x (channel-1). First read the test record at 0x0010/0x0014 (230.0 and 12.34) to prove your float word order.
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 20 | Reference: channel 2 value | FLOAT32 ABCD | Test value 12.34 - check word order once | Read |
| IR 270 | Device 1: common alarm / device lost | BITMAP16 | Common alarm and device-lost flags | Read |
| IR 272 | Device 1: channel 1 value | FLOAT32 ABCD | Channel 1 measured value | Read |
| IR 274 | Device 1: channel 1 AT&T / R&U | UINT16 | Channel 1 alarm type and unit | Read |
| IR 275 | Device 1: channel 1 description code | UINT16 | Channel 1 text code | Read |
| IR 64516 | Command status | UINT16 | Status of the last command | Read |
Enable Modbus control & writes
Set IP address, subnet mask, BMS address and 'Modbus control' (on/off) on the gateway's web page (factory IP 192.168.0.254, mask 255.255.0.0). Commands only work while Modbus control is enabled.
Byte order & addressing
- Only FC4 (read input registers) is used for data; up to 125 registers per request. FC16 is used for the command block.
- Some Modbus clients need an offset of 1 (start of the process image becomes 0x0101).
- Commands: always write all four words 0xFC00-0xFC03 in one FC16 request, then poll 0xFC04 until it reads 2 (ready) or 1 (error).
- BMS address 0 is a simulated device holding fixed test values; no real device can use address 0.
Network setup
- Connect a PC to the COM461MT and browse to its IP to change network settings, BMS address, time zone and NTP server.
- Terminate the internal BMS bus (RS-485, 9.6 kbit/s): switch on the COM461MT's terminating switch when it sits at the end of the bus.
- Run a BMS bus scan so the gateway learns the device names shown at +0x00 of each block.
Watch out for
- A block exists for every BMS address but only holds data for devices actually present; check the device-lost flag before trusting values.
- The meaning of each channel depends on the connected Bender device type, not on the gateway.
Bender COM461MT BMS-to-Modbus/TCP gateway 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 | 0doc 0x0000 | Reference: device type text | Test record at virtual BMS address 0; reads the text TEST. | STRING[20] | Read | ||||
| IR | 14doc 0x000E | Reference: common alarm / device lost | Test record; common alarm bit is set. | BITMAP16 | Read | bit 0 = Device lost (LSB of low byte); bit 8 = Common alarm (LSB of high byte) | |||
| IR | 16doc 0x0010 | Reference: channel 1 value | Test value 230.0 (undervoltage). Use it to check your float word order. | FLOAT32 | ABCD | V | Read | ||
| IR | 20doc 0x0014 | Reference: channel 2 value | Test value 12.34 (overcurrent); raw words 0x4145 0x70A4. | FLOAT32 | ABCD | A | Read | ||
| IR | 256doc 0x0100 | Device 1: device name | Device type text learned by the gateway's BMS bus scan. | STRING[20] | Read | ||||
| IR | 266doc 0x010A | Device 1: timestamp year / month | High byte = year (YY), low byte = month. | UINT16 | Read | ||||
| IR | 267doc 0x010B | Device 1: timestamp day / hour | High byte = day, low byte = hour. | UINT16 | Read | ||||
| IR | 268doc 0x010C | Device 1: timestamp minute / second | High byte = minute, low byte = second. | UINT16 | Read | ||||
| IR | 270doc 0x010E | Device 1: common alarm / device lost | Alarm summary and communication-loss flag for this BMS device. | BITMAP16 | Read | bit 0 = Device lost / no communication (LSB of low byte); bit 8 = Common alarm (LSB of high byte) | |||
| IR | 272doc 0x0110 | Device 1: channel 1 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 274doc 0x0112 | Device 1: channel 1 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 275doc 0x0113 | Device 1: channel 1 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 276doc 0x0114 | Device 1: channel 2 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 278doc 0x0116 | Device 1: channel 2 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 279doc 0x0117 | Device 1: channel 2 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 280doc 0x0118 | Device 1: channel 3 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 282doc 0x011A | Device 1: channel 3 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 283doc 0x011B | Device 1: channel 3 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 284doc 0x011C | Device 1: channel 4 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 286doc 0x011E | Device 1: channel 4 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 287doc 0x011F | Device 1: channel 4 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 288doc 0x0120 | Device 1: channel 5 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 290doc 0x0122 | Device 1: channel 5 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 291doc 0x0123 | Device 1: channel 5 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 292doc 0x0124 | Device 1: channel 6 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 294doc 0x0126 | Device 1: channel 6 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 295doc 0x0127 | Device 1: channel 6 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 296doc 0x0128 | Device 1: channel 7 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 298doc 0x012A | Device 1: channel 7 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 299doc 0x012B | Device 1: channel 7 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 300doc 0x012C | Device 1: channel 8 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 302doc 0x012E | Device 1: channel 8 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 303doc 0x012F | Device 1: channel 8 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 304doc 0x0130 | Device 1: channel 9 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 306doc 0x0132 | Device 1: channel 9 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 307doc 0x0133 | Device 1: channel 9 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 308doc 0x0134 | Device 1: channel 10 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 310doc 0x0136 | Device 1: channel 10 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 311doc 0x0137 | Device 1: channel 10 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 312doc 0x0138 | Device 1: channel 11 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 314doc 0x013A | Device 1: channel 11 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 315doc 0x013B | Device 1: channel 11 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 316doc 0x013C | Device 1: channel 12 value | IEEE 754 float; unit given by the R&U byte of the next-but-one word. | FLOAT32 | ABCD | Read | |||
| IR | 318doc 0x013E | Device 1: channel 12 AT&T / R&U | High byte = alarm/test type, low byte = range and unit code. | UINT16 | Read | ||||
| IR | 319doc 0x013F | Device 1: channel 12 description code | Bender text code for the channel, e.g. 71 = insulation fault, 76 = voltage. | UINT16 | Read | ||||
| IR | 64516doc 0xFC04 | Command status | Result of the last command, read with FC4. | UINT16 | Read | 0 = Busy; 1 = Error; 2 = Ready (done) | |||
| HR | 64512doc 0xFC00 | Command: external BMS bus address | Enter 1 when there is no external BMS bus. | UINT16 | Write | ||||
| HR | 64513doc 0xFC01 | Command: internal BMS bus address | Target device 1-150, or 0 for broadcast commands. | UINT16 | Write | ||||
| HR | 64514doc 0xFC02 | Command: BMS channel | Channel 1-12 for relay commands, otherwise 0. | UINT16 | Write | ||||
| HR | 64515doc 0xFC03 | Command: command code | Writing all four words with FC16 sends the command. | UINT16 | Write | 1 = Test ISOMETER; 2 = Test changeover device PRC; 3 = Start automatic changeover test 1->2, end after T(test); 4 = Start test generator without changeover; 5 = Switch over to line 1; 6 = Switch over to line 2; 7 = Reset alarm (broadcast); 8 = Reset alarm EDS (broadcast); 9 = Buzzer off for alarm address; 10 = Switch on relay/switch; 11 = Switch off relay/switch |
Notes on this map
- Only BMS device address 1 is listed. Every other device uses the same layout shifted by its address: BMS address N starts at N x 0x100 (e.g. address 3 channel 2 = 0x0314). Channel numbers in each block follow the BMS device's own channel list.
- Channels 13-32 continue the 4-register pattern up to 0x008F within each block; channels 33-64 (MK800/TM800 master mode, digital only) are one byte each from 0x90 and are not listed.
- Float word order: the manual states big-endian and gives the test value 12.34 at 0x0014 as words 0x4145, 0x70A4 (high word first), so ABCD is documented, not assumed.
- Channel word 2 packs two bytes. High byte (AT&T): bits 0-2 alarm type (0 none, 1 prewarning, 2 device error, 4 alarm yellow LED, 5 alarm red LED), bit 6 internal test, bit 7 external test. Low byte (R&U): bits 0-4 unit (1 none, 2 ohm, 3 A, 4 V, 5 %, 6 Hz, 7 baud, 8 F, 9 H, 10 degC, 11 degF, 12 s, 13 min, 14 h, 15 day, 16 month, 30 CODE), bits 6-7 validity (0 true value, 1 true value smaller, 2 larger, 3 invalid).
- When the unit is CODE the float holds an internal code, not a measurement; read the description code (word 3) and Bender's text table in ch. 7.4.
- Unit ID is not specified in the manual; its example request uses unit identifier 0x01. The TCP port is not stated.
- The device's own BMS address on the internal bus is 2 by factory default (range 1-99).
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 Bender COM461MT BMS-to-Modbus/TCP gateway
What Modbus registers does the Bender COM461MT BMS-to-Modbus/TCP gateway have?
This map lists 50 registers: 46 input registers, 4 holding registers. 4 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.
Are the Bender COM461MT BMS-to-Modbus/TCP gateway Modbus addresses 0-based or 1-based?
The manufacturer's document numbers registers hexadecimal, 0-based. 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. Addresses are printed in hex and go on the wire as-is: the manual's example request for BMS device 1 puts 0x0100 in the start-address field. Block start = BMS address x 0x100; channel n of that device starts at block + 0x10 + 4 x (n-1). Bender notes that some clients need 1 added (process image then starts at 0x0101).
What byte order does the Bender COM461MT BMS-to-Modbus/TCP gateway 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 Bender COM461MT BMS-to-Modbus/TCP gateway?
Start with IR 20 Reference: channel 2 value (Test value 12.34 - check word order once); IR 270 Device 1: common alarm / device lost (Common alarm and device-lost flags); IR 272 Device 1: channel 1 value (Channel 1 measured value); IR 274 Device 1: channel 1 AT&T / R&U (Channel 1 alarm type and unit); IR 275 Device 1: channel 1 description code (Channel 1 text code); IR 64516 Command status (Status of the last command).
How do I enable Modbus control of the Bender COM461MT BMS-to-Modbus/TCP gateway?
Set IP address, subnet mask, BMS address and 'Modbus control' (on/off) on the gateway's web page (factory IP 192.168.0.254, mask 255.255.0.0). Commands only work while Modbus control is enabled.
Where is the official Bender COM461MT BMS-to-Modbus/TCP gateway Modbus documentation?
The source is COM461MT Operating Manual - BMS Ethernet gateway for the connection of Bender devices with BMS support to Ethernet (TCP/IP) using the Modbus/TCP protocol (COM461MT_D00011_01_M_XXEN/08.2020), revision 2020-08, published free by Bender at https://www.bender.de/fileadmin/content/Products/m/e/COM461MT_D00011_M_XXEN.pdf.
Other ac & vrf gateways register maps
- Split AC unit (VRF / split AC gateway built in)
Gree Export residential split air conditioners (built-in Modbus on indoor unit / wired controller)
Gree export residential air conditioners whose indoor-unit controller or wired controller has the integrated Modbus RTU interface; protocol PDF dated 2023-05.
Also known as: Gree residential split Modbus, Gree wall split Modbus, Gree wired controller Modbus - VRF / split AC gateway
Intesis (HMS Networks) IN770AIR***O000 700 Series Air Gateway, Midea application (Modbus)
Intesis 700 Series Air Gateway IN770AIR***O000 with the Midea application (XYE bus), Modbus RTU / TCP server, user manual version 1.0.22 (2025-12-09).
Also known as: IN770AIR00MO000, IN770AIR00SO000, IN770AIRXXSO000 - Lighting gateway (DALI-2 to Modbus)
Intesis (HMS Networks) INMBSDAL0640000 / INMBSDAL1280000 DALI-2 to Modbus RTU / TCP server
Intesis Modbus Server - DALI with one (0640000, RTU + TCP) or two (1280000, TCP only) DALI channels, Modbus Addresses parameter set to Fixed; user manual r1.2 (09/2021).
Also known as: INMBSDAL0640000, INMBSDAL1280000, Intesis Modbus Server - DALI, Intesis DALI-2 Modbus gateway - VRF / split AC gateway
Intesis (HMS Networks) INMBSHIT016O000 Hitachi VRF to Modbus RTU / TCP gateway (16 / 64 indoor units)
Intesis Modbus Server - Hitachi VRF, order codes INMBSHIT016O000 / INMBSHIT064O000 (legacy HI-AC-MBS-16 / HI-AC-MBS-64), user manual User Manual r1.2 EN.
Also known as: INMBSHIT016O000, INMBSHIT064O000, HI-AC-MBS-16, HI-AC-MBS-64, Intesis Modbus Server Hitachi VRF - VRF / split AC gateway
Intesis (HMS Networks) INMBSMIT001I000 Mitsubishi Electric AC to Modbus RTU gateway
One Mitsubishi Electric Domestic, Mr. Slim or City Multi indoor unit via INMBSMIT001I000, user manual r2.8 (11/2024).
Also known as: INMBSMIT001I000, Intesis Mitsubishi Electric Modbus - VRF / split AC gateway
Intesis (HMS Networks) INMBSSAM001R100 Samsung NASA AC to Modbus RTU gateway
Samsung NASA-protocol commercial indoor units on the remote-controller bus, user's manual r1.4 (01/2024).
Also known as: INMBSSAM001R100, Intesis Samsung NASA Modbus
All ac & vrf gateways Modbus register maps →
Source: COM461MT Operating Manual - BMS Ethernet gateway for the connection of Bender devices with BMS support to Ethernet (TCP/IP) using the Modbus/TCP protocol · COM461MT_D00011_01_M_XXEN/08.2020 · rev. 2020-08. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.