1784-PCIC(S) diagnostics
Diagnostic counters are available by right-clicking the processor station in the
RSWho
window. Driver diagnostics are found under the General
, Performance
, and Network Interface
tabs in the tabbed
dialog box. Driver diagnostics are modeless, and can remain on the desktop if you minimize RSLinx Classic. The following is the list of diagnostic counters and the definition of each.General Tab | |
|---|---|
Commands Sent | Total commands sent to this driver by RSLinx Classic. This counter increments when RSLinx Classic attempts to read or write any to any station via this driver. |
Replies Received | Total replies received by this driver. This counter increments when the driver receives a message which looks like a reply. In normal operation, this counter keeps pace with the Commands Sent counter. It cannot be greater than Commands Sent. If it is less, then either some commands are still pending and the station has not yet responded, or the station is not powered up, not connected to the network, or not functioning; therefore the connection from RSLinx Classic to the station is not available. These commands eventually time out and are counted as Communication Errors. |
Unsol. Received | Total unsolicited messages received by this driver. This counter increments when another station on the network attempts to read or write data from RSLinx Classic. |
Unsol. Replied | Total replies generated to unsolicited messages by this driver. This counter increments when RSLinx Classic responds to an unsolicited command. It normally keeps pace with Unsol. Received. If it is less, it means some unsolicited commands have been dropped or ignored by the application that was supposed to answer them (using the RSLinx Classic C API). |
Broadcast Sent | Should be zero for this driver. |
Broadcast Received | Should be zero for this driver. |
Communication Errors | Total commands that could not be sent to the station or to which the station never replied, for any reason. |
Commands canceled | Total commands canceled before a response was received. RSLinx Classic cancels a command when it times out without a response, or when the application that sent the command is stopped. For example, when RSLinx Classic stops polling a processor because all DDE hot links to that processor have closed, RSLinx Classic cancels any poll packets to that processor for which no response was received. |
Commands timed out | Total commands for which no response was received before the specified timeout period. RSLinx Classic attempts to cancel the commands when they time out, and the Commands Canceled counter value is at least as large as the Commands timed out counter value. |
Connections open | Number of connections currently open to 1770-KFD devices. A connection is opened for a station the first time RSLinx Classic sends a command to the device. The connection remains open until it fails, or the device closes it, or the driver's Inactivity Timeout expires with no more commands being sent to the station. |
Total connections initiated | Total number of connections this driver opened since it was started even if those connections are not open now. If this number goes up rapidly, but Connections Open is small, it suggests that one or more connections is failing and being retried repeatedly. |
Server connections open | Total number of inbound connections from other 1770-KFD stations to RSLinx Classic. These are used for sending unsolicited commands to RSLinx Classic. If no 1770-KFD station is currently sending unsolicited commands to RSLinx Classic, this is zero. |
Total connections accepted | Total number of TCP/IP connections other 1770-KFD stations opened to RSLinx Classic, since RSLinx Classic was started, even if the connections are not open now. |
Total Packets Sent | The total of local solicited packets sent and remote solicited packets sent. |
Total Packets Received | Total packets received to both local and remote solicited packets sent. This number should equal total solicited packets sent, but lags behind by a few packets because replies are not back yet. |
Performance Tab | |
|---|---|
Sent packets/second | Total packets sent (solicited and unsolicited) per second by user-mode driver. |
Received packets/second | Total packets received (solicited and unsolicited) per second by user-mode driver. |
Active Connections Tab | A display of all connections the driver currently has open; updated automatically every two seconds. |
Node | The IP address to which the TCP connection is made. |
Station | The mapped station number for this connection. |
Host Name | The host name corresponding to the IP address. If no host name is associated with this IP address, the IP address displays here instead. |
Bytes sent | Number of bytes RSLinx Classic sent on this connection. |
Bytes received | Number of bytes RSLinx Classic received on this connection. |
Event Log Tab | Contains a log of the most recent connection events for this driver. A connection event is any error that causes RSLinx Classic to fail to connect to the processor, or causes an existing connection to close. If communication to a particular processor are not working, check here for error descriptions. |
Time | Time the event occurred. |
Object | IP address where the even occurred. |
Event Description | A description of the event which occurred. |
Provide Feedback