An Application is built to connect to PI via OPC. Is there a way to make PI OPC server to use PI Buffer Subsystem and write to all members of the collective?
Interesting question... Found zero pointers in the documentation.
I can only assume that if you use the Buffer Subsystem, the data will be fanned to all servers in the collective. But that's a weak assumption... I'd suggest to either wait for some other comment or contacting techsupport.
Yes, you can write to a PI Collective using PI OPC DA/HDA Server. If you have buffering enabled correctly then it will write to all members of the collective. One thing to note, the OPC DA 2.05 spec does not support writing values that are not current values.
Please note that the current PI OPC Server only supports DA, not HDA: https://techsupport.osisoft.com/Products/Other-Products/PI-OPC-DA-HDA-Server/
At the moment we are using PI OPC DA server 2010. Buffering is configured correctly, however it seems that it only writes to the primary. Does this only works on version 2015?
Generally speaking, PI Buffer Subsystem is able to buffer all of the main Data Access technologies, including PI API, PISDK and AFSDK; albeit sometimes with some limitations. So pretty much any event writes to the PI Data Archive from our products should be able to be buffered in some way.
That being said, the configuration for buffering changes depending on which Data Access technology is being used. The important distinction here with PI OPC DA Server is that version 2010 will use PI API to write events, whereas PI OPC DA Server 2015+ will use AFSDK to write events.
So given the version that you are using of 2010, it seems like you would want to make sure PI API buffering is enabled correctly. Depending on the version of pibufss, the configuration steps for PI API buffering can be a little different. When you say 'Buffering is configured correctly,' how are you determining this? Please let us know if you require assistance in getting this configured correctly.
Below are the steps in ensuring PI Buffering (v188.8.131.52) is setup
- Created dedicated PI user for this application
- Created Mappings and Trusts for the application as well the servers
- Configured the Buffering via Buffering Manager
1. Configured Buffering Path
2. Selected correct PI collective
3. Configured security method (Mapping or trust)
<Steps above are the steps used when configuring buffering for Interface Node that runs PI OPCInt>
- Set PI OPC DA server to depend on pibufss
As I was about to post screenshots on the buffering configuration and rereading your response, I believe I may have found the culprit. I'll be changing that setting below in the development setup and should that works, I'll move on the production setup.
Retrieving data ...