140 | PGC5000 GEN 2 | 892 J006 MNAH
10 PGC5000A used as a Continuous Analyzer
Controller (CAC) replacement
This chapter is for users that have purchased the PGC5000A controller to be used as a replacement
for the ABB CAC. If not familiar with the basic terms and function of a CAC, review the CAC manual
provided with the CAC 3220/2220-OPS. Contact ABB Technical Support for these manuals.
10.1 Theory of operation
The PGC5000A will be configured to run in simulation mode which allows it to be configured to run
multiple schedules with no oven attached. Each schedule will function like the control program in the
CAC, acting as a logical control to a third-party instrument that is providing analog and digital I/O
signals to the schedule. This allows each schedule to report individually and have the data validated
by schedule, giving each instrument a logical representation in the system.
Where possible, instrument tag names in the system should be used as tag names in the PGC5000A,
allowing the user to quickly associate the schedule name with the instrument that is being monitored
by the schedule.
There are some functions in the legacy CAC product that the PGC5000A does not do. The following list
indicates the main items which could have a possible impact when replacing the existing CAC.
⎯ The PGC5000A cannot sample and report I/O signals faster than 60 seconds.
⎯ The PGC5000A must use scripting to link more than one Digital input signal to an indicator,
which in turn can be used to invalidate collected analog data. The first Digital Input signal can
be assigned to the maintenance alarm in the PGC5000A, which via the schedule, can be used
to invalidate data. Any digital inputs after this will have to be read via a script, which will also
be used to set the indicators.
⎯ The PGC5000A can only run 12 schedules, as opposed to the CAC which can run 16 control
programs.
⎯ All digital output from the PGC5000A must be configured as auxiliary valves.
⎯ The PGC5000A does not have the zero span calibration feature.
⎯ The PGC5000A can be configured to perform a benchmark function. However, the PGC5000A
does not have the same “Step to bench” TCF as the existing CAC. Instead, a valve function will
be used.
⎯ The original CAC could be configured with up to 64 digital inputs and outputs; the PGC5000A
will support 32 of each.
10.2 Recommended naming conventions in the PGC5000A
To allow for a logical conversion from the CAC to the PGC5000A, the following naming conventions are
recommended in the PGC5000A.
⎯ Controller name will be the CAC tag name. Periods are replaced with a dash “–“. For example:
CAC0-1.
⎯ Schedule name will be the incoming tag of the connected instrument. For example: XAT007.
The schedule in the PGC5000A is the logical equivalent of the control program in the CAC.
⎯ Analysis name will be the tag of the connected instrument with ANAL_ appended. For example:
ANAL_XAT007. The Analysis in the PGC5000A is the logical equivalent of the time coded
function table in the CAC.
⎯ Stream name will be the control program number. For example: Control Program 1. This will
allow the user to relate the control program to the physical output from the home screen of the
PGC5000A.
⎯ Component name is the instrument name with COMP appended. For example: COMPXAT007.
⎯ Method name is to be Method appended to the instrument name. For example: Method
XAT007.
⎯ Sequence name is to be Sequence appended to the instrument name. For example: Sequence
XAT007.
10.3 Recommended analysis setup
The following shows a typical configuration to allow for reporting of the result read from third party
instruments.
The analysis is to contain:
⎯ 10 seconds a stream step
⎯ 15 seconds valve on
⎯ 20 seconds valve off
To Next Page
Loading...
