Hester
Member
Scenario: It is a nice sunny 73 (F) day outside. Maybe with a slight temperature inversion. Toni Gibbitz is operating his production line, day dreaming of surfing perfect Lower Trestles, with nobody but himself and just a couple of close friends out. Suddenly Toni smells something funny, and not being much sharper than a marble, reaches over and punches out the EMO.
Maintenance investigates the "smell" and informs the production group that the Burrito factory up the street is making Garlic and Bean Burritos today, and the smell has blown down wind into the "Make up" air port, and being blown all through out the factory - all personnel Please disregard.
The next day, Production Manager Lazie Crotcha, wants to know why 15 minutes were lost recovering the piece of equipment that got EMO'ed.
Automation Engineer Milkey Licker, gets assigned the task of investigating this issue. He finds the Operator must completely clear the line of all product and restart it from the beginning in order to get the line running again. Something has to be done about this. It is "ridiculous¨ crows the VP that recovery should take so long. FIX IT!
And here is where I am at: Could you share your basic philosophy to a PLC greenie, regarding Alarm recovery, Error Recovery, and re-initialization?
What are your general rules or thumb, or design guidelines regarding error recovery. Any links appreciated.
Does one need to make a full matrix of all Discrete Inputs and generate code for testing state of each and every one of the inputs?
How do you guys think about this issue?
Thanks to those who wrote here:
Machine Safety: Pausing Index Table? Thread 6717
How To Start A Ladder. Thread 333
Safety Bypass ????? Thread 2293
RSLogix User Fault Routine Thread 891
Maintenance investigates the "smell" and informs the production group that the Burrito factory up the street is making Garlic and Bean Burritos today, and the smell has blown down wind into the "Make up" air port, and being blown all through out the factory - all personnel Please disregard.
The next day, Production Manager Lazie Crotcha, wants to know why 15 minutes were lost recovering the piece of equipment that got EMO'ed.
Automation Engineer Milkey Licker, gets assigned the task of investigating this issue. He finds the Operator must completely clear the line of all product and restart it from the beginning in order to get the line running again. Something has to be done about this. It is "ridiculous¨ crows the VP that recovery should take so long. FIX IT!
And here is where I am at: Could you share your basic philosophy to a PLC greenie, regarding Alarm recovery, Error Recovery, and re-initialization?
What are your general rules or thumb, or design guidelines regarding error recovery. Any links appreciated.
Does one need to make a full matrix of all Discrete Inputs and generate code for testing state of each and every one of the inputs?
How do you guys think about this issue?
Thanks to those who wrote here:
Machine Safety: Pausing Index Table? Thread 6717
How To Start A Ladder. Thread 333
Safety Bypass ????? Thread 2293
RSLogix User Fault Routine Thread 891
Last edited: