@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

@otca
"You did the right thing.
The Jetpack 4.6.5 version of the kernel does not yet support the MV series cameras.
Please switch to Jetpack 4.6.4 for your operations.

@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

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

@jhaijun 不好意思我们这个论坛是只针对我们公司自己产品的。 sony 机芯的话确实没有搞过。

@joe Sorry for overlooking the information in the earliest post. I think the board in the link below is suitable, as it is compatible with the official nVidia development board.
https://www.alibaba.com/product-detail/Nvidia-jetson-orin-nano-development-board_1600993126148.html?spm=a2747.product_manager.0.0.61e871d2RIVAmD

@flaty 不客气。

@mparem https://github.com/veyeimaging/rk35xx_orangepi/releases
please try the latest image or deb packages.

@flaty 这些报错都不用管。 我们的模组不需要这些供电。

@flaty
正常来说，你只要在这个文件的基础上做如下修改：
//open this line to enable v-by-one hs link
//#include "rk3588-roc-pc-vbyone-overlay.dtsi"
#include "rk3588-roc-pc-cam-veyecam2m.dtsi"
//#include "rk3588-roc-pc-cam-veyemvcam.dtsi"

@joe
Regarding the I2C issue with the J401 baseboard, we have previously resolved it, and the engineers at Seeed Studio have documented the solution on their wiki. Here are two links for your reference.

https://wiki.seeedstudio.com/Solution_for_the_Compatibility_Issue_between_reComputer_and_VEYE_Camera/

https://forum.veye.cc/topic/539/imx327s-with-recomputer-xavier-nano/10

@flaty 就是这个。

@flaty 可以的。

@flaty
参见代码的注释，你的内核缺少这个接口，需要注掉这个函数。