Drives Service & Support

General Resources

      Drives Service & Support > Networking > DeviceNet > 160DN2 > FAQ

1. RSnetworx for DeviceNet shows "Unrecognized Device"
2. Where do I get EDS files for DeviceNet?
3. I replaced a drive on my network, and now it does not show up in a network who. All the status lights seem to be fine, and the scanner does not come up with any errors.  What can I do to make it show up?
4. When I try to view the parameters of a drive the program comes back and says either "Drive Mismatch" or comes up with a "Basic Mode" window?
5. When using DeviceNet, my SDN or DNB scanner keeps getting an error 77 (for 1336S, 1336F, and 1305).
6. I changed some parameters in my drive with RSNetworx for DeviceNet and then when I cycled power to the drive, I lost the changes I just made. Why?

 

1.
Q? RSnetworx for DeviceNet shows "Unrecognized Device"
A! Uploading EDS files online. If you are online with RSnetworx and your screen displays your drives node number with a blue and yellow globe next to it and says "Unrecognized Device". This signifies your computer does not the EDS file for that device. You can either go through the steps above to download the EDS file off the web or if you have RSnetworx for DeviceNet version 2.11.51 or later you can upload the EDS files online. To upload right click on the globe. Select "Register Device". On the pop-up menu select next. Then select "Upload EDS". If this option is not highlighted, its because you are not online, you have to be online. When you get to the Input/Output Connection screen, the default config for all our drives is "polled" with input and output size being 4. RSnetworx will then upload the EDS file.  After uploading your globe on your RSnetworx screen should switch to a drive.

2.
Q? Where do I get EDS files for DeviceNet?
A! All EDS files can be found at http://www.ab.com/networks/eds/.  (If online, try uploaded EDS file.  Look for the question titled "RSnetworx for DeviceNet shows "Unrecognized Device".)  Downloading EDS files off the web:

 For Bulletin 160 using DN1 or DN2:
The Bul 160 EDS files can be found by selecting AC drive in the Device Type field and selecting Allen-Bradley in the Brand field.  All the bul 160 drives will come up.  If if does not state DN1 in the product field then the EDS file is for the DN2.

For any drive that is using a 1203-GK5, GU6, 1336-GM5 or GM6 .
Drives using 1203-GK5 or 1336-GM5 as its DeviceNet interface can find its EDS file under "Scanport" for Device Type. Drives using the 1203- GU6 or 1336-GM6 can find its EDS file under "Scanport-Enhanced".  In the "Brand" field select Allen-Bradley.  You can filter your search by truncating your drives catalog number to just the size of the drive and putting it in the "Catalog Number" field (example 1305-BA04A, or 1336F-BRF100).

After finding your drive, click on the "Allen-Bradley Company" link to download the EDS file.  You can place the EDS file anywhere on your computer's hard drive.  After downloaded, go to RSnetworx and select Tools at the top of the screen.  Then select EDS Wizard from the drop-down menu. A pop-up screen will appear, select next.  On the next screen select "Register an EDS file," click next.  Then by clicking on "Choose file" you can browse your hard drive and select the EDS file you just downloaded.  Select the EDS file and go through the rest of the setup until finished.

3.
Q? I replaced a drive on my network, and now it does not show up in a network who.  All the status lights seem to be fine, and the scanner does not come up with any errors.  What can I do to make it show up?
A! When you originally map a drive (device) to the scanner, it records several things about that node.  They are Device Type, Vendor, and Product Number.  These are all device specific, and by changing the hardware (even replacing a failed module or drive) will cause the scanner to see a different device at that node.  When the scanner sees a different node, it thinks that something is not right on that node because the hardware is not the same, so it just disconnects it from the network.  Since it is mapped to the scanner, the scanner is in control of that node, and you actually have to go through the scanner to see that node, and that is why it has the ability to remove it from your network who.  The best thing to do is to go into the scan list in the scanner, and unmap that node number, save the list to the scanner without that node number, and then remap that node to the scanner.  Remember to save the scan list again after re-adding that node.

4.
Q? When I try to view the parameters of a drive the program comes back and says either "Drive Mismatch" or comes up with a "Basic Mode" window?
A! This is because either you do not have an EDS file for that drive, or the EDS file is corrupted. Check the #2 FAQ question in this section for ways to properly make an EDS file for your drive.  Note:  The 160-DN1 is the ONLY device that cannot make its own EDS file that you use with drives.  The DN-2 does have this functionality as well as any DeviceNet to Scanport device.

5.
Q? When using DeviceNet, my SDN or DNB scanner keeps getting an error 77 (for 1336S, 1336F, and 1305)
A! Your node is either using too many words or too few words, compared to your scanner configuration.
Example:  In your scanner you have 4 words mapped for node 3 and you are getting an error 77 for node 3.  This means your DeviceNet communication module (GK5, GM5 or GU6, GM6) is not setup for 4 words.  You either have your communication device configured for less than or greater than 4 words.  Look at your dipswitches. On the GK5 or GM5 the logic command/status and reference/feedback are turned on all the time.  Thus this is 2 words.  Enabling each datalink is an additional 2 words.  So to use 4 words, Datalink A would have to be enabled.  Remember after each dipswitch change, power has to be cycled to the 1203 device for the change in dipswitch to take affect.  The GU6 or GM6 has no dipswitches, these dipswitches are set through software. Since you are online, double click on the node with error 77 and click on the "Device Parameters" tab.  At the end of the parameters listed you'll find the GU6 and GM6 parameters.  Look for a parameter called Cmd/Stat config this defaults to ON and this is your Logic Command/Status and Speed Reference/Feedback words.  This is 2 words.  The next parameter is called Datalink A Cfg,  Turn this on to enable another 2 words.  An additional step to enable Datalink A is to turn on the second bits of M-S input and MS Output parameters.  All these parameters can be found in Appendix B of the GU6 and GM6 user manual.  Again, after these parameters have been changed you have to reset the comm device, by either cycling power to the communications device or selecting "enable" in the Reset Adapter parameter.  After these parameters have been changed you may download the configuration to your Communications Device.


6.
Q? I changed some parameters in my drive with RSNetworx for DeviceNet and then when I cycled power to the drive, I lost the changes I just made. Why?
A! Go into RSNetworx for DeviceNet.  Check if you are using either a 1747-SDN or a 1756-DNB Devicenet scanner.  Double-click on the scanner and go the tab labeled ADR.  See if you have the box labeled "Enable Auto-Address Recovery" checked and see if you have auto-address recovery or configuration recovery enabled for the drive.  Disable auto-address recovery before making parameter changes in the drive.  When finished with setting up the drive parameters, then re-enable auto-address recovery if you wish.