Imaging (sensors)

I have downloaded the VD6283 GUI application and everything works fine except the "Light Spectrum" panel. From the manual I can see that it should calculate the CCT based on the correlation matrix but the CCT window in the top right is always empty. The CCT_Matrix_Coeff_VD6283.csv file for the matrix is located in the sub-directory "Resources" and I have also loaded it manually but it still does not calculate anything.I am working on Windows 10 x64 and used the default installation path C:\Program Files\STMicroelectronics\VD6283_GUI. Based on the "how-correlated-color-temperature-is-calculated" document from ST I have implemented the calculation in Python but I would like to verify my results as they seem wrong to me. Do I miss anything?

Hi team,I want to detect an moving object using the VL53L1X sensor.However, there is a problem with the installation angle of the sensor, and we arr looking for a solution.As shown in the above figure, there is interference from a fixed object between the sensor and the moving object in environment installed at angle of about 60 degree instead 90 degree. But, I want to detect only moving objects, not these fixed objects.At this time, we ask whether the interference of fixed objects can be avoided by moving the FOV from the default 16x16 ROI & Center 199 to the 16x7 ROI & Center 60 as shown figure. Or, is there another solution?Also, in ideal case, when the linear distance (D) between the sensor and object is 300mm, and the actual measurement distance (E) will be 600mm. However, since the installation angle is not a right angle, the actual measurement distance is expected to be shorter or longer than this from the sensor's point of view. But, if only a certain value is constantl

Hello,I have connected a "VL53L5 Satel" board to my Arduino nano BLE board, with modified example code. It works fine with: distance/motion indicator in 4 x 4, continuous mode, ranging frequency 1-10 Hz ( i tried different f). But it only works fine when all the zones have targets. If there is no target at all or partially have targets, I get status code 2 for some zones. the zone number with "Status 2" varies from scan to scan. The explanation of status 2 is " target phase". What does this mean? How to solve it? Thanks for your help!!

..

Hi all,​I'm planning on building my own electronic target for pistol shooting - 4.5mm pellets (4.5mmx5mm approx) traveling at 500-600 fps.​I've read the documentation on the L0X and L1X but I'm struggling to figure out if these sensors can fit the bill. By my calculations, the pellet will be in detection range for ~30us. Are the sensors capable of detecting such thing ? Is there a "range mode" where a measurement between X and Y is seen as something true ? The 30ms timing budget suggests that multiple measurement are taken, so, seems unlikely to me that a 30us exposure would be seen as a valid measurement.​Also, as the FOV is 25°, multiple sensors would have to be mounted around the target to provide at least 3 measurements in all possible locations. Can the sensors cope with cross talk from other sensors ? I haven't seen any data on that, neither suggesting maximum crossover angles between facing sensors, facing or not.​Thank you, hope you guys can help !​Pedro​

UM2133 says that the available modes are VL53L1_PRESETMODE_RANGING, VL53L1_PRESETMODE_MULTIZONES_SCANNING, VL53L1_PRESETMODE_LITE_RANGING (Obsolete), VL53L1_PRESETMODE_AUTONOMOUS but the only definitions I can find (in API/core/inc/vl53l1_def.h in en.STSW-IMG007_v2.4.5.zip) are VL53L1_PRESETMODE_AUTONOMOUS (3), VL53L1_PRESETMODE_LITE_RANGING (4), VL53L1_PRESETMODE_LOWPOWER_AUTONOMOUS (8).Please, what are the values I should use to provide the functionality described in UM2133?

Hello,I am testing the interrupt modes and I have an issue when CONFIG_GPIO_INTERRUPT_LEVEL_HIGH is set to raise the interrut when far objects are detected, but the interrupt is triggered as soon as the continuos mode is started (whit no object in front of the sensor).Is this the normal behaviour?Regards, Ramon.

Hello,It seems the API does not allow to range up to 600mm, why? I am ranging ok up to ~350mm.I have tried to use x3 upscaling, but error is returned when doing so by:VL6180Dev_t    myDevLong;VL6180_UpscaleSetScaling(myDevLong, 3);It seems as upScaling it is not allowed, but it is enabled in vl6180_cfg.h: Can you please advice if I am doing anything wrong.Regards, Ramon.

Hello,I'm actually working with the VL53L5CX sensor, i would like to how i can implement gesturedetection like those of the VL53L0 sensor? Do i need more than one ? Is there a specific library ?Thanks for your respons.SL

Hi,I'm using the VL53L1X sensor with my raspberry Pi3.Using the python code to read from the two sensors. On starting changing the address using the XSHUT pin.The Pi3 is powered from a battery via regulator. The setup also has an option of being charged via external circuitry.From the past month I'm observing an issue where sometimes the sensor address are being reset when the charging starts. The issue happens very random.I could identify that whatever code (C, python) I use i observe this.I could verify that during the initiation of charging the Pi3 is not getting any error but the sensors are only reset, rest everything is working fine.Also When I searched the Pi forums I saw a post where a guy was claiming that the sensor powers off when an EM interference happens. I think in my case also there could be an EM interference when the charging starts.https://forums.raspberrypi.com/viewtopic.php?p=1828654&hilit=vl53l1x#p1828654Could you please help me on what could cause this issue?

..

 Hi,I saw in a video (See the screenshot above) that the distance of target is extracted by assuming a normal distribution, and for L5 sensor, we can get sigma (See the second screenshot above).My question is, do the received range sigma means the sigma of that normal distribution?

Hi , Can anyone help to understand how to use the available driver for vd6283TX ambient light sensor as i was able to read the device id and revision id of the device from the driver but the data ready flag is not in a state to read the data,and hence there is no data when i call "VD6283TX_GetValues()".Any reference document i should refer?Here is the sequence of API's i am using:VD6283TX_Object_t LSstruct;uint32_t data[6]; LSstruct.handle = &hi2c1; uint8_t ret = VD6283TX_Init(&LSstruct); VD6283TX_Start(&LSstruct,0); ret = VD6283TX_GetValues(&LSstruct,data);TIA,Bipin Chavan

..

Hi,I am doing extrinsic calibration for VL53L5 and a RGB camera, i.e., i need to locate L5's zones in the RGB image (a zone can be representaed by a quadrilaterals in the RGB image after projection). And my question is: How should i understand the multi-zone of L5?(1) Do they divide the FoV equally without overlap so each zone has precisely 63/8 degree (for 8x8 zone mapping)?(2) Or do they occupy same area in the sensor board, so the corner zone cover smaller FoV whie the center zone cover larger FoV?

I´m using multiple sensors for distance ( 3 VL53L1X, 1 HC-SR04, 1 TFMini Plus). I think I need a lot of coverage to shade the measurement point and thus reduce the light to 140 lux (stable in the lab). I tried to switch to short mode and time budget to 200ms but that didn't solve my problem. In the laboratory, the TF mini Plus (850nm) did not generate interference on the VL53L1X (940 nm VCSEL).I ran the experiments for 3 days over several hours, collecting 8622 + 5450 + 1540 measurements, with only 33% useful data from the VLs, 89% from TF and 95 from HC-SR04.Does anyone have a better idea?Looks like the VL53L1X is from "Wayne Enterprises, Inc." It's made for Batman... high tech, exclusive use in the dark. :> I like the features of the VL53L1X. Low cost, low consumption, small size and high sensitivity.

Hi, I´ve been asked for starting new topic for this question.I have general question about speed - in manual, there is line about timing budget which is from 20ms -> 50Hz, but there is InterMeasurement time which is needed to be at least timingBuget + 4ms so single measurement takes (timingBudget + InterMeasurementTime + 4ms) - the measurement time is in this standard approach 25Hz? I know that there is some walkaround for shorter distances but I´m trying to solve this for long range measurements.I´ve get response in another topic:the intermeasurement time is the time from the start of one ranging operation to the next. if you want to go as fast as you can simply do not set it. The next range will start immediately. But if you do set it - presumably to put some dead time between each range you have to understand that the clock that manages the timing budget is different from the one that manages the intermeasurement period. If you put the two numbers too close to each other, your IM

I am planning to place a piece of cover glass over an adafruit vl53l0x sensor connected to an arduino uno. I had a look over the user manual for the vl53l0x and tried using the code provided but it does not work. Is the code not compatible at all for the adafruit vl53l0x sensor? Could someone point me to the right direction?

According the official API code in vl53l0x_api.c , comment says enter standbybut the code was set idle ?Which one is correct ?VL53L0X_Error VL53L0X_StaticInit(VL53L0X_DEV Dev) {   ...   /* Set PAL State to standby */   if (Status == VL53L0X_ERROR_NONE)   PALDevDataSet(Dev, PalState, VL53L0X_STATE_IDLE);   ...   }and the define was different#define VL53L0X_STATE_STANDBY ((VL53L0X_State) 2) /*!< Device is in Low power Standby mode */ #define VL53L0X_STATE_IDLE ((VL53L0X_State) 3) /*!< Device has been initialized and ready to do measurements */​

I interfaced VL53L0X with PIC18F57Q43 and managed to obtain the data, but the sensor requires a hard reset (manually removing the supply and reconnecting it) to obtain continues ranging data. I would like to know how I can obtain the data continuously?

Hi,Is it possible to access the ranging histogram from the zones in the VL53L5. There is a great deal of important information in the histogram which can help enable more powerful applications than just returning peak values.Currently, it does not appear that the API enables access to this.Is it possible for customers to alter the firmware on the device to support this or any other way?Thanks

Hi,I'm the firmware guy on a project using the VL6180X to detect a person walking up to a machine, and reaching towards it. I have boards here with our processor (MSP430 family) running other parts of the system and it's time to get the VL6180X running. I downloaded the API "STSW-IMG003_VL6180X_API_3.2.2_Mass_Market". Just wondering if there are any hints or known problems anyone has run into, and if this is the version of the code I should be using. This will be a huge production run, 100,000 pieces predicted in the first 12 months so anything that will make the driver code more robust would be appreciated.Thanks,Lloyd

Hi,I am working on VL53L1X Sensor for designing obstacle detection sensor. When i am testing my sensor's range in office environment, it is showing range status 2 and 7 so frequently even at Timing Budget 140ms. Distance between target and sensor is only 2m still it's showing fluctuations around 100cm. Please tell me weather i should consider values obtained with range status 2 and 7 or not?Regards and how to reduce fluctuations obtained.Akansha

Hi,I am using 53L0-SATEL-I1 with my nxp imx6ul board. This sensor is not working and not detecting on i2c bus address 0x29. I have checked wiring and code all is fine.I am connecting sensor on 10 pin connector and voltage given is 3.3v also checked with 5v.I have also checked this sensor with 4.7k pull-up but issue is not solved.U can check signal of i2c , image is attached.One thing is noted that sensor is working with removing level shifter from vl53l0x and directly connect vl53l0x with board.To do that i removed r7-r14 resistor and suppling 2.8v to board.then the problem getting removed and we can get range data.So the question is that why the satellite vl53l0x board not working on the side of 10 pin connector, is there is problem with level shifter that down voltage 5v to 2.8v.I have tried that with two vl53l0x both giving same problem.

I have a question;Recently, I got the sample of VL53L3CX and evaluated the spec with GUI​(STSW-IMG016).According to the AN5561, VL53L3CX seems to have the 3 modes, "Short", "Medium" and "Long".However, I couldn't find the mode option on the GUI.Then I checked the datasheet of VL53L3CX, the 3 modes were not defined.Thanks in advance