Basic DNET101 Lab
Basic DNET101 Lab
To complete this lab, you need to have RSNetWorx for DeviceNet 3.0 or newer and a
recent version of RSLinx. You also. This lab was written with the following equipment
at the following nodes:
Note: We show a Bull 160 Drive at node 9, but it is not needed for this lab. Also, if you
do not have a RediSTATION, you can complete most of the lab.
1. 1756-DNB (0), bul 160 drive (9) -- optional, RediSTATION (15), KFD (62) attached
to computer's serial port, and Photoeye (63)
3. Set the Photoeye to node 63, and test if it is working. Set it to light operate mode.
1
Lab 1: Hardware Overview
In this lab you will examine the hardware and cabling of the DeviceNet lab network to
become more familiar with the products.
1) The following section describes the hardware at your lab station. Read the following
section and refer to your lab station for the actual hardware.
The scanner is the DeviceNet master coordinating all control data to
and from all devices on the DeviceNet network. This DeviceNet data is
transferred to and from the Logix5550 processor. This data is then used
in the ladder program to do the actual control logic.
The Series 9000 photoeye is designed to withstand harsh
environments. The sensor for this lab is the retroflective model.
· A 2705T RediSTATIONTM operator interface.
2705T RediSTATION operator interface node number = 15
The RediSTATION operator interface is a pushbutton station
that has a start button, a stop button, and a red pilot light.
2
· RSNetWorx for DeviceNet software connected to the DeviceNet
network via a 1770-KFD interface module.
Software node number = 62
The Bulletin 160 ac drive provides control, drive status and
diagnostic data over DeviceNet.
2) Examine the cabling connection from the main network trunk to the devices.
Once you have completed a review of the hardware you are ready to start configuring the
system.
3
Lab 2: Assigning Node Addresses To
Devices
The first thing you will need to do when setting up your DeviceNet system is to assign
node addresses to all the devices on the network. The node addresses assigned are totally
up to the user. Once assigned though, the node addresses will define the locations of
specific items of data in the DeviceNet map table. For example, if you assign the
RediSTATION the node address 15 and you wish to use the RediSTATION information,
then you will have to find out where in the DeviceNet map table the information for node
15 is stored. One caveat to remember is to leave node 63 available for the
commissioning of devices (commissioning a device means you assign it a node address).
Some nodes power up by default as node 63. The only way to change their node address
is to set them up on the network and have the software assign a new address to the
device. If you have multiple devices which power up as node address 63, then you will
have to put them on the network one at a time and assign them a new unique address so
you can then put the next device on the network (unless they support a feature called
Fault Address Recovery -- which is a topic for a more advanced course).
DeviceNet node addresses are set in one of two ways, hardware or software. Some
devices have switches on them that allow you to set the address. The RediSTATION in
your lab is an example. This device has already been set to node 15 by using the
dipswitches inside the device. Other devices can only be set through software, such as a
Point I/O module. Some devices can be set in either hardware or software, such as the
1756-DNB scanner. In this lab we will assign a node address for the Series 9000
photoeye using RSNetWorx software.
4
RSNetWorx software supports both ControlNet and DeviceNet networks in one package
as of version 2.22 (previously they were independent executables). Therefore, the first
thing we want to do is tell RSNetWorx that we want to work with a DeviceNet network.
3) Select “File” from the main menu and then select “New” from the dropdown menu.
The following window appears.
5
Now that we have a new DeviceNet project created, let’s go online.
6) A list of the available drivers in RSLinx will appear. Select the 1770-KFD DeviceNet
driver and then click OK.
7) Select “OK” to go online. This prompt is there to warn you that your offline file may
not match the online network configuration. In order to make your offline file match
the online network, you should upload the network or download the offline file.
The software will begin browsing the network for devices. When it is finished your
screen should look like the one below.
6
This icon will animate to
indicate you are online.
NOTE
7
Note the five nodes from the lab setup are shown. Also note the photoeye at node 63. As
stated in the hardware overview, the photoeye will be set to node 7 for these labs. Since
we have verified we are communicating properly to the photoeye we can commission it.
9) Select “Node Commissioning” from the submenu. The following screen will appear.
10) Select the “Browse” button. The following screen will appear.
8
11) Select “1770-KFD-1, DeviceNet” in the left pane. The nodes will appear on the
right.
12) Select the photoeye at node 63 and select the “OK” button. The following window
will appear.
13) Set the node address to “7” and select the apply button. When the node is
commissioned you will get a “Node 7 Commissioned” message on the bottom of the
window.
14) Select the “Close” button to close the “Node Commissioning” window.
Notice that the photoeye still shows up as node 63. Remember, Unless you select
continuous browse, RSNetworx only does a browse when you request it (to reduce
unnecessary network traffic, especially when remote networks are involved).
Notice that the Photoeye now shows up at node 7. Also note that a “missing’ photoeye
shows at node 63. Let’s delete the reference to the photoeye at node 63 since it no longer
exists.
9
16) Select the photoeye at node 63 and press the delete key to manually remove the
device from the network configuration
While that process was not too bad, RSNetWorx version 3.0 made the node
commissioning process much easier. Let’s take a look at a couple of other ways we can
commission a node address as of version 3.0 of RSNetWorx.
When the node address has been changed the window will disappear. The photoeye now
appears at node 8. Note that you did not have to browse to see the node change or delete
the old reference to node 7.
There is an even simpler way to change the address. Note the address displayed below the
device in the browse window. You can change the node address by simply typing a new
address over the existing one displayed.
21) Double-click on the node number (8) directly below the photoeye in the browse
window.
The node addresses for the other devices are set. We now have all our nodes on the
network and node numbers assigned. This completes the node commissioning lab.
10
Lab 3: Configuring The Devices
Once you have all your nodes on the network you will want to configure the nodes to
behave in the manner you desire. For example, you will want to set up the photoeye to
operate in dark mode or light mode. In dark mode the output will go on if the light beam
is broken (dark). In light mode the output will go on if the light beam is present (light).
In this lab we will configure the Photoeye. We will also take a look at the RediSTATION
configuration. Before we start our configuration, let’s set the properties for our
DeviceNet project.
1) Select “Network” from the main menu and then Select “Properties”. The following
screen will appear.
The name field displays the current default file name of the project. This field will
display the name of the file we select to save the project to. You can change this name by
performing a “file -> save as” operation and selecting a new file name.
11
3) When you have entered the information select the “OK” button.
4) Select the save icon from the toolbar to save the project as “DeviceNet.dnt”.
We now have a new project created. We are ready to start configuring devices. Let’s
look at the RediSTATION.
The RediSTATION is a simple device, consisting of two buttons and a light. As such
there really is not much to configure for a device like this other than setting the node
address and the baud rate. The RediSTATION has a single dipswitch bank to configure
the device. The dipswitch bank is located inside the box. We will not open the device in
the lab, we will just take a look at what the dipswitches are used for.
5) Refer to the picture below (taken from RSNetWorx for DeviceNet software help. This
information is also in the RediSTATION manual).
12
Note that for this device there are only two things you can configure other than the node
address and baud rate, the output fault state and output flash rate. If we wished to change
the settings for the device we would open it up and change the dipswitches appropriately.
We are now going to configure the photoeye. The photoeye has no dipswitches. All
configuration for the photoeye is done through the software. In order to configure the
photoeye we simply need to select it from network Browse window.
6) Double-click on the photoeye (node 7). The photoeye configuration window will
appear.
The general tab allows you to enter a name and description for the photoeye. It also
displays information about the module such as the node address and revision.
8) Select the “I/O Defaults” tab. The following window will appear.
13
I/O default
is for 1 byte
of strobed
data to be
returned to
the scanner
The I/O defaults define the default configuration for the device in terms of how much,
and what data, the device will exchange with the scanner. By default, the photoeye will
send 1 byte of data to the scanner when it receives the strobe request. If you are unsure
of what is contained in the 1 byte you can simply select the “Input Help” button next to
the size.
9) Select the button labeled “Input Help” to the right of the size listing in the “Strobed”
section of the window. The following window will appear.
14
We now know that the output of the photoeye will be returned in bit 0 and the margin in
bit 1. Let’s take a look at the parameters for the photoeye.
11) Select the “Parameters” tab. If you get a prompt to upload the configuration select
“Upload” The following screen appears.
The lock
means the
parameter is
read only
Note that there are three parameters associated with this device, and that two are read
only. Currently, this device is in light operate mode. Light operate means the photoeye
will turn on its output when it detects the light beam. If you look at the second
parameter, Output, you will note that it’s current value is “on”. Let’s monitor the output
live and see how the photoeye behaves.
12) Select the “Monitors Parameters” icon to start monitoring the photoeye live.
Note that the current setting for the output is on. That is because the photoeye is set to
light operate and the photoeye is seeing the reflected light beam.
15
13) Place your hand between the photoeye and the reflector so that the light beam is
blocked. Note that the output now says “off”.
Let’s set the photoeye to dark operate mode and see what happens.
15) Select the dropdown listbox arrow next to “Light Operate” (Parameter 1) to bring
up a list of selections for the parameter.
17) Select the “Apply” button and then respond “Yes” to the prompt to download to the
device to store the new setting to the photoeye.
19) Notice how now the output is off while the photoeye detects the light beam.
20) Place your hand between the photoeye and the reflector and examine the output
status.
Let’s assume for our application we want the photoeye to operate in light operate mode.
22) Change the photoeye back to light operate mode (remember to download the setting
to the device).
We have completed the Configuring Devices lab. At this point we have assigned node
addresses to all our devices and added them to the network, and then configured each
device to behave how we desire. The next step will be to add the devices to the scanners
scan list (the list that identifies which devices the scanner will communicate to).
16