Machine safety and safety certified networks
Do you remember when PLCs came out in the early 1970s – were there any communication networks available at that time? What is pier to pier? Fishing?
Do you remember when PLCs came out in the early 1970s – were there any communication networks available at that time? What is pier to pier? Fishing? Who knew much or anything then about industrial communications networks?
Control Engineering recently ran three articles on Safety Certified Networks.
Boy, have we come a long way since the late 1970s when communication networks were introduced by the likes of Allen-Bradley, Modicon, and a few others. Today, automation and controls engineers use words like “packets” as frequently as “tweet.” In the late 1970s packets (or satchels, envelopes, boxes, etc.) were used to gather several messages to be hand carried across town by a courier service.
In the 1980s and 90s communication networks contributed significantly to the rapid acceleration and adoption of PLC automation. Until 2002 machine safety controls were excluded by codes and regulations from participating in this transition from electromechanical controls to PLC automation. Likewise, machine safety was excluded from the benefits of communication networks. Now, since NFPA 79, 2002, the entire control system for a machine can include machine safety and can potentially be programmed by a single platform on one computer. And, communication networks can include PLC to PLC as well as machine to machine via communication protocols known as pier to pier clearly having nothing to do with fishing.
Having said that, let’s get back to the term packet. I talk about packets in the general sense on the subject of communication networks. Today there are standard packets and safe packets and both can be on the same safety certified network at the same time. I explain it this way. Imagine a safety network with a combination of standard components and safety certified components. A safety certified network (wired or wireless) allows the mix of standard packets and safe packets and the safe packets can only be communicated between safety certified components.
The standard components are not equipped to engage a safety packet so they essentially fly by a standard component. Additionally, safety packets are redundant to meet the higher reliability requirements for safety applications. So, in this day and age, packets still carry messages but these packets are on a safety certified network.
In summary, the safety network articles referenced here are great examples of how far machine safety has advanced over the past ten years. I recommend that you take the time to read all three. In my opinion, safety automation has accomplished in ten years what standard automation accomplished in 30 years.
Are safety certified networks your helping hand to advance your business?
Your comments or suggestion are always welcome so please let us know your thoughts. Submit your ideas, experiences, and challenges on this subject in the comments section below. Click on the following text if you don't see a comments box, then scroll down: Machine safety and safety certified networks.
Contact: www.jbtitus.com for “Solutions for Machine Safety”.
|Search the online Automation Integrator Guide|
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.