Skip to content

Commit 6bbb6c3

Browse files
authored
Merge pull request #527 from hxy7yx/v2.10
modbus configuration: device degradation
2 parents 6d18fa1 + 778a2ac commit 6bbb6c3

File tree

4 files changed

+44
-0
lines changed

4 files changed

+44
-0
lines changed

en_US/configuration/south-devices/modbus-rtu/modbus-rtu.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,17 @@ After clicking **Create**, you will be redirected to the **Device Configuration*
3232
| **Connection Mode** | Only for the **Ethernet** mode, you can choose Neuron as the TCP client or server. |
3333
| **IP Address** | Only for the **Ethernet** mode, the IP address of the device when using TCP connection with Neuron as the client, or the IP address of Neuron when using TCP connection with Neuron as the server. The default value is 0.0.0.0. |
3434
| **Port** | Only for the **Ethernet** mode, the port number of the device when using TCP connection with Neuron as the client, or the port number of Neuron when using TCP connection with Neuron as the server. |
35+
| **Device Degradation** | Enable or disable device degradation mechanism. |
36+
| **Failure Threshold for Degradation** | The number of consecutive failure cycles required to trigger device degradation. |
37+
| **Recovery Time After Degradation** | The time in seconds after which the device recovers from degradation. |
38+
39+
::: tip
40+
The above configuration can meet the individualized needs of the device:<br>
41+
42+
1. Retry requests are considered as the same request, i.e., a successful retry is regarded as a successful request.<br>
43+
2. In the same read cycle, if a certain tag under a slave id does not receive a response, requests for other tags under the same slave id in that cycle will be skipped.<br>
44+
3. The device degradation is triggered when a certain tag under a slave id fails to respond for multiple consecutive cycles (or can be configured to trigger after just one failed cycle). Once triggered, all requests for that slave will be stopped for the configured period.
45+
:::
3546

3647
## Configure Data Groups and Tags
3748

en_US/configuration/south-devices/modbus-tcp/modbus-tcp.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,17 @@ After clicking **Create**, you will be redirected to the **Device Configuration*
3232
| **Port** | The port number of the device when using TCP connection with Neuron as the client, or the port number of Neuron when using TCP connection with Neuron as the server.|
3333
| **Connection Timeout** | The time the system waits for a device to respond to a command. |
3434
| **Check Header** | Choose whether to verify the message header. After selecting True, when encountering packet header errors, the neuron and device will reconnect. |
35+
| **Device Degradation** | Enable or disable device degradation mechanism. |
36+
| **Failure Threshold for Degradation** | The number of consecutive failure cycles required to trigger device degradation. |
37+
| **Recovery Time After Degradation** | The time in seconds after which the device recovers from degradation. |
38+
39+
::: tip
40+
The above configuration can meet the individualized needs of the device:<br>
41+
42+
1. Retry requests are considered as the same request, i.e., a successful retry is regarded as a successful request.<br>
43+
2. In the same read cycle, if a certain tag under a slave id does not receive a response, requests for other tags under the same slave id in that cycle will be skipped.<br>
44+
3. The device degradation is triggered when a certain tag under a slave id fails to respond for multiple consecutive cycles (or can be configured to trigger after just one failed cycle). Once triggered, all requests for that slave will be stopped for the configured period.
45+
:::
3546

3647
## Configure Data Groups and Tags
3748

zh_CN/configuration/south-devices/modbus-rtu/modbus-rtu.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,17 @@ Modbus RTU 协议采用二进制编码,可以在 RS-232、RS-485 或其他串
2929
| **连接模式** | Ethernet 模式下,可以选择 Neuron 作为 TCP 的客户端或是服务端。 |
3030
| **IP 地址** | Ethernet 模式下,设备的 IP 地址(Neuron 作为客户端);或是 Neuron 本机的 IP 地址(Neuron 作为服务端),默认可填 0.0.0.0。 |
3131
| **端口** | Ethernet 模式下,设备的端口号(Neuron 作为客户端);或是 Neuron 本机的端口(Neuron 作为服务端)。 |
32+
| **设备降级** | 启用或禁用设备降级机制。 |
33+
| **降级失败阈值** | 触发设备降级所需的连续失败周期数。 |
34+
| **降级恢复时间** | 设备从降级中恢复所需的时间(单位:秒)。 |
35+
36+
::: tip
37+
上述配置可以满足设备的个性化需求:<br>
38+
39+
1. 重试请求视为同一次请求,即重试成功视为该请求成功。<br>
40+
2. 在同一读取周期内,如果某个站点号的某个点位未收到回复,则跳过该周期内同站点号下其他点位的请求。<br>
41+
3. 设备降级触发条件为连续多个周期某站点号的点位未收到设备回复(也可以配置为一个周期失败即触发)。一旦触发,在配置的时间段内,所有该站点的请求将停止发送。
42+
:::
3243

3344
## 设置组和点位
3445

zh_CN/configuration/south-devices/modbus-tcp/modbus-tcp.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,17 @@ Neuron 的 Modbus TCP 插件除了支持以 TCP 客户端的模式主动接入
2929
| **端口号** | TCP 连接时,设备的端口号(Neuron 作为客户端);或是 Neuron 本机的端口(Neuron 作为服务端)。|
3030
| **连接超时时间** | 等待设备返回指令响应的时间。 |
3131
| **校验报文头** | 选择是否对报文头进行校验。选择校验后,遇到报文头错误时 neuron 与设备会重新连接。 |
32+
| **设备降级** | 启用或禁用设备降级机制。 |
33+
| **降级失败阈值** | 触发设备降级所需的连续失败周期数。 |
34+
| **降级恢复时间** | 设备从降级中恢复所需的时间(单位:秒)。 |
35+
36+
::: tip
37+
上述配置可以满足设备的个性化需求:<br>
38+
39+
1. 重试请求视为同一次请求,即重试成功视为该请求成功。<br>
40+
2. 在同一读取周期内,如果某个站点号的某个点位未收到回复,则跳过该周期内同站点号下其他点位的请求。<br>
41+
3. 设备降级触发条件为连续多个周期某站点号的点位未收到设备回复(也可以配置为一个周期失败即触发)。一旦触发,在配置的时间段内,所有该站点的请求将停止发送。
42+
:::
3243

3344
## 设置组和点位
3445

0 commit comments

Comments
 (0)