Troubleshooting
PanelView 1000 not talking to SLC-5/02 over DH-485
Short answer
The PanelView path and the SLC-5/02 path are separate: a working DF1 or PIC link to the processor proves nothing about the terminal. Read the full 2711 catalog number, keep the PIC off a lone PanelView DH-485 port because it draws power from the network side, enter the configuration screen — white square for touch, both arrow keys for keypad — clear any duplicate node address, then upload once.
On this page
- Read the full 2711 catalog number before touching cables
- Keep the SLC-5/02 link out of the PanelView diagnosis
- Power the converter correctly on the DH-485 port
- Enter the configuration screen with the gesture that matches the input type
- Worked example: a spare 2711-T10C15 beside a 5/02
- The decision for each case
- Questions asked
That spare PanelView 1000 and your SLC-5/02 are two separate serial paths, and a PC that programs the processor has proven nothing about the terminal. Work the checks in order: read the full 2711 catalog number and confirm the unit is actually a DH-485 terminal; keep the PIC converter off a lone PanelView port, because it draws its operating power from the network side; enter the configuration screen with the gesture that matches the input type — touch and hold the white square at startup on a touchscreen unit, both arrow keys together on a keypad unit; then clear any node address collision and make one clean upload attempt.
Read the full 2711 catalog number before touching cables #
The label inside the bezel carries the complete number after the 2711 prefix. The letter that follows fixes the input type: T on a touchscreen unit, K on a keypad unit. The remaining digits select screen size, display and — the part that decides this fault — the communications variant. The PanelView Standard family shipped as DH-485, Remote I/O and DeviceNet terminals with the network fixed by the catalog number, so a Remote I/O-numbered spare will never answer a DH-485 scan however neatly the cable is dressed.
Pull the manual for the exact number — the PanelView Standard Operator Terminals user manual, publication 2711-UM014, covers the family — and record four things before the next power-up:
- Input type from the number, T or K, because it decides the startup gesture.
- The communications network the number selects: DH-485, Remote I/O or DeviceNet.
- The port, protocol and configuration-screen pages of that manual, marked for this unit.
- The node address stored in the terminal and in the SLC, read from the screens below.
Keep the SLC-5/02 link out of the PanelView diagnosis #
The SLC-5/02 has a single serial channel and it is DH-485; the integrated RS-232 channel that runs DF1 over a plain cable arrives with the later 5/03 generation. Your PC therefore reaches the 5/02 through a converter such as the PIC, and a working scan of the processor proves the computer, the software, the cable and the converter — on that segment, with those settings. It proves nothing about the PanelView port, protocol or stored address.
Read the symptom honestly before the next attempt:
- The software finds the SLC but never the PanelView: the processor path is proven, the terminal path is unverified. Confirm the catalog number and open the configuration screen.
- The PIC worked on the SLC segment but acts dead on the PanelView port: the fault is positional — power and segment arrangement, not a broken converter.
- The PanelView boots to its application normally: that proves the unit runs, not that its stored communications settings match this processor.
Note which driver the working SLC session used. If it went through the PIC, it is already the DH-485 driver — keep it and change only the segment and the terminal's settings. A driver configured for a direct DF1 serial channel, the kind later processors have, will not see a DH-485 terminal; select the converter's driver for the PanelView attempt.
Power the converter correctly on the DH-485 port #
A PIC connected to a DH-485 PanelView port with nothing else on that port stays unpowered: the converter draws its operating power over the DH-485 connection, and the PanelView port alone does not supply it. That is why the same converter looked healthy on the SLC segment, where the attached equipment feeds the link. The vendor's DH-485 connection chapters show the same dependency on the AIC+ converter, powered through the cable from the terminal's port. Shut the segment down before you move converters or wiring — the one safety step this job needs.
The working arrangements, in the order to try them:
- Daisy-chain the spare PanelView 1000 into the powered trunk where the SLC already lives, with both ends terminated as the manual shows.
- Keep the terminal on its own port but attach the device the manual designates to power the converter — a bare converter-to-terminal pair is not a working arrangement.
- Count every station you add, terminal and converter included, against the DH-485 station limit before you scan.
- If you are rebuilding the segment wiring for a replacement, check conductors and pins against the DH-485 wiring and RS-232 pin map for HMI replacement before reapplying power.
Enter the configuration screen with the gesture that matches the input type #
On a touchscreen unit, reboot and watch the lower-left corner during power-up: when the white square appears, touch and hold it. On a keypad unit, hold the left and right arrow keys down together through startup. Where a keypad application claims those arrow keys, the manual routes you to the application's GoTo Configuration Screen button instead. If the square never appears on a touchscreen unit, the timing and display checks in Reaching HMI Config Mode With No Startup Square take over from there.
The configuration screen settles the two settings the upload depends on:
- Communications mode: DH-485 selected on the port you wired.
- Node address: the terminal's stored number, compared against the SLC's DH-485 channel address.
Change only the settings the manual for the exact catalog number identifies, then exit and let the terminal rejoin the segment.
Worked example: a spare 2711-T10C15 beside a 5/02 #
Illustrative example — the values below are read off the units in this scenario, not assumed for yours.
The spare reads 2711-T10C15: the T means touchscreen, so the entry point is the white square, and the manual for that exact number confirms the comms port speaks DH-485. The SLC-5/02's channel address, read over the proven PC link, is 1. The spare's configuration screen also shows 1 — the value this spare happens to carry — and two stations answering to one address break DH-485 token passing, so a scan returns nothing from the terminal. Set the spare to 4. DH-485 allows 32 stations at addresses 0 through 31; the trunk now carries three stations, 3 against a limit of 32, and the addresses 1, 4 and the converter's own station are all distinct numbers inside the range 0 to 31, so the network configuration is legal. The duplicate 1-and-1 was the only violation.
With the driver still the converter's DH-485 driver, the browse now lists nodes 1 and 4. Save what the spare holds before you overwrite it — reading an old HMI program before panel replacement covers what an upload actually captures — then download the new machine program and confirm the terminal drives the intended screens.
The decision for each case #
- The catalog number selects Remote I/O or DeviceNet: no DH-485 wiring will ever connect that terminal. Stop cabling and source a DH-485-numbered unit or migrate the application.
- The PIC is dead on a lone PanelView port and alive on the trunk: power arrangement, not hardware. Daisy-chain the terminal into the powered segment and rescan.
- Configuration screen reached, address made distinct, scan still empty: the remaining suspects are segment wiring and the terminal's comms port. Prove the trunk with a known-good device before condemning the terminal.
- The terminal never reaches the configuration screen under the correct gesture for its input type: the fault is in the terminal, not the network. A standard PanelView 1000 in that state is a discontinued unit that has stopped earning its panel space, and when the repair is not worth it the direct replacement path is a PC-based operator station — the industrial panel PCs category is that hardware.
- If that last decision tips you into retiring the DH-485 operator layer entirely, replacing a fleet of PanelView 550 terminals on DH-485 covers the same network from the migration side.
- Nothing above resolves it: give the vendor's support the full 2711 catalog number, the converter type and the result of each check. That is the data that shortens the call.
Questions asked
Is the PIC converter still the right hardware for this job?
The PIC is discontinued equipment; a current USB-to-DH-485 converter fills the same role between the computer and the trunk. Verify how the new converter is powered and what station it takes, because the checks in this article — powered segment, distinct address — apply to it the same way. Confirm the powering arrangement in its documentation before you conclude the converter itself is dead.
Can a second PanelView share the same DH-485 port on the SLC?
Yes. DH-485 is a multidrop network: terminals, the processor and the converter share one trunk, within the 32-station limit at addresses 0 through 31. Give every station a distinct address, terminate both ends of the trunk as the manual shows, and the token passing serves all of them.
The scan connects, then the transfer dies part way. What does that mean?
A connection that starts and then drops points at the segment rather than the settings: marginal power on the converter, or wiring and terminations that hold until something moves. Stabilize power, conductors and terminations before you retry, because a download interrupted part way can leave the terminal holding an incomplete application.