Integrating WebRTC for Real-Time Video Streaming in SCADA HMI

flowchart LR
    cam["IP Camera (RTSP)"]:::green
    sfu["SFU / go2rtc Server"]:::blue
    hmi["SCADA HMI (WebRTC)"]:::red

    cam -->|Stream| sfu
    sfu -->|"< 500ms"| hmi

    classDef green fill:#16a34a,stroke:#fff,color:#fff,stroke-width:2px;
    classDef blue fill:#2563eb,stroke:#fff,color:#fff,stroke-width:2px;
    classDef red fill:#dc2626,stroke:#fff,color:#fff,stroke-width:2px;

Key Takeaways:

• Standard streaming protocols (HLS, DASH) induce multi-second delays, unacceptable for critical remote operations.
• WebRTC integration in SCADA HMI provides ultra-low latency (< 500ms), enabling real-time tele-operation and monitoring directly in modern browsers.
• Implementing WebRTC on the plant floor requires bridging legacy RTSP feeds and managing NAT traversal via STUN/TURN servers.
• Using a Selective Forwarding Unit (SFU) like Mediamtx or go2rtc scales video distribution to multiple operators without overloading edge cameras.

The Latency Problem in Industrial Video

When an operator needs to remotely jog a servo motor or monitor an emergency stop condition via an HMI, a 3-second video delay is a safety hazard. Traditional video streaming protocols like HTTP Live Streaming (HLS) or DASH were built for broadcasting, relying on heavy buffering to ensure smooth playback. This buffering fundamentally conflicts with the deterministic, real-time requirements of industrial automation.

To solve this, automation engineers are adopting WebRTC. Originally designed for peer-to-peer video conferencing, WebRTC operates over UDP to achieve sub-second, glass-to-glass latency. Native browser support means operators can view high-definition feeds on any device without installing activeX controls or custom plugins.

Architecting WebRTC for the Plant Floor

Deploying WebRTC integration in SCADA HMI is rarely as simple as establishing a peer-to-peer link. Industrial networks are heavily segmented with rigid firewalls. Furthermore, legacy IP cameras output RTSP, not WebRTC. A robust architecture typically involves a gateway or media server.

Bridging RTSP to WebRTC

Most industrial cameras do not natively speak WebRTC. Engineers use lightweight bridging software, such as go2rtc, acting as a universal proxy. It ingests the RTSP feed from the camera and repackages it into a WebRTC stream for the browser, minimizing processing overhead.

Handling Multiple Operators with an SFU

In a direct Peer-to-Peer (P2P) model, an edge device must encode and transmit a separate stream for every connected client. If five operators open the HMI dashboard, the camera’s CPU will bottleneck. The solution is a Selective Forwarding Unit (SFU media server).

flowchart TD
    camera1["Process Camera (RTSP)"]:::blue
    camera2["Security Camera (RTSP)"]:::blue
    sfu["SFU Media Server (go2rtc)"]:::green
    hmi1["Operator Terminal 1"]:::red
    hmi2["Mobile Tablet"]:::red
    hmi3["Control Room Wall"]:::red

    camera1 -->|Single Feed| sfu
    camera2 -->|Single Feed| sfu
    
    sfu -->|WebRTC UDP| hmi1
    sfu -->|WebRTC UDP| hmi2
    sfu -->|WebRTC UDP| hmi3

    classDef blue fill:#2563eb,color:#fff,stroke:#fff,stroke-width:2px;
    classDef green fill:#16a34a,color:#fff,stroke:#fff,stroke-width:2px;
    classDef red fill:#dc2626,color:#fff,stroke:#fff,stroke-width:2px;

The SFU ingests a single high-quality stream from the edge and efficiently replicates it to all connected HMI clients. This decoupling protects the edge hardware while scaling access.

Overcoming Network Constraints (NAT Traversal)

Perhaps the most frustrating challenge engineers face when implementing WebRTC integration in SCADA HMI is NAT (Network Address Translation) traversal. Because WebRTC relies on UDP, routers and strict industrial firewalls often block the traffic.

To establish a connection, the system requires signaling servers to exchange session descriptions, and STUN/TURN servers to discover public IP addresses and relay traffic if direct P2P fails. Setting up a reliable TURN server on a segmented VLAN is mandatory for robust plant-wide deployment.

Protocol Comparison: WebRTC vs Legacy Standards

Conclusion

Achieving ultra-low latency video is no longer a luxury for modern control systems. By bridging legacy RTSP feeds through an SFU and navigating industrial firewalls with proper STUN/TURN configurations, WebRTC integration in SCADA HMI delivers the real-time visibility that operators demand.

FAQ

Is WebRTC secure enough for industrial networks?

Yes. WebRTC mandates encryption by default, using DTLS (Datagram Transport Layer Security) and SRTP (Secure Real-time Transport Protocol). All video and audio data is encrypted end-to-end.

Can WebRTC run on older SCADA systems?

WebRTC relies on modern web browsers (Chrome, Edge, Firefox). If your legacy SCADA HMI supports embedding a modern Chromium-based web view or operates via a web server, you can integrate WebRTC.

What is the difference between an SFU and an MCU?

An SFU (Selective Forwarding Unit) routes video packets directly to clients without decoding them, requiring minimal CPU. An MCU (Multipoint Control Unit) decodes, mixes, and re-encodes streams, introducing latency and requiring significant compute power.

Ready to upgrade your control interfaces? Browse our premium industrial UI assets and templates at the AutomationView Store to build your next high-performance dashboard.