Explainer
Why an HMI logic module will not drive a custom VGA LCD
Short answer
No. The logic module and its display are a paired system: the link carries video and touch plus identification EEPROM that tells the module the display's size, series and revision. A custom VGA LCD cannot supply that data, so the documented path is a display-less industrial PC driving the LCD over standard VGA with USB or serial touch.
On this page
No, it will not work, and the connector drawing in the manual is what makes it look possible. A PanelView Plus logic module is not a computer with an exposed VGA port: it is half of a paired terminal whose display link carries video, touch and identification. The display reports its size so the module can scale the Configuration Mode dialogs of the RSView ME runtime, and an EEPROM inside the display states its series, revision and product family. A custom VGA touchscreen LCD supplies none of that, so no adapter built around the connector satisfies the module. The split that works is the reverse: a display-less industrial PC drives the LCD over standard VGA, the touchscreen connects over USB or serial, and the HMI runtime runs on the PC.
What the display link actually carries #
The family's installation instructions, 2711P-IN004C-MU-P, treat the screen as a module, not a monitor: when a display problem cannot be resolved, the documented action is to replace the 700 to 1500 display module or bezel, and a 1000-size terminal takes a 10 in display module such as 2711P-RDT10C. The logic module plus one of those display modules is the product; the display is not a peripheral you choose.
Three classes of traffic cross the dual connector:
- Video and backlight drive for the integrated panel.
- The touch channel from the panel's own touchscreen.
- Identification, read before the terminal is usable: the display's diagonal, which sizes the Configuration Mode dialogs, and a small serial EEPROM holding the display's series, revision and family heritage.
The identification half is what no custom LCD provides. It is also why a display from the vendor's companion CE computer line cannot substitute: the module reads which family a display belongs to, and the two families' displays are not interchangeable even though their connectors look alike.
Why matching connectors proves nothing #
Every argument for bolting a custom LCD onto the module reduces to one of four assumptions, and each fails the same way:
- The LCD has a VGA input. That establishes a video signal path and nothing more. The module still expects the identification channel it shares with its own display modules.
- The touchscreen is an industry-standard type. A familiar touch controller does not implement the touch channel of this link, and no touch controller supplies the display identification. The brand on the glass says nothing about the protocol behind the connector.
- The connector matches the manual drawing. A connector illustration documents mechanical fit for the vendor's own modules. It publishes no pin assignment, and pin assignments must not be inferred from a drawing.
- A display from a related vendor product will do. The EEPROM records family heritage precisely so that does not work.
Since no public document describes the interface beyond those pairings, every adapter design collapses onto the same gap: guessed pin assignments and guessed EEPROM contents, with no support path when the terminal misbehaves. Stop before the crimp tool.
Checking the LCD diagonals against the display-module range #
Inputs:
- Diagonals of the LCDs to be reused: 18 in and 20 in, the high-brightness daylight-readable modules already in service.
- Documented display-module sizes for this terminal family: 7 to 15 in diagonal, the 700 to 1500 display modules the manual names as the replaceable display.
Rule in words: the logic module pairs only with its own family's display modules, so a display is a candidate only if its diagonal falls inside the range those modules cover.
Arithmetic, subtracting the largest documented module from each requested diagonal:
- The smaller LCD lands 3 in beyond it.
- The larger LCD lands 5 in beyond it.
- Both requested diagonals sit above the family's upper bound, outside its 8 in span.
Result: neither LCD matches, or even approaches, a documented display module.
Decision: any LCD above the largest documented diagonal has no documented pairing to emulate, so the connector question never gets a fair start — go directly to the display-less PC route below.
The documented route: a display-less industrial PC #
Driving your own large daylight-readable LCD is a PC requirement, not a terminal requirement. The replacement half is an industrial mini PC: a compact display-less computer that feeds the LCD from a standard video output, takes the touchscreen over USB or serial, and runs the HMI software. Compact DIN-rail computers of this class have been used exactly this way with 18 and 20 in daylight-readable panels.
The software side has its own rule: HMI runtimes are sold per platform, and the terminal's machine-edition project does not by itself license a PC runtime, so confirm the pairing with which HMI software works with which panel hardware before you plan the migration.
Bring the station up in this order:
- Video first, at the LCD's native resolution, with no adapter in the path.
- Touch second: the touchscreen enumerates in the operating system before the runtime opens.
- Application last: restore the project and confirm live values update.
The procedure for commissioning USB-VGA video and touch on a native HMI walks through that bring-up step by step.
Verifying the station before it runs #
- Image at native resolution, legible at the installed angle in the daylight the screen must survive.
- Touch across the whole screen in the operating system, then again inside the runtime: a working image proves nothing about touch, and working touch proves nothing about the application.
- Configuration, alarm and recipe dialogs legible at the final resolution.
If this station is the operator's only way to stop the machine or acknowledge alarms, make the change during a planned stop and confirm the emergency-stop path never passes through the HMI before production restarts.
The decision for each case #
- Keep the terminal, failed screen: replace the display module or bezel documented for the size, within the 700 to 1500 range, and pair it per the manual.
- Use your own large daylight-readable LCD: display-less industrial PC, standard video to the LCD, USB or serial touch, runtime on the PC. The logic module stays out of it.
- Use a smaller custom LCD: still no. The identification gap is independent of size — only the documented display modules carry it — so the PC route is the answer there too.
Questions asked
Can I emulate the display's identification EEPROM so the logic module accepts my LCD?
Not through any documented path. The link's pin assignments and the EEPROM contents are unpublished, so an emulator would be a guess against an undocumented interface, and even a booting image would leave Configuration Mode unsized or wrongly sized. The engineering time is better spent on the display-less PC route, which needs no emulation at all.
My module powers up but the screen stays dark. Is that the missing identification?
Not necessarily, and you can split the fault before changing anything. A partial image or a working backlight with no boot points at the logic module; a completely dark screen points at the display or its backlight; a loose or oxidized ribbon cable between the bezel and the logic module also gives no display. With every cable removed, wait 30 seconds, reapply power, and see whether the module itself boots.
Which display sizes can the logic module actually pair with?
The documented display modules run from 7 to 15 in diagonal, the 700 to 1500 sizes. Both diagonals you asked about sit above the largest of them, so both are outside every documented pairing. Any diagonal beyond that upper bound closes the terminal route before the connector question even starts.
What interfaces does the display-less PC need for my LCD?
One video output that matches the LCD's native input, one USB port or serial port for the touchscreen controller, and the performance your HMI runtime asks for. Drive the LCD natively with no video adapter during bring-up, and bring touch up separately: a working image proves nothing about the touch channel.
Do I lose the terminal's Configuration Mode by moving to a PC?
You trade it for the PC's own controls. On the terminal, Configuration Mode depends on the display identification; on a PC the operating system's display settings set the resolution and the runtime is administered from the development software, so nothing on the machine side reads display EEPROM data anymore.