1 of 1 people found this helpful
This type of behavior often occurs if a tag that was buffered starts bypassing the buffer (usually due to a configuration issue with the PI Buffer Subsystem).
If you expect this tag to be buffered, let's get a sense of the health of the buffer by running these two commands:
- pibufss -cfg
- pibufss -trace <Point ID of an Interface Tag>
If the tag is currently being buffered, we will want to determine if the buffer subsystem has cached the correct compression settings by running the following command for the same tag as above:
- pibufss -sd <Point ID of an Interface Tag>