{"id":10742,"date":"2020-05-06T11:16:46","date_gmt":"2020-05-06T14:16:46","guid":{"rendered":"http:\/\/kb.elipse.com.br\/en\/?p=10742"},"modified":"2020-05-06T11:16:46","modified_gmt":"2020-05-06T14:16:46","slug":"common-issues-faced-by-modbus-driver-interpreting-addresses-prefixes","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/common-issues-faced-by-modbus-driver-interpreting-addresses-prefixes\/","title":{"rendered":"Common issues faced by Modbus driver: Interpreting addresses prefixes"},"content":{"rendered":"

Question:<\/h3>\n

Some vendors describe the addresses of their drivers in particular ways; therefore, the process of interpreting the Modbus<\/a> addresses prefixes can become rather complicated. So, how can I establish the right interpretation for the prefixes in this device’s address?<\/p>\n

<\/h3>\n

Solution:<\/h3>\n

In order to find the correct process of interpreting the Modbus addresses prefixes correctly, you must realize that they are not always in conformity to what’s expected of them. That is to say, this happens because some vendors will still use an old standard, known as Modbus Convention<\/a>. By this convention, each address increments one value, which in turn depends on the addressing space accessed by the function. The table below lists the increments used by the old\u00a0 Modbus Convention.<\/p>\n\n\n\n\n\n\n\n\n
Data type<\/b><\/td>\nModbus function<\/strong><\/td>\nIncrement<\/strong><\/td>\n<\/tr>\n
Coils<\/td>\n01: Read Coils (0x)
\n05: Write Single Coil (0x)
\n15: Write Multiple Coils (0x)<\/td>\n		00000<\/td>\n<\/tr>\n
Discrete Inputs<\/td>\n02: Read Discrete Inputs (1x)<\/td>\n10000<\/td>\n<\/tr>\n
Input Registers<\/td>\n04: Read Input Registers (3x)<\/td>\n30000<\/td>\n<\/tr>\n
Holding Registers<\/td>\n03: Read Holding Registers (4x)
\n06: Write Single Register (4x)
\n16: Write Multiple Registers (4x)<\/td>\n		40000<\/td>\n<\/tr>\n
File Register (anteriormente, Extended Memory file)<\/td>\n20: Read General Reference (6x)
\n21: Write General Reference (6x)<\/td>\n		60000<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

This increment can also work as a prefix, since these values are all multiple of 10000. Therefore, when setting up the addresses in the driver, you should ignore this increment or prefix. See the examples in the table below:<\/p>\n\n\n\n\n\n\n\n\n\n
Address with Increment
\n<\/strong>(Device)<\/strong><\/td>\n		Address without Increment
\n(Driver)<\/strong><\/td>\n		Modbus function<\/strong><\/td>\n<\/tr>\n
01234<\/td>\n1234<\/td>\n01: Read Coils
\n05: Write Single Coil
\n15: Write Multiple Coils<\/td>\n<\/tr>\n
11234<\/td>\n1234<\/td>\n02: Read Discrete Inputs<\/td>\n<\/tr>\n
31234<\/td>\n1234<\/td>\n04: Read Input Registers<\/td>\n<\/tr>\n
41234<\/td>\n1234<\/td>\n03: Read Holding Registers
\n06: Write Single Register
\n16: Write Multiple Registers<\/td>\n<\/tr>\n
45789<\/td>\n5789<\/td>\n03: Read Holding Registers
\n06: Write Single Register
\n16: Write Multiple Registers<\/td>\n<\/tr>\n
65789<\/td>\n5789<\/td>\n20: Read General Reference
\n21: Write General Reference<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Related articles:<\/h3>\n
\n

The articles below all refer to common issues faced by the Modbus driver:<\/p>\n