Troubleshooting
When the HMI Software Has No Driver for Your PLC
Short answer
If the Device/PLC list in your HMI software has no driver for the controller family, that project cannot open a native connection — no cable, baud rate or tag edit adds one. Confirm the list for the exact software version, then either move the project to software that documents the driver with a panel it supports, or replace the panel side. In the GP2500 case, the count comes to 3 of 4 required matches, which fails.
On this page
If the Device/PLC list in your HMI programming software carries no driver for your controller family, that project cannot open a native connection to the PLC. No cable pinout, baud rate, station address or tag edit creates a driver the software does not have. The check that decides everything is the device list of the exact software version in front of you. This article walks that check for the case where a GP2500 programmed in GP-PRO/PBIII V7.0 faces a Delta DVP-ES2, then lays out the routes that actually work when the list comes up empty.
What the device list decides #
Every HMI programming package draws its native PLC support from a driver set published for that software product. Pro-face, for instance, publishes a connectable-devices list for GP-Pro EX and a separate one for the Blue OS software that runs on PS6000 and PS5000 panels and on third-party PCs. What the list requires is simple: your panel model, your software product and version, your controller family and your interface must appear together as a supported combination, and each driver entry names the controller series it actually serves. The Rockwell communication driver entry lists SLC500, PLC-5, ControlLogix, MicroLogix, CompactLogix, FlexLogix and Micro800 series; the Omron C/CV Host Link entry lists SYSMAC C, SYSMAC α and SYSMAC CV series. A series outside those lines is outside that driver.
Four things must line up, and you check all four every time:
- Panel model — the exact unit on the machine, read from its nameplate.
- Software product and version — the release that owns the project, not a newer one on another PC.
- Controller family — the PLC series, down to the CPU family the driver entry names.
- Interface and port — serial or Ethernet, and the specific port the driver entry documents.
The list also decides the panel side of the same question, which is the mirror problem covered in when an HMI model is missing from the programming software.
Confirm the driver in the exact software version #
Run the check in the software that actually programs the panel — here, GP-PRO/PBIII V7.0 — because driver sets differ between products and releases.
- Open the project and go to the Device / PLC settings area.
- Click the manufacturer group, then look for the series driver. The documented pattern in current software is: after installation, execute GP-Pro EX, click the Device / PLC area's [OMRON Corporation] selection and select [CS/CJ/NJ Series EtherNet/IP]. Every other manufacturer group follows the same two-step shape: group first, series driver second.
- Read the driver entry's supported-models text before selecting anything. A similarly named entry does not establish support; the model list inside the entry does.
- Record the result together with the software version. "No Delta group in GP-PRO/PBIII V7.0" is a fact that drives the decision; it is not a setting you can argue with.
Worked example: GP2500 on GP-PRO/PBIII V7.0 against a Delta DVP-ES2 #
Inputs, each with its source:
- Panel model: GP2500, from the machine the HMI is mounted in.
- Software: GP-PRO/PBIII V7.0, the release that owns the project on the engineering station.
- Controller: Delta DVP-ES2, the PLC the panel must serve.
- Device-list result: no Delta entry in that release's Device/PLC list.
Rule in words: a native HMI-to-PLC link needs four listed matches — panel, software version, controller family, interface — and four of four is the pass mark; anything less fails the whole set.
Arithmetic:
- Required matches: 4.
- Confirmed on site: 3 (GP2500, GP-PRO/PBIII V7.0, DVP-ES2).
- Added by the driver list: 0 — with no Delta entry, the interface match never even opens.
- 3 + 0 = 3 of 4, which is 75 percent.
Decision: at 3 of 4, with the missing item being the controller family itself, stop editing tags, ports and cables — none of them raises the count. The threshold is absolute: below 4 of 4 listed, the fix lives on the software and panel side. Move the project to software whose published list includes the DVP family on a panel that software supports, or replace the panel side with a combination that documents the driver.
Four ways out when the driver is missing #
Once the list result is recorded, pick one of four routes — there is no fifth:
- Rehost the project on a current software release whose published connectable-devices list includes your controller family, using a panel that release supports. The GP-Pro EX driver list is the reference document for that product.
- Replace the panel side. When the installed panel is no longer served by any current software, planning an HMI terminal replacement from an older operator panel is the route, and the candidate software's driver list is a selection criterion, not an afterthought.
- Bind through a protocol the list already covers. If the controller's own documentation offers an open protocol such as Modbus, and the driver list documents that protocol driver for your panel and port, use it; selecting a Modbus TCP HMI panel for an existing controller walks that choice. The controller must genuinely speak the protocol on a port you can wire — never assume this from the model name.
- Put a gateway in the path. Pro-face documents Gateway Mode compatible drivers for its gateway line, with tested entries such as Fuji Electric MICREX-SX Series SIO, Yaskawa MEMOBUS SIO and Toshiba Machine TC Series. A gateway helps only if your controller appears in that tested list.
Driver problem or tag problem: telling them apart #
A missing driver blocks everything downstream, so settle that question first. The table separates the three symptoms you will actually see:
| What you see | What it usually is | First check |
|---|---|---|
| No entry for the controller family in the Device/PLC list | Missing driver | The published list for your exact software version, then the four routes above |
| Driver selected, panel reports a communication error before any value appears | Port, cable or parameter mismatch | Both interfaces, the cable diagram, identical protocol settings at both ends |
| Values update, one tag shows wrong or faulted data | Tag-level fault | That tag's address syntax and data type against the driver's addressing rules and the PLC program |
The split is strict: changing addresses never repairs a missing driver, and selecting a driver never fixes an invalid address. Work one known PLC address, read-only, before anything else.
Proving the link after the driver is bound #
With a documented driver selected, close the physical path before touching tags:
- Take the cable from the vendor's connection-availability lookup, which pairs a display unit with a controller and lets you select the cable diagram, rather than from a hand-drawn pinout.
- Enter the driver's protocol parameters identically at both ends — port, baud, parity and station address where they apply — taken from the driver documentation and the two equipment manuals.
- Build one test tag on an address confirmed present in the PLC program, read-only, and compare what the panel displays against the controller.
A clean compile or a completed download proves nothing about the link; the only pass mark is a correct value read back from a known address. If you must test a write, do it on a scratch register — an output bit that can start motion is not a test tag on any machine that can run.
Questions asked
Can I add or write a driver myself when the list has none?
Not in any way the vendor stands behind. The published list for your software version is the boundary of native support, and a similarly named driver does not extend it. The working equivalents are a software release that lists the controller family, a panel replacement that documents it, or a protocol the list already covers when your controller genuinely speaks it.
Will upgrading the HMI software alone add my PLC?
Only if the newer release carries its own published connectable-devices list with your controller family on it, and that release still supports your panel model. Driver sets are documented per software product — the GP-Pro EX list and the Blue OS list are separate documents — so verify both the PLC entry and the panel's support before converting the project.
Does a successful compile or download prove the driver works?
No. Compilation checks the project, not the link, and a download that completes can still leave the panel polling nothing. The decisive test is one read-only tag on an address you have confirmed in the PLC program, with the displayed value checked against the controller itself.
The list shows a driver with a name close to my PLC. Is that enough?
No. Open the driver entry and read the supported-models text. The Omron C/CV Host Link entry, for example, serves SYSMAC C, SYSMAC α and SYSMAC CV series; if your CPU is not on that line, the name similarity means nothing. Membership in the entry's model list is the test.
Where do the cable and communication settings come from once the driver is listed?
From the driver documentation and the two equipment manuals, never from guesswork. Pro-face publishes a connection-availability lookup that pairs a display unit with a controller and lets you select the cable diagram; the driver entry then defines the protocol parameters that must match at both ends.