• Replies 5 replies
  • Subscribers 584 subscribers
  • Views 223 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
  • If this were a new project then yes. But it's an old brownfields upgrade and so we're not using equipment types. There is too much variability in tags and alarms between equipment. We're just trying to use the equipment hierarchy for alarm filtering and counting. Which is fine for 'filter on this equipment and it's children in the hierarchy', not so fine for 'filter on all equipment in e.g. location X'. It is a significant reduction in usefulness for an equipment hierarchy - object orientated model.
Reply
  • If this were a new project then yes. But it's an old brownfields upgrade and so we're not using equipment types. There is too much variability in tags and alarms between equipment. We're just trying to use the equipment hierarchy for alarm filtering and counting. Which is fine for 'filter on this equipment and it's children in the hierarchy', not so fine for 'filter on all equipment in e.g. location X'. It is a significant reduction in usefulness for an equipment hierarchy - object orientated model.
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.