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

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

2. 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?

3. 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?

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

Hi @veye_xumm

I purchased the MV-MIPI-GMAX4002 camera with ADP-MV1-V2 adapter.

My setup is Jetson Xavier NX 8GB developer kit running nvidia-l4t-core 35.6.1.

I documented my "installation" process on the Jetson as following:

*** Get latest veye BSP:
wget https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tar.gz
tar -xzvf nvidia_jetson_veye_bsp.tar.gz
cd nvidia_jetson_veye_bsp/

*** Find and extract the correct kernel image (mine is l4t_r35.6)
cd kernel_image/
tar -xzvf Image_l4t_r35.6_mvcam_patched_signed_4_xavier_orin.tgz

*** Make a backup of Old boot Image:
sudo cp /boot/Image /boot/Image.backup
sudo cp /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.backup

*** Copy Image files from extracted image folder to boot folder:
sudo cp Image/Image /boot/
sudo cp Image/Image.sig /boot/

*** Go back to main BSP extracted folder:
cd ..

*** Copy camera drivers (Jetpack 5.x)
sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f

*** Register the modules into the system:
sudo depmod

*** Copy the New Device Tree Blob (DTB) for MV cameras, my board (Xavier NX 8GB dev kit)
sudo cp dtbs/Xavier-NX/JetPack_5.1.4_Linux_JETSON_XAVIER_NX_TARGETS/dts\ dtb/MV-MIPI-CAM/tegra194-p3668-0000-p3509-0000.dtb /boot/

*** Update the bootloader CONFIGURATION
sudo nano /boot/extlinux/extlinux.conf

*** I copied the last configuration and modified it with name of my dtb file manually as following:
LABEL VeyeIO
MENU LABEL Custom Header Config: <VEYE MV-CAM Dual>
LINUX /boot/Image
FDT /boot/tegra194-p3668-0000-p3509-0000.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=4210ce41-79b8-4264-8716-c03322463d38 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 video=efifb:off nospectre_bhb nv
-auto-config

*** Then I pasted(appended) it to end of the .conf file

*** I also changed the second line in file to set new config as default:
DEFAULT VeyeIO

*** Reboot board:
sudo reboot

After this i powered off the Jetson, and connected the camera to the MIPI port, taking care of the MIPI cable directions (I took pictures..I will upload later from the phone). I also connected the 5V from the Jetson Xavier NX(pin4 for 5V, pin 6 for GND) to the ADP-MV1-V2 board. Anyway, after powering on the Jetson, I don't see any sign of the camera either with ls /dev/vid* or even if i do: sudo dmesg | grep "veye"

Can you give me some pointers where I may be going wrong??

@veye_xumm
Thanks so much for your answer. I am very glad I asked you this question. Of the latency is 1ms as you mention , then the rest looks suitable too. I will buy some to test.

Some follow up question:

1. With the MV-MIPI-GMAX4002 camera on Jetson, can I also use the camera inside a gstreamer pipeline (and also maintain the low latency)?
2. For the lowest latency and deterministic performance (the application will need to know exactly when the frame was acquired), what would you suggest with these cameras...use from opencv or gstreamer, or does it not matter? Any other tips you can give me for very low latency, real time performance with the MV cameras?
3. What's the usual lead time to buy these cameras in case the cameras are out of stock when purchasing (from a supply chain point of view when my device is in production)
4. How many years do you plan to keep these camera modules available for?

Best Regards

Hi @veye_xumm
I have an application that needs a very low latency (<10ms at maximum. Even less if possible) from capture to being available to the Jetson for real-tim processing. I read in some posts on the forum that veye cameras have more than 100ms latency due to ISP. In that case, is there any VEYE camera that I can still use? My requirements are:

• Bigger pixel size for low light capture (the GMAX4002 seemed decent)
• High frame rate (at least more than 60fps)
• Ability to use a physical trigger signal
• Very low latency (<10ms, even less if possible).

Please guide me if there are any VEYE cameras which will satisfy my requirements. Thank you.

Hi,
I am considering using VEYE cameras in a product line. Before I buy, I just want to clarify few things:

1. Can you confirm that MV-MIPI-GMAX4002M camera is supported by Jetson Jetpack 5.1 and 6.2? I ask because this camera is not listed on the wiki page:
   https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson

2. I would prefer to get the adapter with the 22 pin RPi interface, which I believe is the ADP-MV1-V2 board. However, I don't see a purchase link. On the Aliexpress page for MV-MIPI-GMAX4002M, it is not clear if it ships with the ADP-MV1-V2 or ADP-MV1 version adapter.

3. On the Aliexpress page for MV-MIPI-GMAX4002M camera ( https://vi.aliexpress.com/item/1005008643965893.html? ) if I choose the GMAX4002M ADP-MV1 variant, does it ship with the ADP-MV1-V2 variant of the adapter board? Also, is the C mount adapter included or do I need to buy separately?

4. Is there any issue or limitation I need to be aware of when using the MV-MIPI-GMAX4002M with Jetson Xavier NX and Jetson Orin NX? My application requires use in Freerunning and triggered modes, with using ROIs, and my application requires high frame rate (~200fps or more).

5. To me, this camera seems the best in high low-light sensitivity (big pixel size!). Is this a correct assumption among the Machine Vision or Raw series cameras?

6. What is the main difference between the MV series and RAW series cameras? I couldn't figure out the differences.

Sorry for the very long questions...I just want to make sure the camera fits my needs before I do any purchase.

Thansk and Best Regards,
Saad

I came to the forum asking exactly for this. It would be great to have some color cameras for Machine Vision. I see that the last answer was a year ago..by any chance the plans have changed?

Hi,

Thank you for your response. Ok, understood about no support for 720p60.

Alternatively, we could probably use 1080p30 also (need to look further and discuss with team). We could probably crop to our required image size inside the FPGA. 60fps is not critical.

To that end, I have few questions:

1. Is it possible to output HDR imagery over the MIPI interface (IMX327S/IMX385/IMX462) or do we need to do it inside our own fpga?
2. Is the I2C command set open, such that we could do the camera module configuration from our baremetal application?
3. Can you confirm my understanding that in this case our FPGA will be talking to the onboard ISP chip on your camera board over I2C, and not directly to the camera.
4. Roughly how much is the added latency due to your onboard ISP on the boards?
5. The auto exposure and white balance will be handled by the onboard ISP, and will not need to be handled by our FPGA, correct?

Thanks.

Hi,
I recently came across the VEYE cameras and they seem to show potential for a product that we're working on. We need to use the cameras with our own FPGA board with a RPi style 15 pin MIPI CSI2 connector.

Our main requirements are as follows:

• MIPI CSI2 interface (15 pin) compatible
• Very good low light performance
• Able to support 720p60
• Auto Exposure/White balance (camera internal)
• In-camera HDR if possible
• I2C sequence of commands to start the camera in above settings. We don't necessarily need the datasheet if we can just get a list.

I have seen your cameras based on IMX385, IMX327 and IMX462, however they only state 1080p30 as the output resolution. I am wondering if they are also configurable in 720p60 output mode with above options (Auto Exposure, HDR)?
Kindly help guide to the correct module.

Thank you.