You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Neil, I really like your simple to use Library. I am trying to send data from an Air quality sensor (I2C), then plot this data on an oled screen and send it via BLE to a mobile application. I managed to plott the data on Oled only. However, when I try to send the data via BLE, the I2C bus collapses after some time (random).
Worth mentioning that I am using the server example (generates services and char's) which has all the code inside the condition (BLE deviceConnected), ALSO, the I2C device data code is only executed when the data is available. So, I have two separate if conditions, one for data availability and one for the connectivity.
What happens (most of the time) when I run the code is data is plotted on the Oled screen each time data is available (BLE is not connected). When I connect to my app, and after some time (random), no new data is fetched from I2C and even data coming from analog is not plotted into Oled anymore but only sent to the app. So, everything carries on working including BLE, the only thing collapses is I2C bus.
My question: Do you think that this problem lies on the BLE side (Has some links with I2C from internally or error when conflicting commands at sometimes) or on the I2C device side.
I appreciate your help and time. Thanks!
The text was updated successfully, but these errors were encountered:
Hi Neil, I really like your simple to use Library. I am trying to send data from an Air quality sensor (I2C), then plot this data on an oled screen and send it via BLE to a mobile application. I managed to plott the data on Oled only. However, when I try to send the data via BLE, the I2C bus collapses after some time (random).
Worth mentioning that I am using the server example (generates services and char's) which has all the code inside the condition (BLE deviceConnected), ALSO, the I2C device data code is only executed when the data is available. So, I have two separate if conditions, one for data availability and one for the connectivity.
What happens (most of the time) when I run the code is data is plotted on the Oled screen each time data is available (BLE is not connected). When I connect to my app, and after some time (random), no new data is fetched from I2C and even data coming from analog is not plotted into Oled anymore but only sent to the app. So, everything carries on working including BLE, the only thing collapses is I2C bus.
My question: Do you think that this problem lies on the BLE side (Has some links with I2C from internally or error when conflicting commands at sometimes) or on the I2C device side.
I appreciate your help and time. Thanks!
The text was updated successfully, but these errors were encountered: