IMDTouchKnowledge BaseShop main store

How-to

Showing Tags From Five PLC-5 Processors on One PanelView Plus

HMI and touchscreens Published 6 min read

Short answer

Yes. One PanelView Plus screen can show tags from all five PLC-5/25 processors, because each object resolves through its own shortcut to one controller's station address on DH+. Configure five shortcuts and prove one known live value from each processor before building production screens.

On this page
  1. How one screen reaches five processors
  2. Set the DH+ stations before the shortcuts
  3. Configure the five shortcuts
  4. Prove one known value from each processor
  5. Read the failure pattern
  6. Worked example: five stations, five shortcuts, fifteen objects
  7. Questions asked

Yes — one PanelView Plus screen can display live tags from all five PLC-5/25 processors at the same time. The screen does not merge the processors: every object is bound to one tag, every tag resolves through one shortcut, and every shortcut is a path from the terminal's DH+ module across the trunk to one processor's station address. Five processors therefore means five shortcuts, five paths to prove, and one known live value confirmed from each processor before any production screen is built. The trunk itself is not the constraint — a DH+ link carries up to 64 stations, and this installation uses six.

How one screen reaches five processors #

A PanelView Plus project is built in FactoryTalk View Studio for Machine Edition. In the project's communication setup you create a shortcut and map it to a path: the terminal, its DH+ communication module, the DH+ network, and finally the station address of one specific PLC-5. A tag reference is then written as {[shortcut]address} — {[PLCA]N7:10} for a shortcut named PLCA reading integer address N7:10 — and the address stays an ordinary PLC-5 data-table address.

That structure is what makes the five-processor screen possible. One tag, one shortcut, one controller: objects on the same screen can come from five different processors, and the terminal never treats them as a single data table. It also means that when the same address exists on all five processors — common where one original program was copied to five machines — the shortcut alone decides whose value you are reading.

Set the DH+ stations before the shortcuts #

DH+ has three requirements that are not negotiable: every station on the trunk carries a unique address, addresses are entered in octal across the range 00 to 77 (64 stations), and every station runs the same baud rate, with 57.6 kBd the common setting. The five processors already have addresses; the terminal's DH+ module needs one unused address of its own. A duplicated address does not fail cleanly: both nodes answer, and you chase intermittent values on exactly those two stations.

  1. Record each processor's station address from its channel configuration.
  2. Set the terminal's DH+ module to an unused address and confirm its baud matches the trunk.
  3. Write the map down — processor, station address, shortcut name — five rows, before the first shortcut is created.
  4. Change a processor's address only in a planned stop, never while the other stations depend on it.

Configure the five shortcuts #

Five shortcuts, one per processor, is the whole configuration.

  1. Open the project in FactoryTalk View Studio for Machine Edition and go to the communication setup.
  2. Create the first shortcut and map its path from the terminal through its DH+ module to the station address of processor one. Name it after the machine — PLCA in this example.
  3. Repeat for processors two through five: five shortcuts, five distinct station destinations. Do not plan to re-point one shortcut later; every tag bound to a shortcut follows it.
  4. Create each tag with its connection set to the matching shortcut, keeping the PLC-5 data-table address unchanged.
  5. Confirm the tag browser resolves tags through each of the five shortcuts before any screen work — a FactoryTalk Linx tag browser empty after shortcut setup is a known stall with known causes.
  6. Copy the runtime communication configuration to the terminal with the download; a PanelView keeping its old FactoryTalk Linx configuration after a download will ignore the new paths no matter how correct they are.

Prove one known value from each processor #

Build the proof before the production screens exist.

  1. Make one diagnostic screen with five numeric objects, one bound through each shortcut to an address that changes on its own — a timer accumulator the program continuously increments is ideal. If you have to add that timer in ladder, the PLC-5/25's user memory is finite; resolving insufficient memory errors in Allen-Bradley PLC5/25 processors covers where the room comes from.
  2. Download and run the project on the terminal.
  3. At each processor confirm three things: the object shows a plausible value, the value belongs to that processor and not its neighbor, and the display moves when the source moves. Make the source change only with the machine in a state where a written value cannot command motion or a process — that is the one safety rule of this test.
  4. Record one row per processor: station, shortcut, address, pass or fail. Five passes is the gate; production objects start after the fifth.

Question marks in place of values mean the path did not resolve — read PanelView Plus logic module shows question marks on live values before touching the screens. When a shortcut tests good in Studio but fails on the terminal, why a PanelView Plus shortcut fails to reach an offline PLC covers the path checks.

Read the failure pattern #

What you see Where the fault lives First move
All five test values dead The common path: DH+ module configuration, baud mismatch, trunk wiring, or the terminal's runtime communication configuration Fix the common path; touch no tags
Every tag of one processor dead, the other four alive That station: wrong station address in its shortcut, a duplicated address, or that node's tap or connection Re-check that shortcut's path against the recorded station map
Values that display but are wrong or stale The tag is bound to the wrong shortcut — with one program copied to five machines you are cross-reading another processor Correct the tag's connection, not the path

The HMI does not fail wholesale. It fails per path and per tag, and the boundary of the dead values names the layer to work on.

Worked example: five stations, five shortcuts, fifteen objects #

The numbers are illustrative; the arithmetic is the decision tool.

Stations: five PLC-5/25 processors at octal addresses 01, 02, 03, 04 and 05, with the terminal's DH+ module at 06. Stations used: 5 + 1 = 6 out of the 64 the trunk carries, leaving 64 − 6 = 58 free — capacity is never a reason to split this display across panels.

Shortcuts and tags: PLCA through PLCE, one per station. A production screen of 15 numeric objects spread evenly puts 15 ÷ 5 = 3 objects on each shortcut. When the path to station 03 dies, exactly its 3 objects stop while the other 12 keep moving: 3 of 15 objects dark, all on one shortcut, names the failing station before you open a dialog.

So commit to this shape: one shortcut per processor, one proven live value per processor before production screens, and when a finished screen partly goes dark, count the dead objects and divide by the objects per shortcut you planned — here 3 ÷ 3 = 1 failed path, and the station map tells you which one.

Questions asked

Can one PanelView Plus tag read from two PLC-5 processors at once?

No. A tag resolves through exactly one shortcut to one controller. If you need a figure that spans processors, such as a line total, use a display expression that references tags from several shortcuts, for example adding {[PLCA]N7:10} and {[PLCB]N7:10}, and the HMI does the arithmetic. The five data tables are never merged.

Can the PanelView Plus read the remote I/O racks directly?

No. Over DH+ the terminal reaches the processor's data tables, not the I/O racks behind it. A value the processor gathers from remote I/O must be stored into a data-table address by the ladder before the HMI can display it. The remote I/O scan runs on the processor's own channel, so adding the terminal does not disturb the remote I/O configuration.

Our PanelView Plus has no DH+ option. Can it still join this trunk?

Not directly. An EtherNet/IP PanelView Plus or FactoryTalk View station reaches DH+ processors through a gateway such as the AN-X2-AB-DHRIO, which bridges EtherNet/IP to DH+. Each shortcut then runs from the terminal over EtherNet/IP to the gateway and out onto DH+ to one station address, so the station plan on the DH+ side stays as designed.

Some objects show question marks while their neighbors on the same shortcut still update. What does that mean?

The path is proven and that one tag is wrong. Question marks at runtime mean the tag could not be resolved through its path; when neighboring tags on the same shortcut display live values, the fault is local to the tag, most often a mistyped data-table address or a tag left on the wrong shortcut. Fix the tag and leave the communication path alone.

Keep reading

  • How-to

    Replacing a Fleet of PanelView 550 Terminals on DH-485

    There is no direct swap: the PanelView 550 is Silver Series, so each terminal is a migration. The PanelView Plus 6 600 keeps the 550 cutout but needs a third-party DH-485 adapter; a Plus 6 700 takes the 2711P-RN6 but modifies the cutout. Audit all 25 catalog numbers, convert one application in FactoryTalk View Studio ME, pilot one machine, then buy the fleet.

    HMI and touchscreens

  • Troubleshooting

    Why PanelView Error 436 Says the Remote Device Has Screen Control

    Error 436 means the PLC, the remote device, still owns screen selection on the PanelView. Zero the configured Screen Number Tag in the controller and unset the control bits still set; a restart cannot clear a PLC value that stays above 0. Fix the PLC logic that returns the word to 0 so the error cannot return.

    HMI and touchscreens

  • Troubleshooting

    Why a PanelView Plus Shortcut Fails to Reach an Offline PLC

    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.

    HMI and touchscreens