Actions2
Discover Devices
AI-generatedOverview
This node operation discovers all connected devices (such as inverters, meters, etc.) on a Huawei SmartLogger 3000 device network via Modbus TCP. It scans specified unit ID ranges to identify devices, supporting parallel scanning to speed up the discovery process. This is useful for network administrators or engineers who need to map and monitor devices connected to a SmartLogger system.
Use Case Examples
- Discover all devices connected to a SmartLogger by scanning unit IDs 1 to 247 with a parallel scan count of 10 to quickly identify all active devices on the network.
- Scan a smaller range of unit IDs (e.g., 1-15) to discover devices in a specific segment of the network.
Properties
| Name | Meaning |
|---|---|
| Field Naming Convention | Choose output field naming: Descriptive or IEC 61850 standard. |
| Host | IP address or hostname of the SmartLogger device to connect to. |
| Port | Modbus TCP port to connect to (default is 502). |
| Unit ID | SmartLogger Modbus unit ID (typically 3 for SmartLogger). |
| Connection Timeout (Ms) | Connection timeout in milliseconds for Modbus TCP connection attempts. |
| Retry Attempts | Number of retry attempts on connection failure. |
| Discovery Range | Unit ID ranges to scan for device discovery, specified as comma-separated ranges or individual IDs (e.g., 1-15,21-30 or 12,13,14,15). |
| Discovery Timeout (Ms) | Shorter timeout in milliseconds used specifically for device discovery to speed up scanning. |
| Parallel Scan Count | Number of devices to scan simultaneously to balance speed and network load. |
Output
JSON
allDevices- Array of discovered devices with their details._metadataoperation- The operation performed, here 'discoverDevices'.host- Host IP or name used for connection.port- Port number used for connection.unitId- Unit ID used for connection.timestamp- Timestamp of when the operation was performed.success- Boolean indicating if the operation was successful.
Dependencies
- Modbus TCP connection to Huawei SmartLogger device
Troubleshooting
- Connection failures due to incorrect host, port, or unit ID settings. Verify network accessibility and device configuration.
- Timeout errors if the device does not respond within the specified timeout period. Adjust timeout and retry settings accordingly.
- Errors if the discovery range is improperly formatted or contains invalid unit IDs. Ensure the discovery range string is correctly formatted and unit IDs are between 1 and 247.
- Network load issues if parallel scan count is set too high, potentially causing slower responses or dropped connections. Reduce parallel scans if network instability occurs.