Member Login
member
passwd
remember me on
this computer.

- join now -
- forgot username or password? -

Jump to a Date

Sponsored Communities
Cool stuff
Select a topic of interest:
...and press:
Neat Stuff
Control.com Stuff

Visit our shop for nerds in control lifestyle products.

Fortune
Just about every computer on the market today runs Unix, except the Mac
(and nobody cares about it).
-- Bill Joy 6/21/85
RSS Feed
RSS feed Use this link to get an RSS feed of the Control.com article flow, for private, non-commercial use only:
www.control.com/rss/
To get a personalized feed, become a member at no cost.
Select a Page Style
Select one of the following styles:
- BluFu
- Classic
(cookies required)
advertisement
from the Not so Fail Safe department...
Fail Safe
Application Questions and Problems topic
Posted by cmdFailSafe on 6 November, 2008 - 1:38 pm
I'm looking for online articles or printed publications that discuss the different aspects of designing a Fail Safe system. I know there are fail safe sensors, redundant safety systems, etc. But what I'm looking for is wiring and program logic practices for creating a fail safe system for inputs (sensors) outside of safety etc... i.e. every day prox or photoelectric sensors, etc.


Posted by Abhijit Goswami, Haldia on 4 January, 2009 - 2:00 pm
You need to know how a system (consisting of hardware/firmware/software) may fail (to perform) to design a fail-safe system. Generally FMEDA report from manufacturer is a good help. With increasing awareness of industries toward "functional safety", manufacturers are also forced/encouraged to publish product specific FMEA/FMEDA. Contact vendor or you may refer "www.exida.com" for limited available reports.

Alternative is to fallback on various handbooks to collect failure data/probabilities which are mostly generic and not vendor/model specific.

The website "http://www.safetyusersgroup.com/" is good to start with understanding concepts of functional safety.

Regards.


Posted by Steve Myres, PE on 9 January, 2009 - 9:58 am
The general rule is that you want the signal active in the good condition. If the signal is off in the good condition, then if a wire is broken or a PLC input fails, you won't know when the bad condition occurs. With signal active = good, you'll find out instantly about any broken wires, failed inputs, etc. Unfortunately, they'll simulate the bad condition and may falsely shut down your process, but that's better than going along complacently thinking everything's OK when you've lost the ability to sense the problem.


Posted by anonymous on 10 January, 2009 - 1:06 am
Just indirectly related (but you mentioned input modules), the new (well not really that new anymore) PLC Producer/Consumer model is something to watch out for with sensors wired failsafe on the hardware side. There needs to be more logic put in place to detect failures in input modules.

Hugo


Posted by Timothy Niemczyk on 21 January, 2009 - 2:12 pm
I would suggest reading a very interesting paper, "Loss-Prevention and Risk-Mitigation in Equipment Protection Systems" by Phil Corso. You can contact Phil at cepsicon at aol. com if you can't find his paper. He is very knowledgeable and helpful, especially when discussing Fail Safe Systems.

Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2009 Nerds in Control, LLC. All rights reserved.

Users of this site are benefiting from open source technologies, including PHP, MySQL and Apache. Be happy.

Advertisement
Our Advertisers
Help keep our servers running...
Patronize our advertisers!