Question 1

How do I connect an Eastron SDM630 to Eziwan?

Accepted Answer

The connection is direct and requires no proprietary configuration tools. Connect the SDM630’s A(+) and B(-) terminals to the Eziwan Gateway’s RS-485 port, then connect the shield ground to the GND terminal. In the Eziwan web interface, create a new Modbus device, enter the SDM630’s slave address (1 by default), and select a baud rate of 9600, with no parity, 8 data bits, and 1 stop bit. The preloaded SDM630 template automatically maps the 120 standard registers (voltage, current, active/reactive/apparent power, cos φ, THD, cumulative energy). In less than 5 minutes, your meter will upload its data to the Eziwan cloud.

Question 2

Which Modbus registers are read by default on Eastron meters?

Accepted Answer

The Eziwan Gateway includes predefined templates for all Eastron meters. For the SDM630, the default registers read are: phase-to-neutral voltages L1/L2/L3 (registers 0x0000, 0x0002, 0x0004), currents L1/L2/L3 (0x0006, 0x0008, 0x000A), active power per phase and total (0x000C through 0x0012), reactive power, total and per-phase power factor (0x001E), phase-by-phase voltage and current THD (0x00EA to 0x00F6), imported/exported active energy (0x0156, 0x0158), and reactive energy (0x015A). You can add or remove registers individually from the web interface without restarting the system.

Question 3

Can multiple meters be monitored on the same RS-485 bus?

Accepted Answer

Yes, the RS-485 Modbus RTU bus is a multidrop bus that supports up to 32 nodes in standard mode (247 with a repeater). Each meter must have a unique slave address (1 to 247). The Eziwan Gateway manages sequential polling of all slaves: it polls each meter in turn using its Modbus address. With 10 SDM630 meters, the full refresh cycle typically takes 2 to 5 seconds (depending on the number of registers read per meter). Configuration is done through the web interface by adding as many devices as needed, each with its own slave address.

Question 4

How do I set up alerts for when consumption exceeds a certain threshold?

Accepted Answer

From the Eziwan dashboard, open the Alerts section and create a new rule. Select the relevant variable (for example, Total Active Power of the SDM630-01), choose the condition (greater than), and enter the threshold in watts. You can set a minimum duration for the threshold to be exceeded (for example, 15 consecutive minutes) to avoid false alarms caused by transient spikes. Then configure the notification channels: email, SMS, or a webhook to your CMMS or Teams/Slack. An “back to normal” alert can also be enabled. The history of all alerts is available for review, including the timestamp and value at the time the alert was triggered.

Question 5

Is it compatible with an existing SCADA or BMS system?

Accepted Answer

Yes, through two integration methods. In cloud-to-cloud mode, the Eziwan REST API exposes all data in JSON—your SCADA or AVEVA/Wonderware system can retrieve it via authenticated HTTP requests. In local mode, the Eziwan Gateway can function as a Modbus TCP slave: your existing SCADA system reads meter data directly through the gateway as if it were communicating with the meter itself (Modbus TCP proxy). This second approach requires no modifications to your SCADA system and is transparent to your existing OT architecture. A local MQTT broker can also be configured for integration with modern BMS/GTB platforms.

Question 6

How do I export data to Excel or Power BI?

Accepted Answer

There are three methods available. (1) Manual CSV export from the Eziwan interface: Select a meter, a date range, choose the variables, and download the CSV file, which can be imported directly into Excel. (2) Automatic scheduled export: Set up a weekly or monthly CSV report to be automatically emailed to your energy team. (3) Real-time Power BI connection via the Eziwan REST API: Power BI Desktop can query the API directly using OAuth2 authentication, create dashboards updated hourly, and populate your ISO 50001 compliance reports. A native Eziwan Power BI connector is available in the technical documentation.

Question 7

How can energy monitoring be used to obtain ISO 50001 certification?

Accepted Answer

The ISO 50001 standard (Energy Management Systems) requires the establishment of an energy baseline (EnB — Energy Baseline), energy performance indicators (EnPI — Energy Performance Indicators), and a measurement and verification (M&V) plan. Eziwan’s monitoring system directly addresses these three requirements. The baseline (EnB) is built using Eziwan’s historical data: collect 12 months of actual consumption by category (production, utilities, buildings) to establish the annual baseline. The standard accepts certified electronic meter data as the reference for the EnB. EnPIs are defined directly in the Eziwan dashboards: create custom formulas that relate consumption to the appropriate production variable. Examples: kWh/metric ton produced for the food and beverage industry, kWh/square meter for commercial buildings, kWh/unit assembled for the manufacturing industry. These ratios are calculated automatically by combining Eziwan’s energy data with production data imported via API or entered manually. The audit trail is provided natively: Eziwan retains all raw measurements with NTP-certified timestamps for 5 years, which meets the measurement data traceability requirement set by certification bodies (Bureau Veritas, DNV, SGS, AFNOR). The ISO 50001 management review report can be generated in just a few clicks from the configured dashboards.

Question 8

How Can You Identify Energy Waste Using Industrial Monitoring?

Accepted Answer

Energy monitoring reveals four main categories of waste that companies cannot identify without the right tools. The first is standby energy consumption outside of production hours: machines, compressors, and HVAC equipment that remain powered on at night and on weekends often consume 15 to 25% of total energy without adding any value. Eziwan automatically detects non-production periods (based on the schedule or the production line start signal) and calculates phantom consumption. In a factory with a contracted power capacity of 500 kVA, 10% of non-production consumption represents 35,000 to 50,000 euros per year in wasted electricity. The second source of waste is poor power factor (cos φ): a cos φ below 0.9 results in financial penalties from the electricity supplier (TURPE rate) and indicates an aging fleet of motors or variable-speed drives. Eziwan measures cos φ per phase and per circuit using SDM630 meters (accuracy ±0.5%), making it possible to identify the equipment responsible for the power factor deviation and to size the capacitor banks to be installed. The third issue is exceeding the contracted power (contracted power overrun): under the HTA or LV > 36 kVA rate, each kilowatt of contracted but unused power is billed as an annual subscription fee. Conversely, any exceedance of the contracted power triggers a penalty. Eziwan issues real-time alerts when active power approaches 90% of the contracted power, allowing the operator to shed load from non-priority equipment before the limit is exceeded. The fourth source of waste is excessive compressed air consumption: after electricity, compressed air is often the second-largest energy expense in a factory. Eziwan can monitor the compressor’s power consumption and the system pressure (via a 4–20 mA sensor on the air line) to calculate efficiency (Nm³/kWh) and detect leaks based on deviations in the compressor-to-flow meter ratio.

Question 9

How can energy monitoring be integrated into an SAP, Oracle, or Sage ERP system?

Accepted Answer

Integrating energy monitoring into an ERP system makes it possible to calculate the actual cost of energy by production order, cost center, and finished product—a key metric for cost accounting and ESG reporting. Eziwan integrates with ERP systems in three ways. Via the Eziwan REST API (push or pull mode): Eziwan’s JSON REST API exposes all meter data with OAuth2 authentication. SAP can access this data via the SAP Integration Suite (formerly SAP Cloud Platform Integration) or through middleware (MuleSoft, Dell Boomi, Azure Integration Services). Oracle ERP Cloud has its own integration tool, Oracle Integration Cloud (OIC), which can call third-party REST APIs. Sage 100 and Sage X3 can integrate the data via scheduled CSV imports or through third-party connectors. Using Power BI as a presentation layer: without modifying the ERP, Power BI connects simultaneously to Eziwan (via the REST API) and to the ERP (via a native SAP HANA, Oracle, or Sage connector) to create cross-referenced reports that display ERP production data and Eziwan energy consumption side by side. This method is the fastest to deploy (a few days) and requires no changes to the ERP. Via scheduled CSV export (simple mode): Eziwan automatically generates timestamped CSV files (daily, weekly, or monthly) containing consumption data by meter, by period, and by production unit. These files are placed in an SFTP directory or sent via email and imported into the ERP system using standard import tools. This mode is compatible with all ERP systems without requiring any specific development.

Industrial Energy Monitoringin real time

Why manufacturers
choose us

How It Works

Connect your RS-485 meters to the Eziwan Gateway

The gateway collects Modbus RTU data

View and send alerts from the Eziwan cloud

Supported Energy Meters

A comprehensive EMS platform
for the industry

Multi-register Modbus RTU/TCP data collection

Real-time dashboards

Smart Threshold Alerts

CSV/JSON Export, REST API

ISO 50001 Energy Report

24-Month History

Energy Monitoring
for each sector

Energy Monitoring for the Manufacturing Industry

Architecture Diagram
energy monitoring

Everything You Want to Know
on RS-485 Modbus monitoring

Start your supervision
Modbus Energy Today