• Replies 5 replies
  • Subscribers 584 subscribers
  • Views 222 views
  • Users 0 members are here
Options
Related

Long Alarm Filters

Matthew

Hi.

The citect help files state:

If a requested filter is too complex (for example, it contains too many conditions or too many nested brackets), the filter is cleared (no filter is used). The hardware alarm "Too many alarms in filters" is generated on the client components, and a tracelog error message is logged.

I have a large (1000's of instances) equipment hierarchy. I have added information to the custom fields in equip.dbf that I'd like to use to generate a list of equipment to filter an alarm list on. Something like:

EquipBrowseOpen("CUSTOM1=xyz","NAME")

Then iterate through each record and append each entry to an alarm filter.

Is there a way to filter an alarm list on 10/100/1000/10000 equipment instances without running into a "too complicated alarm filter" error. Users will often filter the alarm list based of equipment X.Y.Z and all it's children, but sometimes they need to filter the alarm list in way that is irrelevant to how the equipment hierarchy is structured and will just end up being a very long list of equipment in different parts of the hierarchy.

Parents
  • The whole point of Equipment is to decrease manual actions needed on your tag and alarm databases, if done right.

    In the definition of your Equipment Types, just link the equipment field you'd like to use to one of the spare custom fields of your alarms, following these steps in the Equipment Editor:

    1) Create or modify an Equipment Type
    2) Add or modify an Equipment Item (select Digital Alarm as type, for example)
    3) Add a Field (for example CUSTOM8)
    4) Enter {equipment.LOCATION} to use the location field of your equipment instance
    5) Repeat this for all alarm definitions of all equipment types you have.

    When generating tags and alarms using the Update Equipment command, every CUSTOM8-field of your digital alarms will be filled with the ID you provided in your equipment definition. No manual copy-paste needed.
Reply
  • The whole point of Equipment is to decrease manual actions needed on your tag and alarm databases, if done right.

    In the definition of your Equipment Types, just link the equipment field you'd like to use to one of the spare custom fields of your alarms, following these steps in the Equipment Editor:

    1) Create or modify an Equipment Type
    2) Add or modify an Equipment Item (select Digital Alarm as type, for example)
    3) Add a Field (for example CUSTOM8)
    4) Enter {equipment.LOCATION} to use the location field of your equipment instance
    5) Repeat this for all alarm definitions of all equipment types you have.

    When generating tags and alarms using the Update Equipment command, every CUSTOM8-field of your digital alarms will be filled with the ID you provided in your equipment definition. No manual copy-paste needed.
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.