How-to
Replacing a Fleet of PanelView 550 Terminals on DH-485
Short answer
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.
On this page
There is no direct replacement for a PanelView 550, and a 25-unit fleet on DH-485 is a migration project, not a purchase. Rockwell moved the PanelView Standard family, the 550 included, to Silver Series in 2011/2012, so every terminal is a planned replacement. Three real paths exist: a PanelView Plus 6 600, which keeps the 550 cutout but needs a third-party DH-485 adapter; a PanelView Plus 6 700 with the 2711P-RN6 communication adapter, which gives a documented DH-485 route but forces a cutout modification; or a C-more EA9 panel with the EA-DH485-CBL cable, which keeps the protocol but means rebuilding every application. Audit all 25 catalog numbers first, convert one pilot application, commission one machine, then order the fleet.
Why there is no direct swap #
The PanelView Standard series entered Silver Series in 2011/2012, and the published phase schedule runs from announcement, through the end of new assemblies, then the end of repair, then support-only. Repair and keypad-membrane availability tightens as the phases advance, which is why fleets this size get migrated instead of maintained.
Rockwell's documented migration mapping is PanelView 550 keypad to PanelView Plus 600 keypad, and PanelView 550 touch to PanelView Plus 600 touch. That mapping fixes the terminal class only. Cutout, operator input method, communication path, and application are four separate compatibility decisions, and a panel chosen on display size alone will mount and then fail to communicate. The general case is covered in planning an HMI terminal replacement from an older operator panel; what follows is the DH-485 fleet workflow.
Audit all 25 catalog numbers first #
- Record the complete catalog number of every installed terminal. The number encodes input type, communication port, and supply voltage, and 25 identical bezels are not 25 identical terminals.
- Decode each number against its documentation and record keypad or touch, the port, and the supply voltage for every unit.
- Record which SLC 5/03 each panel serves and which port it lands on.
- Upload and archive the application from each terminal before disconnecting anything, the same discipline as backing up an HMI with a scratched touchscreen before replacement.
- Count the spares that still boot and hold a usable application.
Group the results by full catalog number, port, and application file. Most of this fleet will be DH-485 to SLC 5/03 processors; whatever is not forms its own group with its own communication hardware. Then verify each planned replacement against the machine it will serve — catalog number, port, cutout, voltage, application — the same pass described for verifying an obsolete HMI replacement before ordering, made 25 times before the fleet order goes in.
Match the cutout, then the protocol #
| Migration path | Cutout | DH-485 route | Application work |
|---|---|---|---|
| PanelView Plus 6 600 | Same cutout as the PanelView 550 | Third-party adapter on every terminal | Convert in FactoryTalk View Studio ME |
| PanelView Plus 6 700 | Opening must be modified | 2711P-RN6 adapter, documented for sizes 700 through 1500 | Convert, then rescale screens to the larger display |
| C-more EA9 | Check dimensions against the installed opening | EA-DH485-CBL cable to the SLC 5/03 DH-485 port | Rebuild every application in C-more programming software |
The 600 leaves every enclosure untouched and requires one third-party adapter per machine, the ProSoft module type a distributor quotes for exactly this gap. The 700 requires one cutout modification per machine and returns the platform-documented 2711P-RN6 route. The EA9 turns communication into a cable and moves all of the work into rebuilding applications. Hold keypad terminals on keypad replacements and touch on touch wherever the audit allows: operator training survives and the conversion has one less variable.
Convert one application before buying anything #
- Open one PanelBuilder application in FactoryTalk View Studio ME and run the conversion to the PanelView Plus 6 target.
- Read the conversion log and give every entry a disposition; Rockwell publications 2711P-AP005 and 2711P-AP006 document what converts automatically, what converts with edits, and what must be rebuilt.
- Recreate the macros. Macros are the known gap in this conversion: they do not come across.
- Walk every screen at the target resolution. Scaling holds on most pages and fails on the rest; fix the failures page by page.
- Correct text alignment and indicator color states, which both shift in conversion.
- Rebuild the communication path for the new terminal; conversion does not carry it.
- Strip F1-F4 references from screen buttons when the target is touch-only, because operators will look for keys that are not there.
The simulator in FactoryTalk View ME proves navigation, graphics, and logic; it proves nothing about the DH-485 adapter path. Use it, then copy the pattern of testing HMI simulation against a live PLC for everything the simulator cannot reach. Commission one pilot machine with the old terminal boxed as the rollback. Lock out the machine and verify the terminal supply recorded in the audit is dead before the door comes open — the swap happens inside the enclosure. Run the pilot across production shifts before the fleet order.
Worked example: splitting a 25-terminal fleet #
An illustrative audit of a 25-unit fleet returns 19 DH-485 keypad terminals, 4 DH-485 touch terminals, and 2 terminals whose catalog numbers decode to RS-232.
- DH-485 population: 19 keypad + 4 touch = 23 terminals.
- Plus 6 600 route: 23 terminals and 23 third-party adapters, plus 2 spare terminals and 2 spare adapters — 25 of each on the order.
- Plus 6 700 route: 23 terminals, 23 2711P-RN6 modules and 2 spares, plus 23 cutout modifications.
- EA9 route: 23 EA-DH485-CBL cables, bounded by one documented limit — the cable is 9.8 ft (3 m), so any panel mounted farther from its SLC 5/03 DH-485 port cannot take this path as wired.
- The 2 RS-232 terminals appear in none of these counts.
Decisions by group:
- The 19 keypad terminals go to PanelView Plus 6 600 keypad with one third-party DH-485 adapter each: no enclosure work, and keypad input survives for gloved operators and vibration.
- The 4 touch terminals go to PanelView Plus 6 600 touch with the same adapter, unless their panels can be modified, in which case a Plus 6 700 with the 2711P-RN6 trades the third-party adapter for a cutout change.
- The 2 RS-232 terminals migrate on their own ports, with no DH-485 hardware bought for them.
- The default for this fleet is the Plus 6 600 path because it touches no enclosure. Take the 700 where modification is acceptable and the documented adapter matters; take the EA9 where the cable reaches and rebuilding simple applications beats fitting an adapter at every machine.
- Standardize all 23 DH-485 replacements on one configuration and hold the 2 spares against it, so one configuration covers the fleet the way one spare HMI panel covers seven machines when projects share hardware.
Wiring the DH-485 side #
On the Plus 6 700, the 2711P-RN6 module carries DH-485 among its supported networks and lands the SLC end on the processor's DH-485 port; for conductor-level work, DH-485 wiring for an HMI replacement covers the pin assignments. On the EA9 path, the EA-DH485-CBL runs from a 15-pin male D-sub at the panel to a 6-pin RJ45 at the SLC 5/03 DH-485 port, shielded, 9.8 ft (3 m) overall. Measure each panel-to-port distance during the audit, not at installation.
When the controller retires too #
DH-485 is on these machines because the SLC 5/03 is. Any machine whose controller is scheduled for replacement should leave this migration before the order: the new controller brings Ethernet, the operator station becomes PC-based, and industrial panel PCs fill that role with no DH-485 adapter to buy. An adapter purchased for a retiring network is the one waste this audit exists to prevent.
Questions asked
Does the C-more EA9 route need anything besides the cable at 120 VAC?
Check the panel's power specification against the cabinet supply before ordering. The DH-485 cable only solves communication; on machines with 120 VAC control power, EA9 installations commonly add the EA-AC power supply to feed the panel. Record the cabinet supply voltage in the audit so power hardware is ordered with the cables, not discovered at install.
What connector plugs into the 2711P-RN6 DH-485 port?
A 6-pin linear-style connector without jack screws, catalog number 1746-RT30. Because the shell has no screw retention, leave slack in the cable and route it so nothing tugs on the connector while the machine runs. Order one connector per adapter, plus spares for the fleet.
How clean is a converted application on a simple PanelView 550?
A ten-screen, mostly-display PanelView 550 application converted to a PanelView Plus 6 600 came across with roughly 99 percent of its content intact, and a conversion run under FactoryTalk View Studio ME V7.0 completed with no conversion errors. That is the best case: simple applications convert well, but every conversion still gets the object-level inspection and a rebuilt communication path.
What software do I need to own before choosing a path?
The Allen-Bradley path requires FactoryTalk View Studio Machine Edition to convert the PanelBuilder application and load the PanelView Plus terminal. Confirm you hold a current license before committing the fleet to it. The C-more path skips that license but every application is rebuilt from scratch in C-more's own programming software, so the cost moves from software to labor.
Will every one of the 25 terminals need DH-485 hardware?
No. The audit usually shows most, not all, of a fleet like this on DH-485; the rest decode to ports like RS-232. Those terminals need zero DH-485 adapters, cables, or modules, and they become their own migration group. Ordering 25 identical DH-485 kits is precisely the error the catalog-number audit exists to catch.