-
Notifications
You must be signed in to change notification settings - Fork 47
DOCS-4017: Add info for "Frame read failed: Too many retries" error #4337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCS-4017: Add info for "Frame read failed: Too many retries" error #4337
Conversation
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
👋 Thanks for contributing! A reviewer will look at it on the next working day! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me but Rand will be better equipped to review accuracy
{{% expand "Frame read failed: Too many retries" %}} | ||
|
||
**Description:** This error typically occurs with IR camera modules and similar specialized cameras. | ||
It happens when the camera module is still initializing or calibrating itself, but `viam-server` is already attempting to read frames from it. | ||
This can also be caused by I2C communication issues between the board and the camera module, particularly on Raspberry Pi 5 systems. | ||
|
||
**Solution:** Try one of the following approaches: | ||
|
||
1. **Reduce the refresh rate for I2C cameras**: | ||
For I2C-based cameras (like some IR modules), try setting the refresh rate to a lower value (for example, 2Hz instead of 4Hz). | ||
This can help with I2C bus timing issues, especially on Raspberry Pi 5 systems. | ||
|
||
1. **Check physical connections**: | ||
|
||
- Ensure the camera module is properly connected. | ||
- For I2C cameras, verify that the SCK (clock) pin is properly connected and not shorted to ground or power. | ||
If the pin has been shorted, this can permanently damage the hardware. | ||
|
||
If these steps don't resolve the issue, check your machine logs for additional error messages that might provide more specific information about the problem. | ||
|
||
{{% /expand%}} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This error might not be generic to all i2c IR cameras - we only have the one module using adafruit's APIs.
It's also mine, not viam official. https://github.com/randhid/waveshare-thermal. Do you want me to just put this guide in that readme?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh okay yeah that sounds good 💡 I will close this PR
@randhid to pull this into relevant readme instead; closing |
Staging link: https://deploy-preview-4337--viam-docs.netlify.app/operate/reference/components/camera/#frame-read-failed-too-many-retries
Add information about the "Frame read failed: Too many retries" error that occurs with IR cameras, including causes and solutions based on the Slack conversation. This will help users troubleshoot this specific camera error.
Trigger Events