Equipment performance

Refrigeration energy monitoring

Meter the complete refrigeration electrical boundary, split selected component loads, and align every comparison with controller state and a declared operating denominator.

ZEM-65 Wireless 3-Phase Electricity Monitor
ZEM-65Electrical boundaries
ZMB-31 Modbus Interface
ZMB-31Operating context
ZGW-20 Gateway
ZGW-20Gateway with Edge
Measure
Refrigeration power monitoring for the whole plant, selected component circuits and controller operating state
Calculate
Cold storage energy monitoring as whole-system kWh, component shares and a site-defined specific-energy denominator NEA
Sensors
ZEM-65, meters each three-phase electrical boundary with its selected CT set ZEM-63 datasheet (PDF, opens in a new tab)
On site
ZGW-20 Gateway, Edge keeps the measured totals, component context and calculated comparisons locally ZGW-20 datasheet (PDF, opens in a new tab)

Define the electrical boundary before choosing meter positions

Start with a one-line diagram of every compressor, condenser fan, evaporator fan, pump, defrost heater and auxiliary that belongs to the refrigeration system. Put one parent meter around the complete declared boundary. Add component meters only where a separate supply can answer a useful question. A controller register adds operating context; it does not replace an electrical measurement.

Define the electrical boundary before choosing meter positions
Measurement layerEpiSensor routeQuestion it answers
Whole refrigeration system ZEM-65 at the refrigeration boardHow much electrical energy crossed the complete declared boundary?
Selected component circuits One ZEM-65 per separately supplied compressor, fan, pump or defrost groupWhich non-overlapping component changed, and does the split reconcile with the parent?
Controller operating context ZMB-31 on a documented Modbus RTU segmentWhich compressors, stages, fans or defrost states were active when the electrical pattern changed?

Hardware for refrigeration power monitoring

Use one ZEM-65 for the parent electrical boundary and additional units only for non-overlapping circuits worth separating. Add a ZMB-31 when the controller has a published Modbus RTU map.

If the controller has a published register map and a suitable RS-485 segment

Cold storage energy monitoring boundaries

The parent meter owns the total. Component meters explain selected parts of it. Keep the operating state and comparison denominator beside both, so a change in load, weather, setpoint or defrost schedule is not presented as an efficiency result.

System architecture

How refrigeration energy reaches Edge

The plant's electrical supplies and documented controller data follow separate measurement paths before they are aligned locally in Edge.

Voltage + CT inputs · L1/L2/L3 + CTs · Per selected supply
Zigbee
Modbus RTU · RS-485
Zigbee
Runs locally
MQTTS / HTTPS
Field measurement
Interface
Gateway
Local Edge
Optional output
MeasurementWhole-system electricity · Component electricityDeclared refrigeration-board boundary · Selected non-overlapping compressor, fan, pump or defrost circuits
Third-party instrumentController operating dataPublished state, setpoint, pressure or temperature registers
EpiSensor interfaceZEM-65Parent and component electricity meters
Optional EpiSensor interfaceZMB-31Optional controller interface
EpiSensor GatewayZGW-20Gateway
Local softwareEdgeLocal trends, calculations and evidence
Optional receiving systemCustomer platformOptional onward data
Real EpiSensor products are shown. ZEM-65 measures electricity; ZMB-31 reads only the registers the refrigeration controller exposes. Edge runs locally on ZGW-20, and an onward platform is optional.
Sensor positions for cold storage energy monitoring boundaries
PositionWhat it tells youReferenceSensor
Complete refrigeration board Total kW, kWh and demand for every electrical load inside the declared refrigeration boundary Include or explicitly exclude compressors, condenser and evaporator fans, pumps, defrost, drain and anti-sweat heaters DOE ZEM-65 (on this page)
Compressor supply The compressor pack's electrical share, starts and changing capacity signature Use a separate meter only where the supply is electrically distinct; retain the parent meter as the system total NEA ZEM-65 (on this page), selected child boundary
Heat-rejection and distribution loads Condenser fans, evaporator fans and pumps that may move differently from compressor electricity Whole-system measurement keeps an apparent compressor saving from hiding a fan or pump penalty NREL ZEM-65 (on this page), selected child boundary
Defrost and auxiliary loads The timing and energy of electric defrost, drain, anti-sweat or pan heaters where separately supplied Record both power and operating time; the daily energy is their product DOE ZEM-65 (on this page), selected child boundary
Controller operating context Which stage, fan, setpoint, pressure or defrost state accompanied the measured electrical pattern Use only the documented model and firmware register map, with address, type, byte order, scale and unit recorded ZMB-3X datasheet (PDF, opens in a new tab) ZMB-31 (on this page)
  • Parent and child meters do not add. A compressor meter is already inside the refrigeration-board total. Use it to calculate a share or reconcile a residual, not to increase the total.

  • The denominator is part of the result. Tonnes stored, tonnes handled, cubic metres, operating hours and cooling output answer different questions. Record the exact denominator and period beside every specific-energy figure.

  • Controller data is context, not proof of energy. A compressor run flag or calculated load percentage cannot replace a direct electrical measurement at the chosen boundary.

How to calculate refrigeration energy performance

Calculate from interval energy inside one stable electrical boundary. Use non-overlapping component meters for shares, and divide by a declared operating denominator only when that denominator is measured over the same period.

component share (%) = Ecomponent ÷ Esystem × 100
specific energy = Esystem ÷ D
Ecomponent
interval energy for one non-overlapping component boundary, kWh
Esystem
interval energy for the complete declared refrigeration boundary, kWh
D
the recorded denominator for the same interval, such as tonnes stored, tonnes handled, refrigerated volume or directly measured cooling output

Worked example

During one recorded day, the complete refrigeration boundary uses 720 kWh. The separately metered compressor pack uses 504 kWh, so its share is 70%. If the site's agreed denominator is an average 90 tonnes stored during that same day, the recorded specific energy is 8 kWh per tonne for that day. It is comparable only with periods that use the same boundary, denominator and operating context.

In Edge

Edge can sum explicit non-overlapping inputs and calculate guarded ratios. Keep source identities, units, interval alignment, stale-input action and output timestamp policy with the result. A missing component is not zero, and repeated instantaneous kW readings must not be summed and labelled kWh.

Commissioning checks

Commission the parent total first. Component analysis is useful only after the complete boundary is credible.

  • Freeze the one-line boundary

    Mark every compressor, fan, pump, heater and auxiliary as included, excluded or separately metered on the current electrical one-line diagram.

    Pass when the diagram, meter labels and Edge point names describe the same physical boundaries.

  • Prove each electrical channel

    With a competent electrical person, verify voltage references, phase order, CT orientation and ratio against a known operating state or reference instrument.

    Pass when phase values, total kW and direction are plausible, and the check is recorded for every ZEM-65.

  • Reconcile parent and children

    Compare the parent interval energy with the sum of non-overlapping child meters and list every load that remains only in the parent.

    Pass when the residual is explainable and no physical load is counted twice.

  • Walk the controller states

    Observe a normal compressor stage change, fan change and defrost cycle while checking each selected register's value, unit and timestamp.

    Pass when every state changes with the plant and restores correctly after a communication interruption.

  • Validate the comparison basis

    Record setpoints, ambient condition, door or production activity, inventory or throughput denominator, defrost schedule and any maintenance change for the baseline and comparison periods.

    Pass when the two periods are comparable, or every material difference is disclosed with the result.

  • Test missing and stale inputs

    In an approved test window, stop one input and inspect the parent total, component share and specific-energy output before and after reporting resumes.

    Pass when a missing input is visible, no partial total is presented as complete, and restoration does not hide the gap.

What refrigeration energy monitoring does not prove

Electrical and controller records explain when and where the plant used energy. They do not, by themselves, prove cooling efficiency, product compliance or a safe control strategy.

  • Electricity, runtime and operating temperatures do not measure useful cooling output, so they are not enough to calculate COP without a separately engineered cooling-output measurement.
  • This page does not replace mapped product-temperature monitoring, food-safety procedures or alarm response; those belong to the cold-chain temperature guide.
  • Energy monitoring does not detect or quantify refrigerant leakage, charge condition, oil condition, vibration faults or mechanical wear.
  • Observing a controller does not authorise setpoint changes, load shedding or demand response; controlled flexibility needs its own engineered permissions, interlocks and recovery test.
  • A lower kWh total is not automatically an efficiency improvement when weather, product load, doors, setpoints, operating hours or the measurement boundary changed.

Sources and related guides

Sources

Related

Reviewed by EpiSensor Engineering on . Revision 2.

Start with the boundary, not a dashboard

We will map the refrigeration circuits and controller, choose each metering path, and define a comparison that cannot hide a missing load.

Contact us