GASSONIC OBSERVER-i
69
6.7.30. Cal Abort (1FH)
Writing to the calibrate abort register will abort calibration and return the Gassonic Observer-i to
normal.
6.7.31. Comm 1 Total Illegal number of registers Errors (20H)
A read indicates the total illegal number of registers errors on the Comm 1 Modbus. The maximum
count is 65535 and then the counter rolls over to zero and begins counting again.
6.7.32. Comm 1 Bus Activity Rate % (21H)
A read indicates the Comm 1 Bus Activity Rate in percent of this Slave's addressed node versus other
addressed nodes. Range of this value is in hex (0-64), which translates to decimal (0-100%).
6.7.33. Comm 1 Function Code Errors (22H)
A read indicates the number of Comm Function Code Errors that occurred in the slave device. The
maximum count is 65535 and then the counter rolls over to zero and begins counting again.
6.7.34. Comm 1 Starting Address Errors (23H)
A read indicates the number of Comm 1 Starting Address Errors that occurred in the slave device. The
maximum count is 65535 and then the counter rolls over to zero and begins counting again.
6.7.35. Comm 1 Total Receive Errors (24H)
A read indicates the total Modbus Comm 1 Only Receive Errors that occurred in the slave device.
These are address, function, etc. type of errors. The maximum count is 65535 and then the counter
rolls over to zero and begins counting again.
6.7.36. RXD CRC Errors (25h)
A read indicates the number of RXD CRC Errors that occurred in the slave device. The maximum
count is 65535 and then the counter rolls over to zero and begins counting again.
6.7.37. RXD CRC Errors (26h)
Same as (25h).
6.7.38. Comm 1 Parity Errors (27H)
A read indicates the number of Comm 1 Only Parity Errors that occurred in the slave device. The
maximum count is 65535 and then the counter rolls over to zero and begins counting again.
6.7.39. Comm 1 Overrun Errors (28H)
A read indicates the number of Comm 1 Overrun Errors that occurred in the slave device. The
maximum count is 65535 and then the counter rolls over to zero and begins counting again.
NOTE
:
An overrun error occurs when the next received byte of data tries to overwrite an existing
received data byte, which has not been processed. Therefore, the next received byte of data is
lost. This can be controlled by implementing the proper DCS or PLC Error Handling Timing
Setting (ex. Reply Timeout Setting, Delay Time, and Number of Retries) and proper Baud Rate
Setting.