Accuenergy AcuRev 1310

Three-phase energy meter

The AcuRev 1310 series is Accuenergy's DIN-rail three-phase power and energy meter, ordered as the AcuRev 1312, 1313 or 1314 with a choice of 5A/1A, 333 mV, mA or Rogowski coil current inputs. It measures 10 to 690 V AC directly, counts active, reactive and apparent energy in both directions with four tariffs, and has a built-in RS-485 port on terminals A, B and S that runs Modbus RTU by default or BACnet MS/TP when selected. Accuenergy's map gives voltage, current, power and power factor as floats from 0x2000, energy counters from 0x2046 and 0x1300, and a SunSpec meter block from 0xC350 whose 16-bit values carry their own scale factors.

Accuenergy AcuRev 1310 series DIN-rail energy meter, side label AcuRev 1314-333-X1
  • Modbus RTU

Three-phase energy meter

Ask an engineer

Compatibility

Compatible with EpiSensor Edge over Modbus RTU

The AcuRev 1310 is compatible with EpiSensor Edge over its built-in RS-485 port running Modbus RTU, the factory default, read through a ZMB-31 Modbus Interface or a Gateway serial port. Accuenergy publishes the FC03 register map with hexadecimal and decimal addresses and data types, and a SunSpec block whose values carry units and scale factors.

AcuRev 1312, 1313 and 1314 meters on the built-in RS-485 port with the protocol set to Modbus, using Modbus map version 1.00 and user manual version 1.2.11. Site check: read the SunSpec ID at 0xC350 and compare the first voltage read with the display before adding points. Read-only monitoring: no writes to the settings, energy, reset or relay registers.

Connect it with

Route into Edge

For a meter in a distribution board where a wireless link avoids running a data cable back to the Gateway

  • Modbus
  • Wireless
  • Edge
  • Platforms
Three-phase energy meter
Interface
Gateway
Edge
Output
AcuRev 1310AcuRev 1310 RS-485 terminals A, B and S
ZMB-31Modbus RTU to the EpiSensor wireless network
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus RTU · RS-485
EpiSensor wireless
Runs locally
Optional onward data
Wire A (+) and B (-) from the meter to the ZMB-31, match the meter address, baud rate and parity (address 1, 19200 bit/s, no parity and 1 stop bit by default) and read with FC03. If a building management system already polls the meter over BACnet MS/TP, the port runs one protocol at a time: agree any change with its owner first. The customer-platform output is optional; Edge remains the local system of record.

When the Gateway sits near the meter, or several meters share one wired RS-485 bus

  • Modbus
  • Edge
  • Platforms
Three-phase energy meter
Interface
Gateway
Edge
Output
AcuRev 1310AcuRev 1310 RS-485 terminals A, B and S
Isolated serial interfaceApproved RS-485-to-host adapter
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus client
Customer platformMQTT · API · files
Modbus RTU · RS-485
Isolated serial
Runs locally
Optional onward data
Daisy-chain A to A and B to B without T branches, earth the shield at one end only and fit a 120 to 300 Ω, 0.25 W resistor at the last device on a long chain. Give each meter its own address and read with FC03 from the map. The manual documents RS-485 only; it describes no Ethernet or Modbus TCP port. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
AcuRev 1312Three current channels; neutral current calculated; Measurement Canada approved; RS-485 Modbus RTU or BACnet MS/TP on A, B and SRead the float, energy or SunSpec registers with FC03 on the serial path.
AcuRev 1313Three current channels; neutral current calculated; the same RS-485 port and mapSame read path.
AcuRev 1314Four current channels, so neutral current is measured (not on the Rogowski coil version); residual current calculated; the same RS-485 port and mapSame read path. Neutral current is at 0x1200 as a float.

Specifications

Models
AcuRev 1312, 1313 and 1314. The 1314 has four current channels; the 1312 is Measurement Canada approved.13
Current inputs
5A/1A, 333 mV, Rogowski coil (RCT) or 80/100/200 mA CTs. CT1 primary 1 to 50,000. 5A/1A CTs are earthed at one end; mV, RCT and mA CT leads are not earthed.13
Voltage
Direct input up to 400 V AC L-N and 690 V AC L-L, 50/60 Hz; PTs above 690 V L-L. Wiring modes 3LN, 2LL, 1LL and 1LN.13
Accuracy
Active energy class 0.5S to IEC 62053-22 and class 0.5 to ANSI C12.20; reactive energy class 2 to IEC 62053-23; voltage, current and power 0.5%, frequency 0.2%.3
RS-485
Terminals A (+), B (-) and S (shield). Modbus RTU by default, or BACnet MS/TP. Address 1 to 247 (default 1); 1200 to 38400 bit/s (default 19200); parity even, odd, none with 2 stop bits or none with 1 stop bit (default). Up to 1200 m of shielded twisted pair.1
Other interfaces
Pulse output on P1 and P2 (1 to 60000 pulses per kWh or kvarh, 20 to 100 ms); optional relay output on R1 and R2 for alarm or control; non-contact infrared port.13
Power supply
100 to 415 V AC, 50/60 Hz, or 100 to 300 V DC on L and N; less than 2 W.3
Housing
35 mm DIN rail; 108 × 90 mm front with sealable terminal covers.13
Environment and approvals
Operating -25 to +70 °C in the datasheet; storage -40 to +85 °C; humidity 5 to 95% non-condensing. IEC 61010-1 and UL 61010-1, CE, RoHS, BTL listed for B-SS.3

Interface

Documented measurements and integration boundaries for AcuRev 1310.

  • The map prints each address in hexadecimal and decimal; both describe the same zero-based PDU address, so 0x200A is decimal 8202 on the wire. Read with FC03. The map's writes use FC16, and the relay output uses FC01 and FC05.
  • Check the address convention once: two registers at 0xC350 (decimal 50000) return the SunSpec ID 0x53756E53, ASCII SunS. An older copy of the SunSpec block starts at 0x1000.
  • Float block, two registers each: total current 0x2000, phase A, B and C current 0x2002, 0x2004 and 0x2006; phase average voltage 0x2008; phase A, B and C voltage 0x200A, 0x200C and 0x200E; line average voltage 0x2010; line AB, BC and CA voltage 0x2012, 0x2014 and 0x2016; frequency 0x2018.
  • Total active power 0x201A with phases A to C at 0x201C to 0x2020; total apparent power 0x2022 with phases at 0x2024 to 0x2028; total reactive power 0x202A with phases at 0x202C to 0x2030; total power factor 0x2032 with phases at 0x2034 to 0x2038: float.
  • The map and manual name these registers float without stating the word order or a unit column; the manual says the communication value of an electrical measurement equals the real value. Confirm word order and whether power is in W or kW against the display on the first read.
  • Energy counters, int32 in two registers: total active energy exported 0x2046 and imported 0x204E, each followed by phases A to C; apparent energy exported 0x2056 and imported 0x205E; reactive energy by quadrant Q1 0x2066, Q2 0x206E, Q3 0x2076 and Q4 0x207E. The map gives no scale, so compare one with the display kWh before setting the multiplier.
  • Tariff and net energy, int32: total active energy 0x1300 with tariffs 1 to 4 at 0x1302 to 0x1308; net active energy 0x130A (signed); imported active energy tariffs 1 to 4 from 0x1314; exported from 0x131C; reactive energy from 0x1324.
  • SunSpec meter block, int16 with a separate scale factor: currents 0xC397 to 0xC39A (A) with the factor at 0xC39B; voltages 0xC39C to 0xC3A3 (V) with the factor at 0xC3A4; frequency 0xC3A5 with the factor at 0xC3A6; active power 0xC3A7 to 0xC3AA (W) with the factor at 0xC3AB; power factor 0xC3B6 to 0xC3B9 with the factor at 0xC3BA. Value = register × 10^factor.
  • SunSpec energy, acc32 in two registers: total active energy exported 0xC3BB and imported 0xC3C3 in Wh, with the shared energy scale factor at 0xC3CB. The map labels 0xC39B both as the current scale factor and as CT Ratio; treat it as the scale factor and confirm current against the display.
  • Settings are readable at 0x200 (address), 0x201 (baud rate), 0x202 (parity), 0x210 (primary or secondary side), 0x211 (wiring mode), 0x212 and 0x213 (CT2, CT1) and 0x215 to 0x217 (PT2, PT1, ten times the real value). Wiring check result is at 0x100 and seal status at 0x101 (0x0A sealed).
  • Settings, the energy counters, resets and the relay are writable. Keep FC05 and FC16 out of a monitoring poll.

Assessment

AcuRev 1312, 1313 and 1314 meters on the built-in RS-485 port with the protocol set to Modbus, using Modbus map version 1.00 and user manual version 1.2.11. Site check: read the SunSpec ID at 0xC350 and compare the first voltage read with the display before adding points. Read-only monitoring: no writes to the settings, energy, reset or relay registers.

InteroperabilitySupported with conditions
Accuenergy publishes Modbus RTU on RS-485 as the factory default, with a register map giving hexadecimal and decimal addresses, function codes and data types, and a SunSpec meter block with units and scale factors. The float and int32 blocks have no stated word order, unit or energy scale.12
AccuracySupported with conditions
Revenue-grade class 0.5S active energy with per-phase voltage, current and power, bi-directional and four-quadrant energy, tariffs and demand. Values depend on the configured wiring mode, CT and PT ratios and current input type.13
SecurityLimited
Settings need a four-digit password (0000 by default), communication writes of resets and energy need a write authority granted with that password, high permission lapses after 30 minutes, and an electronic and physical seal blocks important changes. Modbus RTU itself has no encryption or peer authentication, and the password travels in clear.1
ReliabilitySupported with conditions
Wide auxiliary supply of 100 to 415 V AC or 100 to 300 V DC, IEC 61010-1 and UL 61010-1 safety, a wiring check, run-time counters and event logs. The sources do not state how long data is retained without supply. Treat failed reads as missing data.13
RuggednessSupported with conditions
Rated -25 to +70 °C and 5 to 95% humidity non-condensing on a 35 mm DIN rail, for a dry, dust-free location. No ingress rating is given for the meter; Accuenergy offers a NEMA 4X enclosure as an accessory.13
ScalabilitySupported with conditions
Addresses 1 to 247 on a daisy chain up to 1200 m, shorter with more devices or higher baud rates, and a SunSpec common block with model and serial number for identity records.12
LifecycleLimited
Accuenergy publishes a current, dated manual, datasheet and versioned Modbus map, and notes that protocol switching needs firmware v2.16 or later, but gives no firmware support period, update path or end-of-sale date.13

Setup

Read phase A voltage from the SunSpec block at 0xC39D

AcuRev 1310 Modbus map version 1.00, New SunSpec sheet, lists Phase Voltage AN at 0xC39D (decimal 50077) as int16 in volts and the voltage scale factor at 0xC3A4 (decimal 50084), range -2 to 2, used as a power of ten. Use that map as the starting point and compare the result with the display.

Identity check
01 03 C3 50 00 02 F8 5E reads the SunSpec ID at 0xC350. A reply of 01 03 04 53 75 6E 53 96 F0 is ASCII SunS and confirms the address convention.
Request
01 03 C3 9D 00 08 E9 A6: address 1, FC03, address 0xC39D, eight registers: phase A, B and C voltage, line average, line AB, BC and CA voltage, then the voltage scale factor at 0xC3A4.
Address convention
The hexadecimal and decimal columns describe the same zero-based PDU address: send 0xC39D, decimal 50077. A client that numbers registers from one shows it as 50078.
Synthetic response
01 03 10 08 FC 08 FC 08 FC 0F 92 0F 92 0F 92 0F 92 FF FF F6 13: sixteen data bytes, one register per value, so no word order applies.
Decode
Phase A voltage 0x08FC = 2300 and scale factor 0xFFFF = -1 as a signed int16, so 2300 × 10⁻¹ = 230.0 V. 0x0F92 = 3986 gives 398.6 V line to line.
Acceptance
Keep the point when it agrees with phase A voltage on the meter display at the same time. If the identity check fails, check the address, protocol selection and baud rate before adding more points.

Acceptance: The response bytes are a synthetic decoder check, not a captured meter reply. A real reply must agree with the display before current, power and energy points are enabled.

  1. Identify the meter

    Read the model from the side label, for example AcuRev 1314-333-X1, which gives the model and current input. Note the wiring mode and the CT and PT ratios configured on the meter.

  2. Read the serial settings without changing them

    The all-parameters display shows the device address, baud rate and parity. The settings mode behind the SET key under the terminal cover shows the protocol, which must be Modbus. The defaults are address 1, 19200 bit/s, no parity and 1 stop bit. Enter the same values in the Edge serial client or the ZMB-31.

  3. Wire the RS-485 pair

    Connect A (+) and B (-) to the bus with shielded twisted pair, earth the shield at one end only and avoid T branches. Give each meter its own address.

  4. Make two reads

    Read two registers at 0xC350 and expect 53 75 6E 53. Then read the SunSpec voltage block at 0xC39D as in the worked read below and compare phase A voltage with the display.

  5. Add the points you need

    Add current, power and energy from the SunSpec block with their scale factors, or from the float and int32 blocks after one comparison with the display. Keep FC05 and FC16 writes out of the polling configuration.

Common questions

Which block should I read: float, int32 or SunSpec?
The SunSpec block at 0xC350 is the most completely specified: each value is one 16-bit register in A, V, W or Wh with a published scale factor. The float block at 0x2000 and the energy blocks at 0x2046 and 0x1300 carry more detail per phase and per tariff, but the map does not state their word order or units, so compare one of each with the display first.12
Is 0x200A the same register as 8202?
Yes. The map lists each register in hexadecimal and decimal, and both are the zero-based PDU address. A client that numbers holding registers from one needs 8203.2
Why does the meter not answer at 9600 bit/s?
The default is 19200 bit/s with no parity and 1 stop bit, and the port may have been switched to BACnet MS/TP. Check the protocol, address, baud rate and parity in the settings mode before changing anything on the Edge side.1
Can a monitoring client change the meter by accident?
The map marks settings, energy counters and resets as writable with FC16, and the relay accepts FC05. Resets and energy writes also need the communication write authority set with the meter password, and a sealed meter refuses changes to important parameters. A monitoring configuration should still read with FC03 only.12
Can the AcuRev 1310 be used for billing?
The datasheet gives class 0.5S to IEC 62053-22 and class 0.5 to ANSI C12.20, and the AcuRev 1312 is Measurement Canada approved. The retained sources list no MID approval.3