Simplex 4007ES Panels, Руководство программиста

Страница: 86 / 168

9-2
4007ES Panel Programmer Manual ( 579-1167)
Custom Control
Role of Lists and
Pseudo Points Using lists and pseudo points (both user-defined and system) improves the efficiency of
Custom Control equations and makes it possible for a range of facility-specific operations to be
programmed.
• Digital Pseudo Points . Digital pseudo points store a value of ON or OFF.
• System Digital Pseudo Points , with these you can track when common actions (such as
a system reset) have occurred and activate facility-specific outputs as necessary.
• User-defined digital pseudo points can be used to signal that a specific event has
occurred. (For example, turn on a user-defined pseudo point to indicate when a water
tank is full.)
• Analog Pseudo Points . Analog Pseudo Points store analog values that can be used in
Custom Control equations.
• System Analog Pseudo Points store analog values (the number 128, for example), and
can be used as a threshold value within a Custom Control equation. (For example,
perform some output action when the value of the Number of System Troubles analog
pseudo point (A2) reaches a specific value.)
• User Analog Pseudo Points store user-defined analog values. The exact function of an
analog user pseudo depends on its point type—counter, timer, or analog value.
• List Pseudo Points . With User-Defined Lists you can refer to a specific group of
devices using a single reference. For example, creating a user-defined list called “Floor
1 Pull Stations,” and populating it with only the pull stations from floor 1 provides a
way to monitor all of the pull stations on the floor without writing an equation for each
pull station.
Anatomy of a
Custom Control
Equation As mentioned above, every Custom Control equation has an input side, consisting of input
statements, and an output side, consisting of output statements.
Input Statements are typically used to monitor the status of a point or list, or perform an
action such as delay, cycle, compare two values, or save/recall values. Every input statement
begins with an Opcode, which is the action that the input is performing (for example, monitor
point status, recall memory register). The Custom Control wizard then displays a series of
opcode-specific dialogs. For example if the Opcode is Point Status, the dialogs prompt the user
for Qualifier about the condition (such as, alarm, trouble) and point being monitored.
Figure 9-1. Input Statement Example
Output Statements are the actions that occur only when the input side of the equation is true.
Every output statement begins with an Opcode, which is the general action that occurs when
the input side is true. The opcode is followed by a series of opcode-specific dialogs, with which
you can specify exactly how the selected opcode functions. For example, if you are using the
Set Opcode, the wizard displays a series of dialogs, with which you can specify a qualifier (for
example, on, off) and the point (a signal, for example) on which you want the output action to
execute.
Figure 9-2. Output Statement Example
Continued on next page