![]() If I did i2c.scan() before I polled the sensors, I was most likely to get good data back. I don't have a working library for the light sensor, but left it plugged in so I could push something out to upgrade capability once I figured it out. One is an si7021 temp/RH/Dewpoint sensor and the other is a TSL2961 light sensor. Each is on a short 4-conductor, 24awg ribbon cable, maybe 6-9 inches in length. To my knowledge, there are no internal pull-ups active on any devices on the bus.I have two devices hooked to I2C on my LoPy4 and was having some odd issues. This "voltage bump" happens on both the SCL and SDA lines. Is this is an issue with the device, or is this maybe an issue with my measurement setup?Įdit: Here is the schematic for the ICM-20689. On all subsequent data packages, the voltage stays at 3.7V. My oscilloscope is not the greatest, but the probe is in 10x mode, and I am using the trigger to capture the data on the first packet of data sent. When the master wakes up the device and starts receiving data, the voltage jumps to 3.7V. ![]() Before the master starts talking with the ICM-20689, the bus line is at a voltage of 3.3V. I wanted to look at the bus voltages with an oscilloscope to make sure that everything looked fine, and I noticed something a little odd. I have been able to communicate with the device just fine and get good data. The master device is running at 5V, but only needs 60% (3V) to read a voltage high. The ICM-20689 is running on 3.3V with 3.3V on the VDDIO pin and 10k pullup resistors on the I2C bus. Link to previous issue.Ī little background on my setup. I have redesigned one of my boards to the ICM-20689 ( datasheet) instead of the ICM-20789 because of a voltage issue that I previously had.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |