Member Login
Search
Past & Future Posts
Sponsored Communities
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Cool stuff
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
People who think they know everything greatly annoy those of us who do.
RSS Feed
www.control.com/rss
from the Automation List department...
Redundant PLCHi,
Our next project is in the tyre industry and our client insists on a redundant PLC system. Can you please specify the details regarding the redundant PLCs available in the market and also about your experience working on that?
Our next project is in the tyre industry and our client insists on a redundant PLC system. Can you please specify the details regarding the redundant PLCs available in the market and also about your experience working on that?
Redundant means you require two CPUs with distributed I/O module systems. Try Siemens S7 400. If you require detailed, practical exposure, write to pune @ prolifictraining. com
Yes, the Siemens S7-400H series is the high-availability redundant system. They have 3 ranges to choose from, the entry level is the 412H which is quite affordable (from a redundant controller standpoint). They use real-time synchronization with failover times < 100ms. The program and data is automatically sync’d, no special programming required for redundancy, everything is handled in the background. The redundant controllers can even be placed up to 10km apart from each other.
It supports redundant high speed communications all the way down to the I/O point. You can go nuts with the level of redundancy with 2 comms/remote I/O and then splitting I/O signals into 2 separate modules on 2 separate racks with 2 separate communication links all handled in the background. The system is also supports channel granular passivity, so even if one channel fails on a module the rest of the channels will continue to function and the failed signal will be switched to the redundant channel (usually on a different module).
http://www2.sea.siemens.com/Products/Automation/Programmable-Contr ollers/Redundant+PLC/?languagecode=en
It supports redundant high speed communications all the way down to the I/O point. You can go nuts with the level of redundancy with 2 comms/remote I/O and then splitting I/O signals into 2 separate modules on 2 separate racks with 2 separate communication links all handled in the background. The system is also supports channel granular passivity, so even if one channel fails on a module the rest of the channels will continue to function and the failed signal will be switched to the redundant channel (usually on a different module).
http://www2.sea.siemens.com/Products/Automation/Programmable-Contr ollers/Redundant+PLC/?languagecode=en
Dear Pramod,
I would suggest you to go for redundant controllers in Hot Standby configuration where both the controllers are reading inputs and processing it at the same time, however only one shall write the outputs. Hot Standby controllers increase reliability tremendously. Both controllers are in close synchronization with each other and checking each other in each cycle. The transfer of control on outputs is bumpless and no loss of functionality occurs. Controllers may be hot swappable and swapped controller should automatically get updated. You may also look for controllers to be directly linked to each other without any interfacing device to avoid "Common cause of failure". Almost all reputed players in automation market are providing such controllers.
Regards,
C. Potdar
I would suggest you to go for redundant controllers in Hot Standby configuration where both the controllers are reading inputs and processing it at the same time, however only one shall write the outputs. Hot Standby controllers increase reliability tremendously. Both controllers are in close synchronization with each other and checking each other in each cycle. The transfer of control on outputs is bumpless and no loss of functionality occurs. Controllers may be hot swappable and swapped controller should automatically get updated. You may also look for controllers to be directly linked to each other without any interfacing device to avoid "Common cause of failure". Almost all reputed players in automation market are providing such controllers.
Regards,
C. Potdar
It would help to know why your client insists on redundancy. There's some specific reasoning that should be addressed.
The easiest redundant system I've worked with for critical process control (primarily temperture) is Honeywell's hybrid controller. Just use duplicate controllers, duplicate power supplies, the rack that holds them and the switchover module. Communications can be redundant if you want. No programming changes, no calculations for scan time changes, same programming for redundancy as not.
As a hybrid it won't do fast sequencing like a PLC, but it handles moderate speed discrete I/O adequately.
Bud
The easiest redundant system I've worked with for critical process control (primarily temperture) is Honeywell's hybrid controller. Just use duplicate controllers, duplicate power supplies, the rack that holds them and the switchover module. Communications can be redundant if you want. No programming changes, no calculations for scan time changes, same programming for redundancy as not.
As a hybrid it won't do fast sequencing like a PLC, but it handles moderate speed discrete I/O adequately.
Bud
I think Bud made a good point.
Does the client have safety in mind or reliability? Depending on the answer that may exclude or include some vendors.
Also what level of redundancy? Redundant CPUs, and networks and I/O? What failover time is required if you adopt the hot standby approach? etc.
Does the client have safety in mind or reliability? Depending on the answer that may exclude or include some vendors.
Also what level of redundancy? Redundant CPUs, and networks and I/O? What failover time is required if you adopt the hot standby approach? etc.
From Control Engineering magazine...
Related articles from Control Engineering magazine- OPC: Painless migration, classic OPC DA to OPC UA, partership
- Easier: panel designs, short-circuit current rating compliance
- MechatronicsZone road show kicks off
- Partnership: Advanced, interoperable motion control, machine tools
- Protect intellectual property: Encrypt firmware, control code
- Portable computing: Operators can be mobile with rugged HMI
- Whitepaper: Small form factor HMIs evolve
- Remote control: Get behind firewalls—securely
- Report asks: Will DIN-rail PCs with I/O revolutionize industrial PCs?
Above articles copyright 2008 Reed Business Information. Subject to its Terms of Use.
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-2008 Control Technology Corporation. All rights reserved.
Users of this site are benefiting from open source technologies, including PHP, PostgreSQL and Apache. Be happy.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!



