@nkos Cheers!

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

@nimadibaj You have implemented the function of writing 0xff to 0x000b. Similarly, proceed to write the subsequent registers as well. The method for writing the subsequent registers is the same as that for writing the 0x0b register, but they must be written in sequence. Addr--->data 0x10 0xDE 0x11 0xC2 0x12 0x00 0x13 0x00

@veye_xumm Hello my friend. We are sending I2C commands via a FPGA. 1_ Writing 0xff to 0x000b solved our problem. Thank you. Please give us a command to save this change. 2_ We are trying to change video frame rate (now is 30fps and we need 25fps). by these commands we cannot do this : 0x10 0xDE 0x11 0xC2 0x12 0x00 0x13 0x00 (sending Two byte, then sending next two byte and ... ). Please guide me. Thanks a lot.

@deepcamera Only ISP-related parameters can be persistently saved after power-off through the paramsave command. Therefore, I recommend that you reconfigure your desired parameters in the startup script during program design. As for which commands can be saved, you can refer to the veye_mipi_i2c.sh source code. If the corresponding read/write functions contain operations like './i2c_write $I2C_DEV $I2C_ADDR 0x10 0xDA', it indicates that the function's register belongs to the ISP category and can be saved using paramsave.

@lpcq2000 抱歉现在MCU bypass模式已经不再被支持了。我们的资料有一些迟滞，回头会更新到上面。

@siderat I think this one will work.

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

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

@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 好的 一定

@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. [image: 1752745646927-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 不客气

@linoooooo 你好，fps参数是可以修改的。但是需要先停止取图。曝光时间是被限制到1/fps的。 你可以先设置合适的fps，然后在范围内进行曝光时间的修改。 在这个脚本中，带星号的命令，都是取图中写保护的。 你也可以参考寄存器清单中的part1.3来理解这个设置规则。