@macdaddyfpv

I was thinking that since you took it from a dual board down to a single board that you may be able to reduce the board size and break it out into 2 again to fit everything.

Yes, we have the ability. However, the decision to make a new version of model is more of a commercial consideration. We are now more focused on developing new sensor and new products.
I will seriously discuss your suggestion with my colleagues in the company.
Thank you for your approval and feedback.

@radiohound As far as I know, sony's datasheet is only open to corporate customers who have signed an NDA.

@fancong
请参考：
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/tag/v1.29

@tokabe
Hi,
On i.MX8m Platform, our roadmap is based on SOM board. For now, we have finished MYIR i.MX8m board and AVNET Maaxboard(mini) board.

http://wiki.veye.cc/index.php/NXP_i.MX_Application_Note_Index

The coral.ai board from google is in progress.

So the linux version we use now depends on the system version that comes with the SOM board.
We have a V5.y version driver on raspiberry PI, maybe this will help you.
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi

Of course, we will transplant all product drivers, including CS-MIP-IMX307, to i.MX8m. This work is also in progress.

@desperex said in Please advise compatible mono camera:

About two or three years ago, we tried to connect VEYE series products to rk3399, but at that time there were some problems with its BSP.
Recently we restarted the development plan for rockchip chips.
The first thing we are doing is to connect VEYE series to firefly's RK3566 board. Now the development has been completed and we have made http://wiki.veye.cc/index.php/ADP-Tfirefly. This board is already online for sale.
Next, we have to create the adapter board for MV series to ROC-RK3566/8-PC and develop it.
As for the two boards you mentioned, the rk3399 chip is too old and we have no plans for now.
Orange Pi 5, we have not studied it before. I will submit it to our R&D department.

@nimadibaj
0x3b
This camera has isp module, so you can't control the sensor directly. please refer to the following code.
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/
https://github.com/veyeimaging/raspberrypi/blob/master/i2c_cmd/bin/veye_mipi_i2c.sh

@etale_cohomology

1. If your IMX287 is running in stream mode, please use the upgrade package from the following link for the upgrade：
   https://www.mediafire.com/file/d4yjibcjp1hw8z8/MV-MIPI-IMX287M_C1.37_L2.04_20240306_beta_upgrade.bin/file
2. The camera will generate its own strobe synchronization signal. I suggest using this signal to drive your LED instead of using the Raspberry Pi's IO. For more details on the principle, please refer to the following link:
   https://wiki.veye.cc/index.php/Mv_mipi_camera_manual#Strobe
3. On the ADP-MV1 board, the J3-5 pin will output the strobe signal by default.
   https://wiki.veye.cc/index.php/ADP-MV1_Adapter_Board_Data_Sheet/zh

@mca312 said in IMX287 FPS:

The FPS is listed at 319 but the sensor supports 523. Can I set the ADC bit to 8 to achieve this? 319 is for 12 bit.

We have achieved a frame rate of 720×544 @ 530fps RAW8 in our new firmware version.
https://wiki.veye.cc/index.php/MV-MIPI-IMX287M_Data_Sheet

@mca312 said in IMX287 FPS:

I would also like to mount a CS lens or an M12 lens. What is the dimension needed for the lens mount?

Feel free to provide a note when placing your order, and we'd be happy to gift you an M12 holder.
Regarding CS lenses, unfortunately, they are not supported at the moment. We have a C-MOUNT01 which is compatible with C-mount lenses. You will need to purchase it separately.

@nimadibaj

@nimadibaj said in VEYE-IMX462 Video Format:

1_What is the actual video format?

UYVY

@nimadibaj said in VEYE-IMX462 Video Format:

3_What is the Line Rate of camera?

594Mbps

@nimadibaj said in VEYE-IMX462 Video Format:

2_What is the pixel-per-clock rate?
Should be 594Mbps *2 , Because we have 2lans.

@nimadibaj said in VEYE-IMX462 Video Format:

4_Is there a sample code for XILINX FPGA to receive VEYE-MIPI-IMX462 video output?

Sorry, we don't have the corresponding demos right now.

@etale_cohomology

@etale_cohomology said in IMX-287M: How to synchronize video frame capture with an LED?:

./mv_mipi_i2c.sh -r -f trgexp_delay -b 6
./mv_mipi_i2c.sh -r -f trginterval -b 6

In video streaming mode, these two parameters do not take effect. The camera will output the strobe control signal based on the actual exposure time, whether it is in manual exposure mode or automatic exposure mode.

@stiwana

1. The MV-MIPI-GMAX4002M model was missing on this page and has now been added. Both Jetpack 5.1 and 6.2 are supported. However, we currently only provide the 4-lane mode DTB for Orin NX and Orin Nano under JP6.2 mode, as only these two boards have official baseboards that expose the 4-lane interface.
3. You're right. Just place the order using that link. We will ship ADP-MV1-V2.
4. For Jetson Xavier NX, since the official baseboard only exposes 2 lanes, the DTB in our provided driver remains configured for 2-lane mode, which limits the maximum frame rate.
   As for Orin NX, there is no such restriction. You can refer to the 4 How to Use 4-Lane Modesection to enable 4-lane mode.
5. yes.
6. The MV series products feature ISP (Image Signal Processor) capabilities, including typical functions such as auto-exposure, LUT (Look-Up Table), and more.

@israel_bolo Actually, for the development of new projects, I would recommend using the V4L2 mode, which is the material from the link below.
https://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi

@israel_bolo

May I ask which version of piOS you are currently using? The libdmipicam mode is only suitable for the 32-bit legacy mode of piOS.

@dragos You are welcome.

@dragos
I think the MIPI CSI interface on this board only exposes 2 lanes and uses a 15-pin connector.
Could you check your board to see if that's the case?

@dragos May I ask if the board you're using is an official NVIDIA development board or a compatible third-party board?

@linoooooo 你好，我们的相机内部isp流程是没有整帧缓存的，相机本身引入的delay是毫秒之内。
我觉得你这个延时主要是v4l2取图缓存和显示缓存的缘故。不过说实话SDL库我们不太懂，怎样优化需要您自己研究一下。
至于相机采集后，您这边程序直接导入算法的话，延迟肯定要比这种测量方法小的多。

@israel_bolo
I see some warnings, but no errors. could you please continue and see if it compiles?

@otca
The camera is now successfully probed, which confirms that both the I2C and the enable pin are functioning correctly.
The current issue indicates that the I2C control channel is working, but the MIPI CSI data channel is not. Please verify whether the MIPI CSI interface pin assignment on this carrier board matches that of the official Orin NX development board.
The Device Tree Source (DTS) should be adjusted accordingly to match the carrier board.

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