Posts made by PicantePeperoni

@veye_xumm It works great without having to compile, thank you!

@veye_xumm Thank you so much. Best of luck.

@picantepeperoni dmesg | grep veye
[ 0.050709] platform 3f801000.csi: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/veyecam2m@3b
[ 10.527060] veyecam2m: disagrees about version of symbol module_layout
[ 10.589176] veyecam2m: disagrees about version of symbol module_layout
[ 10.612908] veyecam2m: disagrees about version of symbol module_layout

Hello,
It appears that my raspberry updated to 6.1 today as a part of a standard sudo apt update process. It appears that the system is unable to load the driver for the video0 device. I have tried to go through the installation steps and copy the 5.15.84-v7+ folder to a new folder named 6.1.21-v7+. The installation did not display an error but the camera does not load after reboot.

ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video0'.
Additional debug info:
../sys/v4l2/v4l2_calls.c(608): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: No such file or directory

Thank you,

@veye_xumm If I was to disable the HDR and denoise features, would that reduce the ISP delay?

@picantepeperoni Hello, I would like to follow up on this topic, any thoughts on the device's expected latency from when light hits the sensor to when its communicated to the host device through the CSI connector? I would expect it to be somewhere around 1-2ms but was wiondering if the processign that is occuring on the PCB is expected to take longer before it runs through the PCB due to buffering and/or processing.

@veye_xumm That is very helpful, thank you. Do you happen to know the device's inherent expected latency? Additionally, are there any options to adjust the camera module's data transmission rate either through frequency or blocksize?

@veye_xumm Hello, I have been able to successfully set the i2c commands and the camera module is working great. Is there any way to increase the FPS that is supported by the module as it appears the module will only output a maximim of 30fps?

Additionally, I would like to know if there are alternative colorspace modes other than UYVY that would provide faster latency and allow for faster processing on my raspberry pi device.

@veye_xumm Okay, I think I fixed the issue with low FPS by running it through multiple threads, I seem to be getting a pretty consistent high framerate and low latency.

However, I wanted to know how I can issue commands to the i2c when using the v4l2 driver. Does it have to go thorugh the gstreamer commands or is that something that I issue like normal through the legacy interface? Do I still need to have i2c enabled thorugh Raspi-config?

Thank you,

@veye_xumm Hello, I think I have solved the problem by switching to the v4l2 driver and running the command :

gst-launch-1.0 v4l2src io-mode=dmabuf device=/dev/video0 ! "video/x-raw,format=(string)UYVY, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! v4l2convert capture-io-mode=dmabuf output-io-mode=dmabuf ! autovideosink sync=false -v

However, I have a new problem where I am only getting 5 FPS to be displayed trough the HDMI out. I beleive that this is related to the debayer/conversion from Raw UYVY format to the HDMI output as when I run the FPS test:

gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! videoconvert ! fpsdisplaysink video-sink=fakesink -v

It will show a solid 30 FPS. Also when I run the command for including the timestamp, the framerate is much better, probably because it is down converting to a 640x360 format.

As such, is there some way that I can efficiecntly convert and output the Camera feed to HDMI?

Thank you,

@veye_xumm I can take pictures of my monitor but they will look exactly the same after changing the IO configuraitons. Is there a functionality to display the IO configurations and sensor attributes over the camera feed? For example, can I see the current AGC and shutter speed on the camera output?

@veye_xumm Thank you, that was helpful. Maybe I have a problem with my configuration or the preview method that I am using to display does not use the configurations becuase I dont see much of a difference for denoise, AGC, and lowlight regardless of the settings I use. Do I need to move to the v4l2 driver?

Re: Best Settings for Night Time

Hello,
I would like to follow up on this past topic. I would like to understand what are the best nighttime settings through the IO Config tools. Currently I am using the VEYE-MIPI-IMX462 on a RaspberrPi 3B and displaying the output with HDMI output preview window ./veye_raspipreview -t -1

I have tried to adjust the following IO configurations:
wdrmode = 0x03 (Enabled)
denoise = 0x0 (Disabled)
agc = 0x0 and 0xF (0x0 seems to be a direct output with higher noise, 0xF appears to apply some sort of noise reduction but no change in gain from what I can tell but I would think 0xF would be best?)
lowlight = 0x1, 0x9, 0x11 (No difference from what I can tell but I would think 0x1 would be best?)
mshutter = 0x40, 0x4C, 0x52 (No difference from what I could tell but I would think 0x52 is best?)

help would be greatly appreciated. Am I missing addtional settings?
Thank you,