Examples using I2C should explain that all I2C devices on the board conflict

[marcmerlin]

Unfortunately they were not configured to use different addresses (although it seems possible with small solder points).
An obvious use of the kit is to read pressure or some other I2c value (like accelerometer), but that's not possible since they share I2C and conflict with the OLED. If you turn them on, the OLED stops working.
Not obvious at all for a beginner, documentation is needed.

[marqdevx]

Hey!
We are using u8x8 to save memory, if we use u8g2 we use more than 80% of the memory.

This kit is meant to use it with the content so maki the things simple was te main goal, but you are right that it has some graphic limitations, noted.

I will add some examples using the u8g2 library for advanced users that want to try more capabilities of the Hardware , thanks a lot for your feedback!!

Have a nice one.

[per1234]

@marqdevx I believe your reply was intended to be posted to the other issue: #8

Since this issue has not been addressed, I'll reopen.

[marcmerlin]

(Sorry, I replied on the wrong bug too, I moved that comment to the other bug)

[marcmerlin]

I tried to give a better combined example that exercises most sensors, but wasn't able to combined them all due to this problem. The partial example is here
#6

I'm pretty sure I can make it work by soldering address points on the sensors, but then I'd have code that only works on my board, so it's not useful as an example to your users.

[marqdevx]

@marqdevx I believe your reply was intended to be posted to the other issue: #8

Since this issue has not been addressed, I'll reopen.

Oops, my fault!

[marqdevx]

Hey @marcmerlin
Could you please run the i2c scanner individually for each sensor? and give me your i2c addresses.

I can run both at the same time.

[marcmerlin]

My bad, you are correct.

I2C device found at address 0x19  !
I2C device found at address 0x3C  !
I2C device found at address 0x77  !

Now I need to find out why initializing
//Accelerometer.begin();
or
//Pressure.begin();

stops the OLED from working.
It's been a while since I've worked with I2C, do the drivers auto-scan all addresses to find the right device, and maybe send wrong init messages to the OLED that mess it up?

[marcmerlin]

For what it's worth, running the I2C scanner first, also stops the OLED from working, but that might be a different issue.
Either way, it'd be great to have a generic example, like the one I submitted, that exercises everything, proves that it all works, and helps a novice user running all of them correctly?

[marqdevx]

I'll add an example
thanks for the feedback!! @marcmerlin

[noppatoppa]

An obvious use of the kit is to read pressure or some other I2c value (like accelerometer), but that's not possible since they share I2C and conflict with the OLED. If you turn them on, the OLED stops working.

Can confirm this: using air pressure sensor disables OLED.
Tested both with Arduino IDE and Web Editor with newest library versions.

[marqdevx]

Hello @marcmerlin @noppatoppa
First, thanks for the feedback
And second, could you please test this branch and let me know if now its working fine?
https://github.com/arduino-libraries/Arduino_SensorKit/tree/display_hw_i2c

I think it has been some update in the display library, cause the SW I2C for the display was fixing an issue that we had, but now the issue came back, and switching back to the HW I2C seems to fix it.

Let me know
Have a good one! :D