How-to
Reach a CompactLogix through a ControlNet bridge in RSLinx
Short answer
When autobrowse through a 1784-U2CN ControlNet path lists the bridge's EtherNet/IP module but no CompactLogix or third-party EtherNet/IP devices, add the target IP address manually under that module's Ethernet port in RSWho or the FactoryTalk Linx browse tree, then select the resulting device as the online path in the Logix programming software. The devices are reachable; only discovery fails, and a manual entry needs no discovery.
On this page
- Why does the browse stop at the bridge's EtherNet/IP module?
- What route does the manual entry have to cross?
- How do I check the ControlNet side first?
- How do I prove the CompactLogix is reachable before adding it?
- How do I add the IP address manually in RSWho or FactoryTalk Linx?
- What does the finished online path look like?
- How do I confirm the path is real and not cached?
- Why are transfers slow through the 1784-U2CN?
- When should I stop and escalate?
- Questions asked
When autobrowse through a 1784-U2CN USB-to-ControlNet interface stops at the bridge — the chassis and its EtherNet/IP module appear, the CompactLogix controllers and other EtherNet/IP devices behind them do not — add the target IP address manually under that module's Ethernet port node. RSLinx Classic takes the entry in RSWho, FactoryTalk Linx in its browse tree. Refresh the browse, then pick the resulting device as the online path in the Logix programming software. The hidden devices are healthy and answer the EtherNet/IP driver normally; only discovery across the ControlNet path skips them, and a manual entry does not depend on discovery. The checks below run in the order the path is built: ControlNet link, bridge backplane, target subnet, then the entry itself.
Why does the browse stop at the bridge's EtherNet/IP module? #
Because discovery across the ControlNet path reports ControlLogix-family modules, such as the 1756-EN2TD, but not CompactLogix controllers or third-party EtherNet/IP devices — the missing targets are reachable and answer traffic, and only the automatic browse fails to list them.
In the field case behind this procedure, FactoryTalk Linx detected a 1756-EN2TD in the bridge chassis automatically, while two CompactLogix controllers and a third-party EtherNet/IP switch on the same subnet stayed invisible below the ControlNet path. All three appeared immediately under the EtherNet/IP driver of both RSLinx Classic and FactoryTalk Linx, so the subnet, the devices, and the bridge were sound. The browse result gives you no reason why; the manual entry removes the question, because it states the route instead of asking the network to volunteer it.
What route does the manual entry have to cross? #
A CompactLogix controller has no ControlNet port, so the only route from your PC runs 1784-U2CN driver, ControlNet node, bridge chassis backplane, EtherNet/IP module, that module's Ethernet port, and finally the target IP address.
Every hop in that chain has to exist before the last entry can work, which is why the checks run in order. Chassis bridging of this kind is documented behavior, not a workaround: the FactoryTalk Linx documentation describes reaching a DH+ network through a 1756 EtherNet/IP module bridging across a ControlLogix chassis, and the ControlNet-to-EtherNet/IP case here uses the same chassis bridging. Note the ControlNet node number of the bridge and the slot number of the EtherNet/IP module as you browse; both become entries in the finished route.
How do I check the ControlNet side first? #
Open the 1784-U2CN driver and confirm two things in order: the bridge chassis appears as a ControlNet node, and the EtherNet/IP module appears under that chassis backplane; if either is missing, fix that layer before any manual entry.
| What the browse shows | Likely cause | What to do |
|---|---|---|
| No ControlNet nodes at all | Driver not bound to the 1784-U2CN, a node address collision, or ControlNet cabling and termination | Stop and fix the link; a manual entry cannot repair a dead ControlNet network |
| Bridge chassis listed, no EtherNet/IP module under the backplane | Module not on the backplane path you expect | Verify the module is seated, powered, and in the chassis you think it is |
| EtherNet/IP module listed, CompactLogix missing | Discovery does not report the target across the ControlNet path | Prove reachability, then add the IP address manually |
| Manual add times out | IP, subnet, or route error on the Ethernet side of the bridge | Recheck the addressing and the subnet match |
Once the module appears under the backplane, note its slot number — the finished route needs it.
How do I prove the CompactLogix is reachable before adding it? #
Ping the controller's IP address from a PC on the same subnet as the bridge module's Ethernet port and browse it with the EtherNet/IP driver; if both answer, the device is healthy and only the ControlNet-side browse is failing.
Take three readings: the controller's IP address and subnet mask, the bridge module's port IP address and mask, and the ping. Worked check with illustrative numbers: the bridge port sits at 192.168.1.5 with mask 255.255.255.0, the controller at 192.168.1.20 with the same mask. 192.168.1.5 AND 255.255.255.0 gives 192.168.1.0; 192.168.1.20 AND 255.255.255.0 also gives 192.168.1.0; both hosts share subnet 192.168.1.0, so the bridge reaches the controller directly. A controller at 192.168.2.20 under the same mask gives 192.168.2.0, which does not match, and no manual route crosses that difference — fix the addressing first.
If the bridge port itself needs new settings, browse to the module in RSWho, right-click it, and open Module Configuration, then Port Configuration — the documented path in Rockwell Automation's procedure for changing an Ethernet card's IP settings.
How do I add the IP address manually in RSWho or FactoryTalk Linx? #
Select the bridge's EtherNet/IP module in the browse tree, then add the target IP address under that module's Ethernet port node — in RSWho for RSLinx Classic, in the browse tree for FactoryTalk Linx — and refresh the browse.
- Browse to the bridge's EtherNet/IP module through the 1784-U2CN driver so its node is selected in the tree.
- Add the CompactLogix IP address under that module's Ethernet port node, in RSWho for RSLinx Classic or in the browse tree for FactoryTalk Linx.
- Refresh the browse. The address now shows as a device below the ControlNet path, and the controller's backplane and CPU expand beneath it.
- In the Logix programming software, open the online path dialog and select the CompactLogix from that tree.
- Read every port number and slot number from the tree as the path builds; do not type them from memory.
- Go online, upload, or monitor.
The same add covers any other EtherNet/IP device the autobrowse skips behind the same bridge.
What does the finished online path look like? #
The route reads as one entry per hop: driver, ControlNet node, backplane, EtherNet/IP module slot, Ethernet port, target IP address, target backplane, controller slot — eight entries for a single bridge, taken from the tree, never typed from memory.
Illustrative values, not the field ones: the bridge is ControlNet node 02, its 1756-EN2TD sits in slot 3, the CompactLogix answers at 192.168.1.20, and the controller occupies slot 0 of its own chassis. The route then reads:
1784-U2CN driver → ControlNet node 02 → backplane → slot 3, EtherNet/IP module → Ethernet port → 192.168.1.20 → backplane → slot 0, controller
One entry per hop: the driver, the ControlNet node, the bridge backplane, the bridge module's slot, its Ethernet port, the target address, the target backplane, and the controller slot. A different node or slot number in your tree changes that one entry and nothing else.
How do I confirm the path is real and not cached? #
Close and reopen the online path dialog: a genuine path still resolves to the CompactLogix with its correct catalog number and firmware revision, and the controller name and serial number shown online match the controller you meant to reach.
A wrong IP on a shared subnet lands you on the wrong CPU, so make the identity check before any upload or download. For hard proof of the route, put a network tap on the bridge module's Ethernet side and confirm CIP traffic to the target address while you are online. If devices vanish from RSWho altogether rather than hiding behind a bridge, that is a different fault — start with deleting the harmony files when a PLC disappears from RSWho before touching routes.
Why are transfers slow through the 1784-U2CN? #
Because the 1784-U2CN carries your traffic as unscheduled traffic on the ControlNet network, uploads and downloads through the bridge run slower than over a direct Ethernet connection, so keep a direct Ethernet path for large transfers whenever one exists.
Plan downloads for a machine stoppage: discovering mid-transfer that a slow bridge is your only path is a bad moment on a running line.
When should I stop and escalate? #
Escalate when the ControlNet nodes browse, the target pings from the bridge subnet, and the manually added address still will not resolve or go online — at that point the remaining fault sits below both layers you can test from the PC.
If any of those three checks fails, the fault is still in your hands: driver, addressing, or the entry itself. Ask also for a supported statement of which devices are discoverable across a ControlNet path if you need one on record.
Questions asked
When did the 1784-U2CN stop being sold, and what replaced it?
Rockwell Automation announced the USB-to-ControlNet interface cable as discontinued effective April 01, 2024, no longer available for sale. Softing sells the usbLink CN as the replacement USB-to-ControlNet interface, and its manual directs 1784-U2CN users there. Existing 1784-U2CN units keep working, so the manual path entry above still applies to them.
Will the manual add work for devices that are not CompactLogix controllers?
Yes. The same entry placed a third-party EtherNet/IP switch that autobrowse skipped back into the tree, and the method is not controller-specific. The requirement is that the target answers CIP over EtherNet/IP on the bridge module's subnet; a device that only switches packets or speaks another protocol will not appear as a browsable node.
Does the manually added address stay in the driver?
No. A manual entry does not persist the way a discovered device does: rebuild the driver or move to a different PC and you add the address again. Before each session, refresh the browse and confirm the entry still resolves to the controller you expect.
Why do ControlLogix modules browse across the bridge when CompactLogix controllers do not?
A packet capture on the Ethernet side of a 1768-ENBT/A bridge pointed to additional functionality on ControlLogix-family devices as the likely reason they are detected while the CompactLogix controllers and the third-party switch are not. That is one field capture, not a documented Rockwell Automation limit, and the manual entry works regardless of the cause.