7/19/00

v 1.0

GM-CCRW
DeviceNet Troubleshooting Guide
This manual is written for people who have familiarity with the DeviceNet specification. This is a brief version of a
more detailed troubleshooting guide, which is in the process of being written.
Most DeviceNet troubleshooting can be accomplished with three tools. The tools are a Digital Voltage Meter
(DVM), the DeviceNet Detective, and RSNetworx for DeviceNet. These tools will help you locate the cause of
network problems using basic troubleshooting techniques and aid you in repairing the network in a short time.
Many problems can be found with the DVM as long as its used properly. Here are some basics to keep in mind
while using a DVM.
Always keep the same reference point when making measurements. This allows you to trace wiring problems and
find grounding problems. If you put the black lead on the Earth ground point, make sure you always use the same
point and the same lead. When checking resistance (from the open shield to the Earth ground point or any other
resistance check) you cannot have less than 0 ohms. If you get a - ohm value, its likely that you have voltage
on the ground, or on the wire you are checking. If your system is powered up, start by checking voltage first, then
resistance. Remember, you can not have less than 0 ohms.
You will encounter two general types of DeviceNet network when troubleshooting. Determining which type you are
dealing with will help to focus your troubleshooting techniques. The first type is a new DeviceNet network that has
never been online. The second is a DeviceNet network that has functioned, but now has an intermittent or
continuous failure(s). In either situation, having the proper documentation which details how the network is cabled
and how the power is run is key to finding and fixing the system in the shortest time.
Here are five of the best troubleshooting rules that we have found which work on any problem:
1.
2.
3.
4.
5.

Never assume (never assume the network is wired properly, never assume the documentation is correct,
never assume that the tags are correct, etc.).
If something is not working, be sure the device has power, air, water, etc.
Have the proper documentation for the unit or system you are working on.
Have the right software and/or firmware revisions.
If you have worked on a problem for 45 minutes and have had no progress, it is time to ask for help, or start
over using a different approach.

When working with a new network that will not operate, always remember to check the basics (which are in the
DeviceNet specifications). Wiring the system properly is the key to preventing problems in the future.
1.

2.
3.

4.

Physically check the entire network. Verify all cable lengths and make sure all connections are tight. Be
sure that you have 121-ohm terminating resistors at each end of your network. (Two of the most common
problems are drop lines over 20 feet and excessively long trunk runs with voltage drop). If your nodes
have visible dipswitch selectable settings, verify that address and baud rates are properly configured.
Use the DVM to do some basic voltage and resistance checks. Start by checking for voltage on the shield.
If you find a voltage greater than 10mV dc on the shield cable, you need to determine the source of the
voltage and remove it in order to perform accurate resistance tests.
Power down the network. Verify that CAN H or CAN L are not shorted together or to the shield.
Occasionally pre-molded cables, tap boxes, and even nodes come from the factory with shorts. A voltage
can be induced on the network from outside sources (through Earth ground in a welding environment for
example).
If the cable and nodes check out, the next step is to check the grounding circuit. Many problems have to do
with improper grounding or the way flex I/O power is run. In the main control box for the system, find the
one wire (see Diagram 1) that connects shield to Earth ground and disconnect it. Ground loops are a
major source of DeviceNet network crashes.

file: 301788249.doc

Pg 1 of 5

7/19/00
v 1.0

GM-CCRW
DeviceNet Troubleshooting Guide
Main Control Panel

Main Control Panel

DNet Scanner
Module

DNet Scanner
Module

PLC Rack

DNet Power
Supply

PLC Rack

Aux. Power
Supply

-V

DNet Power
Supply

-V

Shield Wire

Digital
Voltage Meter

Aux. Power
Supply

-V

-V

Shield Wire

COM

Ground Bar

Ground Bar

Fig A

Fig B

Diagram 1.
Causes of ground loops on network nodes
Some nodes have a 1M-ohm resistor connected from shield to the nodes case. When you check the
resistance from shield to Earth ground for the network, you will discover this. If more than one node has a
1M-ohm resistor, you can calculate the expected resistance value using Ohms law for resistors in parallel
connections.
Some nodes may have a Snubber circuit (circuit that is designed to protect the component in question from
high frequency noise) from shield to case. If true, you will measure voltage on shield. If V- on the
DeviceNet power supply (when using multiple DeviceNet power supplies, be sure that all of the V-s are
tied together) is tied to Earth ground, you will measure different resistance values on nodes with Snubber
circuits. Because the Snubber circuit has an active component, you will get different resistance values with
nodes in parallel and/or distances in cable length. In these instances, you may have to disconnect Snubber
nodes from the network in order to conduct an accurate check of the system. If you measure more than
20k-ohm, you do not have any ground loops. If you get less than 20k-ohm, segment the network in order to
find the potential ground loop.
Cabinets with flex I/O are a common source of ground loops. Check these cabinets first to verify that the
network shield is not connected to Earth ground. To protect the shield, some build shops put black shrinkwrap on it, then end up transposing shield and V-. Tap boxes are another common source of ground loops.
Another source of potential problems comes with Auxiliary. power sources. Some devices require an
additional power supply to power their communication interfaces. When the Aux. power supply is briefly
overloaded (one example is firing eight valves at the same time), the voltage drop could cause a node to
reset or go bus off.
5

If the network is properly grounded, verify that the V- on the DeviceNet power supplies (if more than one
supply is used on the network in question) are tied together. This is the reference for CAN H and CAN L.
On a small network, you may not see problems, but numerous CAN frame errors can be created on a large
network as a result of having a multiple reference points for V-.

file: 301788249.doc

Pg 2 of 5

7/19/00
v 1.0

GM-CCRW
DeviceNet Troubleshooting Guide
These steps should help you to find any media errors that the network may have. Once the network has been
checked, power the system up and check to see if the nodes come up.
At this point, with Earth ground is still disconnected, a few more tests can be conducted.
If the network has nodes with Snubber circuits (remember to check voltage first, to insure that you have less than
10mV), the resistance values you measure may be different. Measure the voltage between shield and Earth ground
(anything greater than 10mV dc is a problem). Disconnect one node at a time until the voltage drops below 10mV
dc. Verify that the 5 DeviceNet wires are connected properly. Now do resistance checks on the node.
1) Resistance between CAN H and V+ should be 1M 4M ohms
Resistance between CAN H and V- should be 1M 4M ohms
Resistance between CAN L and V+ should be 1M 4M ohms
Resistance between CAN L and V- should be 1M 4M ohms
2) Resistance between V+ and V- should be 1M-ohm or greater (some nodes have an active over voltage
protection device or voltage regulator between V+ and V- you will read the resistance between 4k-ohm
and 20k-ohm).
3) Shield to case should be 1M-ohm or greater.
4) V- to shield should be open (if there is a Snubber circuit, value should be greater than or equal to 2Mohm).
Reconnect the shield to Earth ground.
After completing the above tests, physically inspect each node. Check the node status light to verify that each node
is functioning properly. If a status light indicates that a particular node is BUS off, verify that the address and baud
rates are properly configured (incorrect addresses/baud rate settings are common problems which prevent networks
from coming up properly). (GM requires that all manufacturers provide dipswitch selectable address and baud rates.
This reduces debug time and makes it easier for plant floor electricians to change out a malfunctioning node).
Now, check DeviceNet power. Remove the terminating resistor at one end of the network. Measure across V+ and
V-. If the value is 20Vdc or greater, you have adequate power for the network. If the value is less than 20Vdc, the
node will still function, but the I/O attached to it may have problems. Remember that the trunk cable is an LCR
circuit. If you have a node at the end of the trunk cable that needs current, you may need to install an additional
power supply. Replace the resistor and move to the other end of the network. Remove the other terminating resistor
and repeat the above measurement.
At this point, the network should be up and running. If there is still a problem, you will need to use a
diagnostic/debugging tool such as the DeviceNet Detective and/or RSNetworx for DeviceNet. These tools will
allow you to plug into the network and inspect various data. It is always a good idea to install an extra tee in the
trunk of the network in an easily accessible location. The extra tee can be used as a Diagnostic port where various
diagnostic devices can be attached to allow you to monitor the network.
RSNetworx for DeviceNet is a software package that can be installed on any PC. You can monitor a DeviceNet
network in real-time which can aid you in diagnosing problems you may encounter. In order to get full use of the
RSNetworx for DeviceNet, you need to have an Electronic Data Sheet (EDS) file for each component in the
network. These files are installed on the hard drive of your PC. The EDS files need to be the same revision level as
the device used on the network that you are inspecting. Also, the EDS file should be detailed, to allow you to use
the full diagnostic capabilities of each component (Basic and/or generic EDS files are not acceptable).
The DeviceNet Detective is a hand held diagnostic tool. It can be connected to the Diagnostic tee of the network
that you are troubleshooting and can quickly allow you to determine the health of the network bus, which can be
found on the diagnostics page.
Use the DeviceNet Detective (or an oscilloscope) to view CAN H and CAN L voltages. Start by measuring CAN H.
You should measure values between 3Vdc and 4Vdc. CAN H should not sink below 2.2Vdc or peak above
4.65Vdc. Now measure CAN L. CAN L should have values that range between 1.5Vdc and 3.5Vdc. If you
measure values outside of this nominal range, you should re-check trunk cable lengths and drop cable lengths. You
file: 301788249.doc

Pg 3 of 5

7/19/00
v 1.0

GM-CCRW
DeviceNet Troubleshooting Guide
may have a node with a bad transceiver. To find the node with a bad transceiver, disconnect one node at a time
while monitoring the CAN voltages. When the average voltages step up by 0.5Vdc, you have found the node with
the malfunctioning transceiver. Replace the node, and see if this change improves the network up time. It is
possible for a node to have a bad transceiver and still function on the network, but to cause CAN frame errors, or to
diminish the CAN signal strength.
The DeviceNet Detective maintains a count of CAN frame errors. This number will let you know how good or bad
your network is. To locate the cause of the CAN frame errors, you should monitor the process of your operation.
Do you see CAN frame errors when a certain operation occurs (during MIG or spot welding, or when
starting/stopping a VFD drive)? If so, you most likely still have a grounding problem. In addition the method used
above (using a DVM), you can use an oscilloscope to locate the source of your problem.
Start by using a cheater plug to float the oscilloscope (three prong 110 Vac adapter plug with ground pin removed,
see Diagram 2). On a weld tool with a base and turntable, attach the ground lead (typically black) to the base and
the other lead (typically red) to the turntable. While welding, monitor the oscilloscope. If you have more than 2V
peak to peak of weld noise, the ground on that tool is insufficient. That noise will find its way onto the DeviceNet
network and cause problems.

Typical MIG Weld Tool Turntable

DVM
(Used to check
resistance)
MIG Welding
Robot
COM

Tool

GND

Base

Tool End Cable

Building Steel

Oscilloscope
Test Lead

2
1
0

BNC

Unacceptable
(Greater than 2 Vp-p)

1
2

Cheater Plug

1
0

Acceptable
(Less than 0.5 Vp-p)

110 Vac

Diagram 2.
The DeviceNet Detective can also find intermittent cable or node problems (or help you by pointing you in the right
direction). Start by scanning the network. Go to the message traffic mode and leave the Detective plugged in for
a while (at least 2 hours). Check the error counter. If you see errors spread throughout the network, you have a
media problem (bad cable or ground loop). If the errors occur on one node (or a group of nodes on a drop), you will
have a good indicator where the problem is located.

file: 301788249.doc

Pg 4 of 5

7/19/00
v 1.0

GM-CCRW
DeviceNet Troubleshooting Guide
These are tests that were developed through practical experience while troubleshooting different DeviceNet
networks. It is a starting point that should get you moving in the right direction when you troubleshoot a DeviceNet
network. The results you get may have small variations from the ones listed here. If you find significantly different
information while troubleshooting/debugging, or if you develop any helpful troubleshooting techniques, please send
a detailed e-mail to one of the people listed below so that your information may improve and enhance the usefulness
of this document.
Erick.W.Rudaitis@gm.com
Steve.Scheller@gm.com
Gary.C.Workman@gm.com

file: 301788249.doc

Pg 5 of 5