verified connector library

Iskra MC3x0x 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
voltage_u12499F32BE1
voltage_u22501F32BE1
voltage_u32503F32BE1
voltage_uavg_ln2505F32BE1
voltage_u122507F32BE1
voltage_u232509F32BE1
voltage_u312511F32BE1
voltage_uavg_ll2513F32BE1
current_i12515F32BE1
current_i22517F32BE1
current_i32519F32BE1
current_neutral_calculated2523F32BE1
frequency2583F32BE1
active_power_l12529F32BE1
active_power_l22531F32BE1
active_power_l32533F32BE1
active_power_total2535F32BE1
reactive_power_l12537F32BE1
reactive_power_l22539F32BE1
reactive_power_l32541F32BE1
reactive_power_total2543F32BE1
apparent_power_l12545F32BE1
apparent_power_l22547F32BE1
apparent_power_l32549F32BE1
apparent_power_total2551F32BE1
power_factor_l12561F32BE1
power_factor_l22563F32BE1
power_factor_l32565F32BE1
power_factor_total2567F32BE1
energy_counter_12603F32BE1
energy_counter_22605F32BE1W
energy_counter_32607F32BE1W
energy_counter_42609F32BE1var

link settings as documented (unverified): RTU; default 115200 8N2; unit ID 33; Modbus and DNP3 protocol are enabled via RS232 or RS485 or USB communication port. Factory settings of communication are #33\115200,n,8,2.

⚠ Service USB communication is not galvanic separated! When using service USB communication, power supply and measuring voltages need to be disconnected! — Starkest reads only; we never write a control register.

bench facts as documented (unverified)
terminalsScrew terminals for RS232, RS485, and M-Bus. USB standard Type B for USB. Mini-B for Service USB. DSUB 9-pin female for Profibus.
isolationRS232/RS485 in accordance with EN 61010-1 standard. Service USB is not galvanic insulated. Profibus and M-Bus are galvanic insulated.
powerAdaptable power supply. Universal power supply: 20...300 V DC / 48...276 V AC. AC power supply: 230, 240 V AC. Consumption < 5 VA.
environmentOperating temperature: -10 to +60°C. Storage temperature: -40 to +70°C. Max humidity: <= 75% r.h.
accuracyAnalogue output accuracy: 0.5% of range. Class 0.5.
certificationsSafety: EN 61010-1, EMC: 2014/30/EU, EN 61326-1, Protection: EN 60529 (Front: IP52, Rear: IP20)
doc revisionFebruary 2017 • Version 8.00

⚠ disputed: voltage_u1 @ 2499 — disputed by Iskra/DEIF Modbus map which lists U1 starting at 2500 (PLC 302501)

⚠ disputed: current_i1 @ 2515 — disputed by Iskra/DEIF Modbus map which lists I1 starting at 2516 (PLC 302517)

⚠ disputed: frequency @ 2583 — disputed by Iskra/DEIF Modbus map which lists Frequency at 2584 (PLC 302585) or 2498 (PLC 302499)

⚠ disputed: energy_counter_1 @ 2603 — disputed by Iskra MC3x0x Modbus map which lists Counter E1 at 30406 (Modbus 405)

field reports — community-sourced, unverified (checked 2026-06-11)
  • Systematic off-by-one addressing shift in the provided register map. All standard floating-point measurements (Voltages, Currents, Powers) are shifted 1 register lower than the actual Modbus addresses defined in the vendor documentation. [source]
  • confirmed: comms defaults — confirmed by Iskra MC3x0x User Manual Appendix A
  • confirmed: control_warning — confirmed by Iskra MC3x0x User Manual Section 2.2
  • confirmed: physical isolation and terminals — confirmed by Iskra MC3x0x User Manual Section 3
  • confirmed: power supply specifications — confirmed by Iskra MC3x0x Technical Data
  • confirmed: certifications and environmental limits — confirmed by Iskra MC3x0x Technical Data

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.