{"id":10727,"date":"2020-05-06T11:15:36","date_gmt":"2020-05-06T14:15:36","guid":{"rendered":"http:\/\/kb.elipse.com.br\/en\/?p=10727"},"modified":"2020-05-06T15:24:59","modified_gmt":"2020-05-06T18:24:59","slug":"common-issues-faced-by-modbus-driver-scrambled-bytes-and-words","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/common-issues-faced-by-modbus-driver-scrambled-bytes-and-words\/","title":{"rendered":"Common issues faced by Modbus driver: Scrambled bytes and words"},"content":{"rendered":"

Question:<\/h3>\n

With Modbus driver<\/a>, certain operations (especially when reading FLOAT-type variables) can take place, but the values are not sorted out in the order they were expected; that is, bytes and words are displayed in a scrambled order. How can I fix this?<\/p>\n

<\/h3>\n

Solution:<\/h3>\n

When reading values that occupy more than one register, the device can send bytes and words in a scrambled order, that is, out of the order they were supposed to be displayed.\u00a0 The driver then allows adjusting the bytes interpretation order. To apply these settings, there are two possibilities, according to how tags are configured: either by numeric parameters (N\/B) or by syntactic parameters (Device or Item). In order to figure out the order they are sent, you must check the documentation supplied by the device’s vendor.<\/p>\n

 <\/p>\n

Numeric parameters:<\/h4>\n

Firstly, we will present a solution which can be applied only to tags with numeric parameters (N\/B)<\/strong>.\u00a0 To do so, use the driver’s settings window, go to Operations<\/strong> tab, and then select the operation you want to edit. After that, click Edit<\/strong> and check or uncheck the Swap Bytes<\/strong> and Swap Words<\/strong> options, according to the device’s standard. Finally, click OK<\/strong> and confirm the changes. In order to get further information on this configuration, check Byte Order<\/em> at the topic Operations Tab<\/em> in this driver’s documentation.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Syntactic parameters:<\/h4>\n

On the other hand, when the driver uses syntactic parameters (Device and Item)<\/strong>, the configuration takes place at the Item parameter. In order to identify the data type parameter in this option, use the byte order described in the table below. For further information on this configuration, check Byte Order<\/em> at the topic Strings Configuration<\/em> in this driver’s documentation.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
\n

Standard<\/strong><\/p>\n<\/td>\n

Swap Bytes<\/strong><\/td>\nSwap Words<\/strong><\/td>\nSwap DWords<\/strong><\/td>\nOrder<\/strong>
\n64 bits, where by0 is lsb and b7 is msb<\/td>\n<\/tr>\n
b0<\/td>\nmsb<\/td>\n<\/td>\n<\/td>\n<\/td>\nby7 by6 by5 by4 by3 by2 by1 by0<\/td>\n<\/tr>\n
b1<\/td>\nsb<\/td>\nX<\/td>\n<\/td>\n<\/td>\nby6 by7 by4 by5 by2 by3 by0 by1<\/td>\n<\/tr>\n
b2<\/td>\nsw<\/td>\n<\/td>\nX<\/td>\n<\/td>\nby5 by4 by7 by6 by1 by0 by3 by2<\/td>\n<\/tr>\n
b3<\/td>\nsb.sw<\/td>\nX<\/td>\nX<\/td>\n<\/td>\nby4 by5 by6 by7 by0 by1 by2 by3<\/td>\n<\/tr>\n
b4<\/td>\nsdw<\/td>\n<\/td>\n<\/td>\nX<\/td>\nby3 by2 by1 by0 by7 by6 by5 by4<\/td>\n<\/tr>\n
b5<\/td>\nsb.sdw<\/td>\nX<\/td>\n<\/td>\nX<\/td>\nby2 by3 by0 by1 by6 by7 by4 by5<\/td>\n<\/tr>\n
b6<\/td>\nsw.sdw<\/td>\n<\/td>\nX<\/td>\nX<\/td>\nby1 by0 by3 by2 by5 by4 by7 by6<\/td>\n<\/tr>\n
b7<\/td>\nlsb \/ sb.sw.sdw<\/td>\nX<\/td>\nX<\/td>\nX<\/td>\nby0 by1 by2 by3 by4 by5 by6 by7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The table below shows some examples of how to use these values to change byte order in a Holding Registers read or write operation (functions 03 and 16), address 1500 in a device with ID 5, interpreting this value as DOUBLE.<\/p>\n\n\n\n\n\n\n
Item parameter<\/strong><\/td>\nOrder<\/strong><\/td>\n<\/tr>\n
5:hr1500.d
\n5:hr1500.double
\n5:hr1500.d.b0
\n5:hr1500.d.msb<\/td>\n		No bytes inversion<\/td>\n<\/tr>\n
5:hr1500.d.b1
\n5:hr1500.double.b1
\n5:hr1500.double.sb<\/td>\n		Less significant bytes from each Word arrive first<\/td>\n<\/tr>\n
5:hr1500.d.b7
\n5:hr1500.d.lsb
\n5:hr1500.d.sb.sw.sdw<\/td>\n		Less significant bytes arrive first<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/h3>\n

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

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