IMDTouchKnowledge BaseShop main store

Selection guide

Selecting a Touch Panel for CODESYS WebVisu in Salt Environments

HMI and touchscreens Published 8 min read

Short answer

A panel qualifies as a CODESYS WebVisu client only when it runs a current Firefox, Chrome, Edge or Chromium engine that renders the served visualization, can be locked into full-screen kiosk operation, and comes with a written no-aluminum material declaration for salt and corrosive dust. Front IP66/IP69 ratings and marine approvals do not satisfy the material rule, so check each requirement independently and pass all three gates before purchase.

On this page
  1. Three gates a WebVisu panel must pass
  2. Gate 1: a current browser engine, not an operating-system label
  3. Gate 2: full-screen kiosk lockdown operators cannot leave
  4. Gate 3: no aluminum, proven by a written declaration
  5. Front and rear protection are separate documents
  6. Field shortlist for a door-mounted client
  7. Worked example: qualifying a 7 in panel for a salt-dust cabinet door
  8. Bench acceptance tests before the panel goes on the door
  9. Questions asked

A touch panel earns its place as a CODESYS WebVisu client by passing three gates: it runs a current browser engine that renders the visualization the controller serves, it can be locked into full-screen kiosk operation so operators cannot wander off to other sites, and it arrives with a written no-aluminum material declaration, because salt and corrosive dust attack aluminum wherever it is exposed. A front IP66 or IP69 rating proves ingress performance and a marine approval proves shipboard acceptance; neither says one word about the browser, the lockdown or the alloy, so no gate substitutes for another. Below is what to demand on the engine, the lockdown and the material declaration, a field shortlist, one worked qualification, and the bench tests that decide.

Three gates a WebVisu panel must pass #

A WebVisu client is a browser on a touchscreen, nothing more: the controller runs the web server, the panel renders what it serves. That split produces three independent gates. Gate 1 is the engine — a current Firefox, Chrome, Edge or Chromium build that renders this controller's output. Gate 2 is lockdown — full-screen kiosk operation an operator cannot leave. Gate 3 is material — a written no-aluminum declaration covering the scope you define. The gates do not borrow from each other: a front IP66 or IP69 rating and a DNV marine approval are ingress and shipboard documents, and neither carries browser, lockdown or alloy information. All three pass, or the panel is out.

Gate 1: a current browser engine, not an operating-system label #

The controller side is fixed: the runtime's web server publishes the visualization, and a browser reaches it on TCP port 8080 at the device's hostname or IP address. CODESYS recommends the latest versions of Firefox, Chrome, Microsoft Edge and Chromium as client browsers, and the client device must have real display and touch support. So the panel question is narrow: which engine ships on it, which version, and can that version be updated over the panel's service life.

The operating-system label answers none of that. 'Windows CE' or 'Linux' on the datasheet says nothing about the engine build, and panels sold for a proprietary HMI runtime often carry the browser as a separate package or operating mode. Confirm in writing that the package is included, how it is licensed, and that it installs through the manufacturer's supported procedure — an Ethernet port and native HMI software prove nothing about browser availability.

Rendering and touch input are separate qualifications, too: a panel can draw every object and still mishandle input, the way a long touch opens the right-click menu in CODESYS WebVisu until it is fixed. And if no door-mount candidate clears this gate, the fallback architecture is choosing a PC-based HMI runtime that talks to the controller directly instead of rendering its web output.

Gate 2: full-screen kiosk lockdown operators cannot leave #

Full-screen mode hides the browser controls; lockdown keeps operators from bringing them back or navigating anywhere else. You need both, and the place to prove both is the bench, not the door. Walk the exits an operator would walk: startup behavior after a power cycle, navigation restrictions, permitted addresses, access to browser and operating-system settings, edge gestures, and an on-screen keyboard that exposes system functions.

On Android-based panels, a configurable kiosk browser and app launcher does this job — Fully Kiosk Browser is one such app, built to lock a display to set websites and block other apps. Whatever the platform, the acceptance bar is the same: after every escape attempt the panel lands back in the full-screen visualization, and launching the HMI application touch-only in forced full screen at startup is the configuration to replicate. A panel you cannot lock down fails Gate 2 outright.

Gate 3: no aluminum, proven by a written declaration #

Define the scope before you shop, because 'no aluminum' means one of two things: no aluminum on exposed surfaces, or no aluminum in any supplied component. Salt plus corrosive dust attacks the metal wherever coating damage or a cut edge exposes it, so for this environment the defensible scope is the whole supplied assembly — front bezel, rear housing, mounting clamps, exposed fasteners, and every accessory in the box.

Then require the answer in writing. A material declaration naming each part and its alloy is a normal document for an industrial panel; a datasheet line saying 'glass front' is not one, because it says nothing about the housing and clamps behind it. Decision rule: no written declaration, no order.

Keep the documents separate in your head. A front IP66 or IP69 rating describes ingress performance under its test conditions; a marine type approval documents ship-environment acceptance. Neither can pass Gate 3, and passing Gate 3 does not earn an ingress rating. For the sealing half of this selection, the companion piece is selecting an IP65 industrial touchscreen for a dusty HMI, which works the same way for the ingress class.

Front and rear protection are separate documents #

The front seal protects the cabinet opening; the back of the panel lives in cabinet air, and manufacturers document the two sides separately. Match the rear rating to what the back of that door actually sees — a cabinet on a washdown aisle gets spray and condensation on both sides, and then the rear rating decides, not the front.

An ingress rating also holds only as installed. The cutout dimensions, the door thickness range, the gasket arrangement and the fastening torque pattern in the mounting instructions are part of the rating; a panel clamped to an out-of-spec door with a pinched gasket has no rating at all. Install to the instructions and file them with the panel's documentation.

Field shortlist for a door-mounted client #

The table below collects the panel families integrators report using for exactly this job. Every figure in it is field-reported, not a datasheet quote: family-wide claims — an IP66 front across a series, a marine approval, a size range — do not automatically transfer to every size variant, so each candidate is confirmed against the current model datasheet before purchase.

Candidate Reported in the field Confirm on the current datasheet
Installed proprietary-runtime panels Do not render this plant's web visualization, which is why two engineering environments are in use today Whether the exact model has a manufacturer-supported browser option at all
Berghof ET and DC series Reported by integrators as working WebVisu clients in similar service Browser support per model and size, enclosure materials, available sizes, kiosk controls
Exor eX700 series Embedded Linux; vendor HMI runtime plus a manufacturer Chromium add-on; sizes reported to 21.5 in; IP66 front reported family-wide with some IP69-front versions; DNV-GL approval reported; dimming available That the Chromium add-on is current, licensed and supported for the exact model; the material declaration
Exor eSMART series Same platform class, sizes reported to 10.1 in The same two checks, plus the lockdown demonstration

When a shortlisted family fails a gate — an aluminum housing, an unsupported browser add-on, no lockdown — the replacement class to evaluate is embedded panel-mount PCs that mount flush in the same cabinet door, judged against the same three gates.

Worked example: qualifying a 7 in panel for a salt-dust cabinet door #

Inputs:

  • Minimum display size: 7 in, the plant's stated floor for this application.
  • Visualization service: the controller's web server on TCP port 8080 at its IP address, per CODESYS documentation.
  • Gates required: 3 — engine, lockdown, material.
  • Candidate A: an eSMART-class panel, largest reported size 10.1 in, polymer front, aluminum rear housing on its material declaration.
  • Candidate B: the same family with a full-assembly declaration listing no aluminum in any supplied part.

The rule in words: a candidate mounts on the door only if its display is at least 7 in and it passes all 3 gates; one failed gate rejects it whatever its ingress rating.

Arithmetic:

  • Size: 10.1 in − 7 in = 3.1 in above the minimum, so size passes (the larger eX700-class option at 21.5 in clears it by 14.5 in).
  • Engine: manufacturer-supported Chromium add-on at a current version — 1 gate.
  • Lockdown: full-screen kiosk demonstrated on the bench — 1 gate.
  • Material: the polymer front passes, the aluminum rear housing fails the whole-assembly scope — 0 gates.
  • Candidate A: 1 + 1 + 0 = 2 of 3, and 2 < 3, so A is rejected.
  • Candidate B: 1 + 1 + 1 = 3 of 3, size unchanged, so B is accepted.

Before any of that counts, point an engineering laptop browser at the controller's IP address on port 8080 from the plant network: if the visualization does not render there, the fault is the controller service or the network path, not the panel.

Decision: below 3 of 3 gates the panel does not go on the door, and no front rating overrides a failed gate — Candidate A's reported IP66 front does not repair its housing.

Bench acceptance tests before the panel goes on the door #

  • Largest or busiest screen: loads complete with no missing objects; failures point at browser compatibility, panel resources or visualization design.
  • Touch entry: numeric and text fields accept values through the on-screen keyboard, with visible feedback.
  • Live update: change a value at the controller and confirm the screen follows it; record the measured delay beside the limit the operating procedure sets.
  • Network pull: unplug the link — the screen must flag stale data explicitly and reconnect by itself on restore. A silent freeze or a required reboot fails the panel.
  • Lockdown attack: try the exits — operating-system gestures, system keys from an attached keyboard, browser chrome, a power cycle. Each attempt must land back in the full-screen visualization.
  • Shift soak: leave the busiest screen running for a full shift and watch memory, because browser-based HMI runtimes can grow until the panel PC throws a virtual memory warning in web HMIs.

Run any test that writes outputs on the bench or with the machine in an approved test state: a WebVisu screen that sets real outputs is not a simulation.

Three gates passed and these tests clean — that panel goes on the door. Anything less, send it back.

Questions asked

Does CODESYS WebVisu support multi-touch gestures?

The web visualization supports multi-touch from CODESYS 3.5 SP6 onward, provided the panel's touchscreen hardware supports it too. Single-touch hardware still runs standard screens and buttons; pinch and zoom need both sides capable. Read the touch controller specification rather than the marketing label, and test the gesture you actually use on the bench before committing the panel.

Is an IP66 or IP69 front rating enough for a salt environment?

No. Ingress ratings describe resistance to water and dust entry, not chemical compatibility with salt, and a marine type approval documents shipboard acceptance, not metallurgy. Even an anodized or painted aluminum part fails a strict no-aluminum rule, because scratches and cut edges expose base metal in salt air. Write the scope, exposed surfaces or whole assembly, into the purchase order and get the declaration in writing.

The candidate panel ships with an older locked browser build. Should we accept it?

Reject it for a long-lived installation unless the manufacturer documents an update path to a current recommended engine. The visualization output follows the CODESYS version on the controller, so a frozen browser ages quickly, and a panel you cannot update turns every controller upgrade into a panel replacement. Ask for the supported browser package, its version and its update procedure in writing before ordering.

Can we reuse the HMI panels already on our machines as WebVisu clients?

Only if the exact model documents a supported browser for the controller's visualization, obtained through the manufacturer's own procedure or licensing. A panel that runs its proprietary HMI runtime is not a browser client because it has an Ethernet port, and native HMI software availability proves nothing about browser availability. Without a documented browser option, plan a browser-capable replacement for that door.

Keep reading

  • Selection guide

    Planning an HMI Terminal Replacement From an Older Operator Panel

    Decide an operator-terminal replacement on installed cost — the terminal, cutout adaptation, application software, engineering, commissioning, downtime and a spare — never on terminal price alone. Measure the opening against the replacement's documented cutout range and count displays before ordering: a slightly smaller terminal needs a bezel adapter, and a large converted application can force the higher-performance model. Convert in the same brand when the source project opens cleanly; rebuild cross-brand when you accept the extra engineering hours for source control.

    HMI and touchscreens

  • Selection guide

    Running a PanelView HMI at -20°C Without Ghosting the LCD

    Yes, with one condition: hold the enclosure air at +5 °C or warmer so the powered terminal never leaves its 0…55 °C operating rating, and expose the screen to -20 °C only for minutes at a time — an arrangement Rockwell Automation knowledge answer 707514 accepts. If the glass must sit bare at that temperature all shift, no PanelView is rated for it; run FactoryTalk View Machine Edition on a wide-temperature touchscreen computer instead.

    HMI and touchscreens

  • Explainer

    Portrait HMI Panel Mounting and Temperature Derating Explained

    No. Portrait mounting does not derate an HMI panel's temperature rating — the vendor's release information for the panels that gained portrait mode states the landscape specifications continue to apply, because rotation in the screen's own plane leaves tilt, convection and dissipation unchanged. The derating that still governs is mounting angle: the 15-inch model's angle table reads the same row in portrait as in landscape.

    HMI and touchscreens