Mobile Round Inspection
This is a view-only mobile screen for checking that collection is working normally while walking the field with your phone. You can tour the line and equipment, compare gateway status, per-connection collection status, and current tag values against the field instruments, and check for any errors that just occurred.
Logging in from a phone browser automatically opens the mobile status screen (/m/dashboard). PC browsers continue to show the existing desktop screen.
Nothing can be changed from the mobile screen — tag value writes, starting/stopping collection, configuration changes, and deletions are all impossible. This is intentional, so that losing your phone or accidentally pressing something in your pocket has zero impact on equipment. If action is needed, do it from the desktop screen.
1. Before You Start (Prerequisites)
| Condition | Description |
|---|---|
| Network | The phone must be on the same factory network (field Wi-Fi) as the gateway. There is no remote access through the platform — this is not for use from the office via LTE/5G |
| Account | The same account and login as on the desktop. There are no mobile-only accounts or separate settings |
| Address | Access https://<gateway-ip>/ from a phone browser → log in → the mobile screen opens automatically |
If you visit without being logged in, you'll be redirected to the login screen. If your session expires while viewing, you'll be automatically returned to the login screen.
2. Removing the Certificate Warning (One Time)
The gateway's HTTPS uses a self-signed (private) certificate. Consequently, your phone browser shows a "This connection is not private" / "Your connection is not secure" warning. This is not a malfunction, and there are two operational procedures to resolve it.
Method B (adding an exception) is quicker, but the warning may reappear depending on browser policies. If you use the phone daily for rounds, doing Method A once is the cleaner approach.
Method A — Install the Corporate CA Certificate on the Phone (Warning Disappears)
First, obtain the corporate CA (root) certificate file used to issue the gateway's certificate (.crt or .pem) from your installation administrator, and receive it on your phone via email, messenger, AirDrop, etc.
iOS (Safari)
- Tap the received certificate file → a "Profile Downloaded" notice will appear.
- Go to Settings > General > VPN & Device Management → tap the downloaded profile → Install.
- Go to Settings > General > About > Certificate Trust Settings → turn on the trust switch for the root certificate you just installed. (Skipping this step will cause the warning to persist)
Android (Chrome)
- Navigate to Settings > Security (Security & privacy) > More security settings (or "Encryption & credentials") > Install a certificate > CA certificate.
- Select "Install anyway" and choose the received certificate file.
Menu names may differ slightly depending on the iOS/Android version and manufacturer. Enter "certificate" in the settings search bar to find the corresponding menu right away.
Method B — Add a Browser Exception (Fast, but the Warning May Reappear)
- Android Chrome: On the warning screen, tap Advanced → Proceed to <address> (Unsafe).
- iOS Safari: On the warning screen, tap Show Details → Visit Website → confirm.
3. The Five Screens
Navigate using the bottom tab bar (Status / Connections / Search / Logs / Desktop).
| Screen | Path | What You See |
|---|---|---|
| Status | /m/dashboard | Overall gateway status — transmission rate, queue, today's errors, CPU/memory/disk, PLC connected/disconnected count |
| Connections | /m/opc | List of connections (PLCs) — problem connections at the top, [All/Issues] toggle |
| Tag Values | /m/opc/<connection-id> | Current values for that connection's tags — large value and unit, elapsed time always shown alongside |
| Search | /m/search | Global search by tag ID/name — results show current value and elapsed time |
| Logs | /m/log | Recent ERROR/WARN entries — for checking "what just happened" |
On the Status screen, problem indicators can be tapped to navigate directly — the Today's Errors card goes to the Logs screen, and the PLC Connected/Disconnected counts go to the Connections list.
4. The Most Important Thing — Value Age (Elapsed Time)
Just because a value is displayed doesn't mean collection is alive. If the value on screen is from 10 minutes ago, collection has been dead in the meantime. The most dangerous misjudgment during a round inspection is "the value is visible, so it's normal."
That's why the mobile screen always shows the collection time (elapsed time) next to every value, and visually disables values that are too old.
| Elapsed Time | Display |
|---|---|
| Within 1 minute | Value is crisp (normal) |
| 1 to 10 minutes | Value appears grayed out — suspect it's older than the collection interval |
| Over 10 minutes | Value appears dimmed + elapsed time is orange — treat as collection stopped and check |
Develop the habit of always reading two things together when checking a value: value → elapsed time, in that order.
5. Distinguishing Between Three States
Field Wi-Fi drops out in corridors or behind pillars. If you can't tell whether "the value looks wrong" is an equipment (collection) issue or a problem with your phone's network, you'll either chase healthy equipment or miss real anomalies. The screen displays these three states differently.
| State | Screen Display | What to Do |
|---|---|---|
| Normal | Value is crisp + short elapsed time. No banner | Move to the next equipment |
| Collection Issue (Gateway responds, but data is bad) | No banner. ERROR tags go to the top of the list with an error message, or the elapsed time is long and the value is dimmed. In the Connections list, that connection moves to the top | Check connection status / scan status in the Connections screen → take action from the desktop |
| Communication Lost (Phone can't reach the gateway) | Banner at the top: "Connection lost — values below are from N seconds ago" + all values on screen are dimmed. The last values are not cleared but retained | This is likely not an equipment problem. Move to a spot with better signal and check if the banner clears |
The key distinction: if a banner is showing, it's a phone↔gateway issue; if only specific tags/connections look wrong without a banner, it's a collection issue.
Even when communication is lost, the last values remain dimmed and the banner continuously updates with the age of the data. Clearing the screen would make it easy to mistake the equipment for being down. The banner doesn't appear for momentary dropouts; it only appears after two consecutive failed refreshes, and it disappears automatically once communication is restored. (This behavior applies to the Connections, Tag Values, Search, and Logs screens)
6. Each Screen in Detail
Status (/m/dashboard)
Refreshes every second with transmission rate (MPS) / queue / today's errors / transmitted points cards, CPU·memory·swap·disk gauges, PLC connected/disconnected·read/write success/failure counts, and platform API·Docker status. A logout button is in the upper right.
Connections (/m/opc)
Each card is one connection — connection name, protocol·IP:port, connection status/scan status/tag count badges. Disconnected and collection-stopped connections are always sorted to the top, and the [All N / Issues N] buttons at the top filter to show only problem connections. Tapping a card opens the tag values screen for that connection. Refreshes every 10 seconds.
Even if the connection status is normal (CONNECTED), if the scan status isn't in collection mode (NOT COLLECT), no values will come in. Cards in this state are classified as issues and move to the top, so be sure to check both badges.
Tag Values (/m/opc/<connection-id>)
Shows the value and unit large for each tag, with the elapsed time below it. ERROR tags come to the top and show their error message. Refreshes every 5 seconds.
For connections with a very large number of tags, only the top 300 are shown, with a message at the top of the screen: "Only showing the top 300 — view the full list on the desktop." Don't assume unseen tags are "normal"; if you need to check a specific tag, use Search.
Search (/m/search)
Searches all gateway tags by tag ID or name using partial match (case-insensitive). The search is triggered automatically as you type, and results (up to 50) show the current value and elapsed time. This is faster than scrolling through a list when you need to compare a specific tag with the field instruments.
Logs (/m/log)
Shows up to 50 recent log entries from the last 24 hours, newest first. The [ERROR / WARN] buttons at the top let you choose the level; the default is ERROR. Refreshes every 15 seconds.
If you tap WARN, ERROR entries will not be visible (it's not "WARN and above"). To see errors, make sure the ERROR button is selected. For more detailed log viewing with time range or message search, use the System Log View on the desktop.
7. Actions Are Taken on the Desktop
Starting/stopping collection, writing tag values, editing connections/tags, and changing configuration are all done from the desktop screen.
- From your phone, you can also tap the [Desktop] button in the bottom tab bar to open the desktop screen (
/ui/main?desktop=1) — useful for quickly checking settings during a round. However, the desktop screen is not optimized for phone size, so we recommend using a PC for editing tasks. - Because the phone automatically navigates to the mobile screen, opening
/ui/mainwithout?desktop=1will return you to the mobile status screen.
8. Known Limitations
| Limitation | Description |
|---|---|
| No pull-to-refresh | Pulling down on the screen doesn't refresh. Rely on the automatic refresh (periods above) or use browser refresh |
| Logs limited to 50 recent entries | There's no "load more". For more, use the desktop System Log View |
| Tag values screen limited to top 300 | Large connections are truncated with a notice. See the desktop for the full list |
| 200 connections / 50 search results | Lists and search have limits |
| Refreshing stops when screen is off | The Connections, Tag Values, and Logs screens stop refreshing when your phone screen is turned off or you switch to another app (to save battery and field Wi-Fi) and resume automatically when you return |
| No notifications/push | This screen is for active, on-the-go checking. It doesn't proactively inform you of anomalies |
9. Common Pitfalls
| Symptom | Cause / Solution |
|---|---|
| Certificate warning every time you access | Self-signed certificate — not a malfunction. Resolve with the procedure in 2. Removing the Certificate Warning |
| Screen doesn't open on my phone at all | Check if the phone is on the factory network (field Wi-Fi) — it can't be accessed via LTE/5G |
| Values are visible but never change | Check the elapsed time. If it's old, it's a collection issue — check status in the Connections screen |
| Suddenly all values go dim with a banner at the top | Communication lost — usually a phone Wi-Fi problem. Move to a location with better signal |
| WARN is tapped but ERROR doesn't appear | The level button shows only that level — tap the ERROR button |
| Not all tags are visible | Top 300 truncation — use Search to find specific tags or use the desktop |
| Repeatedly kicked back to the login screen | Session expired — log in again (same account as on desktop) |
10. Learn More
- View real-time values on the desktop: Real-time Value View
- Connection list / Tag list (desktop): Connection List / Tag List
- Detailed system log search: System Log View
- When a connection fails: Troubleshooting