Runbook · Maxedge

Customer OPC UA / Modbus not delivering data

Datasharing

Symptom

Customer SCADA reads no values or connection refused on 4840 (OPC UA) / 502 (Modbus).

Investigate

docker ps — is the datasharing container Up? Test locally from the VM (port open?). If local works but customer can't connect, it's a VLAN 40 / firewall issue, not Maxedge.

Fix

docker logs --tail 200 datasharing
docker restart datasharing
# test ports from the VM:
ss -tlnp | grep -E '4840|502'

Register/node mapping is part of the unit config — a config change can silently drop customer tags. Compare with the config history.

Steps

docker ps: datasharing Up? No → logs, restart.
From the VM: ss -tlnp | grep -E '4840|502' — both must be listening on the second NIC (192.168.40.x).
Listening but the customer cannot connect → VLAN 40 / firewall. Customer SCADA is only allowed to ports 4840 and 502; check the customer uplink is on switch ports 9–10.
Connected but no values → tag mapping. Dashboard → Configuration → History: did the mapping change? Restore the previous config.
Verify with an OPC UA client from the VLAN 40 side, or ask the customer to confirm tag updates.

Not resolved? Escalate to Product Engineering with docker ps -a, the relevant docker logs and the unit's Masterdata link.