Troubleshooting
FactoryTalk Linx tag browser empty after shortcut setup
Short answer
An empty tag tree after shortcut setup is a stale browser view, not a broken shortcut. Right-click the topmost folder in the Tag Browser, choose Refresh All, then drill to the controller shortcut and click Online to browse the live PLC tags. Check the Design and Runtime paths only when the controller itself is missing from the tree.
On this page
- Nothing changed except the name
- Read the symptom before rebuilding anything
- Fix the empty tree: Refresh All
- When the controller is missing from the tree
- Worked example: the L33ER session, start to decision
- When refresh is slow instead of empty
- Browse offline when the live browse stays slow
- Faults that look like this one but are not
- The decision, case by case
- Questions asked
An empty tag tree after shortcut setup is a stale browser view, not a broken shortcut. Right-click the topmost folder in the Tag Browser window, choose Refresh All, let the rebuild finish, then drill down to your controller shortcut and click Online to browse the live PLC tags. Nothing in the workflow changed: RSLinx Enterprise was renamed FactoryTalk Linx, and Communication Setup still works the way you remember it — add the shortcut, drill down the Ethernet driver to the controller, copy Design to Runtime. Only rebuild a shortcut when the controller itself is missing from the communication tree; that is a path fault, and no refresh can repair it. The sections below separate a stale view from a genuine path fault and end with the decision for each case.
Nothing changed except the name #
FactoryTalk Linx is RSLinx Enterprise renamed. The rename took effect at RSLinx Enterprise CPR 9 SR 2, which shipped as FactoryTalk Linx version 6.00.00, and the communication setup carried over functionally unchanged. In FactoryTalk View version 10 the sequence is still the one you remember: add a shortcut, drill down through the Ethernet driver to the controller's IP address, select the controller, and copy from Design to Runtime. An empty Tag Browser is not evidence of a new workflow; it is the on-screen tree lagging behind the shortcut you just created.
One detail in this step does catch people returning to the software after a year away: the shortcut commits when you confirm the dialog with OK, not Apply, so an Apply-only session leaves a mapping that looks done and is not — why OK commits a FactoryTalk Linx shortcut and Apply does not explains that distinction.
Read the symptom before rebuilding anything #
Four cases cover what you are seeing. Act on the one that matches and leave the rest alone:
- Controller absent from the communication tree — a path fault: driver selection, IP address, cabling or controller state. Fix the path first; Refresh All cannot enumerate a device the workstation cannot see.
- Controller present, shortcut not mapped — the application has no route to the PLC. Map the shortcut, copy Design to Runtime, then refresh.
- Controller and shortcut both present, Tag Browser blank or stale — the common case: the browser has not rebuilt its tree since your changes. Refresh All at the topmost folder is the fix.
- Tags browse fine at the workstation but the panel shows nothing at runtime — a different fault in the Runtime (Target) tab or the terminal's own path; see the section on lookalike faults below.
Do not delete a shortcut that maps correctly because the browser is blank, and do not restart the computer before one honest attempt at Refresh All. Both cost far more time than the refresh and fix nothing when the path and mapping are already right.
Fix the empty tree: Refresh All #
- Open the Tag Browser window.
- Right-click the topmost folder in the tree — the top folder, not the shortcut.
- Select Refresh All and let the browse run to completion before judging it.
- Drill down to your controller shortcut.
- Click Online to browse the live controller tags.
Refresh All forces the browser to rebuild the tree with every change made since it was drawn. Reopening Communication Setup or remapping the same controller does not perform that rebuild, which is why the tree stays blank through otherwise-correct edits. When the tree fills and the online browse lists tags, you are done: the fault was a stale view, and the shortcut was never wrong.
When the controller is missing from the tree #
If Refresh All completes and the controller still does not appear under the Ethernet driver, stop treating it as a display problem and repair the path:
- Ping the controller's IP address from the workstation. No reply means driver, subnet or cabling — the browser was never the problem.
- Confirm the driver selected in the communication tree is the one the controller actually sits on.
- Confirm the controller is powered, fault-free and on the network you think it is on.
Then map the shortcut in Communication Setup: on the Design tab, drill down through the driver and the IP address to the controller and assign it to the shortcut; on the Runtime (Target) tab, copy from Design so the terminal uses the same path at runtime. Where more than one controller is visible, identify the intended one before assigning anything — a valid route to the wrong PLC still shows tags, but they belong to another machine, and on a running line that identification is the one step here worth double-checking.
Worked example: the L33ER session, start to decision #
Illustrative session with the values as they present at the bench: the workstation runs FactoryTalk View version 10, the 1769-L33ER is live and online, you add the shortcut, drill to the Ethernet driver, select the controller and copy Design to Runtime — and the Tag Browser under the shortcut stays blank.
- The tree shows the Ethernet driver and the 1769-L33ER: yes, so path and mapping are good and the blank tree is a stale view.
- Run Refresh All at the topmost folder: the tags appear under the shortcut.
- Click Online: the controller's current tag database lists.
- Decision: the refresh was the fix; leave the shortcut untouched.
Put a number on the choice. The slowest refresh reported for this exact situation was about 30 seconds, on an old laptop, against a replacement machine that updated almost immediately — a reported symptom, not a timeout specification. Deleting and recreating the shortcut, re-entering the driver path and re-copying Design to Runtime is realistically a twenty-minute detour: 20 min ÷ 0.5 min = 40, so refreshing first is roughly forty times cheaper even at the worst reported refresh time, and it is the only action aimed at the actual fault.
When refresh is slow instead of empty #
Browse time grows with the controller's tag count, with the complexity of its UDT structures and with workstation performance — the old-laptop-versus-new-machine contrast in the worked example is the reported evidence for that last factor. Handle it like this:
- Launch one Refresh All and let it finish; repeated launches restart the same work.
- Treat a large program that takes tens of seconds as slow but working, and a tree that never changes as failed.
- If the browse is slow every single time, stop browsing live: define the offline tag file and browse offline, as the next section describes.
- If a browse that used to build stopped right after an upgrade to FactoryTalk Services 6.50, the Rockwell knowledge base documents a patch for that cannot-browse symptom; install it as documented and reboot the workstation before changing any settings.
Browse offline when the live browse stays slow #
The Tag Browser can draw the tree from an offline tag file instead of the live controller. Define the offline file from the controller project once and the browser lists tag names, types and structure from that file without enumerating the PLC, so large programs open quickly and screen development continues with the machine powered down. The offline list carries a verification burden the live browse does not: the file is only as current as the project it was made from, so a tag that browses offline is not proof that the running 1769-L33ER contains it. Regenerate the file whenever the deployed program changes, and treat a mismatch between the offline list and the live controller as a stale file, not a missing tag.
Faults that look like this one but are not #
- Frozen or stale values on the panel while the workstation browses fine — a runtime path mismatch on the terminal, not a browser problem: the article on a PanelView keeping its old FactoryTalk Linx config after a download covers exactly that case.
- The terminal cannot reach the controller at all after the copy — why a PanelView Plus shortcut fails to reach an offline PLC walks through that failure on the runtime side.
- Renamed or changed tags showing old data in other HMI software — the same stale-view logic appears elsewhere: groov View serves renamed tags from a stale cache while the tag itself is fine.
The decision, case by case #
- Controller visible and shortcut mapped, browser blank: Refresh All, then Online. Change nothing else.
- Controller absent from the tree: repair the path, map the shortcut, copy Design to Runtime, then refresh.
- Browse slow every time: switch development browsing to the offline tag file, and browse live when you need to verify against the running controller.
- Panel-side stale values or dead runtime communication after a download: a runtime path fault — follow the two linked articles above, not a refresh.
Questions asked
Did FactoryTalk View version 10 change the communication setup workflow?
No. FactoryTalk Linx is RSLinx Enterprise renamed, and the communication setup carried over unchanged. Version 10 still uses the same sequence — add a shortcut, drill down the Ethernet driver to the controller, copy Design to Runtime — so an empty browser points at a stale view or a path fault, not a new procedure.
Where do I set the Runtime target for the shortcut?
Open FactoryTalk Explorer, select your application, choose FactoryTalk Linx at the bottom of the options, and open Communication Setup. The shortcut has a Design tab for the workstation's browsing path and a Runtime (Target) tab for the path the terminal uses at runtime. Map the controller on the Design tab, then copy that mapping to the Runtime target so both point at the same PLC.
What if Refresh All finishes and the tree is still empty?
First confirm the controller actually appears in the communication tree; if it does not, the path is the fault. If the controller is there and the browse still will not build on a session that used to work, restart the engineering workstation and test once more — a stalled session cleared exactly that way in one reported case. Changing or recreating the shortcut before those two checks wastes the mapping you already had right.
Does Refresh All or online browsing write anything to the controller?
No. Refresh All rebuilds the browser's own view of the tag tree, and clicking Online reads tag names, types and structure through the communication path. Neither action modifies the controller program, the tag database or the HMI application, so repeating them costs nothing but time. The only step in this workflow that changes stored settings is assigning the shortcut itself in Communication Setup.