Professional Documents
Culture Documents
November 13-17
November 20-24
Description This lesson will discuss the concepts of a system based on a computer connected to
of the sensors and/or actuators in a plant for the purpose of control, protection, or monitoring
Lesson (includes various types of computers, programmable logic controllers, peripherals,
interconnect systems, instrument distributed control system controllers, and other
associated equipment).
Learning Outcomes
Intended Students should be able to meet the following intended learning outcomes:
Learning ● To familiarize the students in the components, involve in the Programmable
Outcomes Electronic Systems (PESs).
● To know the operations of a programmable electronic systems and its
functions.
Targets/ At the end of the lesson, students should be able to:
Objectives ● know the components of PESs
● familiarization on the concepts and ideas of each component
● understand the operations of PESs
The online discussion will happen on October 30- November 3, November 6-10,
November 13-17, and November 20-24, 2023 from 8:30-9:30AM.
(For further instructions, refer to your Google Classroom and see the
schedule of activities for this module)
Note: The insight that you will post on online discussion forum using Learning Management
System (LMS) will receive additional scores in class participation.
Lecture Guide
room or within a central computer. The DCS concept increases reliability and
reduces installation costs by localizing control functions near the process plant,
with remote monitoring and supervision.
Distributed control systems first emerged in large, high value, safety critical
process industries, and were attractive because the DCS manufacturer would
supply both the local control level and central supervisory equipment as an
integrated package, thus reducing design integration risk. Today the
functionality of SCADA and DCS systems are very similar, but DCS tends to be
used on large continuous process plants where high reliability and security is
important, and the control room is not geographically remote.
Structure
The key attribute of a DCS is its reliability due to the distribution of the control
processing around nodes in the system. This mitigates a single processor failure.
If a processor fails, it will only affect one section of the plant process, as opposed
to a failure of a central computer which would affect the whole process. This
distribution of computing power local to the field Input/Output (I/O) field
connection racks also ensures fast controller processing times by removing
possible network and central processing delays.
The accompanying diagram is a general model which shows functional
manufacturing levels using computerized control.
● Level 0 contains the field devices such as flow and temperature sensors, and
final control elements, such as control valves
● Level 1 contains the industrialized Input/Output (I/O) modules, and their
associated distributed electronic processors.
● Level 2 contains the supervisory computers, which collect information from
processor nodes on the system, and provide the operator control screens.
● Level 3 is the production control level, which does not directly control the
process, but is concerned with monitoring production and monitoring
targets
● Level 4 is the production scheduling level.
Levels 1 and 2 are the functional levels of a traditional DCS, in which all
equipment are part of an integrated system from a single manufacturer.
Levels 3 and 4 are not strictly process control in the traditional sense, but where
production control and scheduling takes place.
Typical Applications
● Chemical plants
● Petrochemical (oil) and refineries
● Pulp and Paper Mills (see also: quality control system QCS)
● Boiler controls and power plant systems
● Nuclear power plants
● Environmental control systems
● Water management systems
● Water treatment plants
● Sewage treatment plants
● Food and food processing
● Agro chemical and fertilizer
● Metal and mines
● Automobile manufacturing
● Metallurgical process plants
● Pharmaceutical manufacturing
● Sugar refining plants
● Agriculture Applications
The call–return model is illustrated in Figure 1. The main program can call
Routines 1, 2 and 3; Routine 1 can call Routines 1.1 or 1.2; Routine 3 can call
Routines 3.1 or 3.2; and so on. This is a model of the program dynamics. It is not
a structural model; there is no need for Routine 1.1, for example, to be part of
Routine 1.
This call–return model may be used at the module level to control functions or
objects. Subroutines in a programming language that are called by other
subroutines are naturally functional. However, in many object-oriented systems,
operations on objects (methods) are implemented as procedures or functions.
For example, when a Java object requests a service from another object, it does
so by calling an associated method.
The rigid and restricted nature of this model is both a strength and a weakness.
It is a strength because it is relatively simple to analyze control flows and work
out how the system will respond to inputs. It is a weakness because exceptions
to normal operation are awkward to handle.
How much to centralize or distribute really has two aspects to sort out: the
control itself and the I/O subsystems. When establishing your design, start with
the overall control system and then work down to the I/O. Before discussing the
particulars, let's start with some basics.
With this basic working definition of centralized and distributed control, we can
examine the same concept as it applies to I/O systems. A highly centralized I/O
system is characterized by concentrated I/O hardware in a single entity, with
network or hardwired connections extending from that location. A highly
distributed I/O system has the I/O hardware distributed across many
operational and physical areas, with localized network or hardwired
connections extending from these remote locations.
When examined closely, most systems of any substance are generally not
completely centralized or distributed in terms of either control or I/O. While the
control design imposes some limits on the degree in which you can centralize or
distribute I/O systems, these limits could be narrow or quite wide. As system
designers, we need to strike the right balance on this spectrum. Let's examine
some of the factors that can affect how we put this all together.
Relay
INTRODUCTION
PRINCIPLE OF OPERATION
Current flowing through the coil of the relay creates a magnetic field which
attracts a lever and changes the switch contacts. The coil current can be on or off
so relays have two switch positions and they are double throw (changeover)
switches.
THEORY
Relays allow one circuit to switch a second circuit which can be completely
separate from the first. For example a low voltage battery circuit can
use a relay to switch a 230V AC mains circuit. There is no electrical connection
inside the relay between the two circuits; the link is magnetic and mechanical.
The coil of a relay passes a relatively large current, typically 30mA for a 12V
relay, but it can be as much as 100mA for relays designed to operate from lower
voltages. Most ICs (chips) cannot provide this current and a transistor is usually
used to amplify the small IC current to the larger value required for the relay
coil.
The relay’s switch connections are usually labeled COM, NC and NO:
● COM = Common, always connect to this; it is the moving part of the switch.
● NC = Normally Closed, COM is connected to this when the relay coil is off
● NO = Normally Open, COM is connected to this when the relay coil is on
● Connect to COM and NO if you want the switched circuit to be on when the relay
coil is on
● Connect to COM and NC if you want the switched circuit to be on when the relay
coil is off
Choosing a relay
If you are choosing a relay for an existing PCB you will need to ensure that its
dimensions and pin arrangement
are suitable. You should find this information in the supplier’s catalogue.
2. Coil voltage
The relay’s coil voltage rating and resistance must suit the circuit powering the
relay coil. Many relays have a coil rated for a 12V supply but 5V and 24V relays
are also readily available. Some relays operate perfectly well with a supply
voltage which is a little lower than their rated value.
3. Coil resistance
The circuit must be able to supply the current required by the relay coil. You can
use Ohm’s law to calculate the current: Relay coil current =supply voltage coil
resistance
For example: A 12V supply relay with a coil resistance of 400 passes a current of
30mA. This is OK for a 555timer IC (maximum output current 200mA), but it is
too much for most ICs and they will require a transistor to amplify the current.
Advantages of relays:
● Relays can switch AC and DC, transistors can only switch DC.
● Relays can switch high voltages, transistors cannot.
● Relays are a better choice for switching large currents (> 5A).
● Relays can switch many contacts at once.
Disadvantages of relays:
Annunciator
Process alarm switches may be used to trigger a special type of indicator device
known as an annunciator. An annunciator is an array of indicator lights and
associated circuitry designed to secure a human operator’s attention by blinking
and sounding an audible buzzer when a process changes into an abnormal state.
The alarm state may be then “acknowledged” by an operator pushing a button,
causing the alarm light to remain on (solid) rather than blink, and silencing the
buzzer. The indicator light does not turn off until the actual alarm condition (the
process alarm) has returned to its regular state.
This photograph shows an annunciator located on a control panel for a large
engine-driven pump. Each white plastic square with writing on it is a translucent
pane covering a small light bulb. When an alarm condition occurs, the respective
light bulb flashes, causing the translucent white plastic to glow, highlighting to
the operator which alarm is active:
Note the two pushbutton switches below labeled “Test” and “Acknowledge.”
Pressing the “Acknowledge” button will silence the audible buzzer and also turn
any blinking alarm light into a steady (solid) alarm light until the alarm condition
clears, at which time the light turns off completely. Pressing the “Test” button
turns all alarm lights on, to ensure all light bulbs are still functional.
Opening the front panel of this annunciator reveals modular relay units
controlling the blinking and acknowledgment latch functions, one for each alarm
light:
A simple logic gate circuit illustrates the acknowledgment latching feature (here
implemented by an S-R latch circuit) common to all process alarm annunciators:
Your PLC or PAC platform may also affect the choice of programming languages,
as not all automation vendors provide programming software that is fully
IEC61131-3 compatible. In fact, most of the non-European vendors do not offer
this functionality, or only have a very limited spectrum of options, such as
Ladder and SFC.
* IEC 61131-3 is the third part (of 10) of the open international standard IEC
61131 for programmable logic controllers, and was first published in December
1993 by the IEC. The current (third) edition was published in February 2013. Part
3 of IEC 61131 deals with basic software architecture and programming
languages of the control program within PLC.
Another consideration is that not all PLCs are capable of running the various IEC
languages due to lack of memory or processor speed. This tends to be the case
with many micro PLCs.
While many programmers are locked into a customer specification, if they have
the freedom to choose a hardware platform, they should decide which language
or languages will work best for the application, then select the hardware and
software that support it.
Ladder Diagram
Ladder Diagram (LD or simply Ladder) is probably the most widely used
controller programming language. Invented to replace hardwired relay-based
control systems, Ladder programming is used in probably 95% of all
applications. Visually, this language resembles a series of control circuits, with a
series of inputs needing to be “made” or “true” in order to activate one or more
outputs.
It’s also easy to start writing a program in Ladder. With just a basic outline of
input and output signals, one can start churning out code. Most other IEC
languages require more preparation, such as flowcharting of all potential
process flows. Finally, most Ladder implementations allow a program to be
organized into folders or subprograms that can be downloaded to the PLC,
allowing easy program segmentation.
As the complexity of PLC functionality has grown, however, Ladder has been
challenged to meet these advances and still maintain the paradigm of easy
visualization and understanding. Functions, such as PID loops, trigonometry,
and data analysis, now required in many control applications can be difficult to
implement. Another challenge is that as program size grows, the ladder can
become very difficult to read and interpret unless it’s extensively documented.
Finally, implementing full processes in Ladder can be daunting– picture a ladder
rung with an output used in several phases of a process with many input
conditions attempting to control exactly when that output needs to turn on.
In many ways, this graphical language resembles a wiring diagram even more so
than Ladder code. With FBD, the blocks are “wired” together into a sequence
that’s easy to follow. It uses the same instructions as Ladder, but visually is more
understandable to a viewer who is not versed in relay logic. The major advantage
is that programs written in FBD tend to be easy to follow– just follow the path!
However, FBD is not ideal for large programs using special I/O and functions.
The large amount of screen space required can quickly make a program
unwieldy if it reaches any substantial size. Also, writing a program in FBD
requires more upfront preparation to understand the program and how it will
flow before any code is written, since it can be difficult to make corrections later.
On the downside, this style of programming is not suitable for every application,
as the structure it forces on a program could add unneeded complexity. A large
amount of time must be spent up front preparing and planning before any
programming is attempted, or the charts can become unwieldy and difficult to
follow. The overhead required for this type of program causes it to execute
slower than the other languages.
Instruction List
IL can make entering complex functions, such as PID loops and complex
mathematical computations, a struggle. IL does not lend itself well to any form
of structured programming, such as state programming or step ladder, further
limiting its usefulness for implementing large programs. It is also arguable that
the advantages of speed and compactness are less relevant, given the processing
speeds of modern PLCs and the large amounts of memory available.
Structured Text
With its IF…THEN loops, CASE selectors, and lines ending in semicolons,
Structured Text (ST) closely resembles a high-level computer programming
language such as Pascal and C. The aforementioned Control Engineering survey
indicated that of all the IEC61131-defined programming languages, ST has seen
the greatest increase in adoption.
Among IEC languages, ST perhaps best embraces the growing complexity of PLC
programming, such as the process control functions involved in plastics or
chemical manufacturing. Trigonometry, calculus, and data analysis can be
implemented far more easily than in Ladder or IL. Decision loops and pointers
(variables used to do indirect addressing) allow for a more compact program
implementation than can be achieved in Ladder. The flexible ST editor that is
common in most programming packages makes it easy to insert comments
throughout a program, and to use indents and line spacing to emphasize related
sections of code. This makes the task of structuring a complex program easier.
ST text-based, non-graphical nature, which is similar to IL, also runs much faster
than Ladder. An additional ST benefit is that it comes closer than most of the
other languages in achieving the transferability goals of the IEC61131 standard,
emancipating a programmer from the hardware platform.
As a result, control engineers tend to use ST “behind the scenes.” For example,
IEC 61131 allows a programmer to build his or her own functions in one
language, then insert them as sub-programs in another language. With this
option, programmers often encapsulate an ST program inside an instruction,
which is then embedded in a Ladder program.
OPERATOR INTERFACE
1. Graphics
2. Alarms
3. Trends
4. Reports
Engaging Activities
Performance Tasks
PT 1
Directions: After the discussion, discuss your overall safety lifecycle diagram.
______________________________________________________________________________________________________________________
______________________________________________________________________________________________________________________
______________________________________________________________________________________________________________________
______________________________________________________________________________________________________________________
______________________________________________________________________________________________________________________
Learning Resources
Bolton. Instrumentation and Control Systems. Elsevier Science and Technology Books. 2004
Nise. Control System 6th Edition. John Wiley & Sons Inc. 2011
Ogata. Modern Control Engineering 3rd Edition.
Dunn. Fundamental of Industrial Instrumentation and Process Control. McGraw-Hill Co. 2005
https://www.aiche.org/ccps/resources/glossary/process-safety-glossary/programmable-
electronic-system-pes-
0#:~:text=A%20system%20based%20on%20a,%2C%20and%20other%20associated
%20equipment).
https://en.wikipedia.org/wiki/Distributed_control_system
https://ifs.host.cs.st-
andrews.ac.uk/Books/SE9/Web/Architecture/ArchPatterns/CentralControl.html
https://www.controleng.com/articles/choosing-between-centralized-and-distributed-control-
system-designs/
https://automationforum.co/instrumentation-interview-question-what-is-a-controller-area-of-
application/
https://circuitglobe.com/recording-instrument.html
https://automationforum.co/basics-of-relays/
https://instrumentationtools.com/annunciator/
https://www.controleng.com/articles/speaking-in-tongues-understanding-the-iec-61131-3-
programming-languages/
https://en.wikipedia.org/wiki/Graphics
https://en.wikipedia.org/wiki/Alarm_device
Prepared by: