8/12/2015 9:54 AM | |
Posts: 31 Rating: (6) |
Hello, Those are interrupt OB's. Which means they get called by the main program cycle (OB1) when a certain even happens (say, for example, they can be set to be called everyday at 12:00). If they are empty, it only means that even if they are called, nothing will happen. There is nothing wrong with leaving them there, or you can remove them. Upto you. Check this link for more info on the details of Interrupt OB's and how to use them: http://www.infoplc.net/files/descargas/siemens/infoplc_net_sitrain_12_obs.pdf As for SFCs, they are inbuilt functions('System Functions') and you cannot remove them from the PLC. Hope it helps! Vamsi Vegamoor |
Last edited by: Vamsi_VVK at: 8/12/2015 9:56:41 AMLast edited by: Vamsi_VVK at: 8/12/2015 9:58:41 AM |
|
This contribution was helpful to2 thankful Users |
8/12/2015 10:06 AM | |
Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054) |
hi dominik, for using OB´s see this Thread If you don´t use the SFC´s you can delete it in your offline project, but not online. Like already mentioned, SFC´s are inbuilt functions. hope this helps, regards, |
FCK WAR! |
|
This contribution was helpful to2 thankful Users |
8/12/2015 10:49 AM | |
Posts: 34 Rating: (1) |
Hi Vamsi Vegamoor, Nice feedback! Thank you so much Regards, Dominik |
8/12/2015 10:53 AM | |
Posts: 5225 Rating: (1192) |
|
This contribution was helpful to1 thankful Users |
8/12/2015 11:09 AM | |
Posts: 34 Rating: (1) |
Hi William_B, Sorry but I don't know, can you explain me? Thank you Regards, Dominik |
12/15/2015 11:34 AM | |
Joined: 3/19/2010 Last visit: 4/17/2024 Posts: 438 Rating: (12) |
There is a big difference between having empty OB's and not having at at all. Empty OB means that nothing additionally will be exectued within its code, except the most important - CPU will not go to Stop in case of the event covered by the considering OB. In the other words, if you have, for example Rack_Failure, and you don't put OB86, CPU goes to Stop on failure. If you have empty OB86, it "tells" CPU - "Please, don't go to stop, just live with this fault, and continues with program!". If you have some code within OB86, it both tells the CPU not to go to Stop, and execute a code. The same is with OB82, OB83, OB85, OB121, OB122 - to mention only the most tipical. |
Follow us on