Member Login
member
passwd
remember me on this computer.

- join now -

Search

Past & Future Posts
Neat Stuff

Visit our shop for nerds in control lifestyle products.

Cool stuff
Select a topic of interest:
...and press:
Fortune
We don't need no education, we don't need no thought control.
-- Pink Floyd
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
Select a Page Style
Select one of the following styles:
- BluFu
- Classic
(cookies required)
from the Automation List department...
S7 - software redundancy
PLCs topic
advertisement
Posted by H.Hassona on 14 December, 2007 - 12:41 am
I'm developing a program for two SOFTWARE REDUNDANT S7-315-2DP that are serving the same I/Os, which means they both will have atypical software.

I have some PID functions, so I have to use OB35.
The code I wrote is for PID loops and for some digital sequences. I did that before but not for redundant CPUs, and I used to put all PID functions in OB35 and all the other functions and function blocks in OB1. In software redundancy, FB101 must be invoked before and after the duplicated code (in my case PID & sequence).

The question is, is it right to leave OB1 empty and put all the code in OB35? If yes, how can I determine the OB35 cyclic interval??

Posted by Mark Bayern on 16 December, 2007 - 6:39 pm
Why not use OB35 for the loops that require a cyclic interrupt, and use OB1 for the loops and controls that can use a 'normal' PLC scan?

The code that I've written and maintained only used the cyclic OBs for the PID control functions.The rest of the code executes from OB1

Mark

Posted by H.Hassona on 19 December, 2007 - 12:57 am
I normally do what you do, but I don't know how it will work in redundancy. I mean if I have code in OB1 and code in OB35, where should I put FB101???
FB101 should be called in just one single block OB1 or OB35.

Posted by Mark Bayern on 19 December, 2007 - 11:27 pm
OB1

From Control Engineering magazine...
Related articles from Control Engineering magazine
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.

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