Troubleshooting
Why the PanelView passthrough checkbox is missing
Short answer
Enable Pass-Through on the Block Transfer dialog inside the Communication Setup dialog of the PanelView application in PanelBuilder32. RS-232 DF1 terminals do not offer the option, so no processor setting or cable makes the checkbox appear on a DF1 panel; confirm the terminal communication first and upload backups directly.
On this page
- Where is the passthrough checkbox in PanelBuilder32?
- Why is the Pass-Through option missing on a DF1 terminal?
- How do I confirm which communication the terminal runs?
- Does going online with the 1747-UIC prove anything about passthrough?
- How do I enable passthrough on a terminal that supports it?
- Which discrete I/O does passthrough reserve?
- How do I back up DF1 panels when passthrough is off the table?
- What should I verify before rolling the change out?
- Questions asked
Look in the PanelView application, not in the processor: PanelBuilder32 puts the Pass-Through check box on the Block Transfer dialog inside the Communication Setup dialog, and on an RS-232 DF1 terminal the option does not exist at all. The panel that raised this question, a 2711-T6C16L1, turned out to communicate over DF1, so no 1747-UIC reconfiguration, RSLogix 500 channel setup, or serial-lead swap would ever make the checkbox appear. Confirm what communication the terminal runs before touching a cable; if the answer is DF1, plan a direct upload at each panel instead of a network passthrough route.
Where is the passthrough checkbox in PanelBuilder32? #
It is on the Block Transfer dialog inside the Communication Setup dialog of the PanelView application: the PanelBuilder32 user manual 2711-GR003D-EN-P names that exact location, and the PanelBuilder software manual 2711-6.0 repeats it on page 20-11.
The check box is part of the application you download to the panel, so PanelBuilder32 offers it when the application communication is configured for the block-transfer arrangement, which belongs to remote I/O. It never appears in RSLogix 500, in the SLC 5/05 channel configuration, or anywhere on the processor side. When the help text sends you to the Block Transfer dialog and the dialog offers no Pass-Through option, the application communication setting is the reason — read the protocol before reinstalling anything.
Why is the Pass-Through option missing on a DF1 terminal? #
Because passthrough rides on block transfers and a DF1 link carries none: an RS-232 terminal exchanging full-duplex serial messages with a controller has nothing for the check box to switch on.
Manual 2711-um014 documents the RS-232 (DF1) terminals as full-duplex serial partners to controllers — the MicroLogix 1000, 1200 and 1500 families among them — using direct message traffic, with no block transfer read or write in the arrangement. Once the configured communication is DF1, the search is over: replacing the serial lead, reworking the 1747-UIC driver, or toggling processor settings cannot add a capability the communication type does not have. The whole blocker reduces to one question — what communication does this terminal run — and the next section says where to read the answer.
How do I confirm which communication the terminal runs? #
Read it from the panel or the project, never from the cable: the terminal Communication Setup screen shows the configured protocol and node, and the same setting appears in the application settings in PanelBuilder32.
Manual 2711-um014 lists both places as where terminal communication settings are set and changed. The cable proves nothing — the rig that raised this question carried DH-485 traffic on an RS-232 lead, which is exactly why the lead could not identify the panel communication. Copy the full catalog number off the nameplate, the reported example being 2711-T6C16L1, and record the protocol shown before planning any upload or download.
Does going online with the 1747-UIC prove anything about passthrough? #
It proves the processor link and nothing more: the 1747-UIC connection that puts RSLogix 500 online with the 1747-L531E says the network reaches the SLC, not that the panel can bridge traffic.
Passthrough is a terminal-side capability stored in the panel application; processor connectivity is a separate question. If the DH-485 link itself is the doubt, the cable and driver checks are laid out in how to connect an HMI to an SLC 500 over DH-485 serial. Once that link is healthy, stop reworking it — the missing check box is not on the network.
How do I enable passthrough on a terminal that supports it? #
Upload the running application, tick Pass-Through on the Block Transfer dialog, and download the modified application back to the panel: the check box lives in each terminal program, so every panel takes the edit individually.
- Upload the current application from the terminal to the PC — the same upload step used when backing up an HMI with a scratched touchscreen before replacement.
- Open the application in PanelBuilder32 and go to the Communication Setup dialog, then the Block Transfer dialog.
- Tick the Pass-Through check box and note the discrete I/O the manual reserves for passthrough.
- Save, then push the .pva file back with Application > Transfer > Download in PanelBuilder32.
- Repeat for every panel that needs it; editing a fresh offline project changes nothing on terminals already running their own applications.
Which discrete I/O does passthrough reserve? #
The terminal manual lists the reserved discrete I/O locations for passthrough, and the rule is absolute: any application tag on those locations must move, because overlapping use shows up as erratic results, not as an error message.
The reservation is what makes a passthrough rollout able to break screens that ran for years: the panel silently shares part of its discrete I/O table with the passthrough function. Do the first download-and-test on a bench rig, never on a running machine — erratic discrete I/O on live equipment is a machine-behavior fault, not a nuisance.
How do I back up DF1 panels when passthrough is off the table? #
Walk to each panel and upload over the serial link: full-duplex DF1 transfer is a supported mode on these terminals (2711-um014), so one visit per panel completes the backup with no passthrough infrastructure at all.
Illustrative worked example: put the walk at 10 minutes per panel and the fleet at 14 panels. Direct upload costs 14 x 10 min = 140 min, about 2 hours 20 minutes of rounds. Building the passthrough route first costs 14 x (10 min upload + 5 min edit + 10 min download) = 14 x 25 min = 350 min, about 5 hours 50 minutes — and every panel still gets a visit, because the check box has to be placed in each application by hand. Decision: for a one-time backup, direct upload wins outright; passthrough pays back only on fleets that support block transfers and will take repeated network downloads afterwards.
Other panel families treat DF1 passthrough differently; a worked fix case between a PV300 Micro and an SLC 5/04 is in PV300 Micro to SLC 5/04 DF1 passthrough communication fix. And when the panel is a dead end for network work and aging anyway, the migration path is industrial panel PCs at the machine.
What should I verify before rolling the change out? #
Prove it once on the bench rig, then check four things per panel: the full catalog number, the communication shown in the terminal setup, the state of the Pass-Through box in the loaded application, and a discrete I/O map with no overlap.
- The full catalog number off the nameplate, copied verbatim.
- The configured communication read from the Communication Setup screen, not inferred from the lead.
- Which application the terminal actually loads — confirm that copy, not the one on the PC, as covered in how to find the runtime file an HMI terminal actually loads.
- The reserved discrete I/O list checked against every discrete tag in the application.
Any panel that reports DF1 stays on the walk-and-upload plan; panels that show block-transfer communication can carry passthrough. That one split, made from the nameplate and the Communication Setup screen, is the whole decision.
Questions asked
Does a newer PanelBuilder32 version add the passthrough checkbox?
No. Version 03.82.00 already documents the check box on the Block Transfer dialog, so the editor build is not the gap. Whether the dialog offers Pass-Through depends on the application communication configuration and the terminal family. Upgrading the editor will not put the option on a DF1 terminal.
Can a different cable or driver make a DF1 terminal pass traffic?
No. The limit is the terminal communication type, not the wiring. An RS-232 lead carrying DH-485, a 1747-UIC, or any driver choice changes how your PC reaches the network; none of them adds block-transfer passthrough to a panel that does not have it.
Why upload every application just to turn on one check box?
The setting is stored in each terminal application, not in the terminal firmware and not in the processor. A tick saved in a new offline project changes nothing on a running panel, so each display needs its own upload, edit and download, which is also why enabling passthrough costs one visit per terminal anyway.
Is erratic push-button behavior a sign of passthrough overlap?
It can be. Passthrough reserves part of the terminal discrete I/O, and application tags on those same locations fight it, producing erratic results rather than a fault message. Cross-check every discrete tag against the reserved list in the terminal manual before downloading, and prove the first download on a bench rig.
Why does the help file point to a dialog I cannot find?
The help covers every terminal family the editor supports, and the dialogs populate according to the communication configured in the application you have open. A project configured for DF1 simply does not present that passthrough option, so the instruction is correct while the option stays absent.