VEYE IMAGING Forum

veye_xumm

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.

veye_xumm

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

veye_xumm

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

veye_xumm

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

veye_xumm

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

veye_xumm

@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

veye_xumm

@etale_cohomology

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

veye_xumm

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

veye_xumm

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

veye_xumm

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

veye_xumm

@mparem
Since I don't have the tablet board here, the following is just a suggested approach based on my guess. You can try commenting out the following two lines or modifying them as shown below:

clocks = <&ext_cam_ov5647_clk>;  
clock-names = "xvclk";

veye_xumm

@mparem said in OrangePi cm5-tablet RAW-MIPI-SC132M:

his is the decompiled dts, which I modified (set i2c address to 0x3b and changed compatibility to veye,mvcam), compiled, then moved back into /boot/dtb*/rockchip/rk3588s-orangepi-cm5-tablet.dtb (faster than recompiling with orangepi-build)

I haven't used this method before, and I didn't quite understand your source code.
Now it seems the issue might still be with the DTS. I suggest you try editing the DTS source code using conventional methods.

veye_xumm

@mparem
Please post dmesg | grep mvcam output here.

veye_xumm

@mparem
Because on the RK platform, the mvcam driver needs to be built into the kernel, it will not appear in the lsmod list.
Please send me your current DTS and the related error so I can take a look.
The cam2 interface on the tablet corresponds to dcphy0 and i2c6, which is correct.