There is no problem except perhaps of understanding. The sensor shoots out a tiny bit 940nm light and then looks for a retuning signal. The Sun shoots out tons of 940nm light, and it becomes noise in our system.
1) The sensor is sensitive to ambient light. The effect is it cannot range as far. IN really bright light the max range might go down as low as 1 Meter. And if your integration time is low, the problem is exacerbated. If you move in closer, you will find it starts working at some point. And that point will change with the brighness of the sun, location of the sun, and reflectivity of the target.
2) The sensor filters out all but the 940nm light. Unfortunately the sun generates way more 940nm light than does the sensor. And that is your issue. You cannot filter the sun's 940nm light without also filtering the sensor's 940nm light.
3) Modify that code to show the range status when don't get a range (printing x is silly). Try 0xXX when the status is bad, so instead of seeing a useless X you know the status.
People have proposed adding an external 940nm filter, but it adds crosstalk, and cost. If you get the cost down, it can help a bit - some light will 'blow through' our filter, and your filter can help that.
- john
Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised.
ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'
