TCP/UDP RT TcCom diagnostics
The TcCOM object TCP/UDP RT represents the coupling of customer project with the hardware.
In addition to parameters, it therefore also contains diagnostic information, which is described here. Once Engineering can communicate with the target system and the program runs smoothly, various information is provided via the received and sent packets:
Name | Value | Description |
|---|---|---|
IpStackDiagnosis | … | Diagnostic information of the IP stack |
.ip.nSendCnt | 18 | Number of IP packets sent |
.ip.nSendFailCnt | 0 | Number of IP packets not sent |
.ip.nRecvCnt | 20 | Number of packets received |
.ip.nRecvFailCnt | 0 | Number of packets not received |
.arpRequest.nSendCnt | 0 | Arp-Requests: Number of packets sent |
.arpRequest.nSendFailCnt | 0 | Arp-Requests: Number of packets not sent |
.arpRequest.nRecvCnt | 12 | Arp-Requests: Number of packets received |
.arpRequest.nRecvFailCnt | 0 | Arp-Requests: Number of packets not received |
.arpReply.nSendCnt | 12 | Arp-Reply: Number of packets sent |
.arpReply.nSendFailCnt | 0 | Arp-Reply: Number of packets not sent |
.arpReply.nRecvCnt | 0 | Arp-Reply: Number of packets received |
.arpReply.nRecvFailCnt | 0 | Arp-Reply: Number of packets not received |
.pingRequest.nSendCnt | 0 | Ping-Request: Number of packets sent |
.pingRequest.nSendFailCnt | 0 | Ping-Request: Number of packets not sent |
.pingRequest.nRecvCnt | 0 | Ping-Request: Number of packets received |
.pingRequest.nRecvFailCnt | 0 | Ping-Request: Number of packets not received |
.pingReply.nSendCnt | 0 | Ping-Reply: Number of packets sent |
.pingReply.nSendFailCnt | 0 | Ping-Reply: Number of packets not sent |
.pingReply.nRecvCnt | 0 | Ping-Reply: Number of packets received |
.pingReply.nRecvFailCnt | 0 | Ping-Reply: Number of packets not received |
.nLinkStatusChangedCnt | 1 | Number of link changes |
.nAllocFailCnt | 0 | Number of failed allocations |
.nArpTimeoutFrames | 0 | Number of arp frames in the timeout |
.nDroppedFrames | 0 | Number of discarded packages |