• Replies 1 reply
  • Subscribers 585 subscribers
  • Views 91 views
  • Users 0 members are here
Options
Related

Reading CitectSCADA Connetor status in Citect runtime for operator information.....

Hemant

Dear All,

We have Redundant citect SCADA servers and Aveva Historian.

For storing citect scada trend data into Aveva Historian, we are using citectSCADA connector V3.0. All configurations were done and system is running fine. 

Now customer has came up with a requirement that they should receive the alert in scada runtime if citectscada connector is not running or connectivty with historian is broken and data is not storing in historian.

kindly help on how we can achieve this.

Warm regards

Hemant

Parents
  • Natively there is no functionality to monitor the status of the connector through Citect Runtime.

    It will have to be an engineered solution.

    An example,for one customer, we monitor a tag in citect that we know changes frequently every 30s and its trended. Then on the Server running the Historian they created an sql stored procedure to check if the value is changing in the historian every 5 minutes . That then sends out an email to a group mailbox if the trended tag has been stale in the historian. This obviously doesn't cater for a notification on Citect Runtime. You could use the above solution and the Citect SQL functions to read back a value from the SQL server and write it to a tag in Citect which you then alarm.

    Not an elegant solution but it works, if you come up with a solution please do share.
Reply
  • Natively there is no functionality to monitor the status of the connector through Citect Runtime.

    It will have to be an engineered solution.

    An example,for one customer, we monitor a tag in citect that we know changes frequently every 30s and its trended. Then on the Server running the Historian they created an sql stored procedure to check if the value is changing in the historian every 5 minutes . That then sends out an email to a group mailbox if the trended tag has been stale in the historian. This obviously doesn't cater for a notification on Citect Runtime. You could use the above solution and the Citect SQL functions to read back a value from the SQL server and write it to a tag in Citect which you then alarm.

    Not an elegant solution but it works, if you come up with a solution please do share.
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.