Troubleshooting
PanelView 600 Serial Connect Fails: DTE Versus DCE Cabling
Short answer
A PanelView 600 serial port is DCE equipment and a PC serial port is DTE, so the connection needs a straight-through cable, pin 1 to 1, pin 2 to 2, pin 3 to 3, not the null-modem crossover that connects a PC to a controller. Meter the finished lead end to end first; only then let RSLinx auto-configure and sort out DF1 versus DH-485.
On this page
A PanelView 600 that stays silent in RSLinx is almost always a wiring problem before it is a settings problem. The terminal's RS-232 port is DCE equipment, the PC port is DTE, and a DTE-to-DCE link takes a straight-through cable, pin for pin on the DB-9 ends. The null-modem crossover that connects a PC to a MicroLogix crosses exactly the two conductors this connection needs kept straight, so no baud-rate change, driver reinstall or second auto-configure run will rescue a crossed lead. Meter the finished cable end to end first, then let auto-configuration find the terminal, and only then sort out DF1 versus DH-485. The steps below follow that order and end with what each remaining symptom means.
Why the lead that runs your PLC is the wrong lead here #
RS-232, the EIA/TIA-232 electrical standard, gives every serial port one of two roles. Data terminal equipment (DTE) drives its transmit pin and listens on its receive pin; a PC port and the serial ports on Allen-Bradley controllers such as a MicroLogix are DTE. Data communications equipment (DCE) assigns those same pins the opposite way, the arrangement modems were built around, and Rockwell's PanelView Standard operator terminals manual (publication 2711-UM014) lists the PanelView's RS-232 port as DCE.
The role split decides the cable, so state it as a rule:
- DTE to DTE, PC to controller: the two transmitters face each other on matching pins, so the lead must swap the data conductors. That is the null-modem crossover, and it is why the three-wire lead works on a MicroLogix.
- DTE to DCE, PC to PanelView 600: transmitter already faces receiver across matching pins, so the lead connects straight through, pins 1 to 1, 2 to 2 and 3 to 3 on DB-9 ends.
A lead proven on a DTE peer proves the USB adapter, the COM port and the driver stack; it proves nothing about a DCE peer, and this terminal is one. The same fork runs through the rest of the Allen-Bradley serial line, as the 1747-UIC DH-485 cable straight-through versus crossover comparison for the SLC 5/02 shows.
Check the cable before the software #
- Name the port. The 2711-T6C16L1 carries two serial connectors, labelled RS-232 and RS-232 DF1. RS-232 names an electrical interface and DF1 names a protocol, so the labels are not interchangeable; two connectors on one terminal need not accept the same transfer, and the documentation for that catalog number says which port does what.
- Sort the lead into segments. A gender changer changes which connectors mate; whether it also crosses pins is a question for the meter, not the label. Two male ends prove nothing about routing, and a null-modem adapter stacked on a null-modem cable can end up straight through.
- Meter the complete path end to end, through every adapter in the middle, not just the splice you soldered yourself. The worked test below gives the pass and fail count.
- With continuity proven, open RSLinx on a COM port no other program holds and run auto-configuration once.
- If the path is proven and the scan still comes back empty, delete the serial driver and add it back, because the driver instance is a known point of corruption, then check which protocol the terminal was left configured for.
Until the meter passes, stop spending time on the fixes that cannot work:
- repeated auto-configuration runs, because the driver cannot discover a device whose transmit and receive circuits are swapped
- baud-rate and parity changes, because serial settings matter after the electrical path is right, not instead of it
- connecting every remaining conductor, because extra wires cannot undo a crossed data pair and the handshake wiring the port needs comes from the terminal's documentation, not guesswork
Continuity test on a hand-built three-wire DB-9 lead #
The lead under test is the one the reported case built: three hand-wired conductors between two male DB-9s, transmit joined to receive, receive to transmit and ground to ground, known good against a MicroLogix 1200. The pattern it must match is the straight-through arrangement the PanelView-to-PC lead is documented to use, built as pins 1 to 1, 2 to 2 and 3 to 3 with the ground conductor continuous end to end; the 2711-NC13 is the catalog lead of this type. The instrument is a multimeter in continuity mode. Pull the lead out of both powered devices before testing: a continuity meter on a still-connected port reads through the equipment and lies.
The rule in words: every conductor in a straight-through lead must show one continuous path from each pin on one connector to the same pin on the other, and any beep joining pin 2 on one end to pin 3 on the other is a crossover. One crossed data conductor fails the lead.
Meter all four conductors and record what each reads:
- pin 1 to pin 1: continuity, matching the pattern (pass)
- pin 2 to pin 2: open, with the meter beeping between pin 2 on one end and pin 3 on the other (fail, conductor crossed)
- pin 3 to pin 3: open, with the meter beeping 3 to 2 (fail, conductor crossed)
- ground to ground: continuity (pass)
The arithmetic: 4 conductors checked, 2 pass and 2 fail, so 4 - 2 = 2 conductors violate the straight-through pattern, and both are data lines. The two that pass are the ones every null-modem lead also gets right, which is why a spot check on the ground alone would have blessed this lead wrongly.
The result: the lead is a null-modem crossover, the exact wiring a DTE-to-DTE connection needs and a DTE-to-DCE connection must not have. That is why it ran the MicroLogix 1200 and stays mute against the PanelView's DCE port.
The decision: the threshold is total, so every conductor the connection uses must read pin to pin or the lead is out of the test. With both data lines crossed, refit the lead pin for pin or replace it with a documented straight-through lead such as the 2711-NC13, and keep the 1747-CP3 null-modem lead for the DF1 run to a controller, where the crossover is the correct tool. Rerun the meter before anything goes back into a port, because a stack of adapters can hide a crossover that one more beep will find.
What each symptom is telling you #
| What you see | What it actually proves | Next check |
|---|---|---|
| COM port appears but auto-configuration finds nothing | The adapter enumerated; nothing beyond it is proven | Meter the lead end to end and confirm the terminal port |
| The same lead talks to a MicroLogix 1200 | Adapter and driver stack work; the crossover suits a DTE peer | The straight-through test above |
| Auto-configuration succeeds after rewiring | The serial path is proven | Run a controlled read before calling it fixed |
| The lead only mates through stacked adapters | Signal routing is unknown | Meter the finished assembly pin for pin |
| Setup screens stay password-locked | Access control, not communications | The vendor's documented entry procedure and authorized credentials |
Once the wiring passes #
An answered auto-configuration is the electrical test passing, not the job done. Run a controlled read, opening a tag list or pulling a single value, and if transfers then stall or time out on a proven cable, hand the problem to Fixing HMI PLC communication timeout over serial, which picks up from exactly that point.
Check the protocol before blaming the hardware. A terminal configured for DH-485 will not answer a driver set for DF1, and the reverse; the connector label does not say which protocol the last integrator left in the terminal, but its records and documentation do. The wiring and driver settings for the DH-485 route are covered step by step in How to connect an HMI to an SLC 500 over DH-485 serial.
Keep one boundary in mind: configuration access is a separate problem from the serial link. The vendor's documented setup-entry procedure and authorized credentials are the route into a locked terminal. A failed cable test is never evidence that a terminal is locked, and a lock is never evidence that the cable is wrong.
Questions asked
How long can the straight-through serial cable to a PanelView 600 be?
The straight-through 2711-NC13 lead is 16.4 ft, about 5 m. RS-232 runs are conventionally kept within 50 ft, about 15 m, at standard baud rates; a longer run invites errors, so shorten the cable or drop the baud rate before extending it.
Do PanelView Plus 600 terminals use the same cable?
Yes. PanelView Standard 600 and PanelView Plus 600 terminals both use a straight-through serial cable to a PC port, so one proven straight-through lead serves the whole family. Keep the null-modem lead for DTE-to-DTE controller work and label both, so the wrong one never reaches the bench again.
What does RSLinx auto-configuration actually change?
Nothing on the terminal. Auto-configuration cycles the PC-side serial driver's settings, baud rate, parity and error checking, until a device on the other end answers. It writes nothing to the PanelView and cannot damage the application, which is why a silent scan points at the cable, the port or a protocol mismatch rather than at any risk to the terminal.
The terminal shows a setup prompt during boot that asks for a password. Does that block serial communications?
No. That prompt is the terminal's own setup access and lives entirely inside the PanelView; the serial port answers per the protocol the port is configured for, whether or not anyone can open the setup screens. Treat access and communications as two separate checks: follow the vendor's documented entry procedure with authorized credentials for the access problem, and keep metering the cable for the communications problem.