Skip to main content
Weinview

Replacing a Discontinued HMI Panel: Why Screen Size Is the Least of It

When an operator panel goes out of production, screen size is the easiest axis to match. The twelve other axes — protocol drivers, project-file portability, IP rating, certification scope — decide whether the substitute actually drops in. Here is the cross-reference method an independent desk uses for HMI replacement work.

Replacing a Discontinued HMI Panel: Why Screen Size Is the Least of It

An operator panel sits on a machine for fifteen years, then one morning the manufacturer announces the model is out of production and the franchised channel stops quoting. The buyer's first instinct is to find another panel of the same diagonal. Screen size is the easiest axis to match and almost never the one that decides whether the replacement actually works. The twelve other axes — protocol drivers, project-file portability, IP rating, certification scope — are the binding constraints. This article walks through the cross-reference method an independent industrial-automation sourcing desk uses for HMI replacement work.

Data through: September 2026. Independent industrial-automation distributor. Not an authorized distributor of any manufacturer named in this article.

The buyer's question, in their own words

When a Russian or CIS buyer asks «Чем заменить снятую с производства панель оператора?» — a substitute for a discontinued operator panel — the question is rarely about the panel itself. It is about the program that runs on it, the PLC it talks to, the cut-out in the cabinet door, the spare-parts shelf, and the maintenance technician who has to keep the line alive for another decade. The honest answer to that question is rarely a single part number; it is a documented comparison with the unverified axes named and the work that has to happen before commissioning flagged up front.

Two parts can look identical from the front and still differ in the engineering software that compiles the screens, the set of PLC drivers the runtime supports, the file format of the project you spent three weeks building, the IP rating on the front face when the cabinet door is closed, the operating-temperature range when the cabinet sits next to a furnace, or the certification scope that lets the machine ship into its destination market. A cross-reference report that names only the matched axes is misleading by omission — it implies the rest matches too.

Why screen size is the wrong starting line

Screen size is the diagonal of the visible area, measured in inches or centimetres. A 7-inch panel replaces a 7-inch panel; a 10-inch panel replaces a 10-inch panel. Most cross-reference web-tables stop there because the diagonal is the easiest number to publish. It is also the least likely to be the binding constraint on a working machine.

The diagonal decides only one thing: whether the new panel fits the cut-out in the cabinet door. Most machine builders leave a few millimetres of tolerance, so a 7.0-inch panel can often replace a 6.5-inch, and a 10.1-inch can often replace a 10.4-inch with minor rework. The binding constraints live in the other eleven axes — and the axes that bite the hardest are almost never the ones that look like they would.

A packaging-line HMI built around a Weinview MT-series 7-inch panel, for example, will likely face three different constraints when the original panel goes out of production: the project file (EasyBuilder Pro) compiled for the original model often needs to be re-imported into the new toolchain because the firmware family has changed; the PLC driver set on the new panel may not include the exact controller the line uses; and the front-face IP rating drops from IP65 to IP54 on a cheaper substitute, which is invisible from the data sheet but matters the first time the cabinet is hosed down. None of those constraints appears in the diagonal.

The twelve axes we check on every HMI cross-reference

The cross-reference framework this desk applies is the same twelve-axis framework used for any industrial-automation substitution — PLCs, drives, I/O modules, sensors. The twelve axes fall into four groups: physical fit, electrical and functional, software and protocol, and lifecycle and certification. Each axis is reported as matched, differs, or unknown rather than passed over silently. An axis we could not verify is written down as unknown — the manufacturer does not publish the answer, the documentation has not been translated, or the value differs between firmware revisions of the same model number.

Form, fit and dimensions

Form, fit and outline covers the visible diagonal, the cut-out in the cabinet door, the depth behind the panel (including the connector clearance), the mounting method (clamp, screw, or bezel-integrated), and the weight load on the cabinet door. Two 7-inch panels from different families almost never share the same cut-out; the difference is usually two to four millimetres on each edge, which is enough to require a new cut-out or a bezel adapter. The dimensions axis pulls the same data with explicit numerical tolerances — a 192 mm × 138 mm cut-out is not the same as a 198 mm × 142 mm cut-out, even if both are called "7-inch". When the depth behind the panel exceeds the cabinet door by more than the cable-bend radius allows, the connector cannot seat and the panel cannot close.

Terminal and interface assignment

Terminal and interface assignment is the most common silent failure on HMI cross-references. The power terminals (24 V, functional earth) often sit on a different connector; the COM port pin-out for RS-485 two-wire vs four-wire differs across families; the USB port for project download moves from the front face to the side or disappears; the Ethernet port moves from one RJ45 jack to another and the activity-LED behaviour changes. A panel that looks identical from the front can have a completely different wiring diagram, and the wiring diagram is what determines whether the line powers up at all.

Electrical ratings

Electrical parameters covers the supply-voltage range (most industrial HMIs run on 24 VDC ±20 %), the inrush current at power-on (which trips an undersized 24 V supply when an older machine is refurbished), the power consumption under full backlight, and the isolation between the supply and the communication ports. A panel that draws 1.2 A on inrush into a 3 A shared supply is fine; the same panel on a 1.5 A shared supply with two other loads browns out at every cold start.

Function and I/O specification

Function and I/O specification is where HMI cross-references most often hide a real difference. Touch type (resistive vs projected capacitive), touch accuracy, the number of simultaneous touch points (single-touch only on most industrial panels, multi-touch on newer families), display resolution (800 × 480 vs 1024 × 600 on a "7-inch" panel), brightness (200 vs 400 vs 1000 cd/m²), viewing angle, and the colour depth (65 k vs 16 M colours) all live on this axis. A resistive panel works with a gloved hand; a projected-capacitive panel does not. A 200 cd/m² panel is unreadable in direct sunlight; a 1000 cd/m² panel is unreadable at night without dimming. None of these constraints is visible from the diagonal.

Firmware, hardware version and engineering software

Firmware, hardware version and engineering-software compatibility is the axis most often left as unknown, and the one that decides whether the project file actually loads on the new panel. An EasyBuilder Pro project compiled for one MT-series model often needs a target-model change, a recompile, and a tag-database re-export; an EasyBuilder Pro project compiled for a completely different vendor's runtime needs a full screen rebuild because the widget library, the alarm structure, and the macro language all change. The project-file portability is not a property of the panel — it is a property of the engineering software that compiled the project. When we do not have access to the original project files or the original engineering software version, this axis goes on the unknown list by default.

Communication and protocol

Communication and protocol is the axis that decides whether the panel actually talks to the PLC. The protocol-driver library shipped with the panel's firmware has to include the exact controller family, the exact protocol variant (Modbus TCP vs Modbus RTU vs EtherNet/IP vs PROFINET vs Mitsubishi MC vs Omron Host Link vs Siemens S7 MPI/ISO), and the exact addressing mode (zero-based vs one-based, byte-swap vs word-swap). A panel that supports "Siemens S7" may support only the S7-300/400 MPI protocol and not the S7-1200/1500 PUT/GET or S7-communication; the line comes up with a "PLC no response" alarm and the panel is not at fault. The driver set is the answer, not the brand.

Mechanical parameters

Mechanical parameters covers the front-face gasket material and replacement cycle, the touch-screen scratch resistance (Mohs hardness), the connector mechanical life (number of insertion cycles on the USB and COM ports used for project download), and the allowable torque on the power-terminal screws. A panel destined for a high-vibration environment (a press, a stamping line, a weaving loom) needs a connector that is rated for vibration; the data sheet rarely says so explicitly.

Environmental class and EMC

Environmental class and EMC covers the operating-temperature range, the storage-temperature range, the relative-humidity range, the pollution degree, the installation altitude, and the EMC immunity and emission class. A panel rated 0 °C to 50 °C is not a drop-in for a panel rated −10 °C to 60 °C on a cold-storage line or an outdoor cabinet in a Russian winter. The pollution degree (2 vs 3) decides whether the panel can be installed next to a drive without a clearance gap. The altitude rating (2000 m vs 4000 m above sea level) is irrelevant at sea level and binding at a high-altitude installation.

Ingress protection and temperature

Ingress protection and temperature range splits the front-face IP rating (the rating that applies when the panel is mounted in a cabinet door) from the rear-side IP rating (which is usually IP20 and is irrelevant when the cabinet is closed). A panel with IP65 on the front face and IP20 on the rear is the standard industrial pattern; a panel with IP66 on the front face adds resistance to high-pressure hosing but only when the gasket is correctly seated and the cabinet door is closed. The operating-temperature range is the binding constraint on cold-storage lines, foundry lines, and outdoor cabinets; it is rarely the binding constraint on a climate-controlled factory floor.

Materials and construction

Materials and construction covers the bezel material (plastic vs aluminium), the touch-surface treatment (anti-glare, anti-fingerprint, anti-bacterial), the PCB conformal coating (none vs acrylic vs urethane vs Parylene), and the RoHS / REACH status. A panel that lacks conformal coating fails faster in a high-humidity or condensation-heavy installation; a panel with a plastic bezel is harder to wipe down with the solvents used in food-and-beverance lines and picks up scratches faster than an aluminium bezel.

Certifications and lifecycle

Certifications and lifecycle is the axis we explicitly do not write on. We do not hold CE, UL, CSA, EAC or TR CU certifications. We do not issue any declaration of conformity. The panel's own certification scope — the file numbers printed on the nameplate or listed in the manufacturer's declaration — is the certification scope the importer is responsible for, and any change to the panel (a different model number, a different revision, a different firmware version) potentially changes that scope. Lifecycle status (current, phased out, end-of-life, last-time-buy) is the property that decides whether the panel can be ordered again next year or whether the spare on the shelf is the last one the line will ever see.

Three cases where the substitution is the wrong answer

The cross-reference framework is honest because it names cases where no substitution should happen. Three come up often enough to be worth writing down.

Safety-requalified panels. A panel used as part of a safety-related human-machine interface — a fault-display panel on a light-curtain trip, a status panel on a guard-door interlock, a panel that drives an emergency-stop acknowledgement — carries a functional-safety claim that is not transferable to a different model. The new panel has its own SIL / PL rating (or none), its own response-time data, and its own certification scope. An independent sourcing desk does not qualify a safety-related substitute; the safety re-assessment is the machine integrator's responsibility, on the integrator's quality system, with the integrator's documentation. We will quote the panel — we will not make the substitution claim.

Panels tied to a certified application. A pharmaceutical-line HMI, a medical-device HMI (non-implantable), a panel that drives a CE-marked machine into the European market, a panel that ships with a GOST-R / EAC declaration into the Russian market — all of these are tied to a certification scope that the panel shares with the rest of the machine. Substituting the panel may invalidate the scope. We name this on the cross-reference; the importer and the certification holder decide.

Panels where the project file is the asset. A panel whose real value is the project that has been built on it — three weeks of an integrator's time, the tag database, the alarm structure, the macro logic, the recipe handling — is not interchangeable on file format. The hardware may be replaceable; the project may not. A cross-reference report that does not name the project-file portability axis is the cross-report that costs six months in re-engineering. We list the engineering-software family, the runtime version, and the firmware revision in the cross-reference; we do not assume project portability.

How a buyer-facing cross-reference report is actually written

The cross-reference report this desk delivers is short and structured. It does not say "compatible" or "not compatible" — it names the twelve axes and gives a verdict on each. The verdicts are the three states the framework defines: matched, differs, unknown. The structure is the same every time so a buyer can read one cross-reference and know where to look on the next.

The report opens with the two sides — the discontinued panel (manufacturer, model, diagonal, cut-out, the engineering software the project was built on) and the candidate panel (the same five fields, plus the firmware revision and the runtime version). It then lists the twelve axes in order, with a one-line verdict per axis and a one-sentence explanation. The explanations are written for an engineer, not a buyer — terminal pin-out is shown, the protocol driver name is shown, the front-face IP rating is shown with the caveat about rear-side IP20.

Unknown axes are written down. "Unknown — the manufacturer does not publish the function-state for this firmware revision" is the legitimate verdict on firmware_version when the change-log has not been published. "Unknown — we do not have access to the original project file" is the legitimate verdict on firmware_version when the buyer has not supplied the project. Skipping the axis is not an option; omitting it implies it matches.

The report closes with one explicit "do not substitute" scenario (a safety-related re-application, a certification-scope re-application, a project-file incompatibility) and one explicit verification clause: verify against the original manufacturer datasheet and your own qualification process. The verification clause is non-negotiable. The cross-reference report is a comparison; the qualification is the buyer's.

What we can and cannot do on an HMI substitution request

The work this desk takes on an HMI substitution request is bounded, and the boundary is the same boundary we draw on every cross-reference engagement. We can read the project file (or the engineering-software export) and tell you which model and firmware revision it was built for. We can produce a cross-reference report across the twelve axes for any two specific panels you name, with the unverified axes named. We can source both panels — the discontinued one through remaining channel stock, last-time-buy, or documented cross-reference to a current model, and the candidate one through the same channels. We can consolidate both panels into a single shipment with a single set of documents, with the condition (new surplus, refurbished, used) stated per line on the quote.

We cannot re-engineer the project file. We cannot certify that the substitute panel is functionally equivalent to the original on your machine, in your application, with your PLC firmware, under your safety re-assessment. We cannot re-issue the certification scope of the machine. We cannot qualify a substitute panel for a safety-related re-application; that work belongs on the integrator's quality system with the integrator's documentation, not on a sourcing desk's cross-reference report.

How to send an HMI substitution request that gets quoted the same day

Three pieces of information let us turn an HMI substitution request into a quote without a clarifying round-trip. The first is the original panel — manufacturer, full model number (including any revision suffix), the engineering software that built the project, and the project file if the buyer is willing to share it (the file lets us name the firmware-version axis as something other than unknown). The second is the candidate panel, if the buyer has one in mind — same five fields. The third is the application context — the cabinet cut-out dimensions, the operating-temperature range, the protocol the panel has to speak to the PLC, and the certification scope the machine ships under.

What we do not need is the whole machine drawing, the project source code, or the integrator's qualification report. The cross-reference is at the panel level, not at the machine level; the qualification is the integrator's.

To start, send the two part numbers (or photos of the nameplates) and the project file to /inquiry. Quote per line, condition per line, consolidated shipment to the agreed Incoterm. Verify against the original manufacturer datasheet and your own qualification process before commissioning.

Data Notes

As of September 2026, the Weinview MT-series 7-inch line remains listed in the manufacturer's active catalogue, with a number of legacy variants flagged as "phased out" on the manufacturer's product page. Cross-reference work on HMI panels remains consistent with the twelve-axis framework documented in the references bundled with this site; the framework itself is unchanged from earlier revisions. Where this desk has handled a comparable request, the binding constraint was on the protocol-driver library rather than the visible diagonal. As of the same period, no general statement can be made about lead times across the secondary market; condition, price and readiness are quoted per order. The screening posture in this article — end-user and end-use classification before quoting — applies regardless of the destination market the buyer states.

Practical takeaway

The honest answer to «Чем заменить снятую с производства панель оператора?» is rarely a single part number. It is a cross-reference report with the twelve axes in a deliberately fixed order, the matched axes named, the differing axes named, the unknown axes named, one explicit do-not-substitute scenario, and a verification clause that puts the qualification on the buyer's engineering team. The diagonal of the new panel is on the report — it is just not the binding constraint on most real machines. The binding constraint is almost always the protocol-driver set, the project-file portability, or the certification scope — and the cross-reference report is the document that names which one, on this machine, on this application, with these two specific panels.

Send the two part numbers (or photos of the nameplates) and the project file to /inquiry and the cross-reference report comes back with the twelve axes named.

FAQ

What is the first thing to check when an operator panel goes out of production?

The lifecycle status of the panel on the manufacturer's own product page — current, phased out, end-of-life, last-time-buy window open or closed. That answer decides whether the question is a substitution question at all, or a last-time-buy question. The substitution work only starts when remaining channel stock, documented cross-reference and last-time-buy are all exhausted. The first axis to check on the cross-reference itself is the protocol-driver set on the candidate panel, because that axis decides whether the panel can talk to the PLC at all — and most buyers ask about screen size first, not driver library.

Can a 7-inch panel replace any other 7-inch panel?

No. Two 7-inch panels from different families almost never share the same cut-out, the same depth, the same power-connector position, the same COM port pin-out, or the same set of PLC drivers. The 7-inch diagonal is a rough indicator of visible form factor, not of interchangeability. The cross-reference report names the cut-out in millimetres, the depth behind the panel in millimetres, the power-terminal pin-out, and the driver library, not just the diagonal. Substitution depends on those four fields matching; diagonal matching is not enough.

Does a cross-reference report include a recommendation?

No. A cross-reference report is a documented comparison with the unverified axes named. The recommendation — whether to substitute, whether to redesign, whether to leave the panel in place — belongs on the buyer's engineering team, after the report is read against the buyer's application. The report's role is to put the matched, differing and unknown axes on the table in a fixed order so the buyer can make that call with the constraints visible. A report that includes a recommendation is overstepping into the buyer's qualification process.

What if the original project file is not available?

The cross-reference report flags the firmware_version axis and the engineering-software axis as unknown by default. The buyer then has three options: recover the project file from a backup, request a re-build of the screens from the integrator (which is engineering work, not sourcing work), or accept the cost of a full project re-engineering if the panel is otherwise a clean substitute. None of those three options is a sourcing option, which is why the project file is the most expensive missing input on an HMI substitution request.

Can a discontinued panel be sourced new, not used?

Sometimes. Three routes apply in order: remaining franchised-channel stock (if any is left, often at a premium), last-time-buy windows the manufacturer opens before the official end-of-life (the windows are dated and short), and documented cross-reference to a current model the manufacturer has named. After those three are exhausted, the panel is sourced from the secondary channel — new surplus (factory-sealed, unprogrammed), refurbished (tested on a bench, with a per-unit warranty stated on the quote), or used (removed from service, with the source stated on the quote). The condition is stated per line; it is not described as a lot.

Does the substitution change the machine's certification scope?

Potentially. A change to the operator panel may invalidate the certification scope the machine was shipped under — CE, UL, EAC, GOST-R, or the application-specific scope on a pharmaceutical or food-and-beverage line. The panel's own declaration of conformity lists the certifications that apply to that specific model and revision; a substitute panel carries its own declaration, and the certification scope of the machine has to be re-assessed against the new declaration. The cross-reference report names this as a flag; the certification re-assessment is the importer's responsibility, not the sourcing desk's.

Do you re-engineer the project file?

No. Project-file re-engineering — re-importing screens into a new runtime, rebuilding the tag database, recompiling the macros, re-testing the alarm structure — is engineering work that belongs on the integrator's bench, on the integrator's quality system, with the integrator's documentation. The sourcing desk's role is to put the two panels and the engineering software versions on the table; the integrator's role is the re-engineering. A cross-reference report is a comparison; it is not an engineering change order.

Last updated: September 28, 2026