Advantech ADAM-6024 Modbus register map
Universal I/O module: 6 AI, 2 AO, 2 DI, 2 DO, Modbus TCP
- Official
- 18 registers
- Modbus TCP
- 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 TCP
- Unit ID
- 1
- TCP port
- 502
- Byte / word order
- CDAB · bytes big-endian, words low first (word swap)
- Addresses
- 1-based · wire address = address − 1
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 14 holding registers, 4 coils
- Groups
- 5
- Revision
- 2 · 2026-10-17
- Added
- ()
- File
- maps/advantech/adam-6024.mbmap.json · 4 KB · history
- SHA-256
- 134c01305655af8d07427962a9cc05c93acca3b94ccbea6828ece6fcee6bd63a
- Manufacturer
- advantech.com
Sources and notes
- ADAM-6000 Series User Manual · version Edition 9 Appendix B.2, ADAM-6024
Source: Advantech, "ADAM-6000 Series User Manual", Edition 9, Appendix B.2 (I/O Modbus mapping tables)
- Addresses are the Modicon numbers of the manual (00001 = coil 1, 40001 = holding register 1).
- 32-bit counters and pulse settings are low word first (the manual: counter = (40002) × 65536 + (40001)).
- Some registers (floats, GCL, diagnostics) need the CE or D version of the module.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| CO | 1 | bool | R | ||||
| CO | 2 | bool | R | ||||
| CO | 17 | bool | RW | ||||
| CO | 18 | bool | RW | ||||
| HR | 1 | uint16 | R | ||||
| HR | 2 | uint16 | R | ||||
| HR | 3 | uint16 | R | ||||
| HR | 4 | uint16 | R | ||||
| HR | 5 | uint16 | R | ||||
| HR | 6 | uint16 | R | ||||
| HR | 11 | uint16 | RW | ||||
| HR | 12 | uint16 | RW | ||||
| HR | 21 | uint16 | R | ||||
| HR | 22 | uint16 | R | ||||
| HR | 23 | uint16 | R | ||||
| HR | 24 | uint16 | R | ||||
| HR | 25 | uint16 | R | ||||
| HR | 26 | uint16 | R |
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).