5/21/2011 4:23 PM | |
Joined: 10/7/2005 Last visit: 7/15/2024 Posts: 3009 Rating: (1053)
|
Hello Nil96 Gut feeling tells me that you aremissing the appropiate Error OB's (or have a STOP command in them). Have a look at the links below for more on this and I hope this helps: Which organization blocks do you need for error handling? 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 |
|
5/28/2011 10:26 PM | |
Posts: 325 Rating: (13) |
Hi fritz, Here's an update on the latest happenings on the same issue...... There are 2 plc systems. 1) CPU 313C-2DP and CP342-5 [ Slave System] 2) CPU 313C-2DP [ Master System] Both these system when connected thru Profibus cable are working fine. Basically CP342-5 is made as Slave and is connected to the Master PLC system (313C-2DP) via profibus cable. In the Master PLC System , we have inserted the gsd corresponding to CP342-5 and the communication is all good. But the problem comes into picture when the Profibus cable is been replaced by Profibus Radio Modem. We are using Satel make Radio Modem. ( Configuration of the same is attached along with this post ). Also let me tell u guys that this Radio modem doesn’t come with any kind of gsd and also the max profibus speed is 19.2 Kbps. The problem here is that when ever the Master PLC is turned off & on, some times the PLC remains in stop mode, run blkins and Bus fault keeps blinking. All relevant OB have been put, but still this problem is observed. What we found was that if the Profibus connector @ Master CPU DP port is removed and inserted then the bus fault vanishes and cpu goes into run mode. We are trying hard to fix this, but are unsuccessful. We also tried deactivating proibus slave initially(during CPU start up) by making use of SFC12 and again activating after 20 or 25 seconds. Nothing worked………. Need some help plz…. AttachmentConfig1.pdf (97 Downloads) |
5/29/2011 11:55 AM | |
Joined: 10/7/2005 Last visit: 7/15/2024 Posts: 3009 Rating: (1053)
|
Hello Nil96 I can't tell you if it'll fix the problem you are experiencing, but gut feeling tells me that you have ticked "Test, commissioning. routing" in the Operating mode tab of your CP342-5 properties. This would at least explain that the CP342-5 (configured as a DP Slave) does transmit when in Stop. Reason being is that when this innocently looking tick made is made, the DP Slave will toggle between DP Slave (its normal/configured mode) and DP Master mode (done to give the "Slave" more bus access time and tospeed uponline programming access). If youfor example operate a CP342-5as a DP Slave behinda Y-Link, this "Test, commissioning. routing"function MUST be unticked (the same also appliesif a CPU is used an I-Slave sincethe Y-Linksimply can NOT handle a DP Master downstream of it). Perhaps your Satel Radio modems have similar "issues" (which would mean that they are NOT a fully transparent modem) in which case this may actually fix your problem (fingers crossed). I hope this helps and please let us know what you find. |
Cheers |
|
This contribution was helpful to5 thankful Users |
Follow us on