rtcollins14
New member
Sorry that I am unable to post code, I just can't find enough information to be able to understand the current issue. I am using a Teensy 3.2.
I am calling for an interrupt ever 500ms to modify an LED array. in between the modifications, I am reading 30 sensors via I2C using the Wire library. The sensors read perfectly when the interrupt is off, but the clock line is pulled high and the data line is pulled low after a few seconds when the interrupt is enabled.
Based on what I saw on the o-scope when reading data, it looks like the data drops out mid-read of the sensor due to the interrupt being triggered.
I read that the Teensy 2.0 uses the Wire library as an interrupt, while the 3.0+ do not; is that correct? If that's the case, then I can see why the LED updates would happen mid-read. If there is any documentation regarding the Wire library pertaining to the Teensy 3.2, I would love to read through that. Also, I did try the i2c_t3 library and got the same results.
Thank you
I am calling for an interrupt ever 500ms to modify an LED array. in between the modifications, I am reading 30 sensors via I2C using the Wire library. The sensors read perfectly when the interrupt is off, but the clock line is pulled high and the data line is pulled low after a few seconds when the interrupt is enabled.
Based on what I saw on the o-scope when reading data, it looks like the data drops out mid-read of the sensor due to the interrupt being triggered.
I read that the Teensy 2.0 uses the Wire library as an interrupt, while the 3.0+ do not; is that correct? If that's the case, then I can see why the LED updates would happen mid-read. If there is any documentation regarding the Wire library pertaining to the Teensy 3.2, I would love to read through that. Also, I did try the i2c_t3 library and got the same results.
Thank you