Most people build the status tag as an integer. For that reason (and to keep things simple) we didn't have you build a digital state set.
Building a state of "4" may be a bad idea as the number four can occur commonly in legit data. I'll explain later why this could be bad.
If you built the pump status points as digital types, you would have needed to supply the name of a digital state set. Lets create a new custom digital state set called PumpStatus. the states (0-4 order) might be (0) LowLow Speed, (1) Low Speed, (2) Normal, (3) High Speed, (4) HighHigh Speed. Digital Sets must be created before you can build digital points which will use them. For each pump status point, you would enter the digital set name "PumpStatus".
You didn't tell us which digital state set you added "4" to, but it was probably the System state set. The system State set is where PI System gets status codes for various things including alarms, SQC, various bad data statuses, and more. In the System state set: The states in the range of 193 to 320+ are reserved and set by the system, so don't edit or change or add states in this range of records. States in the range of 1-192, PI Admins may add status codes appropriate to their needs - but these should not be states or status codes for digital points. State 0 in the system state table must not be changed or cleared or removed.
If you build a digital state set like I propose, it might look something like this:
Adding numerical values as digital states to the System state table or any other digital state set may be a bad idea. Why? Because of the way new data are parsed and classified during storage to snapshot and archive.
1) Every PI Point can have either a value or a status. Status values are recorded as digital states.
2) Since it is possible for any PI point to have a status value, the PI system tests incoming data to see if the status is good or bad.
a) on finding a bad status, the PI system records the status to the archive instead of the value.
b) If the status is good, the value is stored.
A digital state like "4" can create an ambiguous situation. Is the number four a status or is it a number (integer or float) which is a good value to store in PI system?
The digital state was for one we created in the lesson called pump status.
Sent from my Android phone using TouchDown (www.symantec.com)
Ok I know the issue, the video “Create PI Points in PI System Explorer using AF Templates” created a digital state called PumpStatus
0 = Slow 1 = Fast 2 = Yay and 3 =Nay.
Since I did the AF template video first, I did not pay attention to the digital set the second time.
All fixed thanks
Scott D. Smith | Center of Excellence | OSIsoft | Office 281-677-1053 | Cell 979-220-25135