A driver is a match only when the exact CPU model and the installed communications interface both appear in the panel vendor's documented driver list. This checklist covers what to record from the PLC, the Modbus TCP route for 505-series processors through a 2572-A Ethernet module, a register addressing example, and the stop conditions.
Before you order a panel for an old PLC, put two identifiers on paper: the exact CPU model and the communications interface installed in the chassis. A driver entry in the panel vendor's list is a match only when both appear, together with the interface and mode that driver needs. A family nickname such as 5x5 will not get you there. When the exact CPU has no direct driver, 505-series processors have a documented shared-protocol route: Modbus TCP through a 2572-A Ethernet module in the chassis. Work this checklist before the purchase order, not after the panel is on the bench.
Which PLC details do you match against the HMI driver list?
You match the exact CPU model from the nameplate and the module part numbers from the chassis slots. A family name such as 5x5 covers several processor generations, and a 505-series driver entry does not cover every CPU that family nickname includes.
Record these before you contact any panel vendor:
- CPU model, read from the nameplate and confirmed in the programming software's online view.
- Every communications module, with its slot number and part number.
- The CPU firmware revision, if the software displays it.
- The port type on each module: RS-232, RS-485 or Ethernet.
Driver entries are written against exact processor series, so the vendor's list wants a model number. Write the identifiers down first, then compare. For what to do once the list is open in front of you, see checking the panel driver list before tuning serial settings.
What else must the driver match besides the PLC name?
Two things must match: the CPU family the driver was written for, and the interface your PLC actually has installed. A driver built for a serial port on the processor will not serve traffic arriving through an Ethernet module.
Read the connection method stated in each driver entry:
- Serial drivers name a port type and a wiring scheme: RS-232 point to point, or RS-485 multidrop.
- Ethernet drivers name the protocol carried over TCP, and which end acts as the client.
A serial driver speaks the protocol of the processor port it was written for. An Ethernet module carrying the processor protocol inside TCP packets is a different connection, and the panel side needs the matching client or server mode. The same discipline applies when you replace an old panel instead of adding one: check the PLC serial protocol before replacing a legacy HMI.
What do you do when no driver lists your CPU?
Connect through a protocol both sides document. For 505-series processors, the established route is Modbus TCP through a 2572-A Ethernet module in the PLC chassis, with the panel acting as a Modbus client and the module answering on the network.
The module's Ethernet manual documents two modes. In server mode the module answers requests carried inside TCP/IP packets. In client mode it initiates a TCP/IP message to another node on the network. An HMI poll uses the first arrangement: the module serves, the panel polls. Get that manual for your module revision from the module vendor or its distributor, and confirm the Modbus service and the connection count for your revision before you specify the panel.
Two rules keep this route honest:
- The route belongs to 505-series processors. A different CPU inside the 5x5 family has no claim on it until the module documentation names that CPU.
- The panel sees Modbus registers, not processor addresses. Every value on the screen needs a documented register map.
How do you verify the Modbus TCP path before ordering?
Verify three documented items before the order: the module revision's Modbus server mode, a written panel-side confirmation of Modbus TCP client operation, and the standard Modbus TCP service port 502 open between panel and chassis on your network plan.
Close each item on the list:
- Module side: server mode, supported connection count and TCP port, all read from the manual for your revision.
- Panel side: written confirmation that the panel runs as a Modbus TCP client, at the poll rate you need. One panel maker's Modbus server connection guide documents up to 64 simultaneous client connections on its Ethernet server, which tells you how many panels one chassis module can feed.
- Network side: IP plan for panel and module, port 502 reachable end to end, and no firewall rule between them.
- Data side: a register map in writing, with data type, scaling and a read or write flag per point.
How does the address mapping work in one example?
Work one point end to end before mapping the rest: the panel polls holding register 40001 at unit ID 1 through port 502 every 1000 ms, the PLC word holds an oven temperature in tenths of a degree, and 1873 counts displays as 187.3 °C.
Take one packaging line. A 505-series CPU carries a 2572-A Ethernet module at 192.168.1.50, and the panel sits at 192.168.1.61 on the same subnet. The PLC stores an oven temperature in one 16-bit word as tenths of a degree, and the module maps that word to holding register 40001. Treat that mapping here as illustrative: on a real line the module documentation supplies it.
- Range: 0.0 to 250.0 °C stored as 0 to 2500 counts, since 250.0 × 10 = 2500. One 16-bit word holds 0 to 65535, so 2500 fits with headroom.
- Panel scale: one count = 0.1 °C, so the displayed value = counts × 0.1.
- Commissioning read: 1873 × 0.1 = 187.3 °C. Open the programming software's online view and read the same word: 1873 there confirms the address and the data type in one check.
- Starting poll settings: 1000 ms poll, 3000 ms timeout. A temperature display refreshes fast enough at that rate; if points lag later, fixing Modbus TCP data slow to update on an HMI panel covers the tuning.
Map the remaining points the same way: register, data type, scale, read or write.
What should you send the panel vendor with the quote?
Send hardware identity, data requirements and the network plan. The vendor's driver confirmation is only as good as the identity you provide, and a wrong CPU model in the request comes back as a panel that will not connect.
Group the request in three parts:
Hardware identity
- CPU model and firmware revision.
- Chassis slot map with every module part number.
- Port type on each module.
Data requirements
- Point count, split into reads and writes.
- Data type and scaling for each point.
- Required update rate in ms.
Network plan
- Panel and module IP addresses with the subnet.
- Confirmation that port 502 is open end to end.
- The register map you expect, and a request for the vendor's own map in writing.
Ask for the driver name and its documented CPU list in the quote reply, so the confirmation binds the vendor to the exact processor.
What do you check first when the panel will not talk after install?
Check reachability before registers: ping the module address, confirm port 502 answers between the panel and the chassis, and only then compare register numbers and data types. A device that answers with wrong data has a mapping fault, not a network fault.
Work the checks in this order:
- Link lights and IP settings at both ends.
- Ping the module address from the panel's network.
- Confirm port 502 answers and the panel reports a live connection.
- Read the one point you proved during commissioning.
- Test writes last.
Failure at steps 1 to 3 points to the network. A live connection with wrong values points to the register map. Two articles cover the halves: fixing an HMI PLC Ethernet connection timeout on first setup, and when the HMI pings the PLC but reads fail. Test writes last, on a point whose effect on the machine you have traced, with the operator told first: a wrong register write can start a cycle.
When should you stop and change the plan?
Stop when the exact CPU stays unidentified, when the module documentation shows no Modbus mode for your revision, or when the reply comes back without a register map. No driver choice fixes the link from there, and the decision becomes a communications upgrade or a processor migration.
The three stop conditions, each with its decision:
- The nameplate is gone and the programming software will not connect, so the exact CPU stays unknown. Decision: plan a processor migration and keep the old panel running meanwhile.
- The module documentation shows no Modbus mode for your revision. Decision: upgrade the chassis communications with the current module for that processor line, or migrate the processor.
- The vendor answers the driver question with a family name and sends no register map. Decision: get another quote. A confirmation without the exact CPU behind it supports nothing on your floor.
For machine-side planning once the decision is a retrofit, the PLC and HMI retrofit checklist for an old stretch wrapper walks the same discipline end to end. And if what that floor needs is a notice board with shift targets and safety messages rather than machine control, that screen needs no PLC driver at all: the shop-floor signage in our catalog plays that content from a card, offline, with no subscription.
Recommendation: Order the panel only after the exact CPU model and the installed communications interface appear together in the vendor's documented driver list. When they do not, and the CPU is a 505-series unit, specify the Modbus TCP route through the 2572-A Ethernet module, and hold the order until the module documentation confirms the server mode for your revision and the register map is in writing.
Questions
Can a protocol converter box replace a missing driver?
It can, when the converter documents both sides: your PLC protocol and port on one side, Modbus TCP on the other, plus a register map. It adds a device to maintain and a second failure point, so choose it when the chassis-module route is unavailable. Confirm the converter passes writes as well as reads before ordering.
What if the driver list shows only a family name and no CPU models?
Ask the vendor for the supported CPU list behind that entry, in writing, with the interface and mode. Family-level entries often span several processor generations with different ports, and the exact model decides. If the reply comes back with the family name again, treat the entry as unconfirmed for your CPU and move to the shared-protocol route.
Do you need the PLC program just to check driver support?
No. The nameplate and the chassis give the CPU and module identity the driver check needs. You need the program later, for the register map: the online view shows the data table addresses, the data types and which points the panel must write, and that is what goes into the quote package.
Is Modbus TCP fast enough for HMI screen data?
On a switched plant LAN, yes, for display and operator traffic. A 1000 ms poll of a few dozen registers is a light load for TCP, and one panel maker documents 64 simultaneous client connections on its server. Keep motion control and closed-loop updates off the HMI poll; they belong on their own link.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.