The operator sees an aging, unlabelled HMI that must be repaired or replaced, while the original machine builder is no longer available. The only proposed identification is Pro-face GP230. Treat that as a working candidate, not a confirmed model: select the service path only after the enclosure, electronics, communication interface, and application can be matched.
What is the screen telling you?
An operating screen can prove that the panel still has power, executes an application, exchanges at least some data, and accepts input. It does not prove the manufacturer or model. A custom bezel, removed nameplate, replacement rear cover, or machine-builder branding can hide the underlying product.
Record what the operator sees before cycling power or disconnecting anything. Capture every page, alarm, recipe field, numeric format, unit, language, navigation path, and security prompt. Note which values change with the machine and which remain frozen. These observations become the functional specification if the original application cannot be uploaded.
| Observation | What it indicates | Next check |
|---|---|---|
| All values update | The active driver and controller link are operating | Record cable routing and controller endpoint |
| Screen runs but values do not update | The HMI application may be intact while communications are unavailable | Trace the tag, driver, cable, and controller in that order |
| Touch areas respond incorrectly | The display application may be usable despite a touch-layer or calibration problem | Test each control region without changing the process state |
| Panel does not boot | Identification must come from physical and electrical inspection | Inspect internal markings and interfaces after isolation |
Which replacement approach fits the machine?
Three approaches are practical: repair the installed unit, fit an identical verified panel, or migrate the application. The right choice depends less on the front appearance than on access to the application, controller documentation, and working communications.
| Approach | Best fit | Main dependency | Main risk |
|---|---|---|---|
| Repair the installed HMI | The application still runs and no editable backup exists | A repair path that preserves program memory and configuration | A memory or main-board replacement may return working hardware without the machine application |
| Install the same model | The exact identity and application-transfer method are confirmed | Compatible hardware, firmware behavior, and transfer access | A visually identical unit may have a different interface or hardware revision |
| Migrate to a current HMI | Controller addresses and machine functions can be documented | A new driver configuration and reconstructed or converted project | Missed alarms, scaling, write behavior, recipes, or navigation |
Repair is the preferred first action when the panel operates and no verified backup exists, because it preserves the only known working copy of the application. A same-model replacement is preferable when the complete model identity and a restorable project have been proven. Migration is the controlled choice when hardware cannot be sourced or compatibility cannot be demonstrated.
How do you trace the screen back to the controller?
What the screen is telling you must be traced through four layers: displayed object, HMI tag, communication driver, and controller data. A correct numeric value on one page does not validate buttons, alarms, recipes, or scaled values elsewhere.
- Photograph each screen in a known machine state. Include decimal places, units, alarm text, button states, and access levels.
- Record the cable from the HMI to its next device. Document connector shape, pin use where it can be measured safely, intermediate converters, and whether the route terminates at a controller, network device, or serial adapter.
- Read the controller manufacturer and exact catalog information directly from its installed labels. Do not infer the controller family from the HMI graphics.
- If the running application exposes communication settings, record the driver name, station or node selection, addressing format, and any network values exactly as displayed.
- Change one process condition under controlled operation and follow it from controller input to HMI indication. Then test one nonhazardous HMI command and confirm the intended controller state changes.
The tag is right; the binding is wrong when an object displays the correct type and scaling but points to the wrong controller address or driver endpoint. During migration, compare the source address, data type, scaling, access direction, and update behavior for every critical object.
How do you confirm whether it is a Pro-face GP230?
Pro-face GP230 is the working identification. Confirmation requires markings or a hardware match; appearance alone is insufficient.
- Isolate the panel according to the machine procedure, then photograph the front, rear, sides, connectors, mounting hardware, and cable labels before removal.
- Inspect the rear housing, internal accessible surfaces, printed circuit boards, connector legends, and startup or service screens for manufacturer, model, serial, electrical, or revision markings.
- Transcribe markings exactly. Distinguish
GP230from a family reference, application name, board marking, or machine-builder part number. - Compare the cutout, bezel dimensions, mounting method, power terminals, connector count, connector gender, and port legends with documentation for the candidate unit. A match must cover the rear interfaces as well as the front.
- Confirm the panel supply from its terminal markings and measured installation wiring before connecting a candidate replacement. Never select a supply from appearance or connector style.
- Confirm that the candidate supports the installed controller connection and that the existing application can be transferred, restored, converted, or rebuilt.
If no permanent marking ties the hardware to GP230, catalogue it as an unidentified HMI with GP230 as a candidate. That wording prevents a purchasing assumption from becoming a maintenance fact.
How should the application be recovered before repair?
Preserve the running unit before attempting service that may disturb its storage. A successful upload must contain the machine application rather than only communication settings or a partial runtime package.
- Clone the maintenance investigation on a bench only after recording installed wiring and power requirements.
- Identify the engineering software from existing plant archives, removable media, service laptops, project filenames, or information shown by the panel. Do not install guessed software or initiate a download to the HMI.
- Use a verified communication cable and attempt a read or upload operation only after confirming direction. In HMI tools, download commonly means writing to the terminal and can overwrite the sole application.
- Save the untouched upload as a master copy. Record the software release used to open it, any conversion prompt, transfer settings, and whether the project opens without missing resources.
- Create a second working copy for edits. Export tag lists, alarm definitions, recipes, images, communication settings, and security configuration where the software permits.
- Test restoration to spare hardware or a nonproduction target before relying on the archive.
If upload is blocked or the retrieved file cannot be edited, use the captured screens and controller address map to build a functional specification. Do not treat a screenshot set as a complete project: background scripts, alarm history, recipes, scaling, retained values, and write-on-release behavior may not be visible.
How do you verify the repaired or replacement HMI?
Bench startup proves only that the display boots. Acceptance must test the complete path from operator action through the driver to the controller and back to the displayed state.
| Check | Method | Pass condition |
|---|---|---|
| Power and startup | Use the documented machine supply and observe every boot | No reset loop, display loss, or configuration prompt |
| Communications | Observe changing controller values and communication diagnostics | Values update without stale or substituted data |
| Indications | Apply known controller states | Text, color, units, scaling, and decimal placement match the recorded baseline |
| Commands | Test permitted controls in a controlled machine state | The intended controller bit or value changes once and returns as designed |
| Alarms and navigation | Trigger approved test conditions and visit every page | Alarm text, acknowledgement, page links, and access restrictions operate correctly |
| Power recovery | Perform an authorized power cycle after saving required data | The application starts, reconnects, and retains only the intended values |
Recurring mistakes include ordering from a front-panel resemblance, assuming a connector proves protocol compatibility, powering an unidentified unit from an unverified supply, overwriting the installed application, and testing only passive indications. Finish by executing one approved HMI command, observing the intended controller value, and confirming the resulting machine state returns correctly to the screen.
FAQ
What happens if the panel looks like a Pro-face GP230?
Use GP230 as a candidate until a permanent marking, complete mechanical match, interface match, and compatible application-transfer path confirm it.
What happens if the old HMI still works but no backup exists?
Record every screen and communication detail, then attempt a read or upload before repair. Keep the untouched result as the master and validate restoration on a spare target.
What happens if the replacement boots but values are frozen?
Trace the displayed object through its tag, driver endpoint, cable, and controller address. A running screen does not prove that the communication binding is correct.
What happens if the project cannot be uploaded?
Build a functional specification from screen captures, controller addresses, alarms, recipes, scaling, navigation, security, and observed write behavior, then reconstruct and test the application.
What happens if an identical-looking HMI has different connectors?
Stop the substitution. Verify the full model identity, supply, interface type, pinout, driver compatibility, and application-transfer method before applying power or connecting the controller.