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

Question:<\/h3>\n

A common problem faced by Modicon Modbus Master driver<\/a> is the following: communication takes place as usual, however the values to be read are different from the ones expected. This can happen due to discrepancies in the indexation of addresses of registers used by Modbus<\/a> driver and the device. This situation can happen especially when reading FLOAT-type variables. How can I fix this?<\/p>\n

 <\/p>\n

Solution:<\/h3>\n

The indexation of addresses of registers at Modbus driver can start at two points: from 0, or from 1.\u00a0 If the driver’s indexation doesn’t match the right values, the driver may end up reading some incorrect values , or even accessing invalid addresses. It is crucial, therefore, that the indexation begin right from the expected value, be it 0 or 1.<\/p>\n

To work around this situation, you can use the driver’s configuration window to access the Modbus tab and then check the Data Address Model Offset<\/strong> option according to the device’s addressing standard (whether it starts in 0 or it starts in 1). To find out the device’s addressing standard, you must check the corresponding documentation supplied by its vendor.<\/p>\n

\"Registers<\/p>\n

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