Reinhausen TAPCON 240 Modbus register map
Voltage regulator for on-load tap-changers with the CIC communication card
- Official
- 41 registers
- Modbus RTU
- Revision 2 · 2026-10-18
Official: Written from the manufacturer's documentation, but not tested on a device yet. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.
Communication
- Protocol
- Modbus RTU
- Unit ID
- 1
- Serial
- 9600 8E1 · 9600 baud, 8 data bits, even parity, 1 stop bit
- Byte / word order
- ABCD · bytes big-endian, words high first
- Addresses
- 0-based
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 1 holding register, 4 input registers, 13 coils, 23 discrete inputs
- Groups
- 7
- Revision
- 2 · 2026-10-18
- Added
- ()
- File
- maps/reinhausen/tapcon-240.mbmap.json · 7 KB · history
- SHA-256
- 08e074a385fea62d0766b31e01d31dae7648a5904d5a37db07184a12a61610e9
- Manufacturer
- reinhausen.com
Sources and notes
- Voltage regulator TAPCON 240, Protocol description MODBUS · version 2398449/01 EN, 2011-07 section 5, data points
Source: Maschinenfabrik Reinhausen, "Voltage regulator TAPCON 240, Protocol description MODBUS", supplement 2398449/01 (2011-07), section 5
- Modbus RTU or ASCII over RS-232, RS-485 or fibre. ASCII uses 7E1, RTU 8E1.
- The optional RJ45 port carries Modbus RTU wrapped in TCP (factory port 1234, 19200 baud), not Modbus TCP.
- Coils can only be written (FC05); their state cannot be read back. Write one coil or one register per request.
- Commands from the control system are only executed when the regulator is in remote mode.
- Coil 8 is either 'raise/lower desired voltage value' or 'desired voltage value 1', depending on how MR parameterised the device.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| CO | 0 | bool | W | On raises; only in manual mode | |||
| CO | 1 | bool | W | On lowers; only in manual mode | |||
| CO | 5 | bool | W | ||||
| CO | 8 | bool | W | Optional function, parameterised by MR; replaces desired voltage value 1-3 | |||
| CO | 8 | bool | W | Only when no inputs select values 2 and 3 and raise/lower desired value is not parameterised | |||
| CO | 9 | bool | W | ||||
| CO | 10 | bool | W | ||||
| CO | 11 | bool | W | Sets a flag that the regulator can use like an input | |||
| CO | 12 | bool | W | Sets a flag that the regulator can use like an input | |||
| CO | 13 | bool | W | Sets a flag that the regulator can use like an input | |||
| CO | 15 | bool | W | Parallel operation method | |||
| CO | 27 | bool | W | Parallel operation method | |||
| CO | 28 | bool | W | Parallel operation method | |||
| DI | 0 | bool | R | ||||
| DI | 1 | bool | R | ||||
| DI | 2 | bool | R | ||||
| DI | 3 | bool | R | ||||
| DI | 4 | bool | R | ||||
| DI | 5 | bool | R | ||||
| DI | 8 | bool | R | ||||
| DI | 9 | bool | R | ||||
| DI | 10 | bool | R | ||||
| DI | 11 | bool | R | ||||
| DI | 12 | bool | R | ||||
| DI | 13 | bool | R | ||||
| DI | 14 | bool | R | ||||
| DI | 15 | bool | R | ||||
| DI | 16 | bool | R | The supplement does not say which value means local | |||
| DI | 17 | bool | R | Parameterisable message, on when its input or relay is active | |||
| DI | 24 | bool | R | ||||
| DI | 25 | bool | R | Parameterisable message, on when its input or relay is active | |||
| DI | 26 | bool | R | Parameterisable message, on when its input or relay is active | |||
| DI | 27 | bool | R | ||||
| DI | 28 | bool | R | ||||
| DI | 29 | bool | R | ||||
| DI | 30 | bool | R | Parameterisable message, on when its input or relay is active | |||
| IR | 0 | int16 | R | -40 to 40 | |||
| IR | 1 | uint16 | R | V | ×0.1 | 0-170.0 V | |
| IR | 2 | int16 | R | % | ×0.1 | Percent of the effective voltage level | |
| IR | 5 | int16 | R | % | ×0.01 | ||
| HR | 0 | uint16 | RW | V | ×0.1 | Raw 490-1400 |
No registers match
Try part of the name, an address (decimal or 0x hex) or clear the filters.
Help improve this map
- I tested it on a deviceReport whether it worked, even if you did not write the map.
- Suggest a correctionEdit the file on GitHub; it opens a pull request.
- Report a problemA wrong address, type, scale or byte order.
- Read the formatWhat each key of the file means (SPEC.md).