Elevator Ladder Logic Manual
Advanced insrumentation lab manual. 1. 1 EI 7051 ADVANCED INSTRUMENTATION LAB LAB MANUAL (Y10 Regulations) For IV /IV B.Tech (VII Semester) E. E Department of Electronics & Instrumentation Engineering VELAGAPUDI RAMAKRISHNA SIDDHARTHA ENGINEERING COLLEGE VIJAYAWADA-520 007 (AUTONOMOUS). 2 INSTRUCTIONS TO BE FOLLOWED IN MAINTAINING THE RECORD BOOK The Record should be written nearly with ink on the right hand page only. The left hand page being reserved for diagrams. The Record should contain: 1.
The number and name of the experiment 3. The aim of the experiment 4.
Characteristic tables of the circuit 5. On the left hand side, circuit should be designed 6. Index must be filled in regularly 7. You must get your record certified by the concerned staff on the every next class after completing the experiment 8. You must get your record certified by the concerned staff at the end of every semester INSTRUCTIONS TO BE FOLLOWED IN THE LABORATORY 1.
You must bring record observations notebook, while coming to the practical class without you may not be allowed to the practical. Don’t touch the equipment which is not connected with our experiment. When the apparatus is issued, you are advised to check their condition. You should not leave the laboratory without obtaining the signature of the concerned lecturer after completing the practical. Damaged caused to the property of the laboratory will be recovered.
If 75% of the experiments prescribed are not completed the candidate will not be allowed for attending examinations. 3 List of Experiments 1.
Implementation of Logic gates using PLC. Implementation of timer using PLC 3. Implementation of counters using PLC 4. Level controller using PLC 5. Pressure Control using PLC 6. Motor speed control using PLC 7. Bottle filling System using PLC 8.
Temperature control using PLC 9. Elevator controller using PLC 10. Batch process Reactor system using PLC 11.
Material Handling System using PLC 12. Process control Simulator 13.
Implementation of PLC programming through SCADA 14. Fan Control using PLC 15. Reaction Vessel Control using PLC NB: A minimum of 10 (Ten) experiments have to be performed and recorded by the candidate to attain eligibility for University practical Examinations.
4 PLC INTRODUCTION A PLC is an industrial digital computer used to monitor I / P’s and depending upon their state make decision based on its program or logic to control its O/P’s to automatic a machine or a process. The main difference from other computers is that PLC’s are protected from savior conditions (such as dust, moisture, heat, cold) and has that facility for extensive I/O arrangements. These I/P arrangements directly connect the PLC to sensor and actuators.
On the actuator side PLC’s operate electric motors, magnetic relays solenoids or analog O/P’s ADVANTAGES: 1. Rugged and designed to with stand vibrators temperature humidity and noise. Easily programmed and have an easily understood programming language 3. Have interfacing for I/P’s and O/P’s already inside the controller DISADVANTAGES: 1. Difficulty with change or replacement 2. When a problem occurs holdup time is in definite usually APPLICATIONS: 1. In any automated system like steel plant, paper industry, COCO – COLA Industry PLC controller is usually the central part of the process system.
To run more complex process, It is possible to connect or PLC controller to a control computer ARCHITECTURE OF PLC: 1. CPU: - The CPU accepts I / P data from various sensing devices, executes the stored user program from memory and sends appropriate O/P command to controlled devices. In small PLC, the processor solid state memory I / P modules and power supply are housed in a single compack unit. The programming devices usually handling unit, a key pad and LCD display are connected to the main unit with a cable.
In large PLC’s the processor and memory are in one unit. The power supply is second unit and I/P interface in additional units. The programming devices in general personal computer are connected to the main with RS232 cable serial data standard. The Microprocessor or microcontroller is a part of PLC, CPU that receives analyses the process and sends data.
The memory unit contains RAM, ROM, the fixed operating program and RAM contains the user program which is writing the ladder diagram language. The I/P system forms the interface by which field devices are connected to the controller. The I/P module converts signals from the process device (12V, 24V, 120V AC or DC) in to logic signals (5V DC) that can be used by the controller. The O/P module converts logic signals (5V DC) in to field level signals (12V, 24V, 120V AC or DC) to power device.
Elevator Ladder Logic Manual (890 Use 146 00)
Programming device: - The programming device or PC is used to enter the desired program in to the memory of PLC processor. This program is entered using ladder logic. The program determines the sequence of operation and ultimate control by process loops TYPES OF PLC: - Name PLC – IC 200NDD101 → Versa max NANO PLC has no. Of I/P’s 6, 24V DC I/P switches → Addresses from 1i to 6i and 4, 24V DC LED O/P’s (address 1Q to 4q) → PLC software: versa pro2.02 About the software: The software used in NANO PLC’s when designing a ladder logic diagram is versa pro 2.02.The software has been designed by GE FANUC. This is a very user friendly program when compared to the other programs. The program has been designed to suit the operating system environment The block diagram of PLC is shown in figure 1: PROGRAMMING LANGUAGES: - The 2 most common language structures are 1) Ladder diagram language 2) Boolean language In laboratory we mostly prefer to use only ladder diagram language The ladder diagram language is basically a symbolic set of instruction used to create the controller program. These ladder instructions are arranged to obtain the desired control logic.i.e, to be entered in to the memory of the PLC.
The main Symbols that are used in PLC programming are. 6 Experiment No:1 IMPLEMENTATION OF – LOGIC GATES USING LADDER PROGRAMMING Write the ladder language code for the logic gates with the help of PLC AIM: To realize the logic gates using ladder programming Procedure: - 1. Interface PC to PLC through Rs – 232 cables 2. Go to versa pro 2.02 Icon 3. Open “FILE” go to “new folder” fill the details and click finish 4.
Go to “Hard ware configuration” and replace module 5. Enter the symbols on to file using symbol on menu bar 6. Given I/P, O/P address 7. Go to PLC click connect 8. After connecting go to PLC clear it and select all 9.
After clearing go to PLC store it 10 Go to PLC go to Run 11. Thus checkout using PLC and realize respective truth tables Result: -logic gate using ladder language are realized using PLC and their truth table are verified REVIEW QUESTIONS: - 1. What are the different symbols for building ladder diagram?
Draw the logic gates for AND,OR,NAND, NOR, NOT,EX – OR,EX – NOR 3. What is the software used for realizing logic gates? Explain the Boolean expression Z= XY + XY Applications: 1. Security Systems 2.
Industrial applications 3. Petroleum collection & distribution. 7.
8 Experiment No:2 IMPLEMENTATION OF TIMERS USING PLC AIM: - Design & verify the operation of timers & counters using PLC ladder language THEORY: - A timer is simply a control that waits to turn ON or turn OFF the O/P after receiving an ‘ON’ or’ OFF’ signal from the I/P. Times are basically 3 types. ON DELAY TIMER: This timer wait a specific amount of time then turns ON an O/P. The ON delay timer (TMR) increments while it receiver flow and resets to zero when flow stops.
Time may be counted in tenth of a sec, Hundredth of a sec or Thousandth of a sec the range is 0 to + 327767 time units. The state of this timer is retentive on power failure, no automatic initialization occurs at power up.
When the current value equals or exceeds the present value (PV) the function begins passing power flow to the right. Timer continues accumulating time to the right. The timer continues accumulating time until the maximum value is reached. When the enabling parameter transitions from ON to OFF, The timer stops. Accumulating time & current value is reset to zero OFF DELAY TIMER: This timer takes turn on an O/P and keeps that O/P ‘ON’ until specific amount of time has passed then turns it OFF. When programming a timer instruction the programmer must specify the timer address (one of the 256 internal resistor of PLC R0 to R255).
Time base (1B) and the preset value (PV).The time base value is an internal that the timer is going to use these values. Can be said to 0.1sec,0.01sec,0.001sec 0.1sec → 1/10 timer 0.01sec → 1/100 timer 0.001sec → 1/1000 timer The present value specifies how many intervals a timer should count before the timing is complete. Also known as done. Timer selling time or delay time equals its present value multiplied by the time base. Delay time = PV X TB A timer is done when its accumulator values reaches its preset value. 9 When ‘ON’ delay timer is enabled, when its ladder rung is true An ‘OFF’ Delay timer is enabled.
When its ladder rung is false When ON or OFF delay timer is timing its rung condition change will cause the timer to stop and its accumulated value to be reset to ‘Zero’ RETENTIVE TIMER: - A retentive timer was like an on delay timer with one difference.That is when its Run conduction changes from the true to false the timer. Simply stops timing but its accumulated value is not reset to zero. When its rung condition goes false to drew. The off delay timer increments while power flow is OFF and resets to zero when power flow is ON. Time may be counted in 10ths (0.1), 100ths (0.01) or 1000ths (0.001) of a sec.
The range is 0 to + 32767 time units. The state of this timer is retentive on power failure, no automatic initialization occurs at power up. When the current value equals or exceeds the present value (PV) the function stops passing power flow to the right. The timer continues accumulating time to the right. The timer continues accumulating time until the maximum value is reached. When the enabling parameters transitions from ON to OFF, the timer stops.
The LogixPro Elevator Simulation LogixPro Multi Floor Elevator Student Exercise Getting Started As we've seen previously, modularizing portions of a program and placing the required logic into subroutines often results in a program which is both easier to read and understand. In extreme cases, a programmer may even elect to modularize the total program. If this approach is taken, then the resultant core or main program will often be nothing more then a list of calls to subroutines where the details are dealt with. Very much like the Index for a book. The index provides an overview from which the reader can readily discern where particular topics are located, and then readily move to that location for further details. In the case of the Elevator simulation, it isn't too hard to visualize how we might modularize many, if not all the tasks that are going to be required.
The tasks of closing and opening the door are obvious candidates for modularization. Almost all programs require an initialization section, and even tasks that require continual execution, such as catching a button press which denotes a request for the elevator to arrive, can often be grouped into a subroutine, and then simply called unconditionally on every scan.
In 1896 the company expands and becomes the Docking Company. Later, in addition to the construction of ships, the company began shipping. Kawasaki gpz 1100 b2 service manual. He found out from his own experience that Europeans have a much greater sense in the courts, and therefore enjoyed European shipbuilding technology. Since in 1894 the Sino-Japanese War broke out. The success of the newly formed company was associated with the receipt of large orders from the Japanese army, which eventually led the firm to the level of the main supplier of military products.
Add a module to track the elevator's motion, and we should already have a fairly good topical outline for our program's Index. Another factor which is somewhat unique to this exercise, is that we are going to need a fair number of flags to keep track of what we are doing, and what must be done next. Fortunately, the switch closures which denote a request to have the elevator arrive, will lead us to latching the built-in lamp of the switch so as to visually confirm the request has been recognized. The lamp for this switch should remain energized until the elevator car arrives, and hence that lamp can serve the dual purpose of flagging that pending requests exists, it's floor, and indirectly the required direction of travel. Employing I/O in this dual purpose manner should not be new, but utilizing latch (L) and unlatch (U) instructions has until now been generally discouraged. You should be well aware of the reasoning behind this by now, but there are situations where the latching instructions are ideally suited to the task, and this happens to be one of them. Exercise #1 - Preparing Your Program's Index.
Open a new program, and enter the rungs shown below into the main or LAD2 section of this program. Once this is accomplished, all further logic that you add to your program should be placed into the appropriate subroutine which has been allocated for the particular task at hand. You will note that a number of flags have already been pre-defined, and these are to be employed to control the logic flow of your final program. Just to make life a little easier on your instructor, you are asked to utilize unused bits in word B3:0 if and when any additional flags are required. Exercise #2 - Taking the Elevator to the Top. In this exercise you will add all the appropriate logic to detect when the wall mounted 4th floor switch (I:1/11) is pressed.
When this occurs, the elevator is to be put into motion and proceed upwards until it arrives at the 4th floor where it will halt. This of course assumes that the elevator starts out in it's default location at the first floor. It's imperative that you accomplish this task while maintaining compatibility with the current program structure. To this end, all 6 subroutines will be utilized, and therefore each must first be programmed with the appropriate logic to accomplish this initial task. U3, Initialization Subroutine: Each time you test your program, you should first reset the simulation using the selection in the simulations menu. This will ensure that elevator is back at the first floor and all the hardware is in it's initial state. When you place your program into the run mode, U3 will be executed, and it is here where you should ensure that all flags etc are in their correct initial state.
In particular, the 'DoNext or Wait' flag should be latched true which will ensure that subroutine U7 (Next Request or Wait) will be actively scanned at this time. U4, Catch Floor Requests: This subroutine is where the logic that will detect, and react to the closure of the 4th floor wall switch should be placed. The lamp for this switch should be latched on, but this should only occur if the elevator is not already at the 4th floor. In later exercises, additional logic will be added for the other switches that can initiate a change in the elevator's location. U5, Next Request or Wait: This subroutine is where the decision to move the elevator will be made. The built-in lamps of the wall mounted switches may be used as a flag to initiate a move of the elevator car.
For now it will only be necessary to monitor flag (lamp) O:2/11 and set the 'Close and Go' flag in response. This will in-turn invoke the 'Close Door and Move' subroutine (U7) which will take care of getting the elevator underway. U6, Close Door and Move: In this subroutine, locate the logic to close the door, and then energize the motor to get the elevator underway. The desired direction is obvious in this case, but later you will most certainly require flags to indicate which direction to proceed in.
Before exiting this subroutine make sure that both the 'DoNext or Wait' and the 'Close and Go' flags are cleared (unlatched), and set the 'Car is Moving' flag so that positioning of the car will be controlled. U7, Track Car Movement: Once the car is moving, this subroutine takes control, and is responsible for deciding where to stop the car. In this exercise the direction and destination are fixed (up, 4th floor), so you will only be required to determine when the car has reached the fourth floor. Once there, the car's location should be flagged by updating the appropriate floor indicator lamps, and the 'Stop and Open' flag should be set (latched) which will in-turn invoke the 'Stop and Open Door' subroutine. The car's vertical position can be determined by reading the motor's shaft encoder (I:5), and equating this reading to those you have gathered for the individual floors. It may take a little trial and error to initially gather these values, but the task can be made easier if you temporarily slow LogixPro's scan rate down somewhat.
U8, Stop and Open Door: The first thing to do here is to stop the motor and reset (unlatch) the 'Car is Moving' flag. You should also extinguish the built-in lamp of the wall mounted request switch. The floor indicator lamps above the door can be utilized to determine which lamp is to be extinguished. Lastly a small 2 second settling delay should be allowed for, followed by opening the door. Once you have your program to the point where the elevator can be moved from it's initial location to the 4th floor as outlined, you should then be ready to deal with returning it to the 1st floor. Exercise #3 - A Complete 2 Floor Elevator Control.
In this exercise, you are asked to add the required logic to implement a complete 2 floor elevator control system. Floors 1 and 4 will be used for this purpose, and all switches and lamps associated with these floors are to be made fully operational. All added logic should be placed into the subroutine deemed appropriate for the particular task, and additional flags may be added as required. When not actively moving, the elevator will be located at one of the 2 serviced floors, sitting at rest with the elevator car door opened. When at rest, the only lamps illuminated will be the appropriate floor indicator lamp located directly above the elevator door. Additionally, your program should not respond to a switch press associated with the elevator's current location On arrival at a floor, the built-in switch lamp for that floor should be extinguished, and the appropriate floor indicator lamp above the door should be illuminated.
The door should then be made to open 2 seconds later. Additionally, the door must remain open for a minimum of 5 seconds before being allowed to process another floor request. Floor requests occurring during this delay period should not be ignored, but only delayed in processing. While working on a solution for this exercise, keep in mind that you will soon have to extend this control to all 4 floors. Flags to indicate in which direction the elevator is traveling will be a must. Fortunately with just 2 floors, determining which direction to go is a trivial task, but one that will become quite complex when additional floors are added. Once you have assured that you can fully control the operation of this 2 floor elevator, you should be well prepared to move onto the multi-floor exercise.
Exercise #4 - Multi Floor Elevator Control. Extending your program to accommodate multiple floors, would appear to be a relatively simple matter of just adding the logic to deal with the additional switches and lamps. This must be done of course, but a new issue arises in a multi-floor system which can prove to be quite a challenge to solve for. With a 2 floor elevator, you really have only one choice when deciding in which direction the elevator should move. In a multi-floor system however, you can be faced with 2 choices of travel whenever the elevator is at an intermediate floor. In addition, you must also take into account whether the elevator is at rest with no requests for service pending, or has stopped temporarily at the intermediate floor while proceeding to a floor further beyond in that same direction. In our multi floor system, the elevator should continue in it's initial direction of travel, stopping at each intermediate floor which has a request pending for that particular direction, and continue in this same direction until the farthest request for service is reached.
At this point the direction of travel should then be reversed if further requests are pending. Any requests associated with this new direction of travel should then be serviced. Once moving towards the farthest requested floor, the elevator should not stop at an intermediate floor if the request at that floor is for the opposite direction; unless this is the farthest request. Otherwise the floor should be bypassed and serviced when the elevator later approaches the floor from the opposite direction of travel. Keeping track of the direction of travel will be critical in this control scheme.
It's therefore suggested that you employ both 'Going Up' and 'Going Down' flags to help in the decision making process. Only when there are no requests pending would the elevator be deemed to be at rest (Waiting), and both direction flags would be set false (unlatched). The first new request detected can then be used to determine the initial direction of travel, and the appropriate flag set (latched).
Once a direction has been flagged, then motion and servicing will continue until all pending requests are serviced. If required, the direction may be changed, but not until all requests are serviced will both direction flags once again become false.
The logic associated with determining the initial direction, change in direction, and achieving a state of rest, ideally belongs in the 'Next Request or Wait' subroutine. This logic will definitely not be trivial to develop, and you are strongly advised to utilize whatever tools you have at your disposal, including pen and paper to attain a suitable solution. Best of Luck!.