Doc PS Rev R 15-71 The module would be configurable to accommodate different types of valves and signalling arrangements
• Different arrangements of position feedback (none, open only, closed only or both open and closed)
• Different opening and closing times
• Handle external fault signals (typical for motorised valves)
• Accommodate different energising states (i.e. energise to open or energise to close)
• Manage different interlock arrangements and signals The module would also determine how the operator could interface with the valve
• Provide manual control (operator can take direct control of the valve)
• Restrict specific manual control functions (this ranges from full control using
simulation to override faults, to no control whatsoever, even restricting the display of faceplate interfaces)
• Allow or restrict the operator from changing operating parameters associated with the valve The PAL will have many of these types of modules in fact this type of modules will makeup the bulk of the PAL software. The
standardmodules within the PAL will be fixed modules, the software within these modules will be written, tested and validated as part of this Project and at only that point will the modules be released for use. Once released, the modules must not be modified or changed
in any unauthorised way, to do so would invalidate the software.
16-71 Doc PS Rev R The
standardmodules will coverall aspects of a control system, at a minimum this will include the following
• System (internal) signal generation
•
Instrumentation • Safety and interlock systems
• Sequence control
• Device handling (valves, drives, control loops c)
• Alarm handling
• Communications There will also be various
standardsubroutines that, while not associated with any
particular piece of equipment, will provide common software functions (e.g. timing functions, conversions c) that will be available to all modules within the controller. The different options available to a
standardmodule should be selectable by the use of particular parameters passed to the module that either activate or deactivate specific modes of operation or pass configuration values to the module (e.g. opening and closing times of a valve, operating range of an instrument. Common arrangements and mechanisms for creating and organising data structures,
passing data, and the numbering and naming conventions for modules and variables will be established to give the software a common look and feel
Share with your friends: