verified connector library

Schneider PM5500-series power meter

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

pointaddress (0-based)typescaleunit
current_phase_a3000F32BE1
current_phase_b3002F32BE1
current_phase_c3004F32BE1
current_neutral3006F32BE1
current_ground3008F32BE1
current_avg3010F32BE1
voltage_a_b3020F32BE1
voltage_b_c3022F32BE1
voltage_c_a3024F32BE1
voltage_avg_l_l3026F32BE1
voltage_a_n3028F32BE1
voltage_b_n3030F32BE1
voltage_c_n3032F32BE1
voltage_avg_l_n3036F32BE1
frequency3110F32BE1
active_power_phase_a3054F32BE1
active_power_phase_b3056F32BE1
active_power_phase_c3058F32BE1
active_power_total3060F32BE1
reactive_power_phase_a3062F32BE1
reactive_power_phase_b3064F32BE1
reactive_power_phase_c3066F32BE1
reactive_power_total3068F32BE1
apparent_power_phase_a3070F32BE1
apparent_power_phase_b3072F32BE1
apparent_power_phase_c3074F32BE1
apparent_power_total3076F32BE1
power_factor_phase_a3078F32BE1
power_factor_phase_b3080F32BE1
power_factor_phase_c3082F32BE1
power_factor_total3084F32BE1
active_energy_delivered2700F32BE1
active_energy_received2702F32BE1
active_energy_delivered_received2704F32BE1
active_energy_delivered_minus_received2706F32BE1
reactive_energy_delivered2708F32BE1
reactive_energy_received2710F32BE1
reactive_energy_delivered_received2712F32BE1
reactive_energy_delivered_minus_received2714F32BE1
apparent_energy_delivered2716F32BE1
apparent_energy_received2718F32BE1
apparent_energy_delivered_received2720F32BE1
apparent_energy_delivered_minus_received2722F32BE1

link settings as documented (unverified): RTU/ASCII/TCP; default 19200 8E1; unit ID 1; FC 01,02,03,04,07,08,11,12,17,20,24,43,100; Supports Modbus RTU, Modbus ASCII, and Modbus TCP. Parity can be Even, Odd, or None. Stop bits: 1 for Odd/Even parity, 2 for None.

⚠ Do not use this device for critical control or protection applications where human or equipment safety relies on the operation of the control circuit. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)
terminalsC, Shield, -, +
A/B polarityPoint-to-point configuration with (+) and (-) terminals
terminationTrace and check that all wiring from the computer to the meter is properly terminated
connectorRS-485 terminals
isolation2.5 kV RMS, double insulated
shield/groundConnect bare wire to Shield terminal. Ground shield wiring at one end only (either at master or last slave, but not both)
wiring notesUses shielded 2 twisted pair or 1.5 twisted pair RS-485 cable. Total distance should not exceed 1200 m (4000 ft).
broadcastsupported
protocol notesConfigurable response timeout (0.1 to 10 s), delay between frames (0 to 100 ms), and silent interval extension (0 to 15).
identification notesModbus register list is not included in this document and must be downloaded separately from www.schneider-electric.com.
FC 43 device IDsupported
powerAC: 100 – 480 V AC ± 10%, 50 or 60 Hz ±10%; DC: 125 – 250 V DC ±20%
environmentOperating temp: -25 to 70 °C (Meter), -20 to 70 °C (Display). Humidity: 5% to 95% RH non-condensing. Altitude: < 3000 m.
accuracyActive energy: ±0.2% (Class 0.2S), Reactive energy: ±2% (Class 2)
certificationsLVD compliance (EN61010-1:2010), cULus (UL61010-1:2012, CSA22.2 No.61010-1-12), MID compliance (EN 50470-1:2006 Class C, EN 50470-3:2006 Class C)
doc revisionHRB1684301-04, 02/2016
field reports — community-sourced, unverified (checked 2026-06-11)
  • ION Setup v3.2.19323.01 contains a bug that throws an 'Invalid Parameter' error when attempting to modify PM5500 Basic Setup parameters. [source]
  • Power Monitoring Expert (PME) 8.1 stops logging onboard meter data from Datalog 1 because the 'File Status' register (19004) returns a value greater than 200 (such as CRC error 211), which requires a device driver update. [source]
  • confirmed: Document revision HRB1684301-04, 02/2016 — confirmed by Schneider Electric PowerLogic PM5500 series user manual [1.1.4]
  • confirmed: Comms defaults (19200 baud, Even parity, 1 stop bit, Unit ID 1) — confirmed by Schneider Electric PM5500 user manual and configuration guides
  • confirmed: Register addresses (current_phase_a @ 3000, voltage_a_b @ 3020, active_energy_delivered @ 2700) — confirmed by Schneider Electric PM5500 Modbus Register Overview
  • confirmed: Certifications (LVD compliance EN61010-1:2010, cULus, MID compliance EN 50470-1/3 Class C) — confirmed by PM5500 technical specifications

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.