6/22/2011 3:22 PM | |
Joined: 3/23/2010 Last visit: 11/11/2024 Posts: 20 Rating: (0) |
Hello Dear friends, when I disconnected profibus socket from Sew driver CPU don't go stop mode, but, when I connect profibus socket on Sew driver CPU 315-2 goes to stop mode, I downloaded ob 85,ob86,ob100,ob101,ob102,ob121,ob122 but I couldn't solve problem. I don't want to cpu go to stop mode. projected was attached. waiting your replay I m sending my best regards. Attachments7project.zip (206 Downloads) |
6/22/2011 3:39 PM | |
Joined: 3/21/2006 Last visit: 11/1/2024 Posts: 10229 Rating: (1181) |
Hello, Meanwhile did you check in Diagnostic Buffer the reasons for Stop mode? Best regards, Hristo Mihalev |
6/22/2011 4:51 PM | |
Joined: 3/23/2010 Last visit: 11/11/2024 Posts: 20 Rating: (0) |
very sory, because of interesting problem on simatic S7 , even if I marked right project, it is archived diffrent project. here my project. yes I have looked to diognostic buffer , it is offered to download OB86, but it is not enough. after download it, when disconnected profibus socket there is no stop, but , if I connect profibus socket on sew driver , cpu still goes stop mode. best regards AttachmentDddd.zip (182 Downloads) |
6/23/2011 1:45 AM | |
Joined: 10/7/2005 Last visit: 11/11/2024 Posts: 3026 Rating: (1057)
|
Hello crazy I'm going out on a hunch here, but your SEW drive mayissue a diagnostic interrupt releated message upon resuming Profibus comms. This will lead to a call of OB82 in your S7, which you don't have in your CPUand as such cause theStop. I hope this helps and have a look too at the link below for more on this: Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails? |
Cheers |
|
Follow us on