Advantech ADAM-6018 Modbus register map
8-channel isolated thermocouple input module with 8 digital outputs, Modbus TCP
- Official
- 80 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
- 28 holding registers, 52 coils
- Groups
- 5
- Revision
- 2 · 2026-10-17
- Added
- ()
- File
- maps/advantech/adam-6018.mbmap.json · 10 KB · history
- SHA-256
- ea9d563c678d5d1a8160e984caa39927217c0360d2c2128a908ff3eb2fe8a2bf
- Manufacturer
- advantech.com
Sources and notes
- ADAM-6000 Series User Manual · version Edition 9 Appendix B.2, ADAM-6018
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 | 17 | bool | RW | ||||
| CO | 18 | bool | RW | ||||
| CO | 19 | bool | RW | ||||
| CO | 20 | bool | RW | ||||
| CO | 21 | bool | RW | ||||
| CO | 22 | bool | RW | ||||
| CO | 23 | bool | RW | ||||
| CO | 24 | bool | RW | ||||
| CO | 101 | bool | RW | ||||
| CO | 102 | bool | RW | ||||
| CO | 103 | bool | RW | ||||
| CO | 104 | bool | RW | ||||
| CO | 105 | bool | RW | ||||
| CO | 106 | bool | RW | ||||
| CO | 107 | bool | RW | ||||
| CO | 108 | bool | RW | ||||
| CO | 109 | bool | RW | ||||
| CO | 111 | bool | RW | ||||
| CO | 112 | bool | RW | ||||
| CO | 113 | bool | RW | ||||
| CO | 114 | bool | RW | ||||
| CO | 115 | bool | RW | ||||
| CO | 116 | bool | RW | ||||
| CO | 117 | bool | RW | ||||
| CO | 118 | bool | RW | ||||
| CO | 119 | bool | RW | ||||
| CO | 121 | bool | R | ||||
| CO | 122 | bool | R | ||||
| CO | 123 | bool | R | ||||
| CO | 124 | bool | R | ||||
| CO | 125 | bool | R | ||||
| CO | 126 | bool | R | ||||
| CO | 127 | bool | R | ||||
| CO | 128 | bool | R | ||||
| CO | 131 | bool | R | ||||
| CO | 132 | bool | R | ||||
| CO | 133 | bool | R | ||||
| CO | 134 | bool | R | ||||
| CO | 135 | bool | R | ||||
| CO | 136 | bool | R | ||||
| CO | 137 | bool | R | ||||
| CO | 138 | bool | R | ||||
| CO | 139 | bool | R | ||||
| CO | 141 | bool | R | ||||
| CO | 142 | bool | R | ||||
| CO | 143 | bool | R | ||||
| CO | 144 | bool | R | ||||
| CO | 145 | bool | R | ||||
| CO | 146 | bool | R | ||||
| CO | 147 | bool | R | ||||
| CO | 148 | bool | R | ||||
| CO | 149 | bool | R | ||||
| HR | 1 | uint16 | R | Raw value of the thermocouple range | |||
| HR | 2 | uint16 | R | ||||
| HR | 3 | uint16 | R | ||||
| HR | 4 | uint16 | R | ||||
| HR | 5 | uint16 | R | ||||
| HR | 6 | uint16 | R | ||||
| HR | 7 | uint16 | R | ||||
| HR | 8 | uint16 | R | ||||
| HR | 9 | uint16 | R | ||||
| HR | 11 | uint16 | R | ||||
| HR | 12 | uint16 | R | ||||
| HR | 13 | uint16 | R | ||||
| HR | 14 | uint16 | R | ||||
| HR | 15 | uint16 | R | ||||
| HR | 16 | uint16 | R | ||||
| HR | 17 | uint16 | R | ||||
| HR | 18 | uint16 | R | ||||
| HR | 19 | uint16 | R | ||||
| HR | 21 | uint16 | R | ||||
| HR | 22 | uint16 | R | ||||
| HR | 23 | uint16 | R | ||||
| HR | 24 | uint16 | R | ||||
| HR | 25 | uint16 | R | ||||
| HR | 26 | uint16 | R | ||||
| HR | 27 | uint16 | R | ||||
| HR | 28 | uint16 | R | ||||
| HR | 29 | uint16 | R | ||||
| HR | 305 | uint16 | 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).