Hi!
I require your help regarding a problem I’m encountering.
Code that will communicate with the Gravity I2C VEML7700 Ambient Light Sensor.
I tried some code I found in the Arduino examples, but it didn’t work.
I did a I2C scan and found that the address is 0x10 not 0x23 as advertised. Changing the address did not help.
Thank you so much in advance for your help!
Hello @DanCot and welcome to the RobotShop forum!
You can find all the documentation here:
And you can find the Arduino library here:
As you can see in the header file (line 89) it says that the I2C_ADDRESS is 0x10 which matches the sensor’s datasheet, I’m not sure where you saw that the address is 0x23.
I hope this helps!
Thanks Geraldine. I don’t know where I saw 0x23 either.
Are you familiar with the DFrobot gravity microwave sensor?
If you are, do you know why the yellow led (it indicates when the sensor has been triggered) stays on when the signal output is connected to the Arduino pin?
The indicator works correctly when the pin is not connected. I tried it in pin 2 as the demo program indicates, and I tried it in another digital pin set to input.
I will try the info that you sent me for the Veml7700.
Thanks again, Dan
According to the wiki here’s how the indicator works:
When the microwave sensor does not detect moving objects, the indicator LED remains off. When the sensor detects moving objects, the LED will turn on and the output level will be change from HIGH to LOW. The LED will automatically turn off about after 0.5s and the output level will change from LOW to HIGH. If the microwave sensor detects continuously moving objects the LED will keep flashing on and off. The output level will fluctuate between HIGH and LOW until the object stops moving.
They also mention this:
Microwaves can penetrate through walls. So sometimes it has inaccuracies when microwaves penetrate through outside walls and detect moving objects in non-target areas. Be sure to choose an installation location to avoid this!
This leads me to believe that interference is most likely causing the error. You may want to isolate your power input. And also try changing the detection range by turning the potentiometer.
These notes may also help:
