`

GCCS-2
Global Common Control Software Design
LMS # 33544
Document Version 6.0

Module 12: RSNetworx and DeviceNet

 DOCUMENT MANAGEMENT INFORMATION

Sponsoring Group:

Manufacturing Engineer: Noel Miller

ME Engineering Group: GM Vehicle Systems-Automation Standards
Manufacturing Engineer Phone: 810-602-9768

Template Version 1.0

Document Revisions:
Date Revision By Revision History
Updated graphics. Synchronized DeviceNet
8-26-13 5.0 J. Hocking
to consistent examples.
Synchronized to G16 with Powertrain and
7-9-15 6.0 J. Hocking
EtherNet I/O

This training is based on the Global Common Software Design Standards, GCCS-1.
Please refer to the GCCS-1 manual found on the “GM intranet” or
www.gmsupplypower.com. The GCCS-1 manual is comprehensive and will have the
latest information. This training manual is used as an instructional guide.
 Copyright Information
Copyright General Motors Company, 2015, Detroit, Michigan. All rights reserved under
U.S., International, and Universal Copyright Conventions. Published in the United
States of America. These materials may be used only with related printed materials.
In no event will the General Motors Company be responsible or liable for
incidental or consequential damages resulting from the use or application of the
materials in this manual.
The examples, diagrams, and charts in this manual are included solely for illustrative
purposes. Because of the many variables and requirements associated with any
particular safety situation, the General Motors Company expressly disclaims all
express and implied warranties relating to the materials in this manual, including
all examples, diagrams, and charts.
Reproduction of the contents of this manual, in whole or in part, without written
permission of the General Motors Company, is prohibited.

© 2015 General Motors Company. All Rights Reserved

i
 Table of Contents
12. RSNetworx & DeviceNet ............................................................... 12-1
12.1. Objectives ........................................................................................................ 12-1
12.2. DeviceNet Limitations in GCCS-1 .................................................................. 12-2
12.3. EDS Files for DeviceNet Devices ................................................................... 12-3
12.3.1. Registering an EDS file in RSNetworx .................................................... 12-3
12.4. Creating an RSNetworx .DNT Configuration File ......................................... 12-9
12.5. Configuring a Device .................................................................................... 12-16
12.6. The DNB Scanlist .......................................................................................... 12-19
12.7. Downloading the Configuration to the DNB ............................................... 12-27
12.8. Uploading Parameters from a Device ......................................................... 12-28
12.9. Uploading the Entire Network ...................................................................... 12-29
12.10. Replacing a Node on the DeviceNet Network ........................................... 12-30
12.11. Certifying the Network ................................................................................ 12-30
12.12. Troubleshooting a DeviceNet Network ..................................................... 12-31
12.12.1. Bus Errors ........................................................................................... 12-32
12.12.2. Bus Traffic........................................................................................... 12-35
12.12.3. Bus Power .......................................................................................... 12-35
12.12.4. Shield Voltage ..................................................................................... 12-36
12.13. Common Mode Voltage .............................................................................. 12-37
12.14. CANH/L Differential Voltage (Recessive – Data 1) ................................... 12-37
12.15. CANH/L Differential Voltage (Dominant – Data 0) .................................... 12-37
12.16. Exercise 1: Configure the DeviceNet Scanlist .......................................... 12-38
12.17. Review.......................................................................................................... 12-39

© 2015 General Motors Company. All Rights Reserved

ii
 Table of Figures
Figure 1: Node Limitations on DeviceNet.................................................................. 12-2
Figure 2: Using the EDS Wizard in RSNetworx for DeviceNet .................................. 12-3
Figure 3: Register an EDS File – Descriptions & Definitions..................................... 12-4
Figure 4: Select EDS File to Register ....................................................................... 12-4
Figure 5: Select EDS File to Register - Descriptions & Definitions............................ 12-4
Figure 6: EDS File Installation Test Results .............................................................. 12-5
Figure 7: EDS File Installation Test - Description & Definition .................................. 12-5
Figure 8: Change Graphic Image .............................................................................. 12-6
Figure 9: Change Graphic Image - Descriptions & Definitions .................................. 12-6
Figure 10: Select a New Graphic Image (Icon) ......................................................... 12-7
Figure 11: Select a New Graphic Image (Icon) - Descriptions & Definitions ............. 12-7
Figure 12: EDS Wizard is Complete ......................................................................... 12-8
Figure 13: EDS Wizard is Complete - Description & Definition ................................. 12-8
Figure 14: RSNetworx for DeviceNet ........................................................................ 12-9
Figure 15: Open Network Properties window .......................................................... 12-10
Figure 16: Set Online Path...................................................................................... 12-10
Figure 17: Select the Correct DeviceNet Network Path .......................................... 12-11
Figure 18: Scanning all Nodes on Network ............................................................. 12-12
Figure 19: Scanning All Nodes on Network - Descriptions & Definitions................. 12-12
Figure 20: Network Scan Complete – All Nodes Found .......................................... 12-13
Figure 21: Saving a DeviceNet Network File .......................................................... 12-14
Figure 22: Naming the DeviceNet Network File ...................................................... 12-14
Figure 23: Enter the *.dnt File Name....................................................................... 12-15
Figure 24: Siemens ET200S Communication Adapter Properties .......................... 12-16
Figure 25: Siemens ET200S Communication Adapter - Descriptions & Definitions 12-16
Figure 26: Upload or Download Decision................................................................ 12-17
Figure 27: Siemens ET200S Communication Adapter - Descriptions & Definitions 12-17
Figure 28: Siemens ET200S Adapter Parameters .................................................. 12-18
Figure 29: Siemens ET200S Communication Adapter - Descriptions & Definitions 12-18
Figure 30: Opening the Scanlist .............................................................................. 12-19
Figure 31: Accessing Scanner Properties - Descriptions & Definitions ................... 12-20
Figure 32: DNB Properties in RSNetworx ............................................................... 12-20
Figure 33: DNB Properties in RSNetworx - Descriptions & Definitions ................... 12-20
Figure 34: Upload from DNB to RSNetworx ............................................................ 12-21
Figure 35: Move Devices from Available Devices to Scanlist ................................. 12-22
Figure 36: Move Devices from Available Devices to Scanlist - Descriptions & Definitions
................................................................................................................................. 12-22
Figure 37: All Available Devices Added to Scanlist ................................................. 12-23
Figure 38: Changing the I/O Parameters for a Configurable Device ....................... 12-24
Figure 39: Edit I/O Parameters for a Configurable Device ...................................... 12-24

© 2015 General Motors Company. All Rights Reserved

iii
Figure 40: Individual Device I/O Mapping into DNB ................................................ 12-25
Figure 41: Using AutoMap to Map the I/O for Each DNB Node .............................. 12-26
Figure 42: Using AutoMap to Map the I/O for Each DNB Node - Descriptions &
Definitions ................................................................................................................ 12-26
Figure 43: Click OK or Apply at Any Time to Download to the DNB ....................... 12-27
Figure 44: Upload Individual Node Settings ............................................................ 12-28
Figure 45: Upload all Parameters from the Entire Network ..................................... 12-29
Figure 46: Upload All Parameters from the Entire Network .................................... 12-29
Figure 47: NetAlert NetMeter for DeviceNet (P/N : DN-MTR) ................................. 12-31
Figure 48: Example DeviceNet Network with Bus-Off Condition or Error Traffic..... 12-32
Figure 49: Terminators Moved in to DNB................................................................ 12-33
Figure 50: One Terminator Moved to Original Location .......................................... 12-33
Figure 51: Terminator Moved to First Tee on Troubled Half ................................... 12-34
Figure 52: Terminator Moved to Next Tee on Troubled Half ................................... 12-34

© 2015 General Motors Company. All Rights Reserved

iv
12. RSNetworx & DeviceNet
12.1. Objectives
1. The student will be able to define a DeviceNet network.
2. The student know how to troubleshoot a DeviceNet network.
3. The student will be able to use RSNetworx to configure the DeviceNet
network.
4. The student will be able to develop a DNB scan list.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-1
12.2. DeviceNet Limitations in GCCS-1
• The defined baud rate for DeviceNet in GCCS-1 is 250k in all PLC applications.
Refer to the proper GM Robot Specifications for the speed of the network
between the robot and the end of arm tooling.
• In GCCS-1, the DeviceNet scanner in the MCP is always assigned Node 0 or
Node 1.
• DeviceNet allows for 64 total nodes on a network. However, GCCS-1 allows
fewer nodes on the network, as shown in Figure 1. These node limitations are
due to design considerations such as maximum network length, network
troubleshooting, cumulative drop length, and available bandwidth.

Area Maximum Maximum Total Nodes

Safe Nodes
Bodyshop 10 20
Conveyors 15 30
Paint 15 30
General Assembly 10 20
Press 10 20
Figure 1: Node Limitations on DeviceNet
• Node number 62 is never used in GCCS-1.
• Nodes should never be assigned to Node number 63; this is the default node
number for nodes that have a software selectable node number.
• If a DeviceNet network is longer than the maximum distance of 820ft at 250k
Baud, a repeater must be placed into the network such that the repeater B
network begins at a distance of no more than 820ft from the scanner.
• A maximum of one repeater is allowed per DeviceNet network.
o A Repeater does not count as a node.
o Does not change the maximum node limits.
• If the network has more than the number of nodes shown in Figure 6 above, an
additional DeviceNet network should be used.
• Overloading of the network with too many nodes will cause the safety nodes to
have connection problems and the safety system to fail to a safe state.

12-2 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.3. EDS Files for DeviceNet Devices
Each type of DeviceNet device requires an EDS file registered in RSNetworx to work
properly. EDS files are simple text files used by network configuration tools such as
RSNetworx to help identify products and easily commission them on a network. EDS
files describe a product's device type, product revision, and configurable parameters on
a DeviceNet network. Allen Bradley devices are already registered with RSNetworx by
default. EDS files for the devices typically used by GM MAAC are included with each
GCCS-1 release in the Software directory.

12.3.1. Registering an EDS file in RSNetworx

Figure 2: Using the EDS Wizard in RSNetworx for DeviceNet

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-3
 Item Description Definition
1 EDS Wizard Select the EDS Wizard from the Tools menu.
2 Welcome Screen Read Wizard tasks and click Next.
3 Register an EDS Select to register a single EDS file or a directory of
file(s) EDS files.
4 Next Proceed with the option selected.
Figure 3: Register an EDS File – Descriptions & Definitions

Figure 4: Select EDS File to Register

Item Description Definition

1 Register a single file. Selection will register one EDS file.
2 Register a directory of Selection will register an entire directory of
EDS files. EDS files.
3 Browse Browse for the desired directory or file.
4 Look in subfolders Select the Look in Subfolders check box
to include subfolders in the registration.
(Enable after browsing for a directory of
EDS files.
5 Next Continue the registration process.
Figure 5: Select EDS File to Register - Descriptions & Definitions

12-4 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 Figure 6: EDS File Installation Test Results
From the EDS File Installation Test Results screen, click Next to continue.
To change the icon, if required, click the desired file in the installation results list.
Then click Next to change to a different icon.

Item Description Definition

1 Next Continue from EDS File Installation Test Results.
Figure 7: EDS File Installation Test - Description & Definition

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-5
 Figure 8: Change Graphic Image

Item Description Definition

1 Current Select device to change icon.
Icon
2 Change Click to open a selection of available images
icon (optional).
3 Next Continue from Change Graphic Image. Click Next
if the graphic image is OK for the device.
Figure 9: Change Graphic Image - Descriptions & Definitions

12-6 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 Figure 10: Select a New Graphic Image (Icon)

Selecting a new graphic image is optional.

Item Description Definition

1 Select Icon Select a new icon (graphic image) for the device.
2 Browse Click Browse to search for an icon on the
computer.
3 OK Accept the new icon.
Figure 11: Select a New Graphic Image (Icon) - Descriptions & Definitions

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-7
 Figure 12: EDS Wizard is Complete

Item Description Definition

1 Finish Click to close the EDS Wizard.
Figure 13: EDS Wizard is Complete - Description & Definition

Note: EDS files need only be registered once per computer. RSNetworx will
automatically recognize the devices the next time it is used.
The graphic image (icon) representing the device can be changed from the EDS
Wizard as a separate task or while registering the EDS file for a single device.

12-8 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.4. Creating an RSNetworx .DNT Configuration File
1. Begin by opening RSNetworx for DeviceNet.
2. Click the Online button, when working from a new file or to use the current
Online path.

Figure 14: RSNetworx for DeviceNet

Note: It may be necessary to change the Online Path. See steps 3-5.
3. Click the Network menu.
4. Select Properties. See Figure 15.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-9
 3

Figure 15: Open Network Properties window

5. Click the Set Online Path button.

Figure 16: Set Online Path

6. Click on the DeviceNet Network that is under the desired scanner module.
7. Click OK.

12-10 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 6

Figure 17: Select the Correct DeviceNet Network Path

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-11
 1

2
3

Figure 18: Scanning all Nodes on Network

Item Description Definition

1 OK Click OK on the advisory screen;
(Configuring online devices requires first an
upload or download).
2 1756-DNB/A The DeviceNet scanner module is first to
Node 0 appear once the online scan begins.
3 Graph Display In the Graph view, this line is populated with
Line devices that RSNetworx for DeviceNet
detects when scanning.
4 Browsing Network Indicates DeviceNet Network browsing (node
window scanning) progress.
5 Cancel Click to terminate the active scan.
Figure 19: Scanning All Nodes on Network - Descriptions & Definitions

12-12 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 RSNetworx will scan all of the nodes on the network as shown in Figure 20 and
display them on the screen. If a node is not displayed on the screen, it may be
set with a duplicate address or it may be set with an incorrect baud rate. Devices
with node addresses that are software configured only must be connected to the
network one-at-a-time until the addresses have been set.

Figure 20: Network Scan Complete – All Nodes Found

Important: Verify against the drawing that all nodes in the network are
represented in the completed online scan.

Once the network scan has been started a *.dnt network file can be saved. As
configuration of the network continues, the file can be saved again at any time.
Use the following procedure to save a *.dnt file:
1. Click File.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-13
 2. Click Save. See Figure 21.

Figure 21: Saving a DeviceNet Network File

3. Enter the name of the file; AA110DNet06.dnt in this example.
When saving the DeviceNet network, the format is a combination of the MCP or
controller name followed by the DNet and finally the slot where the DeviceNet
scanner resides.
Note: Some upper level systems have limited characters available. The name
format BA_AB030B01DNet06 may be necessary.

BA_AB030B01DNet06

PLC DeviceNet DeviceNet

Name network scanner
identifier Slot

Figure 22: Naming the DeviceNet Network File

12-14 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 4. Click Save. See Figure 23.

3 4

Figure 23: Enter the *.dnt File Name

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-15
12.5. Configuring a Device
Certain devices may need to be configured inside RSNetworx. The Siemens ET200S
Point IO module is a flexible I/O module that consists of a communication module and a
variable amount of input and output cards.

Figure 24: Siemens ET200S Communication Adapter Properties

Item Description Definition

1 Siemens Icon Double click the device icon to open the
Properties window.
(200S Adapter)
2 General Tab General information for the device.
3 Parameters Tab Select to view parameters.
Figure 25: Siemens ET200S Communication Adapter - Descriptions & Definitions

12-16 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 1 2 3

Figure 26: Upload or Download Decision

When the software and device do not match, the user will be prompted to upload or
download the configuration or settings.

Item Description Definition

1 Upload Uploads the configuration of the device.
2 Download Downloads the settings in RSNetworks
software to the device.
3 Cancel Closes the Properties window.
Figure 27: Siemens ET200S Communication Adapter - Descriptions & Definitions

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-17
 1
2
3

Figure 28: Siemens ET200S Adapter Parameters

Item Description Definition

1 Data Input Size Write this number down. It will vary depending
on the I/O connected to the adapter module.
2 Data Output Size Write this number down. It will vary depending
on the I/O connected to the adapter module.
3 Operating Mode Set to Auto Config Mode.
4 I/O Status Byte Set to Enable.
Enable
Figure 29: Siemens ET200S Communication Adapter - Descriptions & Definitions

12-18 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
Important: Always ensure the module is in Auto Config Mode and the I/O Status Byte
is Enabled. Write down the Data Input Size (Item 1) and the Data Output Size (Item 2)
as shown in
Figure 28. The data sizes are used in the mapping of the device into the scanner since
the .EDS file is generic. Note that the I/O size will vary with the quantity of I/O
connected to the adapter module.

12.6. The DNB Scanlist

The DNB contains a Scanlist that configures where the individual nodes map I/O in the
scanner. This ensures that the processor can easily retrieve and set the data. The
Scanlist is simply a look-up table that aligns the nodes with a memory location. The
scanner contains 124 input words (32-bit (DINTs)) and 123 output words (32-bit). In
GCCS-1 the standard for mapping device I/O to the scanner I/O Image is at
DINT[Node Number x 2]. Using this rule, each node is allowed 8 bytes of data (2-32
bit words) before it will overlap with the next node.
Example:
Node 20 maps into the DNB with a starting address of word 40.
Node 31 maps into the DNB with a starting address of word 62.

Figure 30: Opening the Scanlist

Item Description Definition

1 Scanner (Node 0) Double-click to open Properties.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-19
 Figure 31: Accessing Scanner Properties - Descriptions & Definitions

Figure 32: DNB Properties in RSNetworx

Item Description Definition

1 Scanlist Click the tab to view the Scanlist.
2 Input Click the tab to view the Input parameters for
devices in the Scanlist.
3 Output Click the tab to view the Output parameters for
devices in the Scanlist.
4 Address Node address for the displayed device.
DeviceNet (DNB) Scanner is always node 0 for
GCCS-1.
Figure 33: DNB Properties in RSNetworx - Descriptions & Definitions

Selecting the Scanlist, Input, or Output tabs will produce the Upload/Download decision
prompt as shown in Figure 34.

12-20 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
Important: When configuring a new network, like this example, the Scanlist is not
configured in RSNetworx so the proper selection is to always Upload from the DNB.

Figure 34: Upload from DNB to RSNetworx

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-21
 Figure 35: Move Devices from Available Devices to Scanlist

Item Description Definition

1 Scanlist Scanlist tab is active.
2 Automap on Add Always deselect. Does not map to GCCS-1
standards.
3 >> Click to move all Available Devices into the
Scanlist.
Figure 36: Move Devices from Available Devices to Scanlist - Descriptions & Definitions
In Figure 36 above, the list of Available Devices came from RSNetworx online browsing
the network. It is important to uncheck the “Automap on Add” checkbox (Item #2)
on the Scanlist tab. “Automap on Add” allows the scanner to automatically map in the
devices for the user when they are added to the Scanlist. However, there is no
standard as to how the nodes are mapped; they are placed into the next available
memory location. Click on the >> key to add all Available Devices to the Scanlist. At
this point, the screen should look like Figure 37.

12-22 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
.

Figure 37: All Available Devices Added to Scanlist

Most devices will be configured automatically when they are added to the Scanlist
because the .EDS file contains the correct info for RSLinx to determine parameters and
settings. Any modules that were configured in Module 12.5 will also have to be
configured at this point before mapping the I/O. After adding the devices to the Scanlist,
highlight the specific device and select the Edit I/O Parameters button as shown in
Figure 38.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-23
 Figure 38: Changing the I/O Parameters for a Configurable Device

Figure 39: Edit I/O Parameters for a Configurable Device

12-24 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
As illustrated in Figure 39, the user can input the data that was written down for the
specific device in Module 12.5. The reason this information has to be input like this is
that the .EDS file for a device such as the Siemens ET200S is generic and does not
comprehend the number of input and output cards that have been added to it in the final
configuration.
After all of the configurable nodes have the correct I/O settings, map the scanner.
In Figure 40, all of the devices are now being scanned by the DNB but the mapping of
the actual I/O is not yet complete. Continue by selecting the Input tab. Each device
that contains input data is shown.

Figure 40: Individual Device I/O Mapping into DNB

The top node window shows each device: Type of connection (polled or Change of
State (COS)), Size (in bytes), and Mapping of the current location in the DNB.
Node 10 is a Change of State Node; 3 bytes of Input data are required, and it is not
currently mapped to any real I/O in the DNB.
The easiest way to map the data for each node is to adjust the Start DWord to Node
number x 2 and click the AutoMap button. Note that this AutoMap button is different
from the AutoMap on Add checkbox on the Scanlist.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-25
 Figure 41: Using AutoMap to Map the I/O for Each DNB Node

Item Description Definition

1 Node Select a node to configure.
2 Start DWord Adjust to double the node # (this example
Node 10 = Start DWord = 20).
3 Automap Maps the node to the selected StartDword.
4 Bitmap Verify that the device is mapped to the proper
data number.
Figure 42: Using AutoMap to Map the I/O for Each DNB Node - Descriptions & Definitions

In Figure 41 above, Node 10 has been properly mapped into the DNB starting at word
20 in the DNB. In RSLogix 5000, the I/O for Node 10 on a DNB in slot 6 can now be
found at Local:6:I.Data[20]. Continue this same technique for each node in the Inputs
and Outputs until all devices have been correctly mapped.
In Figure 41, it is important to understand that using the Node number x 2 method
allows only 8 bytes in the mapping for each device. If a device contains more than 8

12-26 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
bytes (e.g. RF tag reader/writer) of data, it will utilize the data table area reserved for the
next node. Therefore, that node cannot be used by another device.
Example:
Node 10 contains 24 Bytes of Input Data. When it is mapped starting with word 20, the
data will use up a total of 6-32 bit DNB words, ending at word 25. There cannot be a
Node 11 or 12 on this network since the data location is already being used by Node 10
(Node 11 would have used word 22 and node 12 would have started at word 24).

12.7. Downloading the Configuration to the DNB

After the Scanlist has been properly configured, it must be downloaded to the DNB. To
download to the DNB, the processor in the local chassis must be in either the Program
or Remote Program Mode. Select either Apply or OK in the DNB properties window at
any time while online to download to the DNB module.

Figure 43: Click OK or Apply at Any Time to Download to the DNB

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-27
12.8. Uploading Parameters from a Device
Most nodes will not need individual configuration in RSNetworx. Examples of nodes
that do not need to be configured individually are Safe Nodes (these are configured
inside RSLogix), Prox Blocks, and Valve Stacks.
After double-clicking on a node that has configurable settings, there will be a prompt to
upload, download, or cancel as shown in Figure 44.

Figure 44: Upload Individual Node Settings

Uploading from a node brings the current configuration from the node into the
RSNetworx software. This is preferred at this point in the configuration since the data in
RSNetworx may not be up to date. After a network is completely set up, individual
nodes can be replaced and downloaded from the saved settings in RSNetworxs.

12-28 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.9. Uploading the Entire Network
Before saving the RSNetworx file, it is important to upload all settings from all of the
devices on the Network. This ensures the offline file contains all of the necessary data
to rebuild the network in the event of a device failure. While online, select Network,
then select Upload from Network.

Figure 45: Upload all Parameters from the Entire Network

Figure 46: Upload All Parameters from the Entire Network

After the network upload has been completed, save it to the computer as a .DNT file.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-29
12.10. Replacing a Node on the DeviceNet Network
Most DeviceNet nodes can be replaced by simply setting the new node to the same
address and baud rate and plugging it in. In the case of intelligent DeviceNet nodes,
the configuration may have to be downloaded to the device from within RSNetworx for
DeviceNet. Safe nodes receive their configuration from the processor and generally will
not have to be downloaded.

12.11. Certifying the Network

After the Scanlist has been properly configured and downloaded, each DeviceNet
network must be performance certified.
This certification must adhere to the standards listed on the DeviceNet buy-off sheet
located in GCCS-1i, Appendix B. This document is located on the GM MAAC website.
It is recommended that certification and troubleshooting of the DeviceNet network be
accomplished with a DeviceNet meter such as the NetAlert! NetMeter from Woodhead
Connectivity. A typical multi-meter cannot update fast enough to identify problems on a
DeviceNet network.
Any items identified by the NetMeter with either the or icons must be approved by
the GM Engineer responsible for the project.

12-30 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.12. Troubleshooting a DeviceNet Network
It is important to remember that DeviceNet is a communication network that contains
traffic on the CAN-H and CAN-L wires. Network traffic can be hard to diagnose without
the proper tools.
There are software based tools available that are good at providing the user with
information on the packets of data out on the network. The Net Meter shown below is
the size of a multi-meter, and can be plugged passively into a DeviceNet network to
diagnose issues and take measurements.

Figure 47: NetAlert NetMeter for DeviceNet (P/N : DN-MTR)

Woodhead Connectivity
50 NorthLand Road
Waterloo, Ontario
Canada N2V 1N3
(519) 725-5136
The NetMeter can be powered from either AA batteries or from the DeviceNet network.
Begin by plugging the meter into an available point in the network. It may also be useful
to take measurements at more than one place on the network, such as the farthest
distance from the power sources (typically the MCP and Power Taps).
Each selector switch setting on the NetMeter provides a different measurement of the
DeviceNet network. There are also multiple types of measurements for each item, such
as current running value, and minimum, and maximum values. The minimum and
maximum values represent the network values since the NetMeter was plugged in.
These can be reset by powering off the NetMeter and powering the unit on, or by
cycling from Run to and back to Run.
Pressing the button on the NetMeter cycles the display through each of the

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-31
different measurements available at that particular switch position.
A description of the network errors that the NetMeter can help detect is given in the
following sections.

12.12.1. Bus Errors

DeviceNet is a tolerant network that can remain functional even while error traffic
exists on the network. If a network was stable and has been verified to have no
errors but then at a later point begins to have errors, there is a high probability that
there is a media problem.
The 1756-DNB card in the Logix chassis does not give any indication that error
frames exist on the network. At a certain threshold, the number of errors will
overwhelm the DeviceNet network and the network will go offline (typically a code 91
on the DNB for Bus-Off) The NetMeter tracks data errors in real-time. Any error rate
greater than zero is undesirable in a robust DeviceNet network, even though the
network may continue to function. An error rate of greater than 10 errors per second
indicates a problem that should be investigated as soon as possible.
When a network error is Bus-Off, it is usually very difficult to continue
troubleshooting since communications to the networks are down. In this case. it is
usually easiest to begin isolating the problem section.

Figure 48: Example DeviceNet Network with Bus-Off Condition or Error Traffic
Begin isolating the trouble node or network section by moving the terminating
resistors to the scanner on the network. Then cycle the network by removing
and re-inserting the DNB in the chassis.

12-32 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 TR TR

Figure 49: Terminators Moved in to DNB

In Figure 49, both terminating resistors have been placed immediately next to the
DNB. After a cycle of the network, the scanner should no longer be in a Bus-Off
or error traffic condition. If it is, there is a problem inside this isolated network,
either with the DNB, the power supply(s), or the media.
In Figure 55, the media problem is not in this isolated network. If the scanner
resets properly and begins trying to connect to nodes, move a terminating
resistor (terminator) downstream on one half of the network back to its original
placement as shown in Figure 56.

TR

Figure 50: One Terminator Moved to Original Location

In Figure 50, the network is now divided in half. The Bus-Off or error condition
will now either be present or the network will function properly. In the example
network, the problem is on the other half of the network so there will be no errors
at this point. Continue on to the next step by moving the other terminator out to
the first tee on the network half that has been identified with the problem.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-33
 TR

Figure 51: Terminator Moved to First Tee on Troubled Half

In Figure 51 above, the terminator has been moved out to the first tee in the
problem half of the network. If the meter indicates a problem at this point, the
problem is caused by one of the devices on this tee. In the example network, the
problem is still further downstream, so the meter will still be showing no errors.
Now move the terminator downstream to the next tee.

TR

Figure 52: Terminator Moved to Next Tee on Troubled Half

In Figure 52 above, the terminator has been moved to the tee with the problem
device or cable connected to it. At this point, the network is now showing errors;
if the errors are significant enough, the network may go to a Bus-Off state. The
problem has now been identified as being connected to this tee.
Disconnect all devices on this drop and add them back in one at a time until one
of the device connections causes the problem to surface. The source of the
problem has been identified and can now be corrected.
Excessive cable lengths not to specifications and faulty nodes can cause errors
in the data from other/all nodes on the network. Do not automatically assume that
a node that is having trouble on the network is the one causing the errors on the
network.

12-34 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
 12.12.2. Bus Traffic
The NetMeter can monitor the message traffic on the network and identify the
amount of bandwidth that is being consumed. Networks in GCCS-1 should be
designed with a maximum bandwidth usage of 80% to allow for future changes or
upgrades to the network that may consume additional bandwidth. Note that
bandwidth usage can be a deceptive number.
DeviceNet will always poll the network as fast as it can for the baud rate. On a
network with all standard nodes, the bandwidth will eventually level out and the
polling time will slow significantly. Safe Nodes are a higher priority than standard
nodes and will preempt the communication of standard nodes. This can
potentially slow down communication to the standard nodes.

12.12.3. Bus Power

The NetMeter constantly monitors the quality of the bus power on the DeviceNet
network. It is important to record the minimum and maximum voltage levels as
well as the maximum peak-to-peak voltage. Peak-to-peak transient voltages of
greater than 2V can cause communication faults and network errors;
consequently, they should be investigated.
Transients greater than 10V indicate serious problems that must be investigated
immediately. Some items to check for include cables routed too closely to strong
sources of interference, or possibly a power supply with an unstable output.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-35
 12.12.4. Shield Voltage
The NetMeter can measure live, minimum, and maximum voltages between V- and
shield. The DeviceNet specification requires that the shield and V- be connected to
a single location. In GCCS-1, this location is in the MCP.
The following are characteristics of a properly wired network:
a. There is no current flow in the shield, and it is at the same voltage as V-
throughout the system.
b. Current flow in V- causes a voltage rise in V-.
c. Since the maximum voltage drop in V- is 5V, the negative shift in shield
voltage is between -5V and 0V.
d. Systems connected in accordance to the DeviceNet specifications have a
normal shield voltage between -5V and 0V.
e. If the NetMeter indicates an overload (OL) condition, the shield is not
connected. Make sure the shield is connected at the MCP to V- only.

12-36 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.13. Common Mode Voltage
Transceivers in the devices subtract the CANH and CANL signals to determine the
value of the signal as either a 1 or a 0. Noise that is induced into the system is
induced into both wires and therefore is cancelled out. The transceivers require that
the CANH and CANL signals be within specifications so that a 0 or a 1 are not
confused with each other, otherwise errors will result.
DC Common Mode voltage caused by excessive voltage drop in the cabling can
cause a voltage offset on the network and result in errors. The Common Mode
voltage causes a shift in the DC values without a corresponding shift in the
differential voltage. This can cause the Recessive (0) voltage to be confused with
the Dominant (1) voltage.
The NetMeter can measure the maximum total Common Mode Voltage since it was
powered on in the network. The DeviceNet recommendation is not to exceed DC
Common Mode Voltage of 5.0V.
Check for devices that may be requiring more power than expected on the network.
At this time, also double check the cabling in the network for proper length.
12.14. CANH/L Differential Voltage (Recessive – Data 1)
The NetMeter measures differential CANH and CANL signals and displays the
difference. Data (0 and 1) are transmitted as the difference in voltage between
CANH and CANL. This value is a measure of the quality of the signal. Typically this
value is in the low millivolt range. If the recessive, a data 1, voltage differential is
insufficiently small, it can be misinterpreted as a dominant, or a data 0, and errors
will occur.
Check for shorts or opens in the CANH and CANL wires. Ensure there are only two
terminators on the network and they are positioned at each end of the network.
12.15. CANH/L Differential Voltage (Dominant – Data 0)
The measurement of the Dominant voltage levels is important for the same reasons
as shown above in Module 12.14. The typical dominant differential voltage should
be around 2.0 V. If the differential voltage is too small, it can be interpreted as a
recessive voltage and errors will occur.
The NetMeter measures only when a single node is communicating. A measured
dominant voltage of greater than 3.0V when a single node is communicating
indicates a network problem. Check for shorts and opens in the CANH and CANL
wires. Ensure there are only two terminators on the network and they are positioned
at each end of the network.

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-37
12.16. Exercise 1: Configure the DeviceNet Scanlist
1. Scan the network for nodes. Verify against the drawing that all nodes are
present.
2. Obtain I/O parameters for devices that do not automatically map (e.g.
Siemens adapter modules).
3. Configure the Scan list.
4. Upload the entire network and save the network.
5. Download to the DNB module.

END OF EXERCISE

12-38 © 2015 General Motors Company. All Rights Reserved Rev. 6.0
12.17. Review

1. What is a DeviceNet network?

2. How do you troubleshoot a DeviceNet network?
3. How is a DeviceNet network configured?
4. How is a DNB scan list created?

Rev. 6.0 © 2015 General Motors Company. All Rights Reserved 12-39