Difference between revisions of "Modbus RTU Slave Error Counts"
Jump to navigation
Jump to search
Jimhogenson (talk | contribs) |
Jimhogenson (talk | contribs) |
||
Line 3: | Line 3: | ||
* 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 detected. | ||
+ | * Exception errors are errors in the request which have been reported back to the client/master. | ||
+ | * CRC errors are transmission errors most often due to wiring issues. | ||
+ | * CoProc errors are internal errors in communication between the two processors. |
Revision as of 23:05, 2 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 detected.
- Exception errors are errors in the request which have been reported back to the client/master.
- CRC errors are transmission errors most often due to wiring issues.
- CoProc errors are internal errors in communication between the two processors.