IMDTouchKnowledge BaseShop main store

Troubleshooting

Why a PanelView Plus Shortcut Fails to Reach an Offline PLC

HMI and touchscreens Published 7 min read

Short answer

The shortcut that runs is the one on the Runtime (Target) tab, and it must end at the ControlLogix CPU, not at the 1756-EN2T. Map the route through the EN2T to the CPU slot, copy it to the runtime schema, and download with "replace communications" checked. The EN2T revision is not this fault.

On this page
  1. Why won't the PanelView Plus reach the PLC after you reconnect it?
  2. Which shortcut configuration actually runs on the terminal?
  3. Why can't the shortcut stop at the 1756-EN2T?
  4. What does "Select a different path, selected cannot be used" mean?
  5. What does "Unconfigured shortcut detected" mean at Create Runtime?
  6. How do you build the runtime shortcut while the PLC network is unreachable?
  7. What must be checked in Transfer Utility before the download finishes?
  8. How do you verify the fix from the terminal itself?
  9. When is the network the problem instead of the shortcut?
  10. Questions asked

The running application is not talking to the controller because the shortcut that executes on the terminal — the one mapped on the Runtime (Target) tab of Communication Setup — either stops at the 1756-EN2T instead of ending at the ControlLogix CPU, or never reached the terminal because the .MER was downloaded without "replace communications". The EN2T revision is not the fault; the route is. Fix the runtime mapping in FactoryTalk View Studio, download again, and the panel connects.

Why won't the PanelView Plus reach the PLC after you reconnect it? #

Because the terminal has two separate conversations: the file transfer that loaded the .MER talked to the PanelView Plus, while the running application opens its own connection to the controller using the Runtime (Target) shortcut — and that second conversation has no valid CPU endpoint. The terminal's IP address, subnet mask, and gateway configure its Ethernet interface, and they did their job when the .MER arrived. The shortcut is a separate statement about which controller endpoint the application opens at runtime. Studio gives you two messages that name the broken half before you touch a cable: the path-selection message during configuration, and the unconfigured-shortcut warning at Create Runtime.

Which shortcut configuration actually runs on the terminal? #

The Runtime (Target) schema runs on the PanelView Plus; Development (Local) exists so FactoryTalk View Studio can test against the engineering computer, and a working browse on the local tab proves nothing about the terminal. Communication Setup — the FactoryTalk Linx configuration inside FactoryTalk View Studio ME — shows both schemas, labeled Development (Local) and Runtime (Target). The usual flow is to browse to the controller on Development (Local), click Apply to define the shortcut path, then click Copy to Runtime so the same mapping lands in the target schema. That copy step is where offline projects fail: a successful local browse stays local unless it is copied or the target schema is filled in by hand. After copying, open Runtime (Target) and read the shortcut's device there, because that tab is what the terminal executes.

Why can't the shortcut stop at the 1756-EN2T? #

Because the EN2T is a bridge into the chassis, not the destination: a shortcut that ends at it cannot tell the application which slot the CPU occupies, so the route has no controller to talk to. The EN2T carries the route onto the chassis backplane; the destination is the CPU in its slot. Ending the path one module early leaves the application with a bridge and no controller — which is why a panel can reach the PLC network all day and still show communication errors on screen. On processors whose Ethernet port is built in, the processor itself is the endpoint; the FAQ names those families.

What does "Select a different path, selected cannot be used" mean? #

It means the editor refuses the device you clicked as the shortcut endpoint: you selected the EN2T or something under it, and the message redirects you to the endpoint that works — the CPU. Read it as a statement about your selection, not about the module: nothing in the text mentions a revision or a compatibility limit. Do not change drivers or firmware plans when it appears — extend the path through the backplane to the CPU and the message stops.

What does "Unconfigured shortcut detected" mean at Create Runtime? #

It is a direct finding: the shortcut named in the message was never associated with a device on the Runtime (Target) tab, so the runtime file being created has no controller route for that shortcut. The full message reads: "Unconfigured shortcut detected. The system has detected that the noted shortcut has not been associated with a device on the runtime target tab." That dialog is the whole diagnosis: the shortcut your display objects use has no device on the tab that runs. Associate it with the CPU there and create the runtime again, and treat the warning as a stop condition — a runtime file built past it ships without a controller route.

How do you build the runtime shortcut while the PLC network is unreachable? #

Configure the route by hand on the Runtime (Target) tab instead of browsing: enter the EN2T address you were given, continue across the backplane to the CPU and its slot, then associate the shortcut with that CPU. Losing the live network costs you browsing, not configuration — addresses and slot numbers can be typed in:

  1. Open Communication Setup in FactoryTalk View Studio and list every shortcut the display objects reference.
  2. On Runtime (Target), build the path manually: the EN2T at its assigned IP address, then the backplane, then the CPU at its slot number.
  3. Associate each shortcut with the CPU, never with the EN2T above it.
  4. If Development (Local) is also configured, click Apply there, use Copy to Runtime, then read the target tab back to confirm what actually copied.
  5. Check every address and slot against the network drawing; a hand-entered route is exactly as good as its source document.
  6. Run Create Runtime and stop at any unconfigured-shortcut warning instead of shipping the .MER.

What must be checked in Transfer Utility before the download finishes? #

Two options: "run on startup" so the application launches without a person at the terminal, and "replace communications" so the download carries your corrected runtime schema onto the PanelView Plus instead of leaving an old one in place. Leaving "replace communications" unchecked tells the terminal to keep the communications configuration it already holds, so the corrected route stays inside the .MER and never reaches the running application — the classic result is a perfect route in Studio and the identical failure on the panel. "Run on startup" matters for an unattended reconnect: the application must come up on its own once the terminal is back on the PLC network. If the terminal answers but the transfer itself aborts, that is a different fault, covered under why an HMI is detected but the project download fails.

How do you verify the fix from the terminal itself? #

Run the application and watch live data: if values and indicators update, the route works; if the screen shows communication errors, open the Device Shortcuts menu in the PanelView Plus configuration mode screens and read where the shortcut actually points. Work down this list with the panel back on the PLC network:

  • The shortcut target on the terminal reads the CPU in its slot.
  • The runtime path carries the EN2T address and the CPU slot exactly as drawn.
  • The PLC and terminal clocks are close; a large difference can break the connection even with a correct route.
  • The application runs on startup and the download replaced its communications.

One safety note: commission the reconnected panel on an idle or supervised machine — a terminal that suddenly reaches the CPU again can resume writing setpoints that operators believe are dead. If every item checks out and data flows but drops later, you have left shortcut territory; diagnosing intermittent HMI to PLC Ethernet comms hangs covers that fault.

When is the network the problem instead of the shortcut? #

When the runtime shortcut provably ends at the CPU and the application still fails, check whether the terminal and the EN2T share a subnet — a mismatch silently pushes the route through a gateway that may not exist. Illustrative numbers: terminal at 192.168.1.10 with subnet mask 255.255.255.0 and gateway 192.168.1.1, EN2T at 192.168.1.20.

  • Terminal network: 192.168.1.10 AND 255.255.255.0 = 192.168.1.0, because 192 AND 255 = 192, 168 AND 255 = 168, 1 AND 255 = 1, and 10 AND 0 = 0.
  • EN2T network: 192.168.1.20 AND 255.255.255.0 = 192.168.1.0, because 20 AND 0 = 0.
  • Both endpoints sit on 192.168.1.0, so the terminal delivers frames straight to the EN2T and the gateway address plays no part in this conversation.

Counter-case: an EN2T at 192.168.10.20 gives 192.168.10.20 AND 255.255.255.0 = 192.168.10.0, which does not equal 192.168.1.0, so the terminal hands those frames to gateway 192.168.1.1 — and if nothing routes to 192.168.10.0 from there, the connection dies with a perfect shortcut. Decision: put the terminal and the EN2T on one subnet for a single-panel commissioning link, so the route never depends on a gateway you do not control.

Questions asked

Does the 1756-EN2T revision have to match what was picked in Studio?

No. This fault is a route problem. Both Studio messages name the path you selected or the association that is missing; neither mentions the module's firmware. The shortcut's job is to identify the controller endpoint, and once the path ends at the CPU, a revision mismatch does not produce either of these two messages. Confirm the revision only if a documented compatibility error appears later.

Which controllers make the Ethernet port and the CPU the same endpoint?

The 1756-L8xE series and modern CompactLogix controllers integrate the Ethernet interface in the processor, so the browse ends at the processor itself and no separate bridge hop exists. On those, selecting the processor directly is correct. Only a chassis with a separate module such as a 1756-EN2T needs the two-leg route through the backplane to the CPU slot.

Can the shortcut be reassigned from the terminal without a laptop?

Yes. From the PanelView Plus configuration screens, open the Device Shortcuts menu and reselect the target on the terminal. This helps when the processor sits at a slightly different position in the browse tree than it did in Studio, because the terminal browses the live network it is attached to. Reassign, save, and restart the application.

What happens if "replace communications" is left unchecked at download?

The terminal keeps the communications configuration it already holds, so the corrected Runtime (Target) schema inside the .MER never reaches the running application. The panel repeats the original failure even though Studio shows a perfect route, which is why this option is checked for every download onto a terminal that has run a previous application.

Keep reading

  • How-to

    How to Disable a Remote HMI Display Through PLC Control

    Put the interlock in the PLC, not the panel. Read each panel's current screen through Remote Display Number, force display 21 through Replace Display Number while the disable bit is latched, and on release write the stored number back, hold one second, then write 0 so the panel never reports it is being controlled remotely.

    HMI and touchscreens

  • Troubleshooting

    Why HMI SFTP Cannot See the SD Card Data Log Files

    On a PanelView Plus 7 Series B terminal, the SFTP service publishes internal storage only; the SD card and USB drives never appear to a remote client. A data log whose path root is removable media cannot be retrieved remotely until you redirect it to internal storage or copy it at the terminal with the file explorer application.

    HMI and touchscreens

  • How-to

    One FactoryTalk View ME Project Builds One PanelView Runtime

    One FactoryTalk View ME project creates exactly one .mer runtime, and that runtime runs on one PanelView Plus terminal. Two terminals therefore take the same .mer loaded on both, or two separate projects. For one controller and two identical 2711P terminals, build once and load twice; split into two projects only when screen size, resolution or communication targets differ.

    HMI and touchscreens

Why PanelView Plus Piloted List Selectors Do Not Update