You are on page 1of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Scope
Sometimes it is challenging to connect to a DeviceNet network with RSLinx and successfully do a browse of the network. Then when using RSNetWorx for DeviceNet software for network configuration, there is also interaction between it and RSLinx, that can cause confusing behavior. This document describes a procedure that has always yielded good results when browsing with RSLinx and then configuring the network with RSNetWorx for DeviceNet software. Once a DeviceNet network is completed it is imperative that an archive version of the network is created using RSNetWorx for DeviceNet software. The final, archive file will have a .dnt file extension and should be kept on a computer close to the network, so if devices need to be replaced, the latest device configuration is close at hand. There has been confusion in the past, that merely by browsing a network, that the entire configuration of each device is also uploaded automatically. This is not the case!!! In order to get the configuration of each, individual device on the network, a separate upload operation MUST be done into the project. Conversely, in order to refresh the configuration of a device or load it fresh into a replacement device, a separate download operation must be done, from inside RSNetWorx.

IMPORTANT!! Registering EDS Files for a DeviceNet Network.


It seems that registering a new EDS file into RSNetWorx for DeviceNet software successfully is almost an art form. The following hints will give you a good chance of successfully registering an EDS file the first time. IMPORTANT: I NEVER REGISTER EDS FILES INSIDE THE RSNETWORX SOFTWARE!! I ALWAYS REGISTER THEM ONLY IN RSLINX!! To do this, completely shutdown RSNetWorx for DeviceNet software and RSLinx software along with all of the RSLinx services. Next , under the Rockwell Software folder, select RSLinx Tools and then EDS Hardware Installation Tool.

When the tool screen appears select Add and follow the instructions to complete the EDS installation. Once the EDS file is registered, it has been suggested from various people that a good thing to do is to reboot the computer to have a good chance of the installation being successful. Doing the reboot cant hurt and will just take a little extra time waiting for the computer to initialize. One unusual symptom, I have been fighting in the past is when an EDS file is not completely registered into the computer, by the software. When this happens, the device does not show up on the RSLinx Browse view, even though you know it was on the network, before you tried to register its EDS file. By removing the EDS file, using the EDS Hardware Installation Tool, the device should show up again as an unidentified device on the browse. The only recourse you have is to try the registration again. The second EDS registration is normally the charm and will be successful. If all else fails when unsuccessfully registering EDS files, it has been discovered that removing the RSLinx Harmony files can help that stubborn EDS installation. Knowbase document 40021 details very well how to delete these harmony files from the RSLinx directory.
Page 1 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Browsing Online with a DeviceNet Network


Whenever, you begin using RSNetWorx for DeviceNet software to work on a DeviceNet network, it is strongly suggested that a successful network browse is done first with RSLinx. It is also strongly recommended that RSLinx is kept minimized, with the RSWho function browsing continuously, while using RSNetWorx for DeviceNet software. Start up the RSLinx software first and under the Communications tab select the RSWho function. Next, make sure that the Autobrowse selection box is checked. Using the appropriate DeviceNet network path, burrow down to the desired network. Assuming you have browsed to this path before there may already be a browse screen there to the right of the RSLinx window. If so your browse view may look similar to the image below.

Because it is not known whether the browse screen matches the actual DeviceNet network contents, it is highly recommended that the current, stored browse view be removed and a fresh browse initiated. To easily remove the current view, right mouse click on the A, DeviceNet level of the driver path, on the left hand side of the RSLinx window. Then click on the Remove selection and then click Yes at the Are you sure you want to remove this node? message. Important: This remove function does NOT remove the driver from the RSLinx configuration, but actually only removes the last stored view of the DeviceNet network.

Page 2 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

At this point the network browse screen will blank at the right side of the RSLinx window. Click on the + sign to the left of the A, DeviceNet and the browse view will rebuild after a short time. Be patient, and make sure the browse screen eventually contains all of the expected nodes on your DeviceNet network. Do not close the RSWho screen and minimize the RSLinx software by clicking on the at the top, left hand side of the RSLinx window.

Archiving a DeviceNet Network


The first step to archiving a network is to use RSNetWorx for DeviceNet to do a network browse operation. Start up RSNetWorx for DeviceNet software and the under the File tab select New. This will allow you to open up a blank project to begin with.

If RSNetWorx is loaded for multiple networks, the following box will appear. Select DeviceNet Configuration and then OK.

Page 3 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

The following blank, project appears, which is still off-line from the actual network.

Click on the On-Line icon and the following box appears which asks you for a communication path inside the RSLinx software.

Click on the communication path you normally use to the DeviceNet network, which will highlight it and cause the OK button to appear. Click on OK to continue going on-line. This important message will appear that warns the user, that after the browse finishes, it is necessary to either upload or download the configuration of the individual devices to match the project with the network. Unfortunately, this warning message is generally overlooked and that can cause a project to not contain the device configuration. With a new project you would always want to upload the configuration from the network or run the risk of overwriting a devices configuration with factory defaults later.

Page 4 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Click on OK to acknowledge the message. The browse starts and you see the following progress bar during the browse.

Finally, the completed network scan will complete in about a minute and you will see a screen with icons of the devices on the network. It is imperative that the network browse screen contain ALL of the known devices on the network. If a node does not show up on the screen, that nodes configuration will NOT be stored during the network upload.

Now put the curser on the white part of the browse screen and right mouse click. You see the following box. Important: If you put the curser on an individual device within the browse screen, ONLY that devices configuration will be uploaded, not the whole network.

Page 5 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Select Upload from Network and the following message occurs.

Make sure it says Uploading entire network, before you continue. And you see the Uploading from Devices progress bar. It will show you as it uploads all parameters from the devices, one at a time, from low node number to the highest on the newtork

Page 6 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Once the upload is completed, the progress bar disappears, the local project contains the configuration of the entire network. At this point it is imperative that the project be saved to a file in the computer for archiving.

Click on File and then Save As and enter a file name when prompted and click on Save. Make the file name self explanatory and also put the current date in the file name so there is no confusion as to when it was generated. The file extension will always be a .dnt file. This .dnt file can now be copied between computers, archived to servers or put away for a rainy day as the accurate configuration for the network.

Refreshing/Downloading a Devices or Network Configuration


To easily download the configuration to either a single device or the entire network, you must open up the latest archive file into RSNetWorx software, go on-line and browse the network within RSNetWorx software, as the starting point. This guarantees that any downloads unto the on-line network will be the latest configuration. Start up RSNetWorx for DeviceNet software and then under the File tab select Open. This will allow you to open up the archived project to begin with.

Page 7 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

At the file Open box, browse to your archive file and click on Open.

Your archive project should appear, but will be in OFFLINE mode compared to the real network.

Click on the On-Line icon and this important message will appear that warns the user, that after the browse finishes, it is necessary to either upload or download the configuration of the individual devices to match the project with the network.

Click on OK to acknowledge the message. The browse starts and you see the following progress bar during the browse.

Page 8 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Finally, the completed network scan will complete in about a minute and you will see a screen with icons of the devices on the network. IMPORTANT!! It is imperative that the network browse screen shows all icons with no red X symbols or signs on them, which means one or more device is not actually on the real network. A Not equals sign may also appear, which means that the device on the real network is a different major revision than the device in the project. Clicking the right mouse button on the device and selecting Resolve Device Mismatch will change the archive file to the current device revision. This may also cause the configuration of the device to return to Factory Defaults. If this Defaulting occurs a message will appear in the lower Message area of RSNetWors stating that it occurred. If a node has a red X or sign on it, then that nodes configuration will NOT be restored during the network download. The most common way to cure a red X or occurring, is to double check that the RSWho view in RSLinx is still valid and if so, then restart the RSNetWorx software, reopen the off-line project file and go back on-line

Page 9 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

At this point you have a choice to download the entire network or a single device. It is not normally desired to ever download the entire network on an operational network. Generally, a single node will be downloaded to, to reconfigure it. Important Note: The archive file is a snapshot of a networks/devices configuration at a certain point in time. If a devices configuration has been modified, since the archive was made, downloading will cause these changes to be overwritten with the last values archived. Putting the curser on the white part of the browse screen, while right mouse clicking, will download the entire network. Putting the curser on a single device of the browse screen, while right mouse clicking, will download the only that device. After right mouse clicking, you see the following box

Clicking on the Download to Device selection will show you one off these two messages. This message says that the entire network will be downloaded. Make sure this is actually what you want to do!!.

This message is shown for an individual node being downloaded to.

Click on Yes only if you are positive that the desired download is what you want to do!!! The Downloading to Device(s) progress bar will appear and the download will complete

Page 10 of 11

Knowbase document 41211. Best practices for using RSLinx and RSNetWorx for DeviceNet Software on a DeviceNet network.

Important Notes: All master scanners, except V7.0 revision or higher 1756-DNB modules, can not be downloaded to unless either the scanner is put into Idle mode or the controller they are residing in is put into Program mode. However V7.0 firmware of the 1756-DNB supports On-line Scanlist Changes Allowed at Run (OSCAR and can be downloaded to in Run mode. Some devices, such as drives, may need to have their power cycled after the download for some changes to take effect. If a device mismatch occurred between a device and the project, an error 73 may occur on the master scanner communicating with that node. This will happen if electronic keying is enabled in the scanner for that device. To easily correct this, electronic keying may be disabled for the device in the scanners scan list. While there is an error 73 showing on the scanner, for a device, the node may NOT show up on a network browse. This is due to the scanner normally a communication proxy for the device when a healthy IO connection exists. With an error is showing on the display, the scanner will not communicate for the device and it may not show up on the browse. ADR configuration in a master scanner will be uploaded and saved into a project as part of the scanners configuration. The DeviceLogix program in a device will also be uploaded and stored into a project as part of the devices configuration.

Page 11 of 11