-
Notifications
You must be signed in to change notification settings - Fork 19
New combined demo showing most non I2C input sensors. #6
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
Conversation
It'd be great to query I2C too, but those sensors unfortunately are not setup to use a different I2C address and conflict with one another unless you put some solder bridges to change the address
I unfortunately wasted 1H trying to use the oled due to this example. Display lines need to be 9, 18, 27, 36, 45, 54 Using 33 is not good, it's an incorrect value that ends up in the wrong place, and gives the impression that you can give any Y coordinate, when in fact you cannot. If you don't, text gets overlayed on top of other text, even though it shouldn't according to Y See arduino-libraries#6 for an example.
Are you using the version 1.0.5? |
Oled.setFlipMode(true); | ||
|
||
// Enabling any of those 2 stops the OLED from working | ||
//Accelerometer.begin(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marqdevx enabling any of those 2 lines with library 1.0.5, stops the OLED from working.
correct, I have 1.0.5. See line 75/76 in https://github.com/arduino-libraries/Arduino_SensorKit/pull/6/files |
Without looking in details, is it an issue that your base library does not give I2C addresses for the sensors, and they get auto detected if you use one at a time, but if you use 2 or 3 of them the autodetection fails. However if you were to hardcode the addresses, then they would work at the same time? |
The sensors and the display have a default address, as far as I know only the display's address can be changed. I can use them at the same time |
@marqdevx : since the hardware addresses do not conflict (I was afraid they did, but I2C scan shows they don't), that part is not an issue. If you have a demo that uses all 3 sensors at the same time, please add it to this repo.
I may be doing something wrong, in which case having a known good example, would be even more valuable. |
Any update on this? I'd be happy to write a better combined demo for you, but I'd rather avoid wasting time debugging I2C issues if you already know what's going on |
When pushing the button, output a tone.
i just added support for the buzzer and fixed cursor values for u8x8 |
When pushing the button, output a tone. Show buzzer tone on screen.
And now it shows Hz value on screen and outputs that on the buzzer when pushed. |
Thanks to #13 I can get all sensors working now. |
@marcmerlin Could you have a look at the changes I made? Basically I've just made it more easy to understand, cause the SensorKit its made for not that advanced users, it's nice if a non experience user can understand the flow of the program easily. For example removing the uint8_t can cause doubts. And thanks for the sketch, its working fine, and its super cool, good job :) Have a nice one! |
@marqdevx thanks for the code review and modifications. I assume you tested the code after your modifications (I don't have my board next to me right now), and if so, seems fine to submit, thank you. |
Thanks, yes I get the point of the size, but at this level its not "important", its better to focus to cover a bigger range of user's knowledge. Yes, I did and it works. I will merge it and release a new version. Thanks! Have a nice one 👍 |
Great, thanks for your help and getting I2C to work for all the sensors at the same time. |
It'd be great to query I2C too, but those sensors unfortunately
are not setup to use a different I2C address and conflict with
one another unless you put some solder bridges to change the address