The datatype WSTRING of the MODRTU32 Driver does consider the Byte order for STRING Option in the Settings tab of the MODRTU32 Driver. This Option (Byte order for STRING) should only be considered by variables of type STRING but not by variables of type WSTRING.
Summary
The datatype WSTRING of the MODRTU32 driver gets decoded wrong. The Setting Byte order for STRING in the Settings Tab of the MODRTU32 driver affects the representation of a WSTRING variable. As a result, when having Modbus Standard (Big-Endian) selected, variables of type STRING are displayed correctly in the zenon runtime but variables of type WSTRING are displayed wrongly (inverted Byte order). When having PC-Format selected variables of type WSTRING are displayed correctly but variables of type STRING are displayed wrongly.
Description
The datatype WSTRING of the MODRTU32 driver gets decoded wrong. The Setting Byte order for STRING in the Settings Tab of the MODRTU32 driver affects the representation of a WSTRING variable. As a result, when having Modbus Standard (Big-Endian) selected, variables of type STRING are displayed correctly in the zenon runtime but variables of type WSTRING are displayed wrongly (inverted Byte order). When having PC-Format selected variables of type WSTRING are displayed correctly but variables of type STRING are displayed wrongly.
Solution
Reading and writing of a variable of type WSTRING does no longer consider the option Byte order for STRING
Issue Number: 36190
Fixed on Date: 25.3.2016
Versions: 7.20 0 BUILD 26944