Difference between revisions of "Modbus RTU Slave Error Counts"
Jump to navigation
Jump to search
Jimhogenson (talk | contribs) |
Jimhogenson (talk | contribs) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[File:Modbus RTU slave status page.jpg | + | [[File:Modbus RTU slave status page.jpg]] |
* Click the Clear Counts to reset the counts to zero. | * Click the Clear Counts to reset the counts to zero. | ||
* Click the Refresh button to update the counts. | * Click the Refresh button to update the counts. | ||
| − | The error counts illustrated on this page refer to errors | + | The error counts illustrated on this page refer to errors that occurred when remote clients or masters attempted to read/write registers in this IoTServer device. |
| + | |||
| + | * Total message count is the total number of messages that have been received by this server. | ||
| + | * Exception errors are errors in the request which have been reported back to the client/master. | ||
| + | * CoProc errors are internal errors in communication between the two processors. | ||
Latest revision as of 17:13, 16 May 2019
- Click the Clear Counts to reset the counts to zero.
- Click the Refresh button to update the counts.
The error counts illustrated on this page refer to errors that occurred when remote clients or masters attempted to read/write registers in this IoTServer device.
- Total message count is the total number of messages that have been received by this server.
- Exception errors are errors in the request which have been reported back to the client/master.
- CoProc errors are internal errors in communication between the two processors.
