Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No status
Product PI Connectors
Created by Guest
Created on Aug 20, 2022

PI Connector for IEC 60870-5-104: to filter IOAs

Considering the following scenario encountered by the customer: In IEC-104 data source, there might be 500 signals of single point (type=1, M_SP_NA_1) and 1000 measurements of normalized value (type=9, M_ME_NA_1); however the customer would not like to transfer all those signals and measurements into PI system with PI Connector for IEC 60870-5-104. How to configure the connector to filter them (such as filter them by IOA of signals and measurements)? Just like what can be done with filter file in PI OPC UA Connector?
  • Attach files
  • brijesh gohel
    Reply
    |
    Jul 8, 2024

    As i see in IEC104 Connector, there is no Health status tag like OPC DA, OPC UA.

    Example: Device Status, IORate, etc.


  • brijesh gohel
    Reply
    |
    Jul 8, 2024

    1) I have a multiple make Scada like ABB, Siemens, Bhel make Max DNA and the Protocol is IEC104. As i found that all the data source tag has created in PI system Automatically through the Pi connector for IEC104. I need some specific Tags in PI system.

    Example : ASDU Address is 75. There are 5000 Tags available in SCADA for this Address and I want 1000 Tags for PI system. But the problem is all the Tags created by the connector. Also rebuild PI tag after deletion and no manually creation for the PI tag.


    2) PI tag Naming pattern and PI Points attribute can not change. Due to this unable to make PI AF in Template format. As you know, through templatizing we can consume time and develop systematically. Point source, description also can not change.

  • Guest
    Reply
    |
    Aug 20, 2022
    I have an use case from a customer that is collecting data from 50+ components using IEC 60870-5-104 protocol but just a small subset of data is needed from each component. Since the connector does not support filtering through IOA address (only ASDU), there is no way to collect this data without relying on another gateway (and therefore another potential point of failure) that could do a protocol change to something we could create only the necessary tags to it, like an interface. I believe being able to filter the amount of data one wants to receive from the connector is really important as it enables more control over the kind of data customer wants to bring in to PI.