Huawei SmartLogger icon

Huawei SmartLogger

Read data from Huawei SmartLogger 3000 devices via Modbus TCP

Read Data

AI-generated

Overview

This node reads selected categories of data from Huawei SmartLogger 3000 devices via Modbus TCP. It is useful for monitoring and collecting data such as system information, power metrics, environmental conditions, and alarms from SmartLogger devices in energy management or industrial automation scenarios. For example, it can be used to gather active/reactive power data, temperature, or system alarms for analysis or reporting.

Use Case Examples

  1. Reading power data and environmental data from a SmartLogger device to monitor energy production and weather conditions.
  2. Collecting system information and alarms to track device status and troubleshoot issues.

Properties

Name Meaning
Data to Read Select which data categories to read from the SmartLogger (system, power, environmental, alarms).
Field Naming Convention Choose output field naming style: Descriptive or IEC 61850 standard.
Host IP address or hostname of the SmartLogger device.
Port Modbus TCP port (default: 502).
Unit ID SmartLogger Modbus unit ID (typically 3 for SmartLogger).
Connection Timeout (Ms) Connection timeout in milliseconds.
Retry Attempts Number of retry attempts on connection failure.

Output

JSON

  • system - System information data such as date/time, location, and DST settings.
  • power - Power data including active/reactive power, current, energy, and CO2 reduction.
  • environmental - Environmental data like temperature, irradiance, wind speed, and direction.
  • alarms - System alarms and status information.
  • _metadata
    • operation - The operation performed (readData).
    • host - Host IP or name of the SmartLogger device.
    • port - Modbus TCP port used.
    • unitId - Modbus unit ID used.
    • timestamp - Timestamp of the data read operation.
    • success - Indicates if the operation was successful.

Dependencies

  • Modbus TCP communication with Huawei SmartLogger devices

Troubleshooting

  • Connection failures due to incorrect host, port, or unit ID settings. Verify device network accessibility and parameters.
  • Timeouts if the device does not respond within the specified timeout period. Increase timeout or check network conditions.
  • Retries exhausted if the device is unreachable after multiple attempts. Check device status and network connectivity.
  • Errors thrown for unknown operations if the operation parameter is set incorrectly. Ensure 'readData' is selected for this operation.

Discussion