Introduction
The BMENOR2200H module communicates with the other parties based on TCP/IP. The protocol is DNP3 or IEC104, and the other parties could be SCADA, RTU or other controllers. The network connection is various and combined with lots of switches/routers and other network devices.
In some abnormal cases (for example, the ethernet cable between remote device and switch is broken), the communication may be stopped due to the lost heartbeat packet from partner device, but the link status is still working well. In these cases, it needs some time to retry and timeout finally.
BMENOR2200H module provides a new Device DDT to allow manually reset communication for a quick recovery.
Reset RTU Communication by Variables
The TCP communication or protocol can be reset on the Device DDT.
In the Project Browser, expand the .
Expand the "CONN” parameters to see the variable RESET_TCP:
Name: RESET_TCP
Type: WORD
W: writable
Variable Name |
Value |
Description |
|---|---|---|
| RESET_TCP |
0 |
0 is the initial value and it means no command. |
Change value to 1 |
If the value is changed to 1, the sever TCP channel and the client will be reset, which means that the TCP connection will close and reopen. There will be no impact on the protocol and events. |
|
Change value to 2 |
If the value is changed to 2, the client TCP channel and the sever will be reset, which means that the TCP connection will close and reopen. There will be no impact on the protocol and events. |
|
Change value to 3 |
If the value is changed to 3, the protocol will be rest.
The reset protocol has two functions:
|