Our system has a DNP3 client connection to a front-end data concentrator. For our incoming data, the INVALID bits and timestamps are driven by the communication status/validity between that data concentrator and the end device as you would expect. Because the concentrator provides useful INVALID bit data, it is not providing a simple binary point for communication between the concentrator and the end devices.

I am trying to figure out the best way to access the INVALID wordbits from these points (particularly from analogs) for my own purposes; such as triggering email alerts. The source variables are analog quantities with their own unique hi/low alarm limit values, so I can't apply a reaction matrix to check the quality bit unless I make a reaction matrix for every single variable (since I can't mix the reaction matrix INVALID check with variable-specific limit value thresholds).

Another forum post (https://selfservice.copadata.com/portal/en/community/topic/readandsetinvalidbit-qspawndtrs) mentions using the IEC 61131-3 logic engine to pull the INVALID bit out. However, my incoming variables all have spaces in the variable names, so from what I understand (and I might be wrong) I would have to rename them to pull them into the logic engine since that programming language doesn't support spaces in variable names.

Is there a way to pull those variables into the IEC 61131-3 engine without renaming them? Or is there some other way to pull out the INVALID bit that I am missing? Or maybe there is another way of configuring limit values to get arbitrary limit values and metadata-bits driven limit values all attached to a variable?