Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

Exicution of OBs

Created by: Anil Belkery at: 9/2/2011 7:51 AM (3 Replies)

Rating (0)

Thanks 0

4 Entries

9/2/2011 7:51 AM	Rate (0)
Anil Belkery Posts: 52 Rating: (0)	Hi All, In order to avoid CPU going into the STOP mode following OBs have been called in my code: OB10,OB35,OB80,OB82-OB87,OB100,OB121 & OB122. I have a requirement to keep a track of how many times these OBs are called inand display this information on HMI/SCADA. What could be the best option to achieve this requirement? Iguess, writting the logic in respective OBs could be one of them. Regards, Anil
Anil Belkery Posts: 52 Rating: (0)
Suggestion To thank Quote Answer

9/2/2011 9:12 AM	Rate (0)
Wizard Diamond Member Joined: 4/24/2006 Last visit: 7/31/2025 Posts: 9027 Rating: (1199)	Anil Belkery .... OB10,OB35,OB80,OB82-OB87,OB100,OB121 & OB122. I have a requirement to keep a track of how many times these OBs are called inand display this information on HMI/SCADA. What could be the best option to achieve this requirement? Iguess, writting the logic in respective OBs could be one of them. Hello, OB10 is a Time-of-Day interrupt. (So it will be called every day or even every minute) OB35 is a Cycle interrupt and will be called every 100 ms (Programmed in Hardware config.) The other OB's are error OB's and will be called, when necessary. You can write logic inside the respective OB's (a counter to count every time it is called) (But it is called when there is an error and also when error is gone) Best regards, Wizard

Suggestion To thank Quote Answer

9/2/2011 10:09 AM	Rate (0)
umencho Diamond Member Joined: 3/21/2006 Last visit: 3/30/2025 Posts: 10239 Rating: (1183)	Hello, Just take alook at TEMP variables in error's OBs. There have a variable with a name OBx_DATE_TIME means Date and time OBx started... Best regards, Hristo MIhalev

Suggestion To thank Quote Answer

9/4/2011 11:19 AM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 8/31/2025 Posts: 6874 Rating: (1368)	Dear Anil Belkery Anil Belkery Hi All, In order to avoid CPU going into the STOP mode following OBs have been called in my code: OB10,OB35,OB80,OB82-OB87,OB100,OB121 & OB122. Check chapter one of the following manual for more information on "Organization Blocks".There are some OBs , if they are not loaded and an error occures,STOP the CPU. http://support.automation.siemens.com/WW/view/en/44240604 If you have not programmed OB87 and a start event for OB87 occurs, your CPU will react as follows: • An S7-300 CPU changes to STOP mode. • An S7-400 CPU does not change to STOP mode. Also note,OB10-OB17 are time of day interrupt OBs and OB30-OB38 are cyclic interrupt OBs and they may not cause the CPU to STOP if you do not load them to CPU. To count the number of times , an OB executed check the following codes as an example to be written in OB86. [code] //OB86 AN M10.0 = M10.0[/code] [code]//OB1 A( A M10.0 FP M11.0 O( A M10.0 FN M11.1 ) ) CU C0[/code] In each execution of OB86,status of M10.0 may change from false to true or vice versa.Count both edge changes with 2 edge detection parallel like an OR.The counter is called in OB1 due to global address (memory M10.0) used to create pulses.Check the attachment for sample codes. It is not recommended to be used for OB35. Also you can try this as a simple solution: [code]//OB86 L MW 100 L 1 +I T MW100[/code] Best regards Attachment Hd.zip (155 Downloads)
	Last edited by: hdhosseini at: 9/5/2011 10:33 AM Last edited by: hdhosseini at: 9/4/2011 11:24 AM Demo Channel on Youtube
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on