Emerson Exchange 365

In reply to István Orbán:

You can go to the controller's History Collection to add these parameters. In the History Collecction dialog, add a tag and paste the path from DIagnostics, (Controller/Comm/Ointeg), delete the controller and slash (Comm/Ointeg) and add .cv (Comm/Ointeg.CV) to create a valid path.

Then you assign the Plant Area to which the controller is assigned and add the controller History Collection to the Continuous Historian.

THis way you don't have to create a module. The tag will have the controller's name with the parameter path.

If you build a module, these unbrowseable paths create a configuration warning when you download because the parameter is not known to the database. They will work, but be prepared for the warning. The advantage to using a module is you can manage the naming structure, but you then use a module name that cannot be the same as the controller. You can use a dynamic reference and configure an Action block to configure the $REF parameters on download. This will eliminate the Download warning.

Maybe simple is better and just add history to your controller.

Andre Dicaire

In reply to Andre Dicaire:

Andre, from the original post I am guessing this is an architecture where there is no Continuous Historian enabled in DeltaV, just PI fetching data through OPC. No module is needed as far as I can tell.

Thanks for the replies, I was able to get it to read data by entering the path from the properties and adding .cv. I do have a continuous historian but I plan to use the Pi system to generate email notifications and eventually work orders. Thanks again for the help.