How-to
How to add a DeviceNet drive node to an SLC 500
Short answer
You cannot add the node from RSLogix alone. A DeviceNet configurator such as RSNetWorx for DeviceNet is required, reached either by pass-through over your DH-485 connection or through a DeviceNet interface card, and on a 1747-SNB or 1747-SDN scanner you place the drive's input and output words in the scan list by hand.
On this page
You cannot add this drive from RSLogix alone. The scan list that tells a DeviceNet scanner which nodes to poll is stored in the scanner module, and only a DeviceNet configuration tool can write it. You need RSNetWorx for DeviceNet, or a third-party configurator proven to edit a 1747 scan list; you need a route from the PC to the trunk, which your existing DH-485 programming connection may already provide through the processor; and you must place the drive's input and output words in the scan list by hand, because the 1747-SNB scanner in this class of retrofit maps nothing dynamically. RSLogix enters the job only at the end, when the ladder reads the words the scan list produced.
Three jobs and three tools #
The programming connection you already own does one of the three jobs. Keeping the tools straight prevents most of the wasted hours:
| Tool | What it does here | What it cannot do |
|---|---|---|
| RSLogix 500 | Edits the ladder that reads and writes the scanner's I/O words | Browse the trunk or edit the scan list |
| RSLinx | Carries the PC-to-processor route over your DH-485 adapter | Act as a DeviceNet interface by itself |
| RSNetWorx for DeviceNet | Browses the trunk, commissions the drive, edits and downloads the scan list | Edit the ladder or map the words for you automatically |
DeviceNet is an open protocol, so other configurators exist — Omron's DeviceNet Configurator and HMS AnyBus-NetTool-DN among them — but openness does not mean every tool can edit an Allen-Bradley scanner's scan list. Confirm that before spending anything on one.
Decision: the configuration software is the one purchase you cannot avoid, unless your site already owns a tool proven to edit a 1747 scan list. The interface hardware you may avoid entirely, by testing pass-through first.
Route the PC to the trunk #
Many SLC 500 processors pass DeviceNet configuration traffic from the programming connection through the backplane to the scanner — the same chassis route used to back a scanner up over the SLC 500 backplane. Whether your processor and scanner combination passes traffic is not worth researching on paper; the test takes minutes and costs nothing:
- In RSNetWorx for DeviceNet, create a new configuration (File > New).
- Go online to the DeviceNet network through the RSLinx driver for your DH-485 PCMCIA adapter, chaining the route through the processor to the scanner. Building that chain is the same path-building job as reaching a CompactLogix through a ControlNet bridge in RSLinx: PC driver, processor, target module.
- Read the browse result. If the nodes on the trunk appear, pass-through works — configure everything through it and buy no interface hardware.
If the browse stops at the processor, the DH-485 link cannot reach DeviceNet in your combination, and you need a DeviceNet interface: the 1784-PCD PCMCIA module, or an RS-232-to-DeviceNet or USB-to-DeviceNet interface.
Commission the drive as a node #
With the route proven, make the drive a working member of the trunk before touching the scanner:
- Set the node address at the drive's DeviceNet option card, using the switch table in the option manual. Addresses run 0 to 63; pick one the online browse shows unused. A duplicate address stalls the whole commissioning.
- Set the option card's data rate to the rate the trunk already runs. DeviceNet uses 125, 250 or 500 kbit/s, and every node must match.
- Apply power and confirm the drive appears at its address in the browse.
- If the tool asks for an EDS file, load the one from the drive manufacturer for the exact drive and option card; it defines the I/O assemblies and parameters.
- Right-click the device and choose Class Instance Editor to read its identity, confirming you are configuring the drive you think you are.
- Record the input word count, the output word count, and the control and status word bit layout from the drive documentation. Never size a node from the free space in the scanner map.
Place the node in the scan list by hand #
Read the catalog number off the scanner label and use that exact number in every documentation check. Retrofits of this age turn up a 1747-SNB or the SLC 500 family's 1747-SDN; the reported 1747-SNB cannot be mapped dynamically by software, so plan on placing the words yourself either way.
- Upload the scanner's current configuration through the working route and save the file. Record every node's I/O size and the word ranges it occupies.
- Check that the new input and output words fit inside the scanner's I/O image without overwriting an existing node's range.
- Add the drive to the scan list and set its input and output sizes to the exact word counts from the drive documentation. A size mismatch leaves the node visible but rejected.
- Allocate consecutive, non-overlapping input and output word ranges for the drive, and write down the PLC addresses they land on.
- Download the scan list. The scanner stops scanning to accept it, so plan the download for a moment the existing devices can tolerate a pause.
Worked example: fitting a 4-word drive at node 12 #
An illustrative commissioning case with typical values; each input states where the real number comes from.
Inputs:
- Trunk data rate: 125 kbit/s, read from the scanner's uploaded configuration — the drive must be set to the same rate.
- Node address: 12, chosen because the online browse shows addresses 0 through 11 in use and 12 free.
- Drive I/O: 4 input words (status) and 4 output words (command) — the 4-in, 4-out assembly listed in the drive option manual.
- Existing scan list: input words 0 through 9 used (10 words) and output words 0 through 7 used (8 words), from the uploaded scanner file.
- Scanner slot: 2, from the rack layout.
Rule in words: a node that claims N input words takes the N consecutive input image words beginning with the first free word; outputs likewise.
Arithmetic:
- First free input word: 9 + 1 = 10. The drive's inputs occupy words 10, 11, 12 and 13; total input words after the addition: 10 + 4 = 14.
- First free output word: 7 + 1 = 8. The drive's outputs occupy words 8, 9, 10 and 11; total output words: 8 + 4 = 12.
- Overlap check: input range 10 through 13 against existing 0 through 9 — clear. Output range 8 through 11 against existing 0 through 7 — clear.
Result: with the scanner in slot 2, the drive's status words are I:2.10 through I:2.13 and its command words are O:2.8 through O:2.11.
Decision: the scanner must present at least 14 input words and 12 output words at that slot. If its configured image is smaller, enlarge the image or choose the drive's smaller assembly before downloading — never let the allocation run over words 0 through 9. Then download, and point the ladder at status word I:2.10 and command word O:2.8.
Wire the ladder and verify #
Back in RSLogix, the drive is nothing exotic: input and output words in the slot image. Write rungs that move the command word to the output address the scan list gave you and read status from the input address, then verify in three steps.
Confirm the scanner's indicators show the new node with no configuration or communication fault. Watch the mapped input word while you cause a harmless local status change at the drive; the word must move. Before touching the command word, make the machine unable to move — lock out motion, then toggle one permitted command bit at a time and confirm the drive's documented response.
Once the words are in the image, commanding the drive is the same word-level job as starting and stopping a drive over EtherNet/IP from a CompactLogix: write the command word, read the status word. Only the network layer changed.
Questions asked
Can I add the drive to the scan list from RSLogix 500?
No. RSLogix edits the ladder; the scan list is stored in the scanner module and written only by a DeviceNet configuration tool. From RSLogix's point of view the drive is just input and output words in the slot image, and its only job here is rungs pointed at the addresses the scan list produced.
Will pass-through work through my DH-485 PCMCIA adapter?
Test it before buying anything: browse from RSNetWorx for DeviceNet through the RSLinx driver for that adapter. If the trunk nodes appear, the processor passes the traffic and no card is needed. If the browse stops at the processor, plan on a DeviceNet interface. Pass-through also runs uploads slower than a direct interface, which rarely matters for a one-node addition.
What is the EDS file the tool keeps asking for?
An Electronic Data Sheet: the drive manufacturer's formal description of the device's I/O assemblies and parameters. Load the file matching the exact drive and option card, taken from the manufacturer's own documentation. It is how the tool learns the input and output word counts; guessing those sizes instead is what leaves a node visible but exchanging no data.
The drive browses fine but the scanner rejects it. What is wrong?
Most often a size mismatch. If the scan list entry claims more or fewer words than the assembly the drive actually runs, the scanner refuses the connection while the drive still answers the configuration tool. Set the scan list entry and the drive assembly to the same input and output word counts, then download again.
Do I have to stop the machine to download the scan list?
Plan on a short pause. The scanner stops scanning the whole trunk while it accepts a new configuration, so every node drops its cyclic I/O, not just the new drive. Choose a moment the existing devices can tolerate a few seconds of silence, download, and let scanning restart before judging the result.