@siderat I think this one will work.

@barbanevosa
Please refer to part8:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson/

@nimadibaj
UYVY 30fps

@nimadibaj said in Veye MIPI imx462 Defaults:

It seems that between each video line, the CSI-2 output from your module enters Low-Power (LP) mode, which causes the video stream to continuously drop in and out.

This complies with the MIPI CSI-2 standard.

@nkos Our driver code is developed based on Radxa's BSP, and the BSP development documentation can be found at the following URL:
https://docs.radxa.com/en/zero/zero3/low-level-dev/kernel

To address the issue you raised, we attempted to set up a Yocto development environment for the Radxa ZERO 3. Unfortunately, we were unsuccessful in this endeavor.

Later, we noticed Radxa's documentation regarding building Linux images with Yocto:
https://github.com/radxa/yocto-manifests

In the "List of Radxa Boards supported" section, the Radxa ZERO 3 is not listed among the supported development boards.

Therefore, we do not recommend using Yocto to build a Linux image for the Radxa ZERO 3.

@veye_xumm
Thank you, I take a some time for tests

@stiwana

@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

Can I use the commonly available RPi-zero Mipi camera FPC to connect the camera to Jetson Orin NX?

Yes.

@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

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

To improve performance in low-light conditions, the main methods are:

Use a lens with a smaller F-number. In either automatic or manual exposure mode, extend the exposure time to the maximum duration you can tolerate. (Note that the exposure time cannot exceed the reciprocal of the frame rate, so you may need to adjust it accordingly based on your specific situation.) Increase the gain.

@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

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?

Sorry, we don't offer this algorithm yet.

@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

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

Sorry, we don't provide this kind of program either.

@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来理解这个设置规则。