Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Event ID: 16#3502 - CPU Fault

Created by: zaid_b at: 5/8/2012 2:59 PM (6 Replies)

Rating (0)

Thanks 0

7 Entries

5/8/2012 2:59 PM	Rate (0)
zaid_b Experienced Member Joined: 10/5/2009 Last visit: 8/8/2023 Posts: 67 Rating: (0)	Dear All , I am programming CPU313-C , I keep getting this fault : " Event ID: 16#3502 OB request error No relevance for user (Z1):0000 Cause interrupt clock pulse generator 6 Causing OB: Cyclic interrupt OB (OB 35) " In OB35 there are 2 custom made blocks which my colleagues always use and I tried to replace them with another new blocks and still I have the same problem . My colleagues never faced such a problem . I tried to increase Scan Cycle Monitoring Time , but it just delayed the fault. I tried to increase OB35 execution time ( times 10 !) and still nothing is working How to solve it ?! Thank you

Suggestion To thank Quote Answer

5/8/2012 3:16 PM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating: (242)	It is possible thet code inside OB35 is executed for loo long, maybe longer your OB35 execution cycle... This is from helo system: NoteYou must make sure that the run time of each cyclic interrupt OB is significantly shorter than its interval. If a cyclic interrupt OB has not been completely executed before it is due for execution again because the interval has expired, the time error OB (OB80) is started. The cyclic interrupt that caused the error is executed later. Could you please tell me what is execution cycle of OB35 even when you prolonged it 10 times ? By the way, CPU313 is not so very powerful so maybe code execution time inside OB35 is really the case ?
	Last edited by: Darius at: 5/8/2012 3:17 PM Last edited by: Darius at: 5/8/2012 3:17 PM Best regards, Darius
Suggestion To thank Quote Answer

5/8/2012 3:34 PM	Rate (0)
zaid_b Experienced Member Joined: 10/5/2009 Last visit: 8/8/2023 Posts: 67 Rating: (0)	Hello , Thank you for your fast response , i tried putting the execution time to 1000ms for OB35 . Well , now I put the scan cycle monitoring time to 6000ms , it has been working for 10 minutes now , would it be bad if I kept it 6000ms ?

Suggestion To thank Quote Answer

5/8/2012 3:48 PM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating: (242)	zaid_b Hello , Thank you for your fast response , i tried putting the execution time to 1000ms for OB35 . Well , now I put the scan cycle monitoring time to 6000ms , it has been working for 10 minutes now , would it be bad if I kept it 6000ms ? Well it will not be bad until it fits your needs, but think about that it is 6 seconds, so DI will be read and DO will be set/reset with 6 seconds latency. I think it is a lot, but it depends on your application. Still I think if you control just any hardware, you'd better go for faster CPU, or try lo lower scan time to the point where you again get an error. You will get error in 1 second as OB35 execution time is 1 second. Make a tests.
	Best regards, Darius
Suggestion To thank Quote Answer

5/8/2012 3:58 PM	Rate (0)
Marciano Bronze Member Joined: 4/30/2007 Last visit: 3/9/2023 Posts: 231 Rating: (23)	Zaid_b, that note from Darius is very important, whatever is inside your OB35 should not take so long.. One second? Please monitor you cpu scantime, updating frequently and see how behaves,normally it is better to see a small alternation in the times instead some big zigzags… Try to determine also the execution time of those blocks, for this you could read the system time before and after the Block Call and see the difference, or just run one Block alone inside OB1.

Suggestion To thank Quote Answer

5/8/2012 10:20 PM	Rate (0)
gre_m Posts: 947 Rating: (45)	increase the duration of OB35. Insert ob80
gre_m Posts: 947 Rating: (45)
Suggestion To thank Quote Answer

5/19/2022 3:33 AM	Rate (0)
Utalika Experienced Member Joined: 1/11/2012 Last visit: 11/16/2022 Posts: 45 Rating: (3)	take a look this post OB80 interrupt - Entries - Forum - Industry Support - Siemens seems there is block which causing this

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on