Selection guide
Replacing a Local HMI With a Phone App on a PLC
Short answer
Yes, where the access is documented: a phone app reads and writes controller tags like an HMI over a tag-level driver in the app, pages served by the controller itself, or a Modbus TCP mapped block. Keep the sequence in the PLC and give the phone a small validated data contract; go phone-only on machines touched at service visits and keep a station where an operator works every shift.
On this page
Yes, replace the panel with a phone app when the interface is touched only at service visits and the controller documents tag access — in the worked example below, a packaged unit used for 3.0 h annually against 8,760 h of panel duty (a duty factor of 0.034%), served by a 24-word Modbus TCP contract polling at 488 bit/s. The phone reads and writes tags like an HMI over one of three documented routes: a tag-level driver in the app (normally Modbus TCP), pages served by the controller's own web server, or an HMI runtime on a small computer that serves the phone as a client. The selection rule is interaction frequency, the PLC keeps the sequence in every case, and the phone gets a small mapped data contract with each write validated in the controller, not in the app.
When phone-only is the right selection #
The case for deleting the panel is duty, not novelty. On a packaged unit that runs unattended — a drive motor started on sensed flow, a timed solenoid valve, tank-level monitoring — the interface exists for the monthly service visit: reset hour meters, adjust setpoints, leave. That panel still demands a weatherproof enclosure, a door cut-out, and its own failure modes, while the smartphone already rides in the technician's pocket.
So the rule is: interface used at service visits only, phone-only and delete the panel; an operator at the screen every shift, the station stays and the phone becomes the supplement. Where the station stays, that choice is its own selection, and Panel PC HMI or PLC plus HMI for meter data display works through it.
Deleting the display deletes none of the machine's control requirements, but everything the panel hosted — screens, remote access, data conversion, alarms, trends, scripts — has to land somewhere. List those functions before you remove the panel, and decide for each whether it moves into the controller, into the serving app, or is dropped deliberately.
The documented access paths #
| Path | The phone talks to | What must be documented | Fit |
|---|---|---|---|
| Panel-remote app | A remote-access server inside the panel, which hosts the project | Panel stays powered and connected; per-account restriction via internal tags where the app supports it | Keeping remote access to a panel you keep |
| Tag-level app over Modbus TCP | The controller's Modbus TCP server | Register map: address, width, signedness, scaling, write permission per item | Phone-only on an occasionally serviced machine |
| Controller-served pages | The controller's web server, from the phone browser | User-defined page support and web-server user management | Status and service screens with no added hardware |
| HMI runtime on a cabinet computer | The runtime's web or mobile clients | The controller driver, simultaneous client count, runtime license | Many machines served from one computer |
| Remote desktop to the panel | The panel's screen through a remote-access tool | A reachable host and an account | Occasional troubleshooting, not operation |
| USB or Bluetooth link | The controller's device interface | A supported interface plus a driver the app can use | Rare; verify before designing around it |
Three rows deserve emphasis. The panel-remote app is a client of the panel: the day you remove the panel, the app loses its server, so it can never be the phone-only route. Controller-served pages are documented on some controllers — a Siemens S7-1200 configures user-defined Web pages from the CPU's "Web server" properties in the Device Configuration view, and its web server carries its own user management, so read-only and service accounts are separated at the controller. When your controller cannot host screens, the project lives on a computer instead, and choosing a PC-based HMI runtime for a Modbus TCP PLC works through that option. A USB or Bluetooth pairing establishes a physical link, not tag access.
Keep the sequence in the PLC #
A phone link is intermittent by design: coverage drops, the screen locks, a call arrives, the browser closes. An unattended machine must run through all of it, so motor-per-flow logic, valve timing, and level monitoring stay in the controller program. The phone adjusts permitted settings and requests actions; it never carries timing or a heartbeat.
Define, for each operating mode, what happens when the client disappears mid-command, and separate a request from the resulting state: a requested motor start can be refused by a permissive, and the screen shows the machine's actual state, not the request. Protective stops and interlocks stay hardwired and independent of every client, so no phone path can defeat them.
Prove it once: disconnect the client during a controlled test and confirm the sequence and the defined loss behavior hold without the phone connected.
Map a small data contract #
The phone gets a mapped block, never an unrestricted memory editor. Build the service interface from item types like these, each with its controller-side rule:
- Status (flow, tank level): read-only words with engineering units and a freshness indicator.
- Timer setpoints: show value, unit, and allowed range; the controller rejects out-of-range requests.
- Level thresholds: the measured level and the adjustable threshold are separate items.
- Momentary commands: request, acceptance, and actual response shown separately.
- Hour-meter reset: an explicit service action restricted to the intended meter.
For every item, record address, data type, width, signedness, scaling, and permitted access, then read the accepted value back — the accepted controller value is the result, not the phone's entry field. Thresholds that must move together take effect as one validated group, so a half-entered set never becomes an operating configuration.
Worked example: one packaged treatment unit #
Service use is one monthly visit with 15 minutes of interface time each. Interface time annually: 12 visits × 15 min = 180 min = 3.0 h. The panel-and-enclosure alternative is on duty continuously: 365 d × 24 h = 8,760 h. Duty factor: 3.0 h ÷ 8,760 h = 0.00034, or 0.034%. A weatherproof enclosure and a door cut-out exist for three hours of use a year — that is the phone-only case, and the panel goes.
Size the contract: 12 status words + 8 setpoint words + 4 command words = 24 words. The phone reads the 20 read words in one Modbus TCP function-03 request: 12 bytes out (7-byte MBAP header, 1 function code, 2 start address, 2 quantity) and 49 bytes back (7 + 1 + 1 byte count + 40 data), so 61 bytes per cycle. At one poll per second that is 61 B/s × 8 = 488 bit/s, which is 0.0005% of a 100 Mbit/s link. That is wire load only, before device response time and app scheduling; with one client the wire never decides this selection — the controller's documented simultaneous-connection count does.
Network exposure and accounts #
Never forward a controller port to the public internet. Phones reach the controller over a VPN into the plant network or a routed service VLAN, and on controller-served pages the web-server user management holds distinct read-only and service accounts. Monitoring without control is its own pattern: making a read-only web client mirror of an HMI screen gives status to everyone who needs it while granting writes to no one.
The decision, by machine #
- Unattended packaged machine, interface used at the monthly service visit: phone-only, over a mapped Modbus TCP block or controller-served pages; delete the panel and its enclosure.
- Machine an operator works every shift: keep the local station and add the phone for troubleshooting; the phone replaces nothing here.
- Existing panel whose remote app already works: keep the panel — the phone is its client, and removing the panel removes the server.
- Controller that documents no tag access for any app: host the screens on an industrial mini PC in the cabinet and let the phones connect as clients, or keep the panel.
Questions asked
Can I keep using the existing panel's phone app after I remove the panel?
No. Those apps are clients of a server inside the panel: the panel hosts the project, the screens, and the remote-access path. Remove the panel and the phone has nothing to connect to. That route is a reason to keep a working panel in service, not a way to delete one.
What is the safest pattern for a start command from a phone?
Write a request bit, never a run command the logic obeys blindly. The PLC checks permissives, executes once, resets the request, and sets a separate status word the phone reads back. A repeated or stuck transmission then causes one action, and the screen shows the machine's actual state instead of the request.
Is a USB or Bluetooth link from the phone simpler than the network path?
Only if the controller side documents that interface with a driver the app can use. A cable or a pairing establishes a physical link, not tag access, and most industrial controllers expose no supported phone driver over USB or Bluetooth. Modbus TCP over the plant network is the path you can verify in documentation.
How many phones can connect at once?
The controller documentation states the simultaneous-connection count for its Modbus TCP server or web server, and that number, not bandwidth, is the limit — one phone polling 20 words once a second is about 488 bit/s of wire load. Plan the service procedure around one phone at a time so the documented count never decides the job.