Remote Devices via RSLinx Gateway diagnostics
Diagnostic counters are available by right-clicking the processor station in the RSWho window. RSLinx Classic Gateway diagnostics are found under the General, Performance, Connection Event Log, and Active Connections tabs in the tabbed dialog. The Configuration tab contains a checkbox that allows you to enable the RSLinx Classic Gateway. When you choose to enable the RSLinx Classic Gateway, the changes will not take effect until you shut down and then restart RSLinx Classic.
Driver diagnostics are modeless; therefore, they can remain on the desktop if you minimize RSLinx Classic. The last four counters
–
related to number of connections –
are not
reset by the Reset Counters operation on the Station Diagnostics window. The following is the list of diagnostic counters shown 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 the A-B Ethernet driver. |
Replies Received | Total replies received by this driver. This counter increments when the A-B Ethernet 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 Ethernet station has not yet responded, or the Ethernet station is not powered up, not connected to the network, or not functioning; therefore the connection from RSLinx Classic to the Ethernet 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 | Total number of packets sent on CIP connections to a 1756-ENET module. Should be zero if the server is not a 1756-ENET. |
Broadcast Received | Total number of packets received on CIP connections from a 1756-ENET module. Should be zero if the server is not a 1756-ENET. |
Communication Errors | Total commands which could not be sent to the Ethernet station or to which the Ethernet 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 PLC because all DDE hot links to that PLC have closed, RSLinx Classic cancels any DDE poll packets to that PLC 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 | The number of TCP/IP connections which are currently open to Ethernet devices. A connection is opened for an Ethernet station the first time RSLinx Classic sends a command to the device. The connection remains open until it fails, or the Ethernet device closes it, or the driver's Inactivity Timeout expires with no more commands being sent to the Ethernet station. |
Total connections initiated | The total number of TCP/IP connections which this driver has ever 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 | The total number of inbound TCP/IP connections from other Ethernet stations to RSLinx Classic. These are used for sending unsolicited commands to RSLinx Classic. If no Ethernet station is currently sending unsolicited commands to RSLinx Classic, this is zero. |
Total connections accepted | The total number of TCP/IP connections which other Ethernet stations have ever opened to RSLinx Classic, since RSLinx Classic was started – even if the connections are not open now. |
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. |
Connection Event Log Tab | Contains a log of the most recent 255 connection events for this driver. A
connection event is any error that causes RSLinx Classic to fail to connect to the
PLC, or causes an existing TCP connection to close. If communication to a
particular PLC is not working, check here for error descriptions. |
Time | Time the event occurred. |
Node | The IP address to which the connection was being made. |
Error Description | A description of the event which occurred. |
Active Connections Tab | A display of all TCP 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 (0-63 decimal) for this connection. |
Host Name | The DNS 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. |
Provide Feedback