Skip to main content

Network & Integration Guide for IT/OT Teams

Connectivity options, network requirements, local protocols, and integration paths for Verdigris Energy Data Gateways.

This guide covers what your IT and OT teams need to connect Verdigris Energy Data Gateways (EDGs) to your network and integrate the data into your own systems.

1. Connectivity options

The EV2 Energy Data Gateway supports three connection types. No hardware changes are needed to switch between them.

  • LTE (default): Included in your plan pricing. No setup required.

  • Ethernet (native): 100 Mbps to 1 Gbps link speed. Recommended for permanent installs and sites with weak cellular signal.

  • Wi-Fi: 802.11 b/g/n, 2.4 GHz only (not 5 GHz), channels 1-11, signal strength of -85 dBm or better, at least 1 Mbps bandwidth.

2. Network requirements

  • IP addressing: DHCP and static IP are both supported. Static IP is recommended.

  • Firewall: Outbound only. All data transmission and remote support use port 443 (TLS). No inbound ports are required.

  • Allow-listing: Verdigris can provide the MAC address of each gateway on request.

  • Data usage: Typically a few hundred MB per gateway per month. Usage varies with circuit count and data settings.

3. Local data access

Gateways can serve data directly on your local network, independent of the cloud connection:

  • Modbus TCP

  • BACnet/IP

  • MQTT Sparkplug B: Coming soon.

  • Local API: A set of 1s telemetry is available directly from the gateway for low-latency applications. Contact Verdigris for details.

The full data set is available from the Verdigris cloud through the Verdigris REST API.

4. Integration paths

  • Ignition (Inductive Automation): Read gateway data with Ignition's native Modbus TCP driver. Once Sparkplug B is available, it can connect through Ignition's MQTT Distributor/Engine modules with auto-discovered tags. The customer provides the MQTT broker (for example, MQTT Distributor); Verdigris does not supply one.

  • Rockwell / Logix PLCs: Bring data in through Ignition or a Modbus TCP protocol gateway.

  • BMS (Niagara and others): Use BACnet/IP or Modbus TCP. See How does the Verdigris system work with existing BMS, BEMS, or EMS?

5. Cloud connection, retention, and support

  • Keeping the outbound cloud connection enables remote monitoring, gateway health checks, and firmware updates from the Verdigris team.

  • Local Modbus and BACnet data keeps flowing on your network even if the internet connection drops.

  • Cloud data retention is described in What is Verdigris' data retention policy?

Related articles

Did this answer your question?