IMDHMIControls LibraryShop main store

How-to

Choosing the DeviceNet configuration connection path

Industrial networks Published 6 min read

Short answer

RSNetWorx for DeviceNet cannot reach a 1769-SDN through the MicroLogix 1500 serial port: that port talks to the controller, not to the trunk. Configure the scanner from a direct DeviceNet interface such as a 1770-KFD or 1784-PCD, or route through a Logix controller port such as Ethernet on an L32E. RSNetWorx is still required for scan-list work; Auto-Configure covers only simple I/O blocks.

On this page
  1. Why the serial port reaches the controller and not the trunk
  2. Steps to put RSNetWorx on the trunk
  3. Auto-Configure covers only the simple nodes
  4. Worked example: two trunks, one decision
  5. What each failed browse is telling you
  6. The decision for each system
  7. Questions asked

RSNetWorx for DeviceNet cannot reach a 1769-SDN through the MicroLogix 1500 serial port. That serial channel is a path to the controller, not to the DeviceNet trunk, so the configuration software stops at the processor every time. Two documented paths reach the trunk: a direct DeviceNet interface such as a 1770-KFD or 1784-PCD, or a routed connection through a Logix controller port such as Ethernet on an L32E. The scanner's own user manual, publication 1769-UM009, requires the same two things: a DeviceNet adapter for the path and RSNetWorx for the configuration. Work the path first, and neither the software nor the scanner takes the blame for a route that was never there.

Why the serial port reaches the controller and not the trunk #

Two conversations run on a machine like this, and they do not share a path. The serial cable from the computer to the MicroLogix 1500 carries controller traffic: programming, monitoring, upload and download. The MicroLogix 1500 user manual, publication 1764-UM001, documents the controller connection over exactly such a cable, and RSLinx shows the processor online through it. That proves the controller link and nothing else.

The 1769-SDN sits in the Compact I/O bank as a scanner: it masters the DeviceNet trunk and exchanges its I/O image with the controller across the bank. On the SLC and MicroLogix families that exchange never becomes a route a PC can borrow. Only Logix-family processors allow RSNetWorx to reach the network through the DeviceNet module behind them, and the 1756-DNB, 1788-DNBO and 1769-SDN are the modules built that way. A serial link to a MicroLogix stays a controller link at any baud rate and through any driver, and a scanner running I/O proves just as little: operating the scan list shows the list was written, not that the PC has a path to the trunk.

Steps to put RSNetWorx on the trunk #

The work decides the path, and the path has to exist before any scan-list edit:

  1. Sort the work. Controller programming and monitoring belong on the serial cable through RSLinx. DeviceNet configuration, meaning scan lists, device parameters and node commissioning, belongs on the trunk, and the serial cable cannot carry it.
  2. Find a direct interface. A 1770-KFD or 1784-PCD class adapter connects the computer to the trunk itself. Put it on the network, select that path in RSLinx, and browse online in RSNetWorx for DeviceNet.
  3. With no direct interface available, check the controller family. A Logix processor with a routable port carries RSNetWorx traffic through the backplane to the scanner: serial on an L31, Ethernet on an L32E or L35E, ControlNet on an L32C or L35C. Confirm the route against the processor and scanner documentation for your exact versions before scheduling work around it.
  4. On a MicroLogix 1500, read the answer as final: no controller port routes to the trunk, so connect a direct interface for configuration sessions or migrate the machine to a 1769-L31-class CompactLogix whose port does route. The migration changes the route; it never removes the configuration software.
  5. Test the path to the network, not to the processor. Going online in RSNetWorx should list DeviceNet nodes. If the browse stops at the controller, the path is wrong, so fix the path before touching scan lists, drivers or hardware.
  6. Edit scan lists with the machine stopped and locked out, because a scan-list change is a change to live I/O.
  7. Close the loop in run: scanner status, device status, and the expected I/O arriving in the controller.

The same route-versus-tool question follows the scanner onto Logix platforms. If your 1769-SDN sits behind a CompactLogix, whether RSNetWorx is still required for a 1769-SDN on CompactLogix addresses it for that platform.

Auto-Configure covers only the simple nodes #

Newer scanners support a mode called Auto-Configure that builds scan-list entries for simple, non-configurable I/O blocks without RSNetWorx. Treat it as a first-commissioning shortcut for sensor and actuator blocks. A drive or any other parameterized device needs RSNetWorx for DeviceNet, and so does every later edit: a changed node address, a reworked scan list, a new device on the trunk. When the job is scanner-side mapping of real devices, mapping a 1747-SDN scanner for DeviceNet drive control walks that work, and adding a DeviceNet drive node to an SLC 500 covers the node side of the same job.

Worked example: two trunks, one decision #

DeviceNet allots 64 node addresses, 0 through 63. The trunks below are an illustrative example, not a measured network.

Trunk A: a 1769-SDN at node 0, eight sensor blocks at nodes 1 through 8, four drives at nodes 9 through 12. That is 12 nodes in use of 64, of which 12 - 8 = 4 are parameterized devices. Auto-Configure cannot build that scan list, so RSNetWorx for DeviceNet is required, and on a MicroLogix 1500 the path to it is a direct interface on the trunk or the migration to a routable-port CompactLogix. The serial cable keeps doing controller work only.

Trunk B: the same scanner at node 0, six identical I/O blocks at nodes 1 through 6. That is 6 nodes in use, of which 6 - 0 = 0 are parameterized devices. On a scanner that supports Auto-Configure, the initial scan list can be created without RSNetWorx. The first drive added at node 7 moves this trunk back into the RSNetWorx column.

Same decision on both trunks: the devices pick the tool, and the controller picks the path.

What each failed browse is telling you #

What you see What it means The next check
RSLinx shows the MicroLogix online; RSNetWorx finds no network The path ends at the controller Add a direct interface or move to a Logix routed port; reinstalling drivers adds no missing hop
RSNetWorx goes online but fewer nodes appear than expected Trunk-side problem, not a path problem Check device power, node addresses, wiring and the scanner configuration
The scanner runs I/O but the PC still cannot browse Running the scan list proves the list, not the PC path Give the PC its own route: a direct interface or a documented routed port
Browsing still stops at the controller after a processor upgrade The new port does not carry routed configuration traffic Confirm routed-port support for that exact processor version, then reselect the path in RSLinx

When the symptom is an RSNetWorx error around the scanner or POINT I/O nodes, resolving RSNetWorx POINT I/O errors for a 1734-OB8 and a 1769-SDN works through those specific combinations.

The decision for each system #

  • MicroLogix 1500 or SLC with a 1769-SDN: the controller port reaches the controller only, so every configuration session runs through a direct DeviceNet interface on the trunk.
  • Logix controller with the scanner behind it: configure through the processor's routable port from step 3, and keep a direct interface on the shelf for the fault that requires taking the scanner off the network path.
  • Simple I/O blocks only, on an Auto-Configure-capable scanner: Auto-Configure can write the first scan list; the first parameterized device or the first edit brings RSNetWorx back.
  • Every platform: a processor or port upgrade changes the route, never the tool. RSNetWorx for DeviceNet stays in the project.

Questions asked

Can one serial cable serve both controller programming and DeviceNet configuration?

The MicroLogix 1500 serial port carries controller traffic only, so keep it for programming and online monitoring with the controller software. DeviceNet configuration needs its own path: a direct interface such as a 1770-KFD or 1784-PCD on the trunk, or a routed connection through a Logix controller port. Planning the two paths separately avoids the time lost reinstalling software that was never the problem.

Does moving the 1769-SDN to a CompactLogix remove RSNetWorx from the project?

No. The upgrade changes the route, not the tool: an L32E Ethernet port, an L31 serial port or an L32C ControlNet port can carry RSNetWorx traffic through the backplane to the scanner, but RSNetWorx for DeviceNet still writes the scan list and the device parameters. Budget for the software license either way; the port choice only decides whether you also need a direct interface.

What can Auto-Configure actually build on a 1769-SDN?

On newer scanners it creates scan-list entries for simple, non-configurable I/O blocks, so those nodes can be commissioned without RSNetWorx. It does not set parameters inside drives or other parameterized devices, and it does not replace RSNetWorx when you later edit the scan list, change a node address or add such a device to the trunk. Treat it as a first-commissioning shortcut, not as the configuration tool.

Why keep a direct DeviceNet interface on hand after commissioning?

It gives you a path to the trunk that does not depend on the scanner. If a configuration fault takes the 1769-SDN offline, or you must disconnect it to isolate a problem, the interface still lets you browse nodes, read device status and check node addresses on the network. On a MicroLogix or SLC system there is no routed alternative, so that independence is worth planning for from the start.

Keep reading

  • How-to

    How to add a DeviceNet drive node to an SLC 500

    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.

    Industrial networks

  • Selection guide

    How to select a CODESYS fieldbus master for industrial Ethernet

    Select the master around the device, not the connector: the 750-340 is a PROFINET IO coupler, and a PROFIBUS station needs a different coupler. Confirm three matches — device protocol, runtime master package, supported network adapter — then size the bus cycle from the process budget; the worked example clears a 10 ms sensor-to-actuator budget at a 2 ms cycle and fails it at 4 ms. Bench-test a laptop NIC only if the runtime documents it.

    Industrial networks

  • How-to

    How to map a 1747-SDN scanner for DeviceNet drive control

    Seeing the drive in an RSNetWorx browse is not an I/O connection. Put the drive in the 1747-SDN scanlist, read the M-file words the scanner mapping assigns, and reference those mapped words in the SLC 5/04 ladder. A node address is not an integer-file offset: the mapping view, not node 10, decides where each command and status word lives.

    Industrial networks