@sanlu

@veye_xumm Hi, Firmware update does not solve the problem, after software reset auto exposure mode works normal

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

@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.

@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.

@stiwana Sorry, we do have this in mind, but no actual plans or projected time of completion at this time.

使用脚本可以，感谢

@veye_xumm Thank you, graet news

@veye_xumm Perfect. Now is working as expected. Thanks!

@victor Sorry for the late reply. After communicating with the sensor manufacturer, I found that the built-in temperature sensor in the SC130GS is extremely inaccurate and cannot be used properly.

@zang 相机是支持这个分辨率配置的。你的整个操作报什么错误吗？ 可以用mv_mipi_i2c.sh脚本读取一下相机实际roi确认是否已经配置到camera里面。 另外300不利于对齐，你可以试试304

@alex_ai said in IMX462M pixelformat on RPi5: I need wait for clear sky to test and provide feedback Finally tested, for gain value 20 it is looks pretty same with color sensor with ISP, but background no so black as for color sensor. For me this issue resolved, attached examples to compare (10 seconds stacks) IMX462 mono [image: 1723360275505-imx462m_small.jpg] IMX462 color with ISP [image: 1723360306335-imx462c_small.jpg]

@nb 您好，我遇到了类似的问题，请问一下您的解决方案就是将4.6的opencv更换成4.2的opencv吗？

@dan Please try this image. export I2C_BUS=7 export WIDTH=1280 export HEIGHT=1024 export FPS=108 media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']' v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null [image: 1721129322062-93427bda-d9b6-4263-be24-30aac77b3df5-image.png]

@xym 可能是pipeline效率的原因，buffer不够用导致丢帧了。

@veye_xumm Thanks, this should be enough I think

@nb https://wiki.veye.cc/index.php/Mv_mipi_camera_manual/zh#Sony.27s_Global_shutter.EF.BC.88.E5.85.A8.E5.B1.80.E6.9B.9D.E5.85.89.EF.BC.89 2.4.3

@veye_xumm 好的 感谢