Advantech ADAM-4015 / ADAM-4015T Modbus register map
6-channel RTD input module (ADAM-4015T: thermistor inputs), RS485 Modbus RTU
- Official
- 28 registers
- Modbus RTU
- Revision 2 · 2026-10-17
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 8N1 · 9600 baud, 8 data bits, none parity, 1 stop bit
- Byte / word order
- ABCD · bytes big-endian, words high first
- Addresses
- 1-based · wire address = address − 1
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 22 holding registers, 6 coils
- Groups
- 3
- Translation tables
- 1
- Revision
- 2 · 2026-10-17
- Added
- ()
- File
- maps/advantech/adam-4015.mbmap.json · 5 KB · history
- SHA-256
- de965f0397d1c344f0ab57576605f21c996fcf5c4a82a0d3419860d652fd3903
- Manufacturer
- advantech.com
Sources and notes
- ADAM-4000 Data Acquisition Modules User's Manual · version Edition 10.7 Appendix G, table 1; type codes from chapters 5 and 6
Source: Advantech, "ADAM-4000 Data Acquisition Modules User's Manual", Edition 10.7, Appendix G (I/O Modbus mapping table)
- Addresses are the Modicon numbers of the manual (00001 = coil 1, 40001 = holding register 1).
- The module ships with the ADAM ASCII protocol; Appendix H of the manual switches it to Modbus RTU.
- Channel values are raw 16-bit values of the range chosen by each channel's type code; the manual gives the conversion for the ASCII protocol only.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| CO | 201 | bool | R | ||||
| CO | 202 | bool | R | ||||
| CO | 203 | bool | R | ||||
| CO | 204 | bool | R | ||||
| CO | 205 | bool | R | ||||
| CO | 206 | bool | R | ||||
| HR | 1 | int16 | R | Raw value of the range set by the type code | |||
| HR | 2 | int16 | R | ||||
| HR | 3 | int16 | R | ||||
| HR | 4 | int16 | R | ||||
| HR | 5 | int16 | R | ||||
| HR | 6 | int16 | R | ||||
| HR | 201 | uint16 | RW | ||||
| HR | 202 | uint16 | RW | ||||
| HR | 203 | uint16 | RW | ||||
| HR | 204 | uint16 | RW | ||||
| HR | 205 | uint16 | RW | ||||
| HR | 206 | uint16 | RW | ||||
| HR | 211 | uint16 | R | The manual's table repeats another module's value here | |||
| HR | 212 | uint16 | R | ||||
| HR | 213 | uint16 | R | ||||
| HR | 214 | uint16 | R | ||||
| HR | 221 | bool bit 0 | RW | ||||
| HR | 221 | bool bit 1 | RW | ||||
| HR | 221 | bool bit 2 | RW | ||||
| HR | 221 | bool bit 3 | RW | ||||
| HR | 221 | bool bit 4 | RW | ||||
| HR | 221 | bool bit 5 | RW |
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).