Difference between revisions of "Modbus TCP Client Error Counts"

From Control Solutions IoTServer Documentation
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
[[File:Modbus TCP client status error counts.jpg|850px]]
 
[[File:Modbus TCP client status error counts.jpg|850px]]
 +
* Click the Clear Counts to reset the counts to zero.
 +
* Click the Refresh button to update the counts.
  
 
This page shows an error summary on a device by device basis. There will be one line per each device configured for access by the Modbus TCP Client. If there is a non-zero error count for a device, you can begin to track down where this error is occurring by viewing the Read and Write Data pages for the Modbus TCP Client.
 
This page shows an error summary on a device by device basis. There will be one line per each device configured for access by the Modbus TCP Client. If there is a non-zero error count for a device, you can begin to track down where this error is occurring by viewing the Read and Write Data pages for the Modbus TCP Client.
  
Click the Clear Counts to reset the counts to zero. Click the Refresh button to update the counts.
+
Socket errors will be an error code reported by the system if nonzero. Refer to the '''[[Socket Errors]]''' list for these errors.

Latest revision as of 03:29, 21 May 2019

Modbus TCP client status error counts.jpg

  • Click the Clear Counts to reset the counts to zero.
  • Click the Refresh button to update the counts.

This page shows an error summary on a device by device basis. There will be one line per each device configured for access by the Modbus TCP Client. If there is a non-zero error count for a device, you can begin to track down where this error is occurring by viewing the Read and Write Data pages for the Modbus TCP Client.

Socket errors will be an error code reported by the system if nonzero. Refer to the Socket Errors list for these errors.