Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Communication Issues

Created by: RDH at: 5/17/2014 1:51 PM (8 Replies)

Rating (2)

Thanks 15

9 Entries

5/17/2014 1:51 PM	Rate (0)
RDH Posts: 3 Rating: (0)	We have a Mater and Slave set up for aMonitoringSystemon our facility, with a CPU314C-2DP as the Master and 2 ET200M's as theSlave units. Our facility was struck by lightning a few nights ago and the master lost comm's with the slave units. I changed out the slave units and one have come back up ok but the otheris sitll not communicating the the master. I have since checked all the cabling (copper wire), checked the connectorsand also changed out the Master unit, Still not working. Does anyone have any ideas on how to fix this issue?
RDH Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

5/17/2014 2:05 PM	Rate (0)
hdhosseini Diamond Member Joined: 1/28/2009 Last visit: 6/9/2023 Posts: 6805 Rating: (1346)	RDH We have a Mater and Slave set up for aMonitoringSystemon our facility, with a CPU314C-2DP as the Master and 2 ET200M's as theSlave units. Our facility was struck by lightning a few nights ago and the master lost comm's with the slave units. I changed out the slave units and one have come back up ok but the otheris sitll not communicating the the master. I have since checked all the cabling (copper wire), checked the connectorsand also changed out the Master unit, Still not working. Does anyone have any ideas on how to fix this issue? Hello, The moral of story and all other similar stories is improper grounding of the plant.PROFIBUS DP doesn't not have a robust and strange physical layer.A driver for RS485 and some elements to reduce adverse effect of high frequency on data transmission.They can be easily damaged! I remember neumerous cases in power distribution systems with improper grounding and adverse effect of electromagnetic fields there and lightening in the worst case. They only change the damaged slaves and OLMs with new one and after a test in a shop most of them were mamaged! I sugget the same,Change them with new one and test them in a test set-up (with a module or a dummy module).If you don't have a test CPU,Try it with a PROFIBUS DP master simulator.Finally, contact your lokal SIEMENS representative for more help regarding repairing the modules! Best regards, Hamid Hosseini
	Last edited by: hdhosseini at: 5/17/2014 2:36 PM Last edited by: hdhosseini at: 5/17/2014 2:12 PM Demo Channel on Youtube
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users metwally mustafa S7 AUTOMAN RDH

5/17/2014 2:14 PM	Rate (1)
H-H Platinum Member Joined: 7/2/2008 Last visit: 3/14/2023 Posts: 928 Rating: (303)	HelloRDH, Have you changed the DIP switched on the second ET200M according to its DP address in the HW config.? Could you connect your PG/ES/Notebook to the Profibus network and detect the accessible nodes? Can you take the IM153 out of the rack (i.e. split the IM153 aside of IO modules)and test the network? Best regards, H-H

Suggestion To thank Quote Answer
This contribution was helpful to 4 thankful Users hdhosseini metwally mustafa Ste39 RDH

5/17/2014 7:27 PM	Rate (0)
metwally mustafa Silver Member Joined: 10/10/2010 Last visit: 5/26/2023 Posts: 299 Rating: (14)	try to rplace the module it's defective

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users RDH

5/18/2014 3:32 AM	Rate (0)
RDH Posts: 3 Rating: (0)	Hi H-H, I set the DIP switches to the same as the ones that they replaced. I have connected theLaptop top the network with the MPI adaptor and I can only see 2 nodes, the master and one one on the slave nodes, when I try to get the module information it says that it can not detect it (see attachment). I have also tried just the network with all the IO modules and still the same issue, I also took the one that I got working and put it in the place os the one that was not (I changed the DIP switches accordingly), and still it get the same outcome. Best Regards, RDH Attachment Z:\Rig ET files\ET\Monitoring System\Monitoring System Fault 16-5-2014\Radio Room.jpg (53 Downloads)
RDH Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

5/18/2014 6:17 AM	Rate (1)
hdhosseini Diamond Member Joined: 1/28/2009 Last visit: 6/9/2023 Posts: 6805 Rating: (1346)	RDH Hi H-H, I set the DIP switches to the same as the ones that they replaced. I have connected theLaptop top the network with the MPI adaptor and I can only see 2 nodes, the master and one one on the slave nodes, when I try to get the module information it says that it can not detect it (see attachment). I have also tried just the network with all the IO modules and still the same issue, I also took the one that I got working and put it in the place os the one that was not (I changed the DIP switches accordingly), and still it get the same outcome. Best Regards, RDH Hello, You changed the master station and slave station and still have problem on one of the slaves, right?Have you changed the connectors/cables to test? This time try to reduce the baud rate for test only and check the result.Please also consider connectors as potential source of problem as their behavior may vary by frequency and continuity test doesn't suffice to conclude the operation. Note:Channging slave addresses(via DIP switch) is normally effective after a module re-start, I hope this helps! Hamid Hosseini
	Last edited by: hdhosseini at: 5/18/2014 6:18 AM Demo Channel on Youtube
Suggestion To thank Quote Answer
This contribution was helpful to 4 thankful Users IBN-Service Ayman Elotaify H-H RDH

5/20/2014 2:04 AM	Rate (0)
RDH Posts: 3 Rating: (0)	Hi, Thanks to the people that posted on this issue, I have managed to sort it out. It was the connector on the master unit. Cheers, RDH.
RDH Posts: 3 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users hdhosseini

5/20/2014 10:07 AM	Rate (0)
hdhosseini Diamond Member Joined: 1/28/2009 Last visit: 6/9/2023 Posts: 6805 Rating: (1346)	RDH Hi, Thanks to the people that posted on this issue, I have managed to sort it out. It was the connector on the master unit. Cheers, RDH. Hello RDH, Thank you for your feedback.There is still a pending fact at your factory.I strongly recommend to revise your grounding policy and asking an Expert in this field for more tips and modifications.The elementary task of ground system is to save properties and module in case of fault.The problem still exists in your system and with the next fault, you also should change too modules. With the current system, your SIEMENS local sales office will the happiest Best regards, Hamid Hosseini
	Last edited by: hdhosseini at: 5/20/2014 10:11 AM Demo Channel on Youtube
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users RDH

5/20/2014 11:05 PM	Rate (0)
Mostref Bronze Member Joined: 1/17/2010 Last visit: 5/4/2023 Posts: 77 Rating: (5)	I do beleive that profibus network termination is very important. Profibus cabling must be properly terminated in order to stop reflections on the cable that can corrcupt telegrams and lead to communication problems. Each segment should be terminated at the two ends and nowhere else. A common problem is when the last node is powered down or unplugged. So I highly recommend the use of an external termination resistance wich powered separately. Reference number for the termination resistance 6ES7972-0DA00-0AA0 Good luck.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users RDH

|

Share this page:

Share this page on...

Follow us on