Regulatory Control
Developing regulatory control in UCOS is similar to using function blocks. But in UCOS, regulatory control schemes are easier to define and read.
UCOS uses a graphical interface to drag and drop regulatory control objects into the project from a library of pre-defined regulatory objects.

The underlying functional characteristics of regulatory devices are based on widely accepted industry standards and, therefore, do not need to be defined.
 Larger Image (20K)
For example, rather than requiring you to program each PID loop controller's functionality, UCOS uses graphical techniques and fill-in-the-blank forms to configure each controller device.
You enter a unique name for the new controller device, the FCU or controller where the logic for the device is solved, the point to which the controller device output is assigned, and a backup point (if applicable).
You can also modify default tag names and definitions for alarms, set points, commands, and other defaulted parameters.
Keep in mind that the reason you don't have to develop any logic for regulatory control devices is that the UCOS FCU or controller already has the logic programmed into it.
Other regulatory devices are configured using a similar procedure. UCOS regulatory devices include:
- Switch
- Transmitter
- Controller
- High Signal Select
- Low Signal Select
- High Signal Limit
- Low Signal Limit
- A user-defined computing device that applies your formula to multiple input points and constants using a range of standard operators and functions
Using these regulatory objects and UCOS device templates, you can build a wide range of regulatory applications.
< Previous 1 2 3
|