You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To check or not to check for errors ? then my advice is at the bottom of the page: Check for bus errors ?
It is possible to keep the last error in a variable. That can be used if something goes wrong.
It is also possible to increment an error count. That error count can be checked every few hours and if it was increased then the quality of the I2C bus has a problem. This is very useful for diagnostics. It could be displayed on a special diagnostics or service page.
It is possible to do a few retries when the I2C went wrong.
In my opinion this all could be useful, but not with the Arduino Wire library. The Arduino Wire library does not handle I2C bus problems very well itself.
You may remove the
while (Wire.available() < 14);
after the Wire.requestFrom().Explanation: Common-mistakes#1
The text was updated successfully, but these errors were encountered: