Skip to content
  • There are no suggestions because the search field is empty.

NIO interface issue in 5.4 (default data type handling)

When using the NIO interface, dynamic item references that do NOT include the "@datatype" specifier do not fall back to their default type as they did in earlier releases. The type applied for an item that should default to 'Word' appears to be a 64 bit value instead. This causes significant problems with reading and writing the correct data (user thinks they're reading K1 as a word but are reading as a 64 bit so they are reading/writing to K1-K4…not good).

Channel1.Device1.K1 (this item reference to a SimDemo item would end up using a 64 bit type instead of 16bit)

:::::::::::::::::::::::::::::::::::::::

This issue only affects:

(customers using the 5.4 release) AND (the NIO interface) AND (dynamic item references without the @datatype reference)