@veye_xumm could you please tell if there are any updates?

Hi @veye_xumm ,
Thank you for all your help, I was able to get the camera to work. I have some follow up questions:

Can I use the commonly available RPi-zero Mipi camera FPC to connect the camera to Jetson Orin NX? Currently, I am using the (22pin-to 15pin) cable that came with the camera, but I need bit more distance between the camera and Jetson. I am wondering if I can use the commonly available RPi 22pin-to-15pin CSI cables of if the camera configuration on your camera is different. Mine came with ADP-MV1-V2.

I need to get the best low light performance possible (the most important point is that a human observer can see more things, even if image is noisy). After experimenting, so far I have come up with the following for my "night mode":

****** Low light night time auto settings ****
./mv_mipi_i2c_new.sh -w fps 15 -b 2 -> Can't be done while in acquisition
./mv_mipi_i2c_new.sh -w gammaenable 1 -b 2
./mv_mipi_i2c_new.sh -w aemaxtime 500000 -b 2

Following so that gain stays maximum and auto function only reduces exposure time If not, the default algo will reduce gain first, then exposure time (not best for fast moving objs?)
./mv_mipi_i2c_new.sh -w gainmode 0 -b 2
./mv_mipi_i2c_new.sh -w mgain 24 -b 2 Now we can set the exposure quality by changing just one parameter (can be changed on the fly - 40 seems a good all around value at night for dark n bright situations) Adapts well to changes in lighting and doesn't over expose in ample light, while still giving max gain in dark Since gain stays fixed at 25db (noisier), it should only be used in night time
./mv_mipi_i2c_new.sh -w aatarget 40 -b 2

My question: Is there anything else I can do to increase the low-light performance? Did i miss another setting that can help?

I do notice that at higher gain the images get these fixed patterns probably due to the FPNU or PRNU of pixel array. Is there a way to do a calibration on the image sensor to make the image response more uniform?

Is there any gstreamer pipeline I can use to get 12 bit image stream out and display it as 8bit in real time?

Best Regards

@veye_xumm sorry for necro-posting, but this method stopped working. on fresh system I have Failed to set I2C address after running make.sh under mv_tools_rpi/sources on rpi5. do you know if something has changed there?

@lozinski Sorry, we currently do not have products that meet your requirements. The VEYE-LVDS-327 has been discontinued for a long time.

@mparem
https://github.com/veyeimaging/rk35xx_orangepi/releases/tag/v1.2_mvcam_tablet_cm5
Please try this image file on cm5-tablet.

@barbanevosa
The issue occurs because the camera sensor outputs a resolution of 3088 × 2064, but the receiving side (V4L2 buffers) aligns each line to a stride of 3136 bytes for memory alignment. When OpenCV is used directly with cv2.CAP_V4L2, it applies the width setting (3088) both to the sensor and to the buffer interpretation. Since the actual buffer has padding (3136 vs. 3088), OpenCV misinterprets the data layout, which results in visible image artifacts (stripes).

We recommend using a GStreamer pipeline to handle the stride and alignment internally, so that OpenCV receives a clean image with the correct resolution.

@veye_xumm 好的 一定

@veye_xumm
Thank you for providing this option. I will review it and follow up if I encounter any issues.

@jhaijun 不好意思我们这个论坛是只针对我们公司自己产品的。 sony 机芯的话确实没有搞过。

@goooofy 好的。

Your current image is Jetpack 5.1.2 with L4T version r35.4.1. The mvcam driver included in it is relatively old, so the mv_probe.sh script cannot work properly. — For more details, you can refer to the comments at the top of the mv_probe.sh script.

081b1526-6747-417e-af94-d33ffbbc08cb-image.png

In addition, please try running the following script and see if it shows continuous messages indicating that data is being received. If it still fails to receive data, please run sudo dmesg to check whether there are any error messages.

export WIDTH=2560 export HEIGHT=1544 export FPS=50 v4l2-ctl --set-ctrl roi_x=0 v4l2-ctl --set-ctrl roi_y=0 v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY v4l2-ctl --set-ctrl frame_rate=$FPS v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null

@golden0514 你好。
我们相机有一个底层逻辑，fps参数会优先于曝光时间设置。
如果你想要1秒的曝光时间，需要先将帧率设置为1帧/秒，然后再设置曝光时间即可。

@veye_xumm 这样啊，好的麻烦您了，我再跟公司里沟通一下

@nian 好的

@nian 不客气

@linoooooo
你好，fps参数是可以修改的。但是需要先停止取图。曝光时间是被限制到1/fps的。 你可以先设置合适的fps，然后在范围内进行曝光时间的修改。

在这个脚本中，带星号的命令，都是取图中写保护的。
你也可以参考寄存器清单中的part1.3来理解这个设置规则。

@fumyang 请问您用的是哪个相机模组？

@veye_xumm Thanks! I'll read and reinstall the SO.
Hopefully, I'll be able to show if the problem is resolved in the next few days.

@dragos You are welcome.