PortDock

Rootech Accura 3500 Modbus register map

3-phase multifunction power meter with optional IO modules. Modbus TCP/RTU, all data in holding registers (FC03), 32-bit high word first. Measurements come from aggregation buffers: read 19911 to fetch, then read. The Accura 3550 uses the same meter map. · Power meter · Accura 3500, Accura 3550

An unofficial summary of facts (addresses, types, units, scaling) from the maker's manual. Not affiliated with the maker; values can differ by firmware or model. Always check the device manual before writing (run commands, settings).

Default communication

ProtocolModbus RTU, Modbus TCP
Baud (factory)9600 bps — options: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
Data · parity · stop— · Even · 1
TCP port502
32-bit orderABCD
Max per request125 registers
Manual address style1-based numbers (wire address + 1)

Registers (60)

«Wire» is the 0-based address in the request frame (PortDock's «0-based» notation). Value = raw × scale. Table: HR holding register, IR input register, CO coil, DI discrete input. Function codes in hex.

60

Swipe the table sideways — the first column (manual address) stays put.

ManualWireTableNameTypeUnit · scaleR/WFCDetails
1000110000 (0x2710)HRProduct IDU16R03
3500 for Accura 3500, 3550 for Accura 3550
p.15 System Information
1000310002 (0x2712)HRSerial numberU32 ABCDR03
p.15 System Information
1000810007 (0x2717)HRMajor application versionU16R03
p.15 System Information
1000910008 (0x2718)HRMinor application versionU16R03
p.15 System Information
1001010009 (0x2719)HRApplication revisionU16R03
p.15 System Information
1290112900 (0x3264)HRRemote setup lockU16R/W03·06·10
Write 2300 → 0 → 700 → 1 to unlock; any other write locks. Per connection; relocks at power-off.
0 = Unlocked · 1 = Locked
p.19 Remote Setup Unlock
1370113700 (0x3584)HRAccess for RS-485 setupU16R/W03·06·10
Read fetches device settings into 13702-13705 (bit 15 = 1 on success); write 1 to apply 13702-13705.
p.27 RS-485 Setup
1370213701 (0x3585)HRRS-485 device addressU16R/W03·06·10
Range 0 ~ 247
p.27 RS-485 Setup
1370313702 (0x3586)HRRS-485 bit rateU16R/W03·06·10
0 = 1200 bps · 1 = 2400 bps · 2 = 4800 bps · 3 = 9600 bps · 4 = 19200 bps · 5 = 38400 bps · 6 = 57600 bps · 7 = 115200 bps
p.27 RS-485 Setup
1370413703 (0x3587)HRRS-485 parityU16R/W03·06·10
0 = None · 1 = Odd · 2 = Even
p.27 RS-485 Setup
1370513704 (0x3588)HRRS-485 stop bitU16R/W03·06·10
0 = 1 stop bit · 1 = 2 stop bits
p.27 RS-485 Setup
1990119900 (0x4DBC)HRAggregation selectionU16R/W03·06·10
0 = 0.2 s · 1 = 1 s (default) · 2 = 5 s · 3 = 1 min · 4 = 5 min · 5 = 1 h · 6 = 6 h · 7 = 1 day · 255 = Max/Min since reset
p.58 Aggregation Selection
1990219901 (0x4DBD)HRIndex selection update modeU16R/W03·06·10
How 19904 changes when 19911 is read. Newest (1) always fetches the latest data (p.123: newest index by default).
0 = Fixed · 1 = Newest · 2 = Auto increment
p.59 Index Selection
1990419903 (0x4DBF)HRIndex selectionU16R/W03·06·10
Range 0 ~ 9999
p.59 Index Selection
1990619905 (0x4DC1)HRNewest indexU16R03
p.59 Index Selection
1991119910 (0x4DC6)HRData fetchU16R03
Reading fetches the selected aggregation/index into 19914-48000. Per connection.
0 = Fetch failed · 1 = Fetch succeeded
p.60 Data Fetch
1991319912 (0x4DC8)HRIndex of fetched dataU16R03
p.60 Data Fetch
1993019929 (0x4DD9)HRValidity of meter measurement dataS16R03
p.126 lists UInt16, but values are -1/0, so Int16 per p.61.
-1 = Invalid · 0 = Valid (meter data)
p.61 Measurement Header
2000120000 (0x4E20)HRVoltage VanF32 ABCDVR03
p.62 Measurement Data
2000320002 (0x4E22)HRVoltage VbnF32 ABCDVR03
p.62 Measurement Data
2000520004 (0x4E24)HRVoltage VcnF32 ABCDVR03
p.62 Measurement Data
2000720006 (0x4E26)HRAverage phase voltageF32 ABCDVR03
p.62 Measurement Data
2001120010 (0x4E2A)HRVoltage VabF32 ABCDVR03
p.62 Measurement Data
2001320012 (0x4E2C)HRVoltage VbcF32 ABCDVR03
p.62 Measurement Data
2001520014 (0x4E2E)HRVoltage VcaF32 ABCDVR03
p.62 Measurement Data
2001720016 (0x4E30)HRAverage line-to-line voltageF32 ABCDVR03
p.62 Measurement Data
2001920018 (0x4E32)HRCurrent IaF32 ABCDAR03
p.62 Measurement Data
2002120020 (0x4E34)HRCurrent IbF32 ABCDAR03
p.62 Measurement Data
2002320022 (0x4E36)HRCurrent IcF32 ABCDAR03
p.62 Measurement Data
2002520024 (0x4E38)HRAverage currentF32 ABCDAR03
p.62 Measurement Data
2005720056 (0x4E58)HRFrequencyF32 ABCDHzR03
p.62 Measurement Data
2005920058 (0x4E5A)HRVoltage THD phase AF32 ABCD%R03
p.62 Measurement Data
2006120060 (0x4E5C)HRVoltage THD phase BF32 ABCD%R03
p.62 Measurement Data
2006320062 (0x4E5E)HRVoltage THD phase CF32 ABCD%R03
p.62 Measurement Data
2007120070 (0x4E66)HRCurrent THD phase AF32 ABCD%R03
p.63 Measurement Data
2007320072 (0x4E68)HRCurrent THD phase BF32 ABCD%R03
p.63 Measurement Data
2007520074 (0x4E6A)HRCurrent THD phase CF32 ABCD%R03
p.63 Measurement Data
2009520094 (0x4E7E)HRActive power phase AF32 ABCDkWR03
p.63 Measurement Data
2009720096 (0x4E80)HRActive power phase BF32 ABCDkWR03
p.63 Measurement Data
2009920098 (0x4E82)HRActive power phase CF32 ABCDkWR03
p.63 Measurement Data
2010120100 (0x4E84)HRTotal active powerF32 ABCDkWR03
p.63 Measurement Data
2010920108 (0x4E8C)HRTotal reactive powerF32 ABCDkVARR03
p.63 Measurement Data
2011720116 (0x4E94)HRTotal apparent powerF32 ABCDkVAR03
p.63 Measurement Data
2011920118 (0x4E96)HRPower factor phase AF32 ABCDR03
p.63 Measurement Data
2012120120 (0x4E98)HRPower factor phase BF32 ABCDR03
p.63 Measurement Data
2012320122 (0x4E9A)HRPower factor phase CF32 ABCDR03
p.63 Measurement Data
2012520124 (0x4E9C)HRTotal power factorF32 ABCDR03
p.63 Measurement Data
2013820137 (0x4EA9)HRTotal power factor lead/lag statusU16R03
0 = None · 1 = Lead · 2 = Lag · 3 = No load (apparent power 0)
p.64 Measurement Data
2013920138 (0x4EAA)HRVoltage unbalanceF32 ABCD%R03
p.64 Measurement Data
2015720156 (0x4EBC)HRCurrent unbalanceF32 ABCD%R03
p.64 Measurement Data
2016920168 (0x4EC8)HRDevice temperatureF32 ABCD℃R03
Reported in ℉ when the Locale temperature unit is Fahrenheit.
p.64 Measurement Data
2025120250 (0x4F1A)HRReceived active energyU32 ABCDkWhR03
Unit follows the energy-unit setting (default kWh, can be Wh).
p.64 Measurement Data
2025320252 (0x4F1C)HRDelivered active energyU32 ABCDkWhR03
Unit follows the energy-unit setting (default kWh, can be Wh).
p.64 Measurement Data
2025720256 (0x4F20)HRNet active energy (received − delivered)S32 ABCDkWhR03
Unit follows the energy-unit setting (default kWh, can be Wh).
p.64 Measurement Data
2026720266 (0x4F2A)HRPositive reactive energyU32 ABCDkVARhR03
p.65 Measurement Data
2026920268 (0x4F2C)HRNegative reactive energyU32 ABCDkVARhR03
p.65 Measurement Data
2027520274 (0x4F32)HRApparent energyU32 ABCDkVAhR03
p.65 Measurement Data
2049720496 (0x5010)HRAverage demand currentF32 ABCDAR03
p.66 Measurement Data
2050520504 (0x5018)HRTotal demand active powerF32 ABCDkWR03
p.66 Measurement Data
2059120590 (0x506E)HREnergy unitU16R03
Follows the Locale energy-unit setting; 1 means active energy is in Wh.
0 = kWh · 1 = Wh
p.66 Measurement Data

Notes

Read it with PortDock

  1. Install the free PortDock Modbus Master and connect with the device's settings.
  2. On the table toolbar, «Device profile…» → pick this device → «Load». Polling tables, names, types and the Slave ID are filled in (optionally the serial settings too).
  3. Names carry the unit and scale (e.g. «×0.01 Hz»). Values on screen are raw — multiply by the scale.
  4. To test your program without the device, PortDock Modbus Slave's «Emulate device…» serves the same map with example values.

Download JSON

Sources