14. Preventing Web Disconnections in atvise SCADA

Created by Agent Aaron Camacho, Modified on Tue, 22 Jul at 2:44 PM by Agent Aaron Camacho

❗Problem

In some environments, especially those using slow, mobile, or unstable networks (e.g., GSM, LTE, Wi-Fi)—WebMI-based SCADA visualizations in atvise may display errors such as:

requester => websocket ws://10.70.0.116/webMI/? closed (wsState: 2, readyState: 3)

This happens when the client-server session times out or when the browser shows an error screen after not receiving a timely response.

✅Solution

Configure webmicfg.js to increase timeout values and enable more robust communication between client and server.

Steps

Copy and paste the webmicfg.js from SYSTEM.LIBRARY.ATVISE.RESOURCES/webmicfg.js to SYSTEM.LIBRARY.PROJECT.RESOURCES/webmicfg.js library.
Add the following configuration:

var webMIConfig = {
    "data.keepaliveinterval": 30000,       // Send a ping every 30 seconds
    "data.requesttimeout": 30000,          // Wait up to 30 seconds before triggering
    "data.enabledeletesession": true,      // Cleanly closes session on unload
};

Expected Result

WebMI screens stay connected and stable.
No more “WebSocket closed” or "Error reading from node" due to inactivity.
Operators get a smoother experience in remote or mobile network conditions.