Imaging (sensors)

I feel this would solve a couple problems. First, it would allow for more energy to be returned to the detector, increasing the signal to noise ratio and second, it would allow customers to focus on more specific areas. My questions are - can this be done? (imported question)

..

Hi,I am porting the one of legacy VL53L1 stack (STM api ver 1.1.37.12156 ) for one of the project. This stack is stable and well tested. However, i am surprised to see the RAM consumption(5.43KB) of the VL53L1_Dev_t  object. This is different in new STM api ver 1.2.11.1840 (932B). I can understand that new api might have optimized or deprecated some of implementations. Why is VL53L1_Dev_t  object consuming RAM memory of 5.43KB? It will really help me if any change list file is available to download or can provide here.

Hello, Is it possible to setup ROI to read SPAD array sequentially one by one or matrix of 4*4 SPADs. I.e to get a map of the measurings?

I'm currently using the VL6180x in a project, and I'm encountering some issues where I believe the prox sensor is being reset. I'm operating in Interrupt + Continuous mode. The symptom is that after running an unpredictable amount of time, while being handled, and moved, the VL6180x no longer produces an interrupt when the minimum distance threshold is passed. I am trying to discover a way to read out the mode of the VL6180x on a periodic basis to determine if it is operating correctly. If it is not, a reset and reconfiguration will recover the device. My confusion is this. I can't seem to find a register that reflects whether continuous mode is running or not. The SYSRANGE__START register is the closest, but it only shows which mode it is set to, and not if it is currently running. I also can't simply set the start_stop bit of this register, because if it is running correctly, this would halt operation. Main question: What sequence can be used to change the device from

..

We are using your VL6180X Proximity sensor, gesture and ambient light sensing (ALS) module for a time of flight sensing application. We are experiencing a problem with unreliable measurement results from the sensor: some sensors output a low value (10 - 20 mm) with no target present, and sometimes low readings (50 - 60 mm) when a target is ~800 mm away. These problems seem consistent with cover glass selection and air gap distance. Do you have any experience with these types of problems? NOTE: This question and answer originated from a customer support case which was handled by us. We regularly review support cases and add any helpful ones here for all to benefit from.

..

Everywhere I look, the VL53L1X Tof Sensor says that it has a standard fov of 27 degrees (or 16x16) and can be reduced to 15 degrees (or 4x4 SPAD array). But how do I do this on the Raspberry Pi (in python)? In your VL53L1X_register_map.h there is a function called: #define VL53L1_ROI_CONFIG__MODE_ROI_XY_SIZE 0x013F   /*!<   type: uint8_t \n   default: 0x00 \n   info: \n   - msb = 7   - lsb = 0   - i2c_size = 1   groups: \n   ['nvm_copy_data', 'roi_config']   fields: \n   - [7:0] = mode_roi_xy_size   */How do I use this or another function to make my ROI 15 degrees (4x4 SPAD) instead of 27 on the Raspberry Pi like your documentation says it can? Or do I have to hook it up to some software and do it in there to change it?

Is three any driver available for LPC 1769.

..

In Section 5 of the datasheet for the VL6180X you are presented with Normal Operating conditions.It lists that the optimum voltage range [2.7,2.9] and the functional range [2.6,3.0].What exactly does the functional range mean ? If I am 3.1V or 3.3V, will the device not work ?What is the difference between functional and optimum ?

I have VL53L1X SATEL development board, I checked the performance of sensor indoors It was accurate and sturdy. But when I checked it outdoors-in sunlight readings varies continuously and haphazardly for steady position of sensor and obstacle. If this sensor is not suitable in sunlight then please suggest me any other sensor for my obstacle avoidance device which must have minimum range of 400mm and operatable in sunlight.

I checked datasheet of part VL53L0CXV0DH, but i cannot find information about laser power. There is description about power consumption of whole device but no data for laser only. We need this information for application certification process.Is there anybody who have this information ?

..

Hello,I made a PCB with 7 VL53L1x, that I soldered by myself. I'm using the ST VL53L1 API.6 of them are working great, but the # 7 return error -13 : VL53L1_ERROR_CONTROL_INTERFACE, referenced in vl53l1_errror_codes.h as : "/*!< error reported from IO functions */" Everything works until I start VL53L1_StartMeasurement() which returns no error.After that, when I try to get any values, (with VL53L1_GetMeasurementDataReady(Dev1, &measure) for example) It returns error = -13.I changed this sensor with a new one and still get the same error.Do you have any idea to get this solved? Or to disable IO functions? I didn't find anything in the manual.Thanks a lot,Pierre

User manual said "It is the fastestminiature ToF sensor on the market with accurateranging up to 4 m and fast ranging frequency up to50 Hz"I could not reach such frequency with all possible tested configuration. The best result was 37 Hz with the values of TimingBudget 10mS and Inter Measurement Period 5 mS in short range mode. I do understand that the last value is wrong, but it is the only way to reach such speed. So, what do I wrong and what is the way to reach 50 Hz?

Dear St, I'm using the VL53L0X to detect an object at a distance lower than 30cm. I need that the GPIO is activated (turned down to GND) if an object is present below that distance. If possible it would be better if the sensor is able to detect if the object is at a distance above 10cm and below 30cm. At a distance of 40cm I have a screen.Once the VL53L0X has detected the object, it should turn off the port which will turn on the microprocessor that usually is off (in order to save energy).The problem is that the GPIO is turned off everytime i put an object even at a distance of 50 cm or more. It's not turned off if there isn't any object.Apart for this port, the object distance seems to be read correctly by the microprocessor.What is wrong in the code?The code I write work this way:When I want to turn on the VL53L0X I call:VL53L0X_SetLimitCheckValue - with VL53L0X_CHECKENABLE_SIGNAL_RATE_FINAL_RANGEVL53L0X_SetLimitCheckValue - with VL53L0X_CHECKENABLE_SIGMA_FINAL_RANGEV

I'm looking for an example of reducing the ROI with the API for the VL53L1X. I prefer the API released by POLOLU, since I am working with an Arduino, but anything at this point will be greatly welcomed!  POLOLU directed me to your site. From the documentation of your API I cut and paste the setup for reducing the ROI but I must be doing something wrong. A working example of code, be it with the ST'sl API or POLOLU's smaller API might be a big help to me and other VL53L1X enthusiasts.

Explanatory note: The "fat driver" has built in code to detect a "USE_I2C_2V8" flag. If detected, the software writes to register 0x2E. Though the register names for 0x2E and 0x2F suggest that both should be changed to get the interface mode wanted (high voltage for both I2C and GPIO) , the "fat driver" seems to change register 0x2E only (and not to 0x2F: cf. question 2).I could not find any detection code In the "ULD driver" and not any code writing to register 0x2E or 0x2F (cf. question 1) .

@John E KVAMHi, I want to use the VL53L1X in combination with a Murata CMWX1ZZABZ lora module on the B-L072Z-lrwan1 discoboard.When i try to transmit data using:HAL_I2C_IsDeviceReady(&hi2c1, 0x52, 100, 5);I can see the SCL and SDA signals on my scope. But when i try to use the API of the VL53L1X nothing happens on the lines. They stay at 3.24mV. What do i forget?my code:int main( void ) {   VL53L1_Dev_t dev; VL53L1_DEV Dev = &dev; /* STM32 HAL library initialization*/ HAL_Init(); /* Configure the system clock*/ SystemClock_Config(); /* Configure the debug mode*/ DBG_Init(); /* Configure the hardware*/ HW_Init(); /* USER CODE BEGIN 1 */ MX_I2C1_Init(); dev.I2cHandle = &hi2c1; dev.I2cDevAddr = 0x52;     /*** VL53L1X Initialization ***/ VL53L1_WaitDeviceBooted(Dev); VL53L1_DataInit(Dev); VL53L1_StaticInit(Dev); PRINTF("Data init sensor DONE\n"); VL53L1_SetDistanceMode(Dev, VL53L1_DISTANCEMODE_LONG); VL53L1_SetMeasure

Our setup has 6 VL53L1X sensors connected via TCA9545A multiplexors to STM32F303 host. We started with STSW-IMG007 API, but later switched to STSW-IMG009 ULD API. First, the statement that ULD API has "only 4 files" is misleading. The code does not compile with only files included into API package. The example in X-CUBE-53L1A1 links to "fat" driver folder to get an access to about 6 additional .h headers, and then excludes it from compilation.Question 1: Is this the way ULD driver supposed to be used?Second, and most important, is that the sensors stop responding after some random time. Usually it is VL53L1_ERROR_CONTROL_INTERFACE returned from VL53L1_RdByte() function. Sometimes it happens after 20-30 min, and sometimes it is as short as 2 min. Note, that we observed same problem with "fat" driver as well, which was the reason to switch to ULD. We also tried Arduino boards with both Arduino and Pololu drivers and VL53L0X sensors. The result is always the same - they work for a while a

..