Huawei SmartLogger3000A

PV plant data logger

Huawei’s SmartLogger3000A manages up to 80 plant devices. The A00, A01 and A03 variants differ in cellular and MBUS hardware. Its user manual documents third-party TCP setup, and the public interface map supplies logger identity and aggregate plant-power reads. Start with those values before adding individual inverter or meter points.

  • Modbus TCP
  • Modbus RTU
  • IEC 60870-5-104
  • IEC 60870-5-103
  • DL/T645

PV plant data logger

Compatibility

Documented local Modbus TCP monitoring

Huawei’s Issue 33 manual defines the TCP monitoring endpoint and IP-limited clients. Issue 43 defines read-only logger identity and signed aggregate power. Use these published revisions as a best-effort starting point and compare values with the installed WebUI.

Record the full A-series model, regional suffix and software. Keep the reader on the protected site network and preserve existing control settings. Physical Edge polling remains untested; this guide includes no plant-control commands.

Connect it with

An installed SmartLogger3000A has an approved local TCP monitoring connection

  • Modbus
  • Edge
  • Platforms
PV plant data logger
Interface
Gateway
Edge
Output
SmartLogger3000AHuawei SmartLogger3000A
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Connect the reader to the logger’s configured site-network endpoint. Preserve existing inverter, meter and plant-controller connections. Standard TCP access is not a read-only account: constrain this client to reads and retain the plant network boundary. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
SmartLogger3000A00; historical public datasheet names SmartLogger3000A00GLWAN and LAN Gigabit Ethernet, three RS485 COM ports, four DI, two DO and four AI; no MBUS and no 2G, 3G or 4G in the current family datasheetRecord the full identity, then use the local TCP setup and logger-level first read below.
SmartLogger3000A01; historical public datasheet names SmartLogger3000A01EUSame published wired ports as A00, with 2G, 3G and 4G support; no MBUS in the current family datasheetCellular capability is an upstream communications option, not evidence of a local Edge data path. Confirm the regional modem variant and commissioned network design.
SmartLogger3000A03Published with MBUS and 2G, 3G and 4G in addition to WAN, LAN, RS485, DI, DO and AIMBUS here is Huawei plant communications hardware. It does not establish an M-Bus meter interface or an Edge protocol route.
SmartLogger3000B02, SmartLogger3000B03 and SmartLogger3000C01Separate families in the same datasheet, with different device counts, fibre, MBUS or microgrid capabilitiesDo not apply this SmartLogger3000A guide to B or C models. Select and document the exact family and variant.

Specifications

Huawei's current family datasheet separates SmartLogger3000A00, A01 and A03 by communications hardware. A00 has neither cellular nor MBUS, A01 adds cellular without MBUS, and A03 includes both cellular and MBUS.1

Exact family
SmartLogger3000A00, SmartLogger3000A01 or SmartLogger3000A03; regional suffix and software version must be recorded1
Managed devices
Up to 80 connected devices1
Ethernet
One WAN and one LAN port, each 10, 100 or 1,000 Mbps; Modbus-TCP and IEC 60870-5-104 named1
Serial and I/O
Three RS485 COM ports from 1,200 to 115,200 bps over a stated maximum 1,000 m; four DI, two DO and four AI1
Variant communications
A00: no cellular or MBUS; A01: cellular, no MBUS; A03: cellular and MBUS1
Environment
-40 to +60 degrees Celsius operating, 5% to 95% non-condensing relative humidity, up to 4,000 m altitude, IP201
Power and size
100 to 240 V AC at 50 or 60 Hz, or 12 V or 24 V DC; typical 8 W, maximum 15 W; 225 x 160 x 44 mm; 2 kg1

Interface

Documented measurements and integration boundaries for SmartLogger3000A.

  • Huawei describes the SmartLogger3000A as managing up to 80 devices, including plant equipment such as inverters, meters and environmental monitoring devices; that device count is not a count of readable Edge points.
  • Issue 43 defines logger ESN 40713 and aggregate inverter/PCS active power 40525. Keep downstream-device addressing and grid-meter import/export separate.
  • Keep logger identity, downstream-device identity, plant totals and individual inverter or meter readings as separate records. A plant total must not be reconstructed from an incomplete device set without a visible quality state.
  • The published zero-export and active-power control functions are commissioned plant-control functions. No write, scheduling, shutdown, export-limit or reactive-power command is approved by this guide.

Assessment

SmartLogger3000A A00/A01/A03, identified regional suffix and software; Issue 43 logger-level TCP reads, with physical Edge operation untested.

InteroperabilitySupported with conditions
Huawei’s Issue 33 manual defines the TCP monitoring endpoint and IP-limited clients. Issue 43 defines read-only logger identity and signed aggregate power. Use these published revisions as a best-effort starting point and compare values with the installed WebUI.134
AccuracyNot yet assessed
The map defines identity and aggregate signed power. Installed measurement accuracy and downstream completeness have not been measured.134
SecurityNot yet assessed
The manual documents IP-limited clients and unauthenticated, unencrypted standard TCP. Installed network isolation has not been inspected.134
ReliabilityNot yet assessed
The map defines responses; installed polling, downstream loss and recovery behavior have not been measured.134
RuggednessSupported with conditions
Huawei publishes the temperature, humidity, altitude and IP20 enclosure limits; the logger still requires an installation appropriate to those limits.1
ScalabilitySupported with conditions
Huawei specifies up to 80 managed devices. The manual allows five third-party TCP clients; this is not a measured polling throughput or point count.134
LifecycleLimited
Retained family datasheets, Issue 33 manual and Issue 43 interface map establish a versioned starting point; record the installed software.134

Setup

Read logger identity and aggregate power

Use the configured local TCP endpoint. Issue 43 assigns logger-level Unit ID 0; verify installed addressing. Register numbers below are literal PDU addresses.

Equipment identity
FC03 address 40713, quantity 10, STR equipment serial number. PDU 03 9F 09 00 0A. Compare ESN with the SmartLogger WebUI before accepting production data.
Aggregate active power
FC03 address 40525, quantity 2: PDU 03 9E 4D 00 02. Signed I32, high word first, gain 1000, unit kW. Synthetic 00 01 86 A0 = 100000 ÷ 1000 = 100.000 kW; FF FE 79 60 = -100.000 kW. Decoder examples, not field measurements.
Keep the measurement boundary
40525 sums output of connected inverters/PCSs. It is neither a selected inverter nor grid import/export. Use the configured communications/logical addressing for downstream devices; logger Unit ID 0 is not their address.
Response checks
Add the TCP MBAP header; the PDUs omit it. Check client IP, listening port and addressing first. Exceptions, incomplete responses and timeouts remain unavailable rather than zero. Compare fresh values with the WebUI before expanding polling.

Acceptance: Record the full A-series model, regional suffix and software. Keep the reader on the protected site network and preserve existing control settings. Physical Edge polling remains untested; this guide includes no plant-control commands.

  1. Record the complete identity

    Photograph the nameplate and record SmartLogger3000A00, A01 or A03, the regional suffix, serial number and installed software version. Do not infer the variant from the enclosure.

  2. Map the commissioned plant boundary

    List every inverter, meter, weather station, protection device and other downstream device managed by the logger. Record the physical bus, device address and owner of each value.

  3. Configure the local monitoring connection

    In Settings > Comm. Param. > Management System, configure the third-party Modbus TCP link. Prefer Enable(Limited) with the reader’s fixed IP; up to five preset clients are documented. Record the listening port and communications/logical address mode. Standard TCP is disabled by default, unauthenticated and unencrypted. Preserve the existing controller configuration.

  4. Separate monitoring from plant control

    Keep every zero-export, active-power, reactive-power, shutdown and grid-dispatch function outside the monitoring client. Record the authorised controller, interlocks, protection settings and fallback behavior separately.

  5. Prove a read-only pilot

    On an isolated approved network, compare identity and a small set of documented values with the Huawei WebUI and source devices. Test stale, missing, restarted and partially unavailable downstream devices before expanding the point set.

Common questions

Can Edge read a SmartLogger3000A over Modbus TCP?
Huawei’s Issue 33 manual defines the TCP monitoring endpoint and IP-limited clients. Issue 43 defines read-only logger identity and signed aggregate power. Use these published revisions as a best-effort starting point and compare values with the installed WebUI.134
Are SmartLogger3000A00, A01 and A03 interchangeable?
No. The current datasheet distinguishes them by cellular and MBUS hardware. Record the full model and regional suffix, then use documentation for the installed software and variant.1
Does MBUS on the A03 mean it can read ordinary M-Bus meters?
No such claim is established here. Huawei lists MBUS as a variant communications feature. Do not reinterpret it as the wired meter protocol M-Bus or as a native Edge interface without an exact manufacturer contract.1
Can Edge issue zero-export or active-power commands through the logger?
Not under this guide. Huawei documents those product functions, but no safe Edge command path, writable point contract, interlock design or failure behavior has been established. Plant control remains with the commissioned Huawei and grid-control design.1