Best Way to Use INVALID Bit for

Best Way to Use INVALID Bit for

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?

    Disclaimer

    This document governs the use of our Community Forum. By registering and using the platform, you accept these conditions.

    The COPA-DATA Community Forum serves to encourage the exchange of information and experience about the zenon software between forum users respectively zenon users.

    Please mind that any published information on the Community Forum is the subjective opinion and view based on the experience and the level of knowledge of the author. COPA-DATA does not overtake any responsibility for the content and the accuracy of the shared information.

    Users of the Community Forum are encouraged to share only well-founded experiences and to point out any risks associated with the implementation of proposed solutions to problems. COPA-DATA at its absolute discretion, reserves the right to moderate the forum. In this connection COPA-DATA may remove any information containing false facts, potentially dangerous solutions, bad language or content that may insult, degrade or discriminate others. COPA-DATA may block a non-complying user from forum access if the user violated this provision.

    COPA-DATA reserves the right to change this document from time to time at own discretion.


    Ing. Punzenberger COPA-DATA GmbH
    Karolingerstraße 7b · 5020 Salzburg · Austria
    www.copadata.com