I've been trying to troubleshoot a DLR network for the past month with some forward progress, however I've exhausted all of the things to try that dont require downtime. This is a new installation down in mexico and here is some "useful" information that I can supply:
We are getting ring faults about once or twice a day, which isnt localized. Many times the faults are shutting the line down because it is dropping out a section of the ring, not just a single point ring fault.
The ring consists mostly of 294e armorstarts and a few Point IO with a safety module in it.
There is a group of 3 armorstarts at the far end of the ring all within 1-2ft from eachother and the middle drive is receiving most of the media errors (FCS, alignment, mac transmit, and mac receive errors), the drives next to it are getting a few errors but not to the extent the middle drive gets.
The motors are about 5ft away from the drives with shielded Belden VFD cable with the shields terminated on both sides.
I hooked up a scope from the ethernet shield to the conveyor structure to see if there was any noise being induced into the ethernet cables and found that there is one drive that has lots of noise, but it is the drive next to the one with all the errors.(it was about 20v peak, before we shielded both ends of the cable, then it dropped to 10v. The Armorstart housing ground terminal is at the same potential as the ethernet shields.)
Before I start going off on all the details of **** I tried Im wondering if you get media errors on a certain node does that mean the data is getting corrupted inbetween that node and the next? or could the data be getting corrupted somewhere else on the ring and the other nodes before it just pass it along if its not their IP address? I havent found any useful information on the method on how data gets transfered throughout the network at the most basic level and how/when it determines if there are errors in the packets?
Any information would be great! There are still many "bad practices" left from the install but nothing sticks out as a potential problem.
We are getting ring faults about once or twice a day, which isnt localized. Many times the faults are shutting the line down because it is dropping out a section of the ring, not just a single point ring fault.
The ring consists mostly of 294e armorstarts and a few Point IO with a safety module in it.
There is a group of 3 armorstarts at the far end of the ring all within 1-2ft from eachother and the middle drive is receiving most of the media errors (FCS, alignment, mac transmit, and mac receive errors), the drives next to it are getting a few errors but not to the extent the middle drive gets.
The motors are about 5ft away from the drives with shielded Belden VFD cable with the shields terminated on both sides.
I hooked up a scope from the ethernet shield to the conveyor structure to see if there was any noise being induced into the ethernet cables and found that there is one drive that has lots of noise, but it is the drive next to the one with all the errors.(it was about 20v peak, before we shielded both ends of the cable, then it dropped to 10v. The Armorstart housing ground terminal is at the same potential as the ethernet shields.)
Before I start going off on all the details of **** I tried Im wondering if you get media errors on a certain node does that mean the data is getting corrupted inbetween that node and the next? or could the data be getting corrupted somewhere else on the ring and the other nodes before it just pass it along if its not their IP address? I havent found any useful information on the method on how data gets transfered throughout the network at the most basic level and how/when it determines if there are errors in the packets?
Any information would be great! There are still many "bad practices" left from the install but nothing sticks out as a potential problem.