-
Notifications
You must be signed in to change notification settings - Fork 15
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
I2C not working correctly #6
Comments
Are you using the Arduino IDE? If so, which ATtiny85 core are you using? You say it's an ATtiny85 clone. Which one exactly? |
I'm not sure the Digispark supports I2C - search the web for information. I recommend using Spence Konde's ATTinyCore which does support I2C. |
Why don’t you try an ATtiny85 on a breadboard?
David
|
You have not disclosed your code. Maybe you did not included <Wire.h> before <TinyBME280.h>? |
Hi, I am also trying to use the TinyBME280 lib with a Digispark attiny85 board. It gives me accurate measurements for temperature and humidity but returns a very low value for pressure. Using Adafruit_BME280 lib on an arduino uno i get a value of 92239 while digispark give me 26797. Any ideas ? |
The Digispark causes a lot of compatibility problems. Try a standard ATtiny85. |
Unfortunately that is true. I am giving up on digispark. Thanks for your reply. |
I am using the Arduino 1.8.9 IDE on a ATTiny85 clone with a BME380. 10K pullups are on the I2C lines. An external battery assures that 5v is adequate.
I can compile properly. I can serial print to NotePad using keyboard.h. I can blink LEDs successfully.
What I can not do is successfully implement I2C. I do not know how to troubleshoot the problem.
If I use I2C scanner, the device is detected but I get back address 0x40 for a BME280. Clearly this is wrong. The address is 0x76.
If I try reading the BME280 (at any address), I get decimal 12378. Something is definitely wrong. I am very familiar with the ESP8266 family but I am too new with this device to work toward a solution by myself.
The text was updated successfully, but these errors were encountered: