-
Notifications
You must be signed in to change notification settings - Fork 20
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
I'm getting a ReadTimeoutError on my sensor #2
Comments
It looks like some of the wisdom for the Enviro+ repository hasn't distilled down to here- chiefly that the PMS5003 wont work unless the Pi's UART is switched over to a full hardware UART instead of the "miniUART" since the miniUART is- even at 9600 baud- apparently unstable. Try adding: If you're missing the
I think this needs to be better documented here. |
I'm going off of memory, which I'll double check when I get home tonight.
I do remember chcking /boot/config.txt manually to see if this was there.
|
Checking back. The raspi-config when I select Interface Options -> Serial, it asks me if I want "ARM I2C Interface to be Enabled" and I've tried both Yes/No and neither worked for me. |
You want the ARM I2C Interface to be Enabled, and the Serial Terminal to be disabled. Other people encountering this issue have also suggested reseating the connector for the PMS5003, since it could be a good old-fashioned wiring problem. |
I stumbled upon this and it took me 30 minutes to realize I actually need the external hardware sensor and it's not embedded in the hat board. Silly me! |
Easy mistake to make! And useful to know- since I wouldn't otherwise have thought of asking "do you have a PMS5003 sensor connected at all?" Thank you! |
I'm using this with the enviro+, but I keep getting read error.
/dev/ttyAMA0 exists, but I'm not sure if it's setup properly, since the install script in the enviro+ library had several errors, and did not install everything properly.
I'm using Ubuntu-Mate 18.04.2 (for a Raspberry Pi ARMv8 64-bit system) on a Raspberry Pi 3 B
The text was updated successfully, but these errors were encountered: