I am a software engineer of the VEYE team and will try my best to help you.
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.
@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
@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 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 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.
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.
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
@joe said in VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected:
Questions:
What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?
Under normal circumstances, as long as the I2C communication is working, the /dev/video0 node should be generated properly. Based on my initial assessment, your issue likely stems from differences in the usage of MIPI CSI pins between the J401 carrier board and NVIDIA's official developer kit when paired with the Orin Nano core module. Since our DTBO is based on the device tree of NVIDIA's official developer board, it may not be fully compatible with the J401 out of the box. You can try analyzing the full dmesg output to identify any errors. I suggest reaching out to Seeed for further assistance on this issue.
@golden0514 你好。
我们相机有一个底层逻辑，fps参数会优先于曝光时间设置。
如果你想要1秒的曝光时间，需要先将帧率设置为1帧/秒，然后再设置曝光时间即可。
@mv
It appears that the camera was successfully probed on i2c-10. Next, you can refer to Part 9 and Part 10 in this link to try capturing images.
You can also try using veye_viewer.
@myzy said in 请教IMX287M驱动移植到RX3588的操作:
如果没有linux驱动的基础的话，不建议做这个工作。有一定的门槛和难度。
你的主板是什么型号的？
需要首先编译你主板的系统，然后在系统中增加我们摄像头模组的驱动，做出新的系统。
@golden0514 你可以进一步将fps设置小，相应的最大曝光时间也会拉长。
@golden0514 这篇文章没有修改曝光时间的东西吧？ 有设置格式，分辨率，帧率，取图相关的内容。