I had made a change in release v6.0 (maybe documented eleswhere, maybe not) that after 6 errors reported from the interface to RoboClaw or the application read an out of range value from the quadrature registers, I would stop communicating with it. It proved unworkable. Over time errors would accumulate and the communication to RoboClaw would stop. A more appropriate measure would be errors per 15 minute interval or some such a scheme. Currently, if an out of reange value is read from the quad registers, it is thrown away but its value is printed in the log. No action is taken on the error count.
I had made a change in release v6.0 (maybe documented eleswhere, maybe not) that after 6 errors reported from the interface to RoboClaw or the application read an out of range value from the quadrature registers, I would stop communicating with it. It proved unworkable. Over time errors would accumulate and the communication to RoboClaw would stop. A more appropriate measure would be errors per 15 minute interval or some such a scheme. Currently, if an out of reange value is read from the quad registers, it is thrown away but its value is printed in the log. No action is taken on the error count.