How-to
Connecting an HMI to a Saitel DP embedded web interface
Short answer
A Saitel DP has no dedicated physical screen; its embedded webserver is the standard operator interface, served over the network to any modern JavaScript- and HTML5-capable browser. Connect a browser terminal to the Saitel DP's subnet, open the configured address, and accept the hardware only after the exact model and browser version pass a live display test.
On this page
- Does a Saitel DP need a dedicated screen for local HMI access?
- What can you use as the browser terminal in the cubicle?
- How does the terminal reach the Saitel DP webserver over the network?
- How do you open the Saitel DP interface in the browser?
- Which browser features does the interface actually depend on?
- How do you acceptance-test the panel before committing the design?
- What result do you accept and what do you record?
- Questions asked
A Saitel DP has no dedicated screen to wire up. The platform's embedded webserver is its standard operator interface, so the local HMI for a cubicle is a browser terminal — a PC, tablet, smartphone, or an industrial touchscreen panel that runs a browser — connected to the controller's network and pointed at the webserver's address. The browser must support modern JavaScript and HTML5, and no panel model is proven until the exact model and browser version pass a live test. This article gives the network path with a subnet check you can verify, the access sequence, and the acceptance test that decides which terminal passes.
Does a Saitel DP need a dedicated screen for local HMI access? #
No dedicated screen exists for a Saitel DP: the platform's embedded webserver is the standard operator interface, and you reach it over the network from any terminal whose browser can render the interface, which is exactly how a cubicle display gets planned.
Schneider Electric ships the interface inside the platform itself: the webUI user manual covers the design and operation of this lightweight web-based substation HMI, and the platform's own user manual covers installation and wiring of the unit. Neither names a dedicated operator screen as part of the controller. Plan the terminal and its network drop instead of a screen cable: the display lives wherever a browser and a network path exist, including a panel mounted on the cubicle door next to the unit.
What can you use as the browser terminal in the cubicle? #
Any terminal that runs a modern browser is a candidate: the web interface has been exercised on PCs, tablets and smartphones as device classes, while a fixed operator panel qualifies only after a live test on the model you will actually install.
PC, tablet and smartphone are the documented device classes, but the documentation names no tested models or browser versions, so one phone rendering the page proves that phone and nothing else. A fixed panel that runs a browser directly is a legitimate third path, yet no specific panel model carries a confirmed result in the material available, which keeps its compatibility an open line item until the bench test passes.
| Terminal class | Documented status | Decision |
|---|---|---|
| PC, tablet, smartphone | Exercised device classes; models and versions unnamed | Test the actual device and browser build before deployment |
| Operator panel with built-in browser, Magelis or similar | No model confirmed in the available documentation | Bench-test the exact model; keep it an open acceptance item |
| Other browser-capable terminal | Not identified in the documentation | Verify JavaScript and HTML5 support, then live-test the interface |
For the always-on terminal a cubicle usually wants, an industrial panel PC turns the browser into a machine-mountable touchscreen instead of a shared tablet on a shelf. If a panel candidate fails its test, the fallback is a terminal that talks to the controller directly instead of through the webserver, and the selection discipline in Selecting a Modbus TCP HMI Panel for an Existing Controller carries over unchanged.
How does the terminal reach the Saitel DP webserver over the network? #
Physical proximity proves nothing: the terminal needs a working path to the Saitel DP's Ethernet interface, so take the controller's address and mask from the project records, put the terminal on that subnet, and prove reachability before you blame the browser.
A display mounted next to the controller is not connected merely by being close. Set the terminal into the site's addressing plan, confirm link state, then run the site's approved reachability test before touching the browser at all.
Worked example — same-subnet check. Project records list the Saitel DP Ethernet port as 10.42.7.60 with mask 255.255.255.0, and you assign the cubicle terminal 10.42.7.61 with the same mask:
- 10.42.7.61 AND 255.255.255.0 = 10.42.7.0
- 10.42.7.60 AND 255.255.255.0 = 10.42.7.0
Equal network IDs put both addresses on 10.42.7.0/24, so a direct switch path connects them and no gateway is involved. Suppose instead the terminal must live on the office segment as 10.42.8.24/24: 10.42.8.24 AND 255.255.255.0 = 10.42.8.0, which differs from 10.42.7.0, so every browser session must route through the segment gateway — 10.42.8.1 in this example — and pass that path's firewall rules. Prove the routed path during commissioning, not on handover day.
One recurring trap: a terminal whose Wi-Fi profile claims an address the wired side already owns will look connected and still fail. The failure mode and its fix are laid out in Why a PC Fails to Reach an HMI When Wi-Fi Owns Its Address.
How do you open the Saitel DP interface in the browser? #
The webserver serves its interface to the browser like any web page: launch the terminal's browser, enter the Saitel DP address from the project records, complete the login the site configured, and confirm the values on screen belong to the controller you intend to watch.
The installation's project records define the address, scheme and credentials; the platform's webUI user manual is the reference for how the interface itself is designed and operated. If your installation serves the interface over HTTPS with a certificate the browser does not yet trust, the established vendor pattern for web access to HMI devices is to export the application certificate and install it in the browser as trusted before the first login. Serving an operator view from a device webserver and consuming it in a browser is an established pattern on industrial systems; the walkthrough of RSView32 WebServer setup for browser-based HMI monitoring shows the same browser-client idea on an older platform. A page that loads but shows the wrong station's data proves only that the network works, so check one known measured value against the controller before you call the interface live.
Which browser features does the interface actually depend on? #
Two capabilities decide it: the browser must support modern JavaScript and HTML5, because the interface renders and reacts inside the terminal's browser, and it must hold that behavior through a full-screen, always-on session on the panel you actually purchased.
The documented requirement — a modern JavaScript- and HTML5-compatible browser — is a class description, not a per-model verdict: each browser build renders and reacts a little differently, and the interface's scripts execute in the terminal's browser process, not on the controller. Where that execution actually happens, and why a browser terminal differs from a panel running its own runtime, is laid out in Where JavaScript and WebAssembly Actually Run on an HMI. Browsers on always-on terminals update themselves, so record the exact build that passed: the version that works today is not guaranteed to be the version on the panel next quarter.
How do you acceptance-test the panel before committing the design? #
Acceptance runs on the exact model and browser version you will install, at its native screen size: render the required pages, operate the required controls, then restart the browser and drop the network link to prove the operator regains the interface unaided.
Run this sequence on the final terminal, in its final location, with the browser build you intend to leave installed:
- Connect the terminal to the Saitel DP subnet per the addressing plan and confirm link state.
- Open the configured address in the browser and complete the login.
- Identify the station: confirm one known measured value matches the intended Saitel DP.
- Open every page the operator will use and operate every control they will touch, checking target sizes at the panel's native resolution.
- Close and reopen the browser, then reload and log in again.
- Interrupt the network link, restore it, and confirm the interface recovers without a support call.
- Record the terminal model, browser version, address source, certificate step and all results in the commissioning file.
Keep the safety boundary where the project puts it: a browser tab is an operator view, so alarms and trips that protect equipment stay in the protection devices and the documented SCADA chain, not in this interface.
What result do you accept and what do you record? #
Pass means the installed terminal reaches the webserver, renders every page the operator needs, recovers after a browser restart and a network reconnection, and the record names the terminal model, browser version and address source that produced that result.
Do not generalize a pass. A result on one model and browser build says nothing about a sibling model, a different browser, or the same terminal after an auto-update, and re-running the sequence after any terminal OS, browser or Saitel DP firmware change is what keeps the acceptance true. When a terminal fails acceptance and no panel candidate passes either, the display becomes the replaceable part, and the decision boundary is the one described in Planning an HMI Terminal Replacement From an Older Operator Panel: fix the network and the browser first, replace the terminal only when the exact model cannot pass on the interface it will live with.
Questions asked
Do I need to install client software on the terminal besides the browser?
No. The operator view is served by the Saitel DP's embedded webserver and rendered entirely in the terminal's browser, so the terminal needs only that browser and network access. Keep engineering tools off it: the platform's configuration software belongs on the engineering PC, which also stops the operator terminal from becoming an unofficial change point for the running controller.
What if the pages render but the touch targets are hard to hit on the panel?
Treat it as a real acceptance finding, not cosmetics. Check the interface at the panel's native resolution rather than through a preview, because scaling distorts target sizes. If targets stay small, apply the browser's zoom, step up to a larger panel, or move the most-used controls to the home page, and document the fix against the exact model and browser version.
How often should a browser HMI terminal be re-tested?
Re-run the acceptance sequence after any browser update, terminal operating system update, or Saitel DP firmware change that touches the webserver, because rendering and session behavior can shift silently. A periodic spot-check on the installed terminal catches browser auto-updates, and the recorded browser version tells you exactly what changed between the passing test and the failing one.
What usually causes an interface that worked yesterday to fail today?
The three usual causes are an address change on the Saitel DP or the terminal, a browser update that dropped the trusted certificate after an HTTPS access change, and the terminal drifting onto another network such as a Wi-Fi profile claiming a conflicting address. Restore reachability first, then re-check certificate trust, then reload the interface and log in again.