Imaging (sensors)

I am trying to use VL53l8cx with STM32F407VGT6 to find depth . I have previously worked with VL53l5cx and VL53l1cx  and was comfortab;e with both of these .  I am unable to use this sensor at all as everytime a hard fault arises . I have been able to use it on Arduino but wasnt able to use it with any st controller or dev board.  The link to the projects is below: https://drive.google.com/drive/folders/1tsidyGcB8i_SaHW2IKRrtKeJuAWvVb6X?usp=drive_link https://drive.google.com/drive/folders/17VWmdfnXCuZRXwIgr5QM44ov2SjAzd09?usp=drive_link This is where the hardfault occurs :

Hi,i know that there are already a few posts on this topic, and i know the VL53L8CX has the same table as the VL53L5CX. But i just wanted to know, if anyboy could post the calculations for the LookUp-Table?Thanks!

Are the SATEL-VL53L4CD breakout boards pre-soldered, which can be connected using female jumper wires?

HelloI need to trigger an action whenever a small object (aprox 1 cm diameter) is at a fixed distance (around 10 cm) of the sensor.Using VL53L0X the readings I get are very much affected by the background, for example if the object is in range and the background (1 m behind) changes from dark to white, the reading  changes to indicates a much larger distance.What can be done to improve this behavior? Absolute accuracy is not important, but repeteability is.

Dear Sir or Madam,what is the absolute minimum measurement distance of VD55H1 3D iToF sensor die?Could you provide a (detailed) datasheet and application notes? Currently, there is only a data brief. Best regardsLukas Bath

Hi,  I was reading @John E KVAM excellent post on Time of flight sensor glass:https://community.st.com/t5/mems-and-sensors/time-of-flight-cover-glass/ta-p/49259and this documentationhttps://www.st.com/content/ccc/resource/technical/document/application_note/group0/9d/93/be/33/13/be/46/19/DM00326504/files/DM00326504.pdf/jcr:content/translations/en.DM00326504.pdf And was just wondering, how important is the IR coating:

 Hi Team, We are using the VL53L4CX in QCS8550 platform.Below are queries listed below for clarification. Query 1:Load Capacitance I'm using a same I2C for 5 sensors of VL53L4CX. Is that good to connect or any load capacitance issues will occur Need to understand the max load capacitance of the sensor Query 2: Slave Address configuration 

I want to operate the VL53L5CX to accomplish gesture recognition operations using an ARM Cortex-M4F microcontroller chip. So can libGesturesMZ_m4.a be used with Cortex-M4F?I am trying to port the en.STSW-IMG035_F401 project to an ARM Cortex-M4F controller chip and the HT_set_square_resolution() function returns -5 at runtime.Operation flow: lmz_platform_init -> vl53lmz_init -> gesture_library_init_configure(Err -5, HT_set_square_resolution() failed).

Hi! I am trying to use motion detection data from VL53L8CX sensor. Where can I find deeper explanation of results data and configuration structure than is it in datasheets.RESULTSstruct{uint32_t global_indicator_1;uint32_t global_indicator_2;uint8_t status;uint8_t nb_of_detected_aggregates;uint8_t nb_of_aggregates;uint8_t spare;uint32_t motion[32];} motion_indicator;   CONFIGp_motion_config->ref_bin_offs

I have the STEVAL-56G3MAI1 evaluation kit for the VD56G3 image sensor and the STEVAL-EVK-U0I1 to connect and take snapshots from the sensor.  I have been looking into script generation and register setting and I would like to set the exposure time to be a known duration in microseconds.  I referenced UM2602 titled "How to integrate and configure the VD56G3, VD66GY, and VD16GZ devices from a hardware and software perspective", which contains all the register configuration information for this sensor.  Section 14.7.2 of UM2602 is for configuring the manual exposure and it talks about a register called "MANUAL_COARSE_EXPOSURE".  The description of the "MANUAL_COARSE_EXPOSURE" register is "Integration time is controlled by the MANUAL_COARSE_EXPOSURE register. The value is expressed in line equivalent".  The manual also states that the value is a 16-bit unsigned integer. However, there is no information in the manual for how to configure this value to set

I am currently implementing a series of  vl53l4cd sensors into a project. These work really well and I am able to address these individually on one shared i2c line. These sensors are working perfectly fine on this shared line when measured independently but when an object is blocking both sensors, the readings speed up and the readings of both sensors becomes much less accurate and noisy. Is there a specific approach to reading sensor data from both sensors simultaneously? As a test I did move one of these sensors onto another i2c line, and the issue continued. I originally thought it was congestion on the i2c line but it clearly isn't and may be the way I am getting the distance data from both sensors. I am using the Arduino library - https://github.com/stm32duino/VL53L4CD/ I have attached a video which should hope

I have a VL53L8CX time of flight sensor connected via I2C on a custom board. The Board has other devices that can talk on I2C no problem. now i cant see the i2c address of the ToF device. from my understanding everything seems to be fine and in accordance with the datasheet. However there are two things that might be not correct and i want to make sure that my assumptions are not wrong. about the LPn pin (A2) in the datasheet this is written:Enables communication. Drive this pin to logic 0to disable I²C communication when the device isin low-power mode. Drive this pin to logic 1 toenable I²C communication in low-power mode.This pin is typically used when you need tochange the I²C address in multidevice systems. Ifit is not used, or if interfacing via the SPI,connect to IOVDD with a 47 kΩ p

Hi:I am trying to use en.STSW-IMG037 (VL53L7CX_GUI_v2.2.29009) software to evaluate the VL53L7CX ToF sensor. I implemented firmware on the NUCLEO-H755ZI-Q board with VL53L7CX sensor from Pololu based on the firmware example in the "en.X-CUBE-TOF1\Projects\NUCLEO-F401RE\Examples\CUSTOM\VL53L7CX_SimpleRanging. I initialized the UART with 460800 baud and sensor is dumping the data on a terminal software. The next step, I would like to use the GUI software installed in the en.STSW-IMG037 to evaluate the sensor. I launched the software, and it detect the ST-LINK. However, the "Connect" b

Hii,       I am writing to seek support regarding an issue I am facing with the VL53L4CX Time-of-Flight sensor. In my current setup, I’m consistently encountering incorrect distance measurements beyond 2 meters, where the sensor tends to report values that are approximately 75-85 cm more than the actual distance.Details of the Issue:Setup: Indoor environment, with stable power supply, targeting a white sheet-covered wall.Timing Budget: Set to the maximum value of 200ms.Observations: While the sensor occasionally reports the correct distance, more often than not, the values are incorrect, with a significant error margin of 75-85 cm. The status returned is also zero, indicating no error according to the API.Steps Already Taken:

Hello,We have been using multiple VL53L3CX sensors for some time but only using one zone. Now, we want to use all four of them but we are running into some issues: Specifically, we can only read one zone while the rest all return status 255. In addition to this, only one object is found which makes sense considering the status. But, as said before, we need to use all the zones. The issue that we have is very similar to this thread but sadly it was not solved. So, is there any procedure, configuration or calibration that we need to do before attempting to use the rest of the zones?Our setup consist of an Arduino Due connected to the sensor and we do the following to initialize it:  (void)VL53LX_WaitDeviceBooted(&dev); (void)VL53LX_DataInit(&dev); (void)VL53LX_SetDeviceAddress

I am getting occasional readings from this sensor of zero(0) reading result with the error code 31.  According to the header file this error corresponds to:#define VL53L1X_WARNING_OFFSET_CAL_MISSING_SAMPLES ((VL53L1X_Error) - 31)/*!< Thrown if there is less than the requested number of* valid samples. */This is not during Calibration offset process,  which we do use,  but at run time after SetOffset using the stored offset value.  Very confused why I would get this error,  occasionally,  at run time?Thanks,Will   

Hello everyone.I'm currently working with ToF sensor VL53L5CX. I wanted to use it in collaboration with a digital camera.But I can see the laser from ToF if the target has a high reflection level. I know that I can simply use the IR filter,but I wanted to synchronize camera acquisition and ToF ranging on/off in a software part. Also, I'm using stop_ranging and start_ranging for autocalibration of temperature drift. I have approximately 200 ms delay before I get the first data from ToF. Is there any possibility to increase this part? In examples of API there only usage in the way, that ranging starts -> loop -> stop ranging. Is it possible to use it with switching _on/switching_off  without delay? Parameters used:Frequency 30hz, 4x4 resolution, continuous mode, xtalk calibration.Thank you!

Firstly, on behalf of our company, I would like to appreciate the great products that have been delivered by STM through the years, wish STM well and prosper.#----------------------------------------------------------------------------------------------------Recently we are working on using the VL53L5CX TOF for our ML project.Settings in fw :I2C speed : 1MHzResolution : 8x8Ranging Frequency : 2HzRanging Mode : ContinuousTarget Order : ClosestSharpener Percentage : 20%MCU : ESP-32Platform : Arduino IDEWith Cover GlassRoom environment, curtains are opened

I need to work with three tof sensors (VL53L0X) at once. First i checked one sensor and it worked well. the code is below.  #include "main.h" #include "vl53l0x_api.h" // Define the I2C handle I2C_HandleTypeDef hi2c1; // Define GPIO pins for XSHUT control #define XSHUT_PIN GPIO_PIN_0 #define XSHUT_PORT GPIOA // Define GPIO1 pin #define GPIO1_PIN GPIO_PIN_3 #define GPIO1_PORT GPIOB // Define new I2C address for the sensor #define SENSOR_NEW_ADDR 0x30 // Global variable to store distance measurement uint16_t sensor_distance = 0; void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_I2C1_Init(void); void VL53L0X_Init_Sensor(VL53L0X_Dev_t *sensor, uint8_t new_address); int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_I2C1_Init(); // Define sensor device VL53L0X_Dev_t sensor; // Initialize sensor VL53L0X_Init_Sensor(&sensor, SENSOR_NEW_ADDR); while

Background:I'm building a battery-powered device with an extremely tight energy budget (14mAh battery).I take a ranging once every 10 seconds (configurable, can be down to 1s).We need good accuracy indoors in close distances (up to 2m).Outdoors and at larger distances we prefer to have more distance and less precision.For initial testing I set the ranging profile to long and the timing budget to 33ms.My initial choice has been VL53L4CX, based on the datasheet information and my utter lack of experience. However:The device doesn't seem to handle GetMeasurementDataReady correctly - it immediately returns true after I execute StartMeasurement. Test code and code output below.I'm really struggling to lower the power consumption in one-shot mode. It seems that the minimal time needed to acquire a measurement is about 60ms between StartMeasurement and StopMeasurement - really stretching my power budget.

Hello, i've recently made a board including a VL53L8 Time of flight sensor connected to an STM32G071 over SPI.I'm using the VL53LMZ api to connect to it and after modifying the platform.c file i've managed to talk to the sensor (vl53lmz_is_alive() sets the IsAlive flag to 1).But all the other functions fail after that, i've managed to track down the problem using the debugger to the line 5 below:   /* Enable FW access */ if (p_dev->revision_id == (uint8_t)REVISION_L8) { status |= WrByte(&(p_dev->platform), 0x7fff, 0x01); status |= WrByte(&(p_dev->platform), 0x06, 0x01); status |= _vl53lmz_poll_for_answer(p_dev, 1, 0, 0x21, 0xFF, 0x4); } else {   within vl53lmz_init().It looks like the L8's register that is being monitored by this function is set to 0 and never changes.I have verified the transmitted data

We are using part number VL53L3CX on the X-NUCLEO-53L3A2 board, and one feature we were expecting, for example, is for the sensor to generate an interrupt via configurable GPIO in the following situations:it is inside or outside a measurement window,above a measurement.below a measurement.By default, this interrupt is generated every time a measurement is completed by the sensor.Is it possible to configure the sensor to generate interrupts only in the situations mentioned above?If so, can you help us with some examples?Is there a part number with these functions?Thanks

I have two VL53L7CX Time of Flight sensors connected to a STM32F401CCU6. I was able to modify the X-CUBE-TOF VL53L7CX template to support both sensors, but I can't get low power mode to work for some reason.  specifically, trying to use a sensor after calling:CUSTOM_RANGING_SENSOR_Stop(Instance);does not work. Even if I turn it back on with:status = CUSTOM_RANGING_SENSOR_Start(Instance, RS_MODE_BLOCKING_CONTINUOUS);It also seems to not be doing what it's supposed to either, as the system still draws a lot of current even when it's supposed to be in low power. This was not a problem with the single sensor setupI've included all code that might be relevant here: https://github.com/youcefs21/multi-tof

Hello,I intended to use VL53L4CDV0DH in my project.Could VL53L4CDV0DH measure reflective wafers material? ThanksChuong

Hi my name is Kevan Sherwood with Rayhawk Technologies, we develop an autonomous solution for opening and closing rails cars during the loading process. We have a toolhead that scans the gantry for a railcar to be opened and it then finds the latches opens them and opens the lid and moves on to the next. There are 2 feet on the bottom that do the opening and closing. We are testing with one of these VCSEL sensors (VL53L4ED) on the breakout boards to track the position of the feet on our tool when it is performing an opening and closing action. The goal is to see based on the foot position where in the process it is going wrong and have a data representation of what a good action looks like compared to a failed action. We have the sensor mounted at the end of the tool bar and it is pointed at a rod that moves with the feet. So it will measure the distance traveled when the feet are pressed. The distance being covered is 350mm total. Our main conc