Plain result-table search
Search symbolic paths, comments, DB numbers, absolute addresses, or offsets with case-insensitive contains matching. Search changes the view only, not results or rules.
Manual
Search and Rule Matching
Search symbolic paths, comments, DB numbers, absolute addresses, or offsets with case-insensitive contains matching. Search changes the view only, not results or rules.
Match: Search and Rule Matching
Result-table search and Rule Center use different matchers: the table supports plain contains search plus `%`; Rule Center name rules support plain terms, `*`, `%`, and `?`.Result-table % wildcard search
When the search text contains %, % means any number of characters. Expressions can match multiple ordered fragments or constrain both prefix and suffix. In real projects, use the site's standard area code, device code, function name, or signal suffix.
Rule Center wildcard support
Keep, exclude, alarm, and trend rules share one matcher. Separate rules with new lines, commas ,, or semicolons ;. Plain terms use contains matching; %, *, or ? preserve the written boundaries.
Wildcard examples
Replace the example placeholders with verified project naming fragments.
NAME_TOKEN
%ALARM_TOKEN%
PREFIX%SUFFIX
*_VALUE_SUFFIX
?1_NAME_TOKENWildcard boundaries
% and * match any number of characters, including zero; ? matches one. NAME_TOKEN% matches a prefix, %NAME_TOKEN a suffix, and %NAME_TOKEN% any text containing NAME_TOKEN.
What rules match
Name rules match the display name and normalized code joined by a space, or the available field when one is empty. Wildcard start and end boundaries apply to that combined text. Comments and absolute-address columns are excluded; sample matching and nonmatching rows after applying rules.
Recommended rule style
Start with a broad keep rule to define the main scope, then use exclude rules for backup, history, and temporary objects. Prefer stable naming fragments instead of short incidental text.
Separators and whitespace
Rule Center splits name rules on new lines, commas, and semicolons, then ignores empty or surrounding whitespace. Keep one stable area, device, function, or signal-suffix concept in each rule.
Rule priority and classification
Keep rules define the candidate set and exclude rules have the final say on whether a point remains. Alarm and trend name rules change only classification flags, not PLC data types; their exclude rules clear a previously assigned alarm or trend flag.