AB Devicenet Troubles

rorye

Member
Join Date
Nov 2006
Location
U.P. of Michigan
Posts
1
I just signed up to ask about some troubles we were having with an AB Devicenet system. I spent about 15 hours on this machine with another guy before we finally found the problem. Two things we found that fixed it - A 3' Devicenet cable that was built wrong and had the shield clamped in the end connectors so it was seeing a ground, (I think this was actually the shortest cable on the whole network!), and the V- was not tied to ground. Once we corrected these problems, everything ran perfect. So, shield grounding and V- grounding only in one spot very important!
 
simple wiring is key factor in networking but when wiring is faulty or not done correctly, it can be hell of a job to find the problem. to make troubleshooting faster and easier it is good idea to connectorize everything or at least network segments.
 

Similar Topics

Hi, I am looking to migrate some of our Electronic Overloads off of a Troublesome Devicenet Segment. Is there any documentation confirming the...
Replies
5
Views
88
We've run into an old system that we are upgrading which is still running Steeplechase with Citect using Devicenet to Wago. I had some experience...
Replies
4
Views
146
Sigh, DeviceNet noob... I have a 1756-L55, with a DeviceNet module, and 10 PF700 all commanded with DeviceNet. One of the PF700's blew up...
Replies
3
Views
133
Good day Forum Members I got a older Lincoln welder and hoping to make it work at our shop. Welder in question is the Lincoln Power Wave 455M...
Replies
4
Views
207
Hello Friends We have 10 Powerfocus 4000 with DeviceNet, We need to backup the configuration, the Powerfocus is detected but as unrecognized...
Replies
0
Views
106
Back
Top Bottom