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
If both VL53L8CX and LTR329 are connected it is not possible to read sensor values.
Expected block behaviour
Before the begin() function for the VL53L8CX is called we need to change the I2C address with the following command: sensor_vl53l8cx.set_i2c_address(0x51);
I propose 0x51, which is 0x29 in 8-Bit, but if you are aware of any sensors already using that address let me know.
Easy enough, but the issue is, that if the set_i2c_address() function is called after the LTR has already been initialized, the LTR somehow reads different values, than it would usually do. I guess, that whatever is happening under the hood of the set_i2c_address() function is messing with settings of the LTR.
So we need to make sure, that the set_i2c_address() is always called before, actually probably best to call it before anything else in the setup.
The text was updated successfully, but these errors were encountered:
Block description
If both VL53L8CX and LTR329 are connected it is not possible to read sensor values.
Expected block behaviour
Before the
begin()
function for the VL53L8CX is called we need to change the I2C address with the following command:sensor_vl53l8cx.set_i2c_address(0x51);
I propose 0x51, which is 0x29 in 8-Bit, but if you are aware of any sensors already using that address let me know.
Easy enough, but the issue is, that if the
set_i2c_address()
function is called after the LTR has already been initialized, the LTR somehow reads different values, than it would usually do. I guess, that whatever is happening under the hood of theset_i2c_address()
function is messing with settings of the LTR.So we need to make sure, that the
set_i2c_address()
is always called before, actually probably best to call it before anything else in the setup.The text was updated successfully, but these errors were encountered: