RTU client server communication: Difference between revisions

From Phobos Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 66: Line 66:
</pre>
</pre>


== Server log when client reconnects after sudden disconnet ==
== Server log when client reconnects after sudden disconnect ==
<pre>
<pre>
2017-09-01 15:56:49.675 [TRACE] Gateway.104port.port - Clear communication buffers
2017-09-01 15:56:49.675 [TRACE] Gateway.104port.port - Clear communication buffers

Revision as of 13:11, 25 September 2017

MarkTomm 25. september 2017, kell 16:05 (EEST)

The IEC 104 TCP was documented on 25.09.2017 when there was an issue with connection. GWM iec 104 server closed the connection every ~20 seconds.

IEC 104 TCP

Client log when server disconnects

2017-09-25 15:48:44.975 [INFO] Gateway.Port16.port - Close connection, connection reset by peer
2017-09-25 15:48:44.977 [DEBUG] Gateway.Port16.link - CommunicationBad
2017-09-25 15:48:44.977 [ERROR] Gateway.Port16.port - Request disconnect, no connection
2017-09-25 15:48:44.977 [ERROR] Gateway.Port16 - Timeout, suppressing following timeout messages!
2017-09-25 15:48:44.997 [DEBUG] Gateway.Port16 - StatusDi: no connection
2017-09-25 15:48:45.000 [ERROR] Gateway.Port16 - Remove from polling
2017-09-25 15:48:45.000 [INFO] Gateway.Port16 - Reset communication

Client log when it connects

2017-09-25 15:48:45.980 [INFO] Gateway.Port16.port - Connecting to 10.0.0.173:2404
2017-09-25 15:48:45.982 [INFO] Gateway.Port16.port - Connected to 10.0.0.173:2404
2017-09-25 15:48:45.982 [TRACE] Gateway.Port16.port - Clear communication buffers
2017-09-25 15:48:45.982 [DEBUG] Gateway.Port16 - Port open!
2017-09-25 15:48:45.982 [DEBUG] Gateway.Port16 - Retry/Establish communication
2017-09-25 15:48:45.983 [INFO] Gateway.Port16 - Enable polling
2017-09-25 15:48:45.983 [INFO] Gateway.Port16 - Reset communication done
2017-09-25 15:48:45.983 [TRACE] Gateway.Port16.port.link - Port connected
2017-09-25 15:48:46.003 [DEBUG] Gateway.Port16.port.write.link - UFormat: STARTDT_ACT
2017-09-25 15:48:46.009 [TRACE] Gateway.Port16.port.write -  68 04 07 00 00 00
2017-09-25 15:48:46.011 [TRACE] Gateway.Port16.port.read -  68 04 0B 00 00 00
2017-09-25 15:48:46.012 [DEBUG] Gateway.Port16.port.read.link - UFormat: STARTDT_CON
2017-09-25 15:48:46.012 [DEBUG] Gateway.Port16.link - CommunicationOk
2017-09-25 15:48:46.012 [TRACE] Gateway.Port16 - Status DI needs updating!
2017-09-25 15:48:46.012 [DEBUG] Gateway.Port16 - StatusDi: connected

Server log when it disconnects

2017-09-01 15:56:48.669 [DEBUG] Gateway.104port.link - CommunicationBad
2017-09-01 15:56:48.669 [ERROR] Gateway.104port.port - Request disconnect, subdevice removed from polling
2017-09-01 15:56:48.670 [INFO] Gateway.104port.port - Close connection, Force disconnect
2017-09-01 15:56:48.670 [ERROR] Gateway.104port - Timeout, suppressing following timeout messages!
2017-09-01 15:56:49.001 [DEBUG] Gateway.104port.db - Time cn (11) event: 57409 time: 2017-Sep-01 15:56:49.000063, buffered

Server log when client connects after reset

2017-09-01 16:09:40.069 [TRACE] Gateway.104port.port - Clear communication buffers
2017-09-01 16:09:40.070 [INFO] Gateway.104port.port - Incoming connection from 10.0.0.231 established.
2017-09-01 16:09:40.070 [TRACE] Gateway.104port.port.link - Port connected
2017-09-01 16:09:40.070 [DEBUG] Gateway.104port - Port open!
2017-09-01 16:09:40.070 [DEBUG] Gateway.104port - Retry/Establish communication
2017-09-01 16:09:40.070 [INFO] Gateway.104port - Enable polling
2017-09-01 16:09:40.070 [INFO] Gateway.104port - Reset communication
2017-09-01 16:09:40.071 [INFO] Gateway.104port - Reset communication done
2017-09-01 16:09:40.097 [TRACE] Gateway.104port.port.read -  68 04 07 00 00 00
2017-09-01 16:09:40.097 [DEBUG] Gateway.104port.port.read.link - UFormat: STARTDT_ACT
2017-09-01 16:09:40.098 [TRACE] Gateway.104port.link - Received U format message with "Start Data Transfer Activation" from master. Reissue "Port connected" to port buffer. This will clear buffers counters and timers.
2017-09-01 16:09:40.098 [TRACE] Gateway.104port.port.link - Port connected
2017-09-01 16:09:40.098 [DEBUG] Gateway.104port.port.write.link - UFormat: STARTDT_CON
2017-09-01 16:09:40.098 [DEBUG] Gateway.104port.link - CommunicationOk
2017-09-01 16:09:40.098 [DEBUG] Gateway.104port - StatusDi: connected
2017-09-01 16:09:40.098 [INFO] Gateway.104port - Connected
2017-09-01 16:09:40.098 [INFO] Gateway.104port - Refresh all values
2017-09-01 16:11:46.093 [TRACE] Gateway.104port.port.write -  68 04 0B 00 00 00

Server log when client reconnects after sudden disconnect

2017-09-01 15:56:49.675 [TRACE] Gateway.104port.port - Clear communication buffers
2017-09-01 15:56:49.676 [DEBUG] Gateway.104port - Port open!
2017-09-01 15:56:49.676 [DEBUG] Gateway.104port - Retry/Establish communication
2017-09-01 15:56:49.676 [INFO] Gateway.104port - Enable polling
2017-09-01 15:56:49.676 [INFO] Gateway.104port - Reset communication
2017-09-01 15:56:49.676 [INFO] Gateway.104port - Reset communication done
2017-09-01 15:56:49.676 [TRACE] Gateway.104port.port.link - Port connected
2017-09-01 15:56:49.677 [INFO] Gateway.104port.port - Incoming connection from 10.0.0.231 established.
2017-09-01 15:56:49.703 [TRACE] Gateway.104port.port.read -  68 04 07 00 00 00
2017-09-01 15:56:49.703 [DEBUG] Gateway.104port.port.read.link - UFormat: STARTDT_ACT
2017-09-01 15:56:49.703 [TRACE] Gateway.104port.link - Received U format message with "Start Data Transfer Activation" from master. Reissue "Port connected" to port buffer. This will clear buffers counters and timers.
2017-09-01 15:56:49.703 [TRACE] Gateway.104port.port.link - Port connected
2017-09-01 15:56:49.703 [DEBUG] Gateway.104port.port.write.link - UFormat: STARTDT_CON
2017-09-01 15:56:49.703 [DEBUG] Gateway.104port.link - CommunicationOk
2017-09-01 15:56:49.704 [DEBUG] Gateway.104port - StatusDi: connected
2017-09-01 15:56:49.704 [TRACE] Gateway.104port.port.write -  68 04 0B 00 00 00
Retrieved from "https://phobos.martem.ee/w/index.php?title=RTU_client_server_communication&oldid=2144"