My use case would benefit from high speed but I'm having trouble getting it to run at 60Hz. I'm using the X-NUCLEO-53L5A1 on an NUCLEO-L476RG board with the XCUBE-TOF1 software. I'm using the SimpleRanging example program: XCUBE-TOF1\Projects\NUCLEO...
I used X-NUCLEO-53L5A1 + 2 VL53L5CX-SATEL, and the data read output speed has a delay in the code: HAL_Delay(POLLING PERIOD), POLLING PERIOD == 1s, and then I want to quickly, so I canceled HAL_Delay() (Picture1), But it took a long time to check (Pi...
root@yocto-linux:~# ./phio -s -Z=1 -S[V]open fd 3 for /dev/stmvl53lx_ranging[V]started status 0[V]keep using fd 3[ 195.463147] STMVL53LX IPP Err in send_client_msg 115 :fail to send data size 608 to pid 1[ 195.463147] [ 195.472822] STMVL53LX IPP Err ...
Hi,I'm building a project that uses 20 VL53L1x sensors to detect any people or objects that go in the danger zone of a machine.The sensor will detect any objects or people below 2 meters distance. We set up the sensor 30cm above the ground.The measur...
Has ST done any research into the level of vibration these sensors can safely withstand? I'd like to use these on an application which experiences intermittently high vibration (up to 15m/s^2, mostly parallel to the sensor measurement direction). Acc...
Let's say I want to limit the field of view to be 200mm wide at a distance of 1500 mm.Can I do this using the ROI settings?If so, how do I calculate what my ROI settings need to be?
As reported in the datasheet, "a 47 KOhm pullup resistor is required" on the LPn signal. In that case the power state machine goes from POWER OFF to HP IDLE during the power up sequence. What would the device state be if the LPn signal was low during...
With the following code the VL53L5CX should get it's firmware uploaded. " /* Download FW into VL53L5 */ status |= WrByte(&(p_dev->platform), 0x7fff, 0x09); status |= WrMulti(&(p_dev->platform),0, (uint8_t*)&VL53L5CX_FIRMWARE[0],0x8000...
I use cube ide when i add the function Status = VL53L0X_StaticInit(pfab);on main.c ,how build it i have this error :arm-none-eabi-gcc "../Core/Src/main.c" -mcpu=cortex-m0plus -std=gnu11 -g3 -DUSE_HAL_DRIVER -DSTM32G030xx -DDEBUG -c -I../Drivers/CMS...
Hello, is there a way (after applying a calibration such as offset calibration or crosstalk calibration) to return the sensor back to the default calibration that was performed at ST? If so, which I2C commands would perform this job?