Advantech ADAM-4024 Modbus register map
4-channel analog output module with 4 emergency digital inputs, RS485 Modbus RTU
- Official
- 22 registers
- Modbus RTU
- Revision 2 · 2026-10-17
- Identity: model
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
- 18 holding registers, 4 coils
- Groups
- 5
- Translation tables
- 1
- Revision
- 2 · 2026-10-17
- Added
- ()
- File
- maps/advantech/adam-4024.mbmap.json · 4 KB · history
- SHA-256
- 5b008d527d6bba06c1eae5c3fa5414d63a21b29b034da583a485c7e3c0133443
- Manufacturer
- advantech.com
Device identity
What a tool can read to check that this map fits the connected device (SPEC.md section 4.7). Registers with a role are read like any other register.
| Role | Register | Address | Type | Values |
|---|---|---|---|---|
| Model | Module name 1 | holding 211 | uint16 | 0x4024 = ADAM-4024 |
Sources and notes
- ADAM-4000 Data Acquisition Modules User's Manual · version Edition 10.7 Appendix G, table 5; 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 | 1 | bool | R | ||||
| CO | 2 | bool | R | ||||
| CO | 3 | bool | R | ||||
| CO | 4 | bool | R | ||||
| HR | 1 | uint16 | RW | Raw value of the range set by the type code | |||
| HR | 2 | uint16 | RW | ||||
| HR | 3 | uint16 | RW | ||||
| HR | 4 | uint16 | RW | ||||
| HR | 201 | uint16 | RW | ||||
| HR | 202 | uint16 | RW | ||||
| HR | 203 | uint16 | RW | ||||
| HR | 204 | uint16 | RW | ||||
| HR | 211 | uint16 | R | ||||
| HR | 212 | uint16 | R | ||||
| HR | 213 | uint16 | R | ||||
| HR | 214 | uint16 | R | ||||
| HR | 215 | uint16 | R | ||||
| HR | 216 | 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 |
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).