Fixing the Shortcut That Won't Browse
Your HMI tags show static. The shortcut in Communication Setup has a yellow question mark, or the browse tree spins forever under the shortcut name. You've restarted the client twice. Welcome to the single most-Googled communications problem in industrial automation.
Here's the diagnostic order that actually resolves it — sorted by how often each step is the culprit, so you fix the common stuff first.
01The Runtime tab you forgot
Open Communication Setup from your View SE/ME project. There are two configurations hiding in there: Design (Local) and Runtime (Target). Assigning the shortcut to your PLC on the Design tab does nothing for the deployed client.
Select the shortcut → assign the device on the Design tab → click Copy from Design to Runtime → Verify → OK → save and re-deploy/restart the client. If you skip the copy button, the runtime client browses an empty path.
02Is the shortcut even pointing at a device?
A shortcut is just a named pointer. In the browse tree under your driver, click down to the controller (not the Ethernet module, not the backplane — the controller icon itself), select the shortcut, and hit Apply. A shortcut that highlights nothing in the tree is pointing at air.
- ControlLogix: path goes EN2T/EN4TR module → Backplane → controller slot. Stopping at the comms module is the classic miss.
- CompactLogix: the controller is the Ethernet device — slot 0, no backplane hop.
03Can the OS even see the PLC?
Rule out the network before blaming the software stack:
ping 192.168.1.10— no reply? It's cabling, VLANs, subnet mask, or a duplicate IP. Linx can't fix layer 1–3.- Reply OK? Try browsing the same device in the FactoryTalk Linx Browser (or RSLinx Classic if installed) directly. If Linx-the-service sees it but your shortcut doesn't, the problem is steps 01–02. If nothing sees it, keep going.
04The RSLinx Classic turf war
RSLinx Classic and FactoryTalk Linx can coexist, but Classic running as a service with an EtherNet/IP driver can hold resources and confuse browsing. Symptoms: intermittent browse, devices appearing in Classic but not Linx.
Set RSLinx Classic to run "as application, not service" (Options → General) unless something genuinely needs it as a service. Reboot. Many plants run both for years without issue — until the one day they don't.
05Firewall ports
EtherNet/IP needs TCP 44818 (explicit messaging) and UDP 2222 (I/O). Windows Firewall on a freshly imaged engineering workstation loves to block the browse while letting ping through — which is exactly the confusing symptom set you have.
06Rebuild the driver, then the shortcut
If the driver's device list is stale or shows red X's that won't clear:
- Delete the Ethernet driver in Linx, re-add it, re-enter the IP range.
- Still dead? Delete the shortcut entirely, save, reopen Communication Setup, recreate it, re-point it, copy Design → Runtime again.
- Nuclear option: restart the FactoryTalk Linx service (services.msc) — schedule it, it drops comms for every client on that machine.
07The name mismatch nobody checks
The shortcut name in Communication Setup must match the shortcut name your tags reference — {::[ShortcutName]Program:Line01.Speed} — exactly, including the one someone renamed six months ago. Tag Browser showing the shortcut but no folders underneath usually means name is fine, path is broken (go back to 02).
Keep a known-good screenshot of your working Communication Setup (both tabs) in the project folder. Next time it breaks, you diff against reality instead of memory.
Six diagnostic layers to read one tag.
In io.codes, a tag binding is one step: pick the device, pick the tag, done — the browser is the runtime, so there's no Design/Runtime split to fall through. If you're curious what comms feel like without a shortcut layer, the builder is free to try.
Open the io.codes builder →