Access bits within integers

FactoryTalk Linx Gateway allows clients to access bits within integers, including OPC UA, MQTT, OPC DA, DDE, and Excel RTD interfaces. If the tag is from Processor and Unsolicited Message shortcuts, you can access and change specific bit values within these data types:
  • SINT
  • INT
  • DINT
  • LINT
  • USINT
  • UINT
  • UDINT
  • ULINT
When an OPC UA client browses the namespace, the integer tags will be visible but the individual bits within integers will not be included in the namespace. You must append a period and the bit’s number to the tag ID, for example, TagA.0, in which “0” means the first bit of the tag. A reference to a non-existing bit would result in FactoryTalk Linx Gateway returning an error for the bit, and the error code is “BadConfigurationError”. Modifying the bit value in the UA client will cause the integer tag value to change correspondingly in the destination. UA tag list and custom namespace supports the format TagA.0 only, but the format TagA/0 or others are not valid.
TIP: When the tag’s data type in the
Custom UA Namespace
 editor does not match that in the controller, this function is not available. For example, a bit is not accessible when a tag’s data type is INT in the
Custom UA Namespace
 editor, while its data type in the controller is DINT.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal