Overcoming I/O Timeout Constraints in PI ProcessBook Displays

When working with OSIsoft PI and AF, you might encounter specific scenarios where traditional methods to configure attributes don't behave as expected. One such scenario involves creating a multi-state display in PI ProcessBook where an attribute should change color to indicate an "I/O Timeout". If you find yourself in a situation where the normal parameter constraints are stuck at invalid values, here's a practical solution and a helpful workaround.

Scenario Challenge

You have an attribute in PI ProcessBook where you'd like to change the color of the display to red upon encountering an "I/O Timeout". However, when attempting to set the states, you find that the constraints remain locked at values that don't make logical sense and display as "invalid".

Implementing a String-Based Solution

What can you do when the numerical limits won't adjust as needed? The answer is to bypass them altogether by utilizing a text-based condition. You can configure your system to evaluate the string content of an attribute. By checking if the attribute's string contains "I/O Timeout", you can intuitively highlight this issue with a red display. Here's how:

1. Access the Attribute Settings

   • Open the desired display in PI ProcessBook.
   • Navigate to the attribute or data item you want to monitor.

2. **Configure a Multi-State

   • Choose the multi-state symbol for the attribute.
   • Instead of numeric constraints, select an evaluation string mode.
   • Define a rule such as: If symbol contains "I/O Timeout" then color is red.

Utilizing AF for a Temporary Switch

What if the "I/O Timeout" indicative strings or values are not readily accessible due to data integrity issues? A clever workaround involves switching the data source temporarily.

1. Change the Data Manually

   • In PI System Asset Framework (AF), change the data source of the troublesome attribute temporarily to one without errors.
   • Carry out necessary edits in PI ProcessBook while this alternative source is active.

2. Edit in ProcessBook

   • Using this temporary data source, perform your multi-state configurations or other adjustments required.

3. Revert the Changes

   • Once complete, revert the data source in AF to its original configuration to resume operations.
   • Using the same user account in AF and ProcessBook ensures changes hold without formal check-ins, simplifying testing.

This method allows you to surmount invalid value issues by utilizing string conditions and carefully managing data integrations – all without committing errors during final deployment.

Conclusion

Handling tricky display and attribute issues within OSIsoft PI can be a unique challenge. With a blend of string-based checks and AF configurations, you can artfully illustrate and manage critical states such as "I/O Timeout". Embracing workarounds like temporary data switches empowers users to align operational displays effectively without being gated by initial design constraints.

Remember, staying flexible and strategic will often stand as key to overcoming digital system challenges.