fundamentals of ethernet/ip -...

Fundamentals of EtherNet/IP 1 of 47 pages

Hands-On Lab Workbook

Fundamentals of EtherNet/IP

Fundamentals of EtherNet/IP of 47


EtherNet/IP Hands-On Lab

About These Hands-On Labs

Welcome to the “Fundamentals of EtherNet/IP” lab. The “IP” in EtherNet/IP puts the “industrial” in standard Ethernet, allowing you to perform I/O control, device configuration, and data collection on a single network. While going through this lab session, you will learn the easy and powerful features of EtherNet/IP.

What you will accomplish in these labs As you complete the labs in this hands-on session, you will understand the following: - How to configure a network - How to do discrete I/O - How to do analog I/O - How to do interlocking As you complete the Optional advanced labs, you will understand how to predict performance of a network and use the web server page to examine the health of your network.

Who Should Complete This Lab This hands-on lab is intended for: - PLC users - Users wondering if EtherNet /IP could work for their application

Before You Begin

Before you begin this lab, please be aware of the following prerequisites:

Working knowledge of the following − RSLogix5000

− RSLinx

Previous experience with Ethernet is also helpful.


Be sure to complete the following steps before beginning the lab exercises.

• Review the demonstration station that you share with your neighbor’s table. Each station is shared by two tables. Depending on room layout, these tables are beside each other (Left and Right) or one in front of the other (Front and Back). The instructor will describe the layout if it's not obvious. "Left" means "whichever of Left or Front applies" in the rest of this workbook, and "Right" means "Right or Back".

• There are ten demonstration stations numbered 0 to 9. The station number is shown as "X" in IP addresses and elsewhere in this workbook. Determine your station number: Look for a label "Station X" or ask a lab assistant.

• Review this diagram which shows the parts of the demonstration station that will be most important in these labs.

• The colored lines show which components are "owned" by each table. The solid lines show which PLC processor each will be programming, and the dotted lines show which I/O modules those PLCs will be controlling. You can see that each PLC will control I/O in the other's chassis. The CompactLogix 1769-L35E will be used by both. Please make sure you know which parts are yours. (Note: It is possible (with restrictions) for two PCs to simultaneously program the same PLC, or for two PLCs to simultaneously connect to the same I/O, but we'd rather you didn't do this

Left / Front PC 192.168.200.1X

Right / Back PC 192.168.200.20X

1756-A7 192.168.200.3X

1756-A10 192.168.200.2X

1788-EN2DN 192.168.200.8X

1769-L35E 192.168.200.5X


accidentally! Feel free to experiment if both you and your neighbor have spare time at the end.)

The chart below contains IP addresses you will use later in the lab:

Left Table Right Table PC 192.168.200.1X 192.168.200.20X 1756-ENBT/B “Parent” 192.168.200.3X 192.168.200.2X 1756-ENBT/B “Child” 192.168.200.2X 192.168.200.3X 1788-EN2DN (None *) 192.168.200.8X 1769-L35E 192.168.200.5X 192.168.200.5X

(* Left table will use the 1756-DNB in "Child" slot 3 for the same purpose.)

• If your PLC is not already in Remote Program/Run mode, use a key to change it to Remote Program.


Document Conventions

Throughout this workbook, we have used the following conventions to help guide you through the lab materials.

This style or symbol: Indicates:

Words shown in bold italics (e.g., RSLogix 5000)

An item that you must click on or a menu name from which you must choose an option or command.

Words shown in single quotes (e.g., 'Controller1')

An item that you must type in the specified field.

✒ FYI The text that follows this symbol is additional information regarding the lab materials, but not information that is required reading in order for you to complete the lab exercises. The text that follows this symbol may provide you with helpful hints that can make it easier for you to use this product.

These labs were designed for a two hour session, but our schedule only allows one hour so some labs have been shortened. The text that follows this symbol describes things we've done to save time, and actions that you can therefore skip.

Note, also, that if the mouse button is not specified in the text, you should click on the left mouse button.


Lab Outline Labs

Lab 1: Adding devices to the network

Lab 2: Adding a computer to EtherNet / IP

Lab 3: Discrete I/O Control

Lab 4: Web Server and Traffic monitoring

Lab 5: Add analog I/O

Lab 6: Processor Interlocking

Lab 7: Add Remote DeviceNet

Optional Advanced Labs

Lab 1: Web Server and Traffic monitoring for Discrete I/O

Lab 2: Web Server and Traffic monitoring for DeviceNet module

Lab 3: Web Server and Traffic monitoring for analog I/O

Lab 4: Web Server and Traffic monitoring for Processor interlocking

Extra Credit:

Try the tasks at the end of each lab for Extra credit


Lab 1: Ethernet Configuration About this Lab

In this Lab, you will configure each device by assigning it a unique IP address.

✒ FYI

Every Ethernet device has a permanent, unique, MAC (Medium Access Control) address. Devices that use Internet Protocol (IP) have a configurable IP address. This applies to everything we're using in these labs.

If an Ethernet device fails and must be replaced, you cannot obtain a replacement with the same MAC address, but you can configure the replacement with the same IP address. Automatic mechanisms enable devices to learn the relationships between IP and MAC addresses.

We have pre-configured all devices with static IP addresses to save time. Read the lab, look at the software, but do not change any IP address.

The way of assigning IP addresses varies depending upon the product. All the devices will be configured using a method called BootP as default.

The table below describes some different ways of configuring IP addresses.

Devices Default Alternatives Notes

1756-ENBT BootP RSLinx or RSLogix5000

RS232 (through the PLC) ControlNet (through 1756-CNB) DH+ (through 1756-DHRIO) EtherNet/IP (through another, already configured, 1756-ENBT module in the same chassis as the uninitialized ENBT module)

1769-L35E BootP RSLinx or RSLogix5000

RS232 (through the PLC)

1788-EN2DN BootP Switches Only for 192.168.1.xxx

In this lab, we will use the BootP server method. This method requires a computer to examine the list of hardware addresses for the devices connected to your network and assign corresponding IP addresses to them. You can tell if an EtherNet/IP node is not configured by looking at its LEDs or other display. If a node has an LED named "Network Status", "Net Status", "Net" or "NS" it will be off. (This comes from the EtherNet/IP specification). Other indications may be present – read the manufacturer's data. For example, an unconfigured 1756-ENBT module would have its OK LED blinking green, the NET LED would be OFF, and the MAC address would be displayed on the module. If it is configured, the IP address would be displayed.


1. For each of your RA Ethernet nodes, record the Ethernet hardware address below (the labels are located on each device or PanelView setup screen).

Because we have pre-configured the devices, you don't need to do this for all of them. Choose one with an easily visible label. The 1788-EN2DN is a good choice – the label should be immediately visible on its top surface. The 1756-ENBT label is on its printed circuit board. You have to remove it from the chassis to see it. 1756 modules support RIUP (Removal and Insertion Under Power) so you can do this without turning off. CompactLogix (1769) modules do NOT support RIUP and it is unlikely that you can see the L35E's label without removing it, so do not choose the 1769-L35E.

Device MAC Address IP Address 1756-ENBT in 10 slot chassis 00 00 BC __ __ __ 192.168.200.2X 1756-ENBT in 7 slot chassis 00 00 BC __ __ __ 192.168.200.3X 1769-L35E 00 00 BC __ __ __ 192.168.200.5X 1788-EN2DN 00 __ __ __ __ __ 192.168.200.8X

✒ FYI

Groups of MAC addresses are allocated to manufacturers. Those beginning with 00:00:BC are allocated to Rockwell. Some of the demonstration stations have the earliest EN2DNs which have addresses allocated by the company that made them for us.

2. On your desktop, double-click the BootP Server application.


As shown below, the Address Relationship window should be empty. The Request History may be empty or have boot requests in it.

There should be none because we've pre-configured the devices!

3. From the Tools menu, choose Network Settings. The Network Settings dialog appears.

4. Enter the following:


This convenience will keep you from entering the same mask and gateway for each of the IP addresses you are about to assign.

5. Click on OK. When BootP server software is open, any “BootP enabled” module will show up in the Request History as shown below. Here is an example for the Right table parent node:

6. Double click on the MAC address.

Or click on the New button and enter the MAC address manually.

The New Entry dialog appears.


7. Enter your desired IP address. In this case, we are using 192.168.200.20 as an example. Optionally enter a host name and description. We are not using DNS (Domain Name Server) in this lab. MAC and IP address are the only required fields.

8. Click on OK.

The newly entered IP address appears in the Relation list. This allows the BootP server to configure that module the next time it receives a BootP request. Wait until the next request is received (in the Request History window) from the module confirming the IP address was assigned to it.

This shouldn't happen because we pre-configured the addresses, so don't wait. If it does happen, then select the IP address from the Relation list and click on Disable BOOTP/DHCP; the status changes to “Command Successful.” This saves the IP address permanently in the ENBT.

Notes: The MAC address is not case sensitive Do not use spaces or other delimiters than shown. (You can use "-" instead of ":" in MAC

addresses.)

9. Repeat steps 6 through 8 for any other devices that need IP addresses. ( There should be none.)


When you have completed these steps, your BOOTP Server screen should have one or more entries in the relation list, something like this:

Note: Your addresses will be different.

10. Verify Ethernet interfaces are configured. The Network Status (or NS or NET) LED on all nodes should be as follows: Blinking green if the module is configured, but has no CIP connections Solid green if the module is configured and has CIP connections

11. Save your BootP configuration file using your first and last name. Example: BillBrown (.bpc will be appended to your name).

12. Exit/close the BootP server.

Now, it is time to verify that the modules are configured properly. We will use a utility called "Ping".

13. Open a DOS shell (command prompt) and ping all 4 of your nodes, one at a time, as follows:

For example, at the DOS prompt, type: Ping 192.168.200.20


✒ FYI

Ping is an Ethernet utility that verifies connectivity at the IP level. You will use it for troubleshooting.

After class, if you want to read about ping, open a DOS prompt, type PING and press Enter. To do this, your PC will need to have TCP/IP installed.

In the DOS shell, you should see multiple Replies from the device you are pinging. Also, ping your own or your neighbor's PC’s IP address. This demonstrates that you can ping any node that has TCP/IP. You will use this many times in the future.

14. Close or minimize the DOS shell.

Summary:

What did you do in this lab? You learnt how to use BootP to configure the devices in your network. Also, you examined the connectivity of those devices using a utility called “Ping”. Rockwell Automation provides the BootP server software along with RSLogix5000 software. Did you know that?

This completes initialization! Lab 1 is complete.


Lab 2: RSLinx and AB_ETH Driver

About this Lab

In this lab, you will configure your computer to be able to talk on EtherNet / IP using RSLinx Ethernet driver.

Getting Started

1. Open RSLinx. If RSWho starts, close RSWho.

2. Click on the Configure Drivers icon to open the list of drivers. If you see one or more AB_ETH or AB_ETHIP drivers in the list, delete them all. At this point, you should still be in the Configure Drivers window.

Add and Configure the Ethernet Driver

3. From the Available Driver Types pull-down menu, choose Ethernet/IP Driver.


4. Click on the Add New button The Add New RSLinx Driver dialog appears. Don’t change the default name of AB_ETHIP-1.

5. Click on OK. The Configure Driver: AB_ETHIP-1 dialog appears.

Make sure that Browse Local Subnet radio button is checked

6. Click on OK The Configure Drivers dialog box appears.


7. Close the Configure Drivers dialog box and click on the RSWho icon The RSWho-1 dialog box appears.

8. Click on ‘+’ sign next to AB_ETHIP-1, Ethernet. This enables the EtherNet / IP driver in RSLinx to browse your network and identify the nodes in your network.


Verify the AB_ETHIP-1 Driver and your IP addresses

You should see a number of IP addresses including the four required for these labs. If you do not see these four, call a lab assistant.

Device IP Address 1756-ENBT in 10 slot chassis 192.168.200.2X1756-ENBT in 7 slot chassis 192.168.200.3X1769-L35E 192.168.200.5X1788-EN2DN 192.168.200.8X

Summary:

Did you notice that you did not have to define any IP addresses in RSLinx? Isn’t this a cool feature!!!

9. Close RSWho.

10. Minimize RSLinx.

This completes configuring your computer using RSLinx Ethernet driver.

Lab 2 is complete!


Lab 3 Controlling I/O over EtherNet / IP About This Lab

The purpose of this lab is to learn how discrete I/Os function on EtherNet/IP when they have been configured, and programmed. Remember, you have previously configured all of your 4 RA Ethernet nodes.

Note that you do not write any ladder code. The necessary ladder rungs are already there in your project.

✒ FYI

A reference section at the end of lab 8 describes how to create a project and how to add modules to the I/O configuration list.

Open RSLogix 5000

1. Click on the RSLogix 5000 icon on your desktop to start the RSLogix 5000 application.

2. From the File menu, choose Open. The Open/Import Project dialog appears.

3. Select the project named Left or Right based on the table at which you are sitting and click on Open.


Your I/O tree in the RSLogix5000 will look like one of the following pictures:

Note: The I/O tree has already been created with all the required modules, but the IP addresses are probably wrong. Verify that the IP addresses (3 for Left, 4 for Right) are correct for your station. Also, verify that the CIP connections for the DNB, EN2DN modules are inhibited. Finally, make sure that the 1769-L35E Ethernet Port Producer is also inhibited. (You don't need to inhibit Producer_Controller.)

✒ Tip

To change an IP address or inhibit a module in your RSLogix5000 I/O tree, right click on the module and choose Properties. IP address is on the General tab, the Inhibit Module checkbox is on the Connection tab.


Download the Project

4. Save your RSLogix5000 file.

5. Turn the PLC key switch to Remote Program mode if it is not already in Remote Program mode.

6. Download the project. You will need to select the communication path. Select menu Communications then Who Active and expand the path until you can see your controller. Be sure to select the correct controller, not you neighbor's! The Download button will be enabled when you click on a controller.

7. Place the controller into Run mode. Examine the list of modules in your I/O Configuration list. There will be small yellow circles for the modules you inhibited and a yellow triangle on any module accessed through an inhibited module. At this point you should have a solid green I/O indication on your controller and no unexplained yellow triangles.

When you select a module with a problem, the Status line below tells you what's happening.

If you select a child of an inhibited module, its status will be "Waiting". (It's waiting for its parent to start working.)


✒ FYI

The circular "Inhibited" symbol is new with this version (13) of RSLogix5000. Previous versions used the same symbol (yellow triangle) for "Inhibited" and other problems.

Notice the different RPIs (Requested Packet Intervals) and different connection types in the Child rack, and DNB or EN2DN modules. To see the CIP connection types and RPIs, right click and select Properties on:

1756-ENBT / A Child 1756-DNB or 1788-EN2DN my_remote_DNet

The values you see should be the same as in the table below. Later, you will require them to calculate frames per second in other labs.

Requested Packet Interval (RPI) Type of connection Child 20 msec Rack Optimized my_remote_DNet 10 msec Data

There is no need to run any other software, including RSNetWorx.

✒ FYI

If you are a ControlNet user, this step calls your attention to the fact that you do not run RSNetWorx to schedule your EtherNet/IP network.

RSNetWorx for ControlNet identifies connections and helps the user to select RPI values. Even though we do not have RSNetWorx for EtherNet/IP, we still need to identify CIP connections and select RPI values.

Some of the modules (inhibited) in the I/O configuration list will have yellow triangles. Other than the inhibited modules, if you see yellow triangle, right-click on the module, choose Properties, and then select the Connection tab. You can then see the status. Call a lab assistant if you need help solving the problem.

8. Expand MainProgram and double click on MainRoutine to have a look at the ladder rungs. Scroll down to the bottom. (The earlier rungs are concerned with the DeviceNet connection which is not active yet. DN_con_OK should be off, so rung 3 has the same effect as rungs 4, 5 and 6.)


The last four rungs copy four discrete inputs to the corresponding outputs.

9. Notice the three columns of I/O devices (buttons, switches, lamps) on the demo stations. The first column is wired to I/O modules in the ten slot chassis, so is controlled by the Right PLC. The second column is wired to the seven slot chassis, so is controlled by the Left PLC. Press some buttons and check that the lights come on.

Your 1756 discrete I/O (pushbuttons and lights) are working.

Summary: In this lab you added discrete modules, configured them, downloaded program to the controller, and controlled I/O over EtherNet/IP

Lab 3 is complete! Congratulations!!!!!!!!


Lab 4: Web Server and Traffic Monitoring

About this Lab

In lab 4, you will learn how to use the web server (running on each 1756-ENBT) to see valuable information, including both connections and I/O messages (frames). Also, notice the CPU utilization counter.

Start Web Browser

The following labs refer to Internet Explorer but you can use either Internet Explorer or Netscape.

1. First, verify that RSLogix5000 is still Online with your PLC processor.

2. Minimize Rslogix5000 and startup Internet Explorer.

3. Enter the IP address where your PLC is located.

For example, in the screen below, the right table would use 192.168.200.2X.

4. At this point, spend 2 minutes investigating Module Information, TCP/IP Configuration and Chassis Who.


5. Now, let’s go back to work by selecting Diagnostic Information located at the bottom of any view. Since there will be many opportunities for you to wander, please stay focused and follow this lab.


Class 1 (CIP) Packet Statistics

Note: The following screenshot and text relate to a system with only one PLC active, but you have two. Your neighbor's PLC uses I/O in your chassis, so you will see some higher numbers.

A class 1 connection is an efficient communication path for higher performance. CIP formatted messages transport multicast and unicast frames over UDP/IP.

6. Click on Class 1 (CIP) Packet Statistics (as shown above) to get to the following screen:

Connections and Traffic in the Parent ENBT module

The screen above shows several important parameters:

Speed Mode


TCP connections Actual class 1 packets per second. CPU utilization

Explanation of the fields:

Packet capacity: Each ENBT is capable of handling 5000 frames/sec Current Number of TCP connections: 2 TCP connections are open

Which is incoming + outgoing TCP connections

Current Number of incoming TCP connections: 1 -- RSLinx online is an incoming TCP connection

Current Number of outgoing TCP connections: 1 -- Remote Child rack is an outgoing TCP connection from ENBT

Class1 Receive field: This field represents number of class1 frames received from the controller during each sec.

Class1 Sent field: This field represents number of class1 frames sent each sec to the controller.

Packet capacity: 5000 is the total (class 1 plus class 3) frames/second capacity of the ENBT

Actual class1 packets per second: 100 is the actual class1 frames/second which is class1 receive (50) + class1 sent (50)

Actual Reserve = Packet capacity (5000) – Actual class1 packets per sec (100) = 4900

What You Should Remember From This Lab

The frames/second capacity (class 1) of 1756-ENBT is 5000. The web page above shows the quantity of TCP connections open.

7. Minimize Internet Explorer.

Lab 4 is complete!

Want to go for Extra Credit?

Can you make Frames/Sec = 400?

If you change the RPI to obtain 400 frames/sec, then put the original RPI back before you move to the next section.


Lab 5: Processor Interlocking About This Lab

The purpose of this lab is to understand how to Produce a tag and Consume a tag. This method enables you to communicate between / among Logix processors without programming.

The 1769-L35E CompactLogix processor will produce a tag. The Left and Right processors will consume the tag.

Produce tag allows a PLC processor to produce a tag and 1 or more processors to consume the same tag. This is used most frequently for interlocking processors. In this lab, two adjacent student stations will work together to experience Produce Tag and Consume tag.

1. Uncheck the "Inhibit Module" box for the 1769-L35E in your RSLogix5000 I/O tree.

Create a Produced tag

Check with your neighbor: This section only needs to be done once, by whoever gets here first. If you are second, you can proceed to the section entitled “Add Remote 1769-L35E”.

2. Open the RSLogix5000 project Producer. You don't need to close your Left/Right project; you can start a second instance of RSLogix5000.

3. In Producer, create a tag called Produced_Tag. There are several ways to get to the Edit Tags screen. For example, choose menu Logic then Edit Tags.

4. Type in the name 'Produced_Tag' and set type to DINT[2].

5. Right click the tag and choose Edit Tag Properties. Check the properties, especially name and data type.


6. Click on Connection and increase maximum consumers to 2 or more.

7. Click on OK.


Initialize Tag

8. Download the program to the 1769-L35E.

9. Click on Monitor Tags and initialize the 2 DINTs to some non-zero values such as 12, 42 as shown:

Add Remote 1769-L35E

You don’t have to add any module; it already exists in your project tree.

10. Select the 1769-L35E Ethernet Port and right click to note its configuration:


Important: Verify all fields shown above. You may have noticed that the L35E looks (in the software) very like a small 1756 chassis containing an ENBT and a PLC. The only obvious difference is the absence of the Comm Format field. If this were a real 1756-ENBT you would select Comm Format None, unless you were also using rack optimized discrete I/O in the chassis. Now, right click on the 1769-L35E controller to check the configuration as shown below.

11. Click on OK.


In your I/O Configuration, only the DNB / EN2DN should be inhibited. All other connections should be running.

Create Consume Tag

12. In the Left/Right project, create a controller tag called Consumed_Tag. Note: You must be offline to do this. Right-click Controller Tags and select New Tag.

Make the tag an array of 2 DINTs as shown below.

(You could also use the tag editor as described under Create a Produced Tag above.)

13. Click on OK.

14. Download your program to your PLC.

15. Put the PLC into Remote Program mode.

Verify Produce and Consume Tag

Look at the consumed tag in the Left/Right PLCs.

Verify that the tag values (e.g. 12, 42) are the same as being produced.

To prove that the tags are being consumed left-click on either of the consumed DINTs and set the value to 0. It should immediately change back to the non-zero value. If one of you is still online to the L35E, change the values there. The changed values should appear in the Left/Right PLCs.


Lab 5 is complete!


Lab 6: Add Remote DeviceNet

About This Lab

The purpose of this lab is to demonstrate access to a remote DeviceNet I/O over Ethernet. By adding a 1788-EN2DN or a 1756-DNB in your Child (remote) chassis, you will verify that the DeviceNet photoswitch can control a discrete output light.

You already have an EN2DN or DNB module defined in the I/O tree. It was inhibited. Remove the inhibit by right clicking on the module, choosing Properties, and then clicking on the Connection tab. In the I/O tree, check that there is no yellow triangle with it.

Note: If you want you know the basic steps to configure a DNB module in the child chassis, go to the reference section at the end of lab 6.

Ladder Rungs for the DNB

Notice the ladder rungs for the EN2DN or DNB module. The GSV and MEQ instructions are used to show that the CIP connection to the DNB or EN2DN is OK (not inhibited or faulted). (This technique is described in RSLogix5000 help.)


1. Put the 5550 processor into Run mode. Look at the DNB display. It should display RUN mode.

2. Put your hand in front of the photoswitch. Does the discrete light illuminate? It should. If not, check the above program and call a lab assistant if you need help.

Summary: We demonstrated the access to a remote DeviceNet I/O over Ethernet. This is how DeviceNet equipment at the plant floor level communicates with the remote Controller over EtherNet/IP.

Lab 6 is complete! Congratulations!!!


Reference Material

To save time in the labs, the details of project configurations have been put in this section.

Lab 3 Reference Materials for Discrete I/O control

Lab 6 Reference Materials for Remote DeviceNet


Lab 3 Reference Material This overview section describes what you skipped in lab 3 for Discrete I/O control and the successive sections will guide you through doing it.

Adding RA EtherNet/IP nodes to the I/O list − 1756-ENBT (“Parent”)

This module is local to the PLC processor.

− 1756-ENBT (“Child” is the remote rack node)

Adding two I/O modules to the 1756 child node

First you opened a project called Left or Right. Then 1756-ENBT module was added in the local chassis.

1. Right click on I/O Configuration and select New Module, and select 1756-ENBT as shown below.

• Click on OK.

• In the next window, complete the Name, IP address (for your table). Disable Keying is selected.


Note that it's more usual to choose Compatible Module instead of Disable Keying. We've disabled keying to give ourselves more flexibility with our demonstration equipment. This would not normally be appropriate in a real project.

• Click on Finish to complete the “Parent”.

Next, the Child 1756-ENBT module is added.

2. Right click on the Parent 1756-ENBT module and select New Module.


• Select another 1756-ENBT/A as shown above

• Click on OK to accept this module. The window below helps complete the fields shown.

• Click on Next. In the window below, the default RPI is changed from 10ms to 20ms.


• Click on Finish.

Add an Input Module to the Child Rack

3. First, make sure you are OFFLINE with your RSLogix5000. This is necessary to add I/O modules.

• Right click on the 1756-ENBT named Child and choose New Module.

• Find the 1756-IB16D in the module list as shown below and click on OK.

• Configure the input module as shown below:


• Click on Next to advance through the configuration screens to view COS (Change Of State) and input filter settings.

• Click on Finish. Your 1756-IB16D is complete.


Add an Output Module to the Child Rack

4. Right-click on your Child 1756-ENBT module, choose New Module, and select the 1756-OB16D as shown below.

• Click on OK.

• Now, complete the configuration as shown below:

• Click on Finish to complete the OB16D output module.


Lab 6 Reference Materials- for adding Remote DeviceNet

This section describes what you skipped in lab 5 and then tells you how to do that.

RSNetWorx for DeviceNet The steps below generate scanlists for the DNB and EN2DN. Scanlists have already been loaded into your scanners. You can verify or create a scanlist as follows:

1. Open RSNetWorx for DeviceNet

2. Browse DeviceNet Your PC is on Ethernet. From your PC, bridge to the DNB via the ENBT module in your remote 1756 chassis or via the EN2DN.

Note: After you see your DNB and photoswitch, cancel Browse

3. Select the scanner

4. Select the Scanlist tab Verify that there is a scanlist. If not, the file ENdnet.dnt is on your PC and needs to be downloaded. Verify that the scanlist has a photoswitch. The photoswitch is in both scanlists, which is normally impossible. You'll see that one of the scanlist entries has a colored "I" next to it. This indicates Shared Inputs – the scanner listens to input messages generated for the other scanner. Right-click the left-hand pane (Available Devices) if you want to enable shared inputs.

5. Verify that Automap box is selected This completes verification.

6. Photoswitch configuration (default of COS is OK)

7. If you don’t already have a list, download the scanlist.

8. Close RSNetWorx for DeviceNet

RSLogix 5000

Add your 1756-DNB under your remote 1756-ENBT.

How to add 1756-DNB to RSLogix5000 Project

1. In RSLogix5000, put your processor into Remote Program and go OFFLINE.


• In your RSLogix5000 project, in the I/O Configuration area, select your remote 1756-ENBT module and right-click to add a 1756-DNB.

How to Configure the 1756-DNB

2. Enter the Input Size. Since the photoswitch has only 1 byte of input data, a single DINT is adequate.

• Enter the Status Size. This is the default size provided by the DNB and RSLogix5000.

• Click on Next and change the RPI to 10ms as follows.

• Note the option to cause a major fault if the connection fails. We aren't using this

because in a classroom environment we expect failures. In real projects this is useful


for any connection which is essential to system operation. An alternative programming technique lets the programmer decide exactly what happens on connection failure. We used that for the remote DeviceNet connection.

• Click on Finish. Your DNB configuration is complete in RSLogix 5000.

• Save your RSLogix 5000 program.

• Download the program to the 5550 processor and verify no yellow triangles. Verify that all modules in the I/O list do NOT have yellow triangles. A yellow triangle means that there is a problem. If you have a yellow triangle(s), select a module and select the Connection tab to view the status. Also, call a lab assistant.

fundamentals of ethernet/ip -...

Documents