Modbus Server
uniflow.plugin.modbusserver •
Category: Industrial Protocols •
Version: v1.0.2
Modbus Server Plugin Reference Manual
1. Overview
Plugin Name: Modbus Server
Type: Industrial Protocols
Identifier: uniflow.plugin.modbusserver
Description
Integration with Modbus TCP Clients.
2. Configuration Parameters
The following configuration fields are available in the User Interface for this plugin:
| Configuration Setting | Description |
|---|---|
| Listening Port | Numeric value specifying the listening port. |
| Unit ID | Specifies the unit id. |
3. Exposed Routes & Data Types
The following routes are available in the Uniflow catalog for this plugin:
| Display Name | Route ID | Kind | Category | Access | Data Type |
|---|---|---|---|---|---|
| point.Name | point.Id | Value | point.Category ?? point.Area.ToString() | point.Access | point.ValueType ?? SourceValueType.Int32 |
| Direct Access | Direct Access | Value | System | Write | String |
Route Parameters: Direct Access
This route requires the following parameters when executing commands or writes.
| Parameter Name | Display Name | Type | Required |
|---|
4. Usage Examples
Scenario A: Reading/Monitoring Data
To monitor data from Modbus Server, add the corresponding Input Node in the Rule Editor and select the desired property from the catalog. Link its output to any logical comparison or directly to an Action Node.
Scenario B: Triggering Actions
If the plugin supports writable properties or actions, use an Action Node in the Rule Editor. Configure the Target property to point to the Modbus Server action, and supply any required parameters mapping from your rule's logic.