12.05.2014 Views

Automating Manufacturing Systems - Process Control and ...

Automating Manufacturing Systems - Process Control and ...

Automating Manufacturing Systems - Process Control and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

plc software - 32.3<br />

32.2.1 Troubleshooting<br />

After a system is in operation it will eventually fail. When a failure occurs it is<br />

important to be able to identify <strong>and</strong> solve problems quickly. The following list of steps<br />

will help track down errors in a PLC system.<br />

1. Look at the process <strong>and</strong> see if it is in a normal state. i.e. no jammed actuators,<br />

broken parts, etc. If there are visible problems, fix them <strong>and</strong> restart the process.<br />

2. Look at the PLC to see which error lights are on. Each PLC vendor will provide<br />

documents that indicate which problems correspond to the error lights. Common<br />

error lights are given below. If any off the warning lights are on, look for<br />

electrical supply problems to the PLC.<br />

HALT - something has stopped the CPU<br />

RUN - the PLC thinks it is OK (<strong>and</strong> probably is)<br />

ERROR - a physical problem has occurred with the PLC<br />

3. Check indicator lights on I/O cards, see if they match the system. i.e., look at<br />

sensors that are on/off, <strong>and</strong> actuators on/off, check to see that the lights on the<br />

PLC I/O cards agree. If any of the light disagree with the physical reality, then<br />

interface electronics/mechanics need inspection.<br />

4. Consult the manuals, or use software if available. If no obvious problems exist<br />

the problem is not simple, <strong>and</strong> requires a technically skilled approach.<br />

5. If all else fails call the vendor (or the contractor) for help.<br />

32.2.2 Forcing<br />

Most PLCs will allow a user to force inputs <strong>and</strong> outputs. This means that they can<br />

be turned on, regardless of the physical inputs <strong>and</strong> program results. This can be convenient<br />

for debugging programs, <strong>and</strong>, it makes it easy to break <strong>and</strong> destroy things! When forces<br />

are used they can make the program perform erratically. They can also make outputs occur<br />

out of sequence. If there is a logic problem, then these don’t help a programmer identify<br />

these problems.<br />

Many companies will require extensive paperwork <strong>and</strong> permissions before forces<br />

can be used. I don’t recommend forcing inputs or outputs, except in the most extreme circumstances.<br />

32.3 PROCESS MODELLING<br />

There are many process modeling techniques, but only a few are suited to process<br />

control. The ANSI/ISA-S5.1-1984 Piping <strong>and</strong> Instrumentation Diagram (P&ID) st<strong>and</strong>ard<br />

www.PA<strong>Control</strong>.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!