Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

cpu stopped problem

Created by: ruel at: 6/27/2010 4:51 PM (8 Replies)

Rating (3)

Thanks 0

9 Entries

6/27/2010 4:51 PM	Rate (0)
ruel Posts: 6 Rating: (0)	hello to every body, i'm new to this forum, so please bear with me. We have a printing machine using CPU315-2 DP while in run mode, the cpu is ok, but during crawl mode the cpu switch to stop mode, sf led is lit, bf led blinks for a while then turns off then stop led is lit. But if I disconnect the run enable wire going to our 2nd unit press main drive, the cpu is ok even if i switch to crawl mode. one more thing i could not understand is during automatic operation this drive enable is also there but the cpu don't swicth to stop. what could be my problem and the possible solution? I am using a lenze drive here connected by profibus. thanks in advance ruel
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

6/27/2010 5:01 PM	Rate (1)
Ayman Elotaify Platinum Expert Joined: 5/28/2008 Last visit: 9/9/2024 Posts: 4515 Rating: (839)	Hello ruel, First, I would like to say "Welcome" to Siemens Forum specially this is your first post. Now, my first quick investigation: the problem comes from the profibus network. could you please draw the profibusnetwork of your machine and attachhere. It will help us to tell you where to look and to find a solution. Also, please have a look on this thread Regards.
	Ayman Elotaify
Suggestion To thank Quote Answer

6/27/2010 5:08 PM	Rate (1)
UMENCHO Diamond Member Joined: 3/21/2006 Last visit: 9/10/2024 Posts: 10228 Rating: (1181)	Hello ruel, Basically if you have some problems with CPU take a look at its Diagnostic buffer. (in Online mode, Ctrl+D). There is possible to find what is wrong there. Take a look also at the following entry tells you which organization blocks do you need for error handling in the S7 program of the CPU: 11499205. best rgeards, Hristo Mihalev

Suggestion To thank Quote Answer

6/28/2010 9:23 AM	Rate (0)
ruel Posts: 6 Rating: (0)	thanks to all your replies, attached is my profibus drawing, please just interconnect them because we dont have a big scanner. i am also attaching my diagnose buffer, as of this writing, all printing units are running but we don't put paint on unit 2 to avoid it from cleaning during idle or change design. this is because when cleaning or change design we need to crawl and that's the time the cpu stopped. hoping for your good advice cause we need to run on 3 colors ruel Attachment New.zip (175 Downloads)
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

6/28/2010 9:29 AM	Rate (0)
ruel Posts: 6 Rating: (0)	sir, this is the continuation of my attached drawing ruel Attachment New1.zip (189 Downloads)
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

6/29/2010 7:57 AM	Rate (0)
ruel Posts: 6 Rating: (0)	UMENCHO Hello ruel, Basically if you have some problems with CPU take a look at its Diagnostic buffer. (in Online mode, Ctrl+D). There is possible to find what is wrong there. Take a look also at the following entry tells you which organization blocks do you need for error handling in the S7 program of the CPU: 11499205. best rgeards, Hristo Mihalev hello and good day, Dear UMENCHU, This is the first time we encounter this kind of problem, only on this machine so, regarding on programming organization blocks, we still lacks the knowledge I already downloaded the manual for OB's and Error handling programs and just started reading it. and i think it will take time before i could handle safe inclusions of OB's on our system, i hope you could share us some ideas to resolve our problem. I checked our program we already have OB86, but in our diagnose buffer event no 6 it says ob not found or disabled or cannot be started in the current operating mode. please see my attached diagnose file ruel Attachment Diagnose.zip (164 Downloads)
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

6/29/2010 8:04 AM	Rate (0)
ruel Posts: 6 Rating: (0)	Ayman Elotaify Hello ruel, First, I would like to say "Welcome" to Siemens Forum specially this is your first post. Now, my first quick investigation: the problem comes from the profibus network. could you please draw the profibusnetwork of your machine and attachhere. It will help us to tell you where to look and to find a solution. Also, please have a look on this thread Regards. Dear mr Ayman, I sent the drawing of my profibus network yesterday, how did you find it? how can i find the problem using the drawing. thank you very much for all you time. ruel
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

6/29/2010 2:28 PM	Rate (1)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 9/10/2024 Posts: 12282 Rating: (2683)	Hello ruel; Basically, the networkschematics you have shown are straightforward, and unless there is a problem with termination at one or both ends of the bus (at Unloader XU and the control panel IM 151-1) then your network seems healthy, at first glance. I mean termination resistor should be ON, and power should be applied in permanence to these 2 units; no terminator on any of the other nodes. In any case, termination problems would not affect your network in the way you have described. Now, the contents of the diagnostic buffer already shows some interesting information, in that it states that you have 3 types of generic errors (represented by the diagnostic OBs declared missing): OB86: rack failure, slave #36, input address 2031 OB82: diagnostic interrupt, same input address as for OB86 (2031) OB122: programming error, on addressPIB400 or PQB400 This should be a good starting point for you, even if you do not plan on adding the missing OBs in the CPU (more about that later). Look in the HWConfig editor of your Step 7 program, and look for slave # 36. Check what range of input/output addresses has been attributed to the modules of that slave and check if they are the same as the ones pointed out in the diagnostic buffer. Then look either for a hardware or a programming fault (the cross-refence module of Step 7 will be of great help there) associated with these addresses. An even better way would be to start by inserting the missing OBs in the CPU's load memory. The diagnostic buffer uses their programming interface to collect data on the problems it ncounters, so your diagnostics would be much more precise, and you would also find other advantages: your CPU could continue working (with a SF LED active) in case the fault is not critical. Simply right-click on the Blocks folder,create a New Block, select type OB, Name it (give it the required number, 82, 86 122). Then select all three new blocks (you do not need to program anything inside them at this time) and download them to the PLC. The next time your CPU encounters the error that causes a problem you will find better information in the diagnostic buffer. Hope this helps, Daniel Chartier
	Last edited by: dchartier at: 6/29/2010 2:31 PM Last edited by: dchartier at: 6/29/2010 2:29 PM
Suggestion To thank Quote Answer

6/30/2010 1:15 PM	Rate (0)
ruel Posts: 6 Rating: (0)	Good day Mr. Chartier, Thank you for your reply, I tried to trace slave 36, it leads me to the last unit of our machine which is the lenze drive in the unloader and the adress 2031 is not there. the range of address in that node is MB 1944 to MB 1991, PIB 400 to PIB 423 and PQB 400 to PQB 423. With this regard, what could be the reason the problem will come from there while we are experiencing the stoppage on unit 2? (On unit 1 to 3 we have a selector switch crawl/run) Whenever we swiched to crawl on unit 2 thats only the time the CPU goes to stop mode. The next move now is to follow your instruction to insert the missing OB's hoping to find a better information on the diagnostic buffer. I hope i could do that until tomorrow because production are still finishing a job on said machine. Thanks for your advice its very helpul ruel
ruel Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on