Imaging (sensors)

I am exploring STM image sensors for a new project and am evaluating different options. To make an informed decision, I would like to refer to EMVA1288 datasheets, especially for details on read noise and dark current performance. Could you please let me know if such datasheets are available for STM image sensors, or how I might obtain this information?For reference, the EMVA1288 standard is freely available, and here is an example of a datasheet template:https://www.emva.org/wp-content/uploads/EMVA1288-3.1_datasheet_template.pdf

Hi, I am testing the SATEL VL53L7CX board, but the SDA on this board is stuck at zero. I have checked that there are no short cuts and that the pull up is there. Any ideas how to solve this?

I found a problem while using the VL53L4CD. My usual practice is to initialize the VL53L4CD after the terminal is turned on. During subsequent use, I only use Start and Stop to control whether to start ranging.Now it is found that when I stop, the terminal enters a low-power state. When this state persists for a period of time, when operating VL53L4CD again and sending the start instruction, no interrupt signal can be received. Moreover, after I send VL53L4CD_ClearInterrupt, the interrupt signal remains at a low level all the time.When I start, I first call VL53L4CD_ClearInterrupt, and then call VL53L4CD_StartRanging. At this time, there is no occlusion before VL53L4CD, and the register value printed out is after the VL53L4CD_StartRanging interface is called.Tof reg [0], value [1]Tof reg [1], value [29]Tof reg [2], value [2]Tof reg [3], value [10]Tof reg [4], value [0]Tof reg [5], value [2f]Tof reg [6], value [bc]Tof reg

Hi, I have downloaded the STSW-IMG302_LNX which has this description "Linux driver for VD6283 6-channel ambient light sensor, with flicker extraction expansion application programming interface (API)", I want to compile this driver for my embedded linux for arm64 platform, I don't know how can I compile it as there are number of files and folders as shown below.The read me doesn't help me either. Do I need to make a module out of it and load that in my embedded linux ? if so then how ? I tried following,I used aarch64-linux-gcc compiler. What I did was I execut

I am having trouble with the VL53L7CX recording incorrect measurements after being powered on. Often times the distance if off consistently until I unplug it and plug it back in (The raspberry pi). Sometimes even that will not solve the problem. I have looked at the calibration function but it seems that it is only for cover glass and I use none. Has anyone had this issue and know how to solve it?

Hello community,I just downloaded ULD driver for vl53l8ch. However it looks only i2c interface is implemented in the driver, no SPI interface related is present. Is there a SPI version of the driver available? or I missed something? Thank you./Roland 

Hi,I have installed the v4l2 driver for the STEVAL-56G3MAI1 camera module on ubuntu 22.04.05 LTS on a RPI CM4. But I am unable to access the module through /dev/video0.I have followed the instructions in the linux start guide fro ST BrightSense but I cannot get it to work.I am not sure if I need to do something in addition to these instructions:cd en.vd56g3_1.0.3/srcmakesudo cp *.ko /lib/modules/$(uname -r)sudo depmod -asudo rebootsudo apt updatesudo apt install device-tree-compilercd en.vd56g3_1.0.3/dts/rpi1_to_4/sudo dtc pcb4188_vd56g3.dts -o /boot/firmware/overlays/pcb4188_vd56g3.dtbosudo sh -c "echo 'dtoverlay=pcb4188_vd56g3' >> /boot/firmware/config.txt"sudo reboot v4l2-ctl --list-devices gives:unicam (platform:fe801000.csi):/dev/media3 Cannot open device /dev/video0, exiting. Is there something I am miss

Hello.We're having issues after installing the libcamera package for the VD56G3 sensor from https://www.st.com/en/embedded-software/stsw-img502.htmlThe ST IPA is (apparently) being treated as untrusted and we're being forced into IPA isolation, crashing the application.[10:02:34.005492925] [181325] ERROR IPCPipe ipc_pipe_unixsocket.cpp:134 Call timeout! [10:02:34.005523463] [181325] ERROR IPCPipe ipc_pipe_unixsocket.cpp:66 Failed to call sync [10:02:34.005531333] [181325] ERROR IPAProxy raspberrypi_ipa_proxy.cpp:261 Failed to call start [10:02:34.009190798] [181325] ERROR IPCUnixSocket ipc_unixsocket.cpp:192 Failed to send: Connection refused [10:02:34.009221799] [181325] ERROR IPCPipe ipc_pipe_unixsocket.cpp:66 Failed to call sync [10:02:34.009228836] [181325] ERROR IPAProxy raspberrypi_ipa_proxy.cpp:43

Hi,I was wondering how things were progressing with writing and possibly mainlining Linux drivers for ST BrightSense and SafeSense Industrial, Consumer and Automotive Image Sensors?We're working on a new state-of-the-art open source system for conservation of Europe's most endangered dormouse, squirrel and bat species using libcamera and embedded Linux and would like to look at integrating ST image sensors.More about our work:https://new-homes-for-old-friends.cairnwater.com/and more detailed analysis of how user requirements translate to implementation decisions:https://github.com/William-Robert-Robertson/WildCameraThank you

We use the VL53L1X in one of our products and have been doing that for over 2+ years now. As this device is not easily solderable, we have been relying on the Chinese supply of breakout boards used in the hobby market.  Just recently we are facing range issues with entire lots of this sensor based boards. All of them exhibit range issues where the Sensor is unable to detect beyond 30 to 40cm. I thought it could be a calibration or offset issue. I've tried getting offset values using the 17% Gray sheets as recommended. Any help in this regard will be appreciated. Thanks.  

I'm using a VL53L4CD as a proximity switch but with a user selectable threshold. I began developing on XNUCLEO-53L4A1 on a NUCLEO-F401 but have since migrated to my own pcb using STM32C071. I am having difficulty with poor status reports from the ToF device at distances above about 300mm on my own board. Under 300mm I get a status of 0 but anything above that and it quickly deteriorates to 1, 2 or 4 and the distance becomes very erratic.Thinking that it was down to the specifics of the pcb I reverted to the F401/XNUCLEO arrangement and I now see it's not that much better and certainly nowhere near 1.2m. I can get to about 500mm with status 0 but much beyond that leads to a status of 1 or 2 and eventually 4. My maximum range is 500mm so it's barely okay on the F401 but not on my own pcb.I'm using the standard API with some mods which don't amount to very much (threshold hysteresis mainly). It doesn't seem to matter whether the (standard) cover glass is fitted or not. Th

I try  STSW-IMG037 software with  Nucleo STM32-F401RE + Expansion board with VL53L7CX+ two Brakout Boards(VL53L7CX).but it dosen't work. STSW-IMG037 software with  Nucleo STM32-F401RE + Expansion board with VL53L7CX is OK.Soft ver v2.2.29327. and 53L7A1_MultiSensorRanging.bin in X-CUBE-TOF1 is OK.What should I do?

Hi ST team,We are encountering an intermittent issue while using the TOF L3 module in a mid-range distance measurement setup. Below are the details: TOF frame rate: 30ms. Readout rate: 50ms. Distance mode: Medium range.Issue Description: When a stable target is present within the TOF field of view, it measures correctly. However, if a hand is moved quickly back and forth between the TOF and the target, an error frame occasionally appears. This frame has:Distance status: 255Distance value: 8191mmThe following frame typically reports:Distance status: 12A valid distance value (matching the original target)Observations and Questions:All frames with status 255 appear on odd-numbered frames (i.e., those with smaller pulse intervals);These frames have abnormally h

Hallo erveryone, I'd like to know if it's possible to use a VL53L8CX to distinguish between a human and an object and other non-living objects. I've done a little analysis of the data collected by the sensor, motion indication, distances, intensity of the signal measured. And I've come to the conclusion that a robust distinction between humans and other objects (animals or non-animated objects) isn't really possible with this sensor. My question at this level may therefore seem a bit ***, but would it be possible to make a reasonable distinction with this sensor, and have I perhaps ignored other details that need to be taken into account?  

Hi everybody. Please help me.  I bought a VL53L4ED sensor and would like to learn how to use it.I have found a number of documents and driver examples, but have been unable to find a document describing the internal registers and their function. (programming manual) . I must be looking for it wrong. Can you please direct me to the proper document?Thank you very much.  Jaroslav

Hello. I have recently made a custom PCB as a learning project and I have issues with getting data from the sensor. I have used multiple VL53L7CX Satel prebuilt breakout boards and those work fine with my software. I have used both the qwiic python library and the ULD driver on a raspberry pi which have worked fine, but when I use the same code for the custom PCB the sensor does not measure data.  When I use check_data_ready() which should turn true when data is available, it never returns true. I have also tried bypassing this and just reading the data, but i get an output of 8x8 zeros.    For simplicity, my code is just a small variation of the code at: https://github.com/sparkfun/qwiic_vl53l5cx_py/blob/master/examples/qwiic_vl53l5cx_ex6_settings.py (Just added my code for

Hi ST Experts, I am working with the P-NUCLEO-53L8A1 evaluation kit and have followed the user guide to install the necessary software packages and GUI. I was able to detect the STLINK COM port connected to the evaluation board. However, after refreshing the list and attempting to flash the firmware, I repeatedly receive an error message and am unable to connect to the sensor successfully, despite multiple attempts.  

Hello,I’ve been reviewing the current consumption section (Section 7.4) of the VL53L8CH datasheet.I’m currently using the Detection Thresholds plugin, and I would like to ask:Which power mode does this correspo

How do you perform a soft reset on the VL53L4CD if XSHUT is not used?  I can't seem to find an example.  I see the VL53L4CD_ULP_SOFT_RESET or VL53L4CD_SOFT_RESET is defined, but I don't know what to write to it.Also, how do you shut the sensor down without XSHUT, is telling it to StopRanging enough?Thanks.

Hi everyone,I'm currently developing firmware for the VL53L1X Time-of-Flight sensor on a breakout board using STM32CubeIDE, and I’m working with the bare driver provided by ST (not the ULD). I’d like to implement the complete calibration sequence, but I’m unsure about the correct procedure and how to manage the physical steps during calibration.Based on the documentation, the recommended calibration order is:RefSPAD CalibrationCrosstalk CalibrationOffset CalibrationI have a few questions regarding the practical and programmatic steps for performing these calibrations using the bare driver functions:1. RefSPAD CalibrationShould this be performed with

Hello everyone, i'm trying to use the vd66gy with the raspbeery Pi x64 connected on cam0 and im following all the steps of the "Linux Start Guide for ST BrightSense" but it still doesnt work. I downloaded the drivers for the camera as well as the libcam st version from this link: https://www.st.com/en/embedded-software/stsw-img503.html?dl=redirect. However i see that even for the vd66gy driver, the en.vd66gy_1.0.3.zip has all the vd56g3 files and the makefile looks like this: ifneq ($(KERNELRELEASE),) include Kbuild else KVERSION ?= `uname -r` KDIR ?= /lib/modules/${KVERSION}/build default: CONFIG_DRIVER_VD56G3=m $(MAKE) -C $(KDIR) M=$$PWD clean: CONFIG_DRIVER_VD56G3=m $(MAKE) -C $(KDIR) M=$$PWD clean endifIs this a mistake? It looks like the vd56g3 driver. You can confirm by do

Hi,I want to know the exposure time of VL53L5CX per frame.I also want to know that it is possible to configure the exposure time?Best,Jsc.

I wish to connect the P-board, which has a 22-pin connector, to a Raspberry Pi that has a 15-pin camera connector (From the Raspberry Pi 1/2/3/4 series, not the 5). The datasheet for the P-board only gives a vague suggestion. Is there a specific cable that has been known to work?

Hi John, Could please confirm if the slew rate requirement of VL53L8CX is satisfied in the EVM X-NUCLEO-53L8A1?  We're considering to use TI's TLV751180330PDSQR to power up the VL53L8CX sensor. But the TLV751180330PDSQR suppor

Hello ! I am calibrating a VL53L4CD ToF sensor. Is it suggested to set a large timing budget (e.g. 200 ms) for the offset and crosstalk calibrations' distance measurement process? In the distance measurement examples, the timing budget is set to 10 ms for 'fast mode' and 200 ms for 'high accuracy mode'. If the sensor will ultimately be operating in both 'fast' and 'high accuracy' modes, is it better to perform the initial offset and crosstalk calibrations in 'high accuracy mode'? Thanks!  Brian