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
@lubertroft
hi,
http://wiki.veye.cc/index.php/CS-MIPI-SC132_version_log
yuyv is supported in this version .
Because it is CS series, of course cs_mipi_i2c.sh is the corresponding script.
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#yuvseq
@consti10 said in Improve DE-coding on snapdragon devices:
turning off the HW decoder for h264 on android doesn't really make sense.
Maybe changing the poc type could fix this issue, too ?
I'm not sure about that.
- When connected via USB (original cable) there can be artifacts (I suspect packet loss via usb or some driver bug)
You are right. This camera will have a probability of packet loss. The higher the cpu performance of the host, the less packet loss.
This problem is still being studied and solved.
- POC type as described above.
@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.
@esjeeybi
About how to compile our drivers on rpi:
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Source_code_cross_compilation
You can get/set FPS, Gain, Brightness, Contrast via:
http://wiki.veye.cc/index.php/CS-MIPI-X_i2c
@ess
Hi, thank you, it is indeed typo.
jetson supports trigger mode, which I have done research on and it has worked. The plan is to organize it and release it along with our new machine vision product line. Estimated 15 days or so.
@jakobvol Sure, you give it a try and let me know if there are still any issues.
@lb said in 关于RAW-MIPI-SC132相机相关问题:
@veye_xumm请问贵司有这几款传感器对应的相机吗？思特威的
这几款暂时还没有产品。
@lb said in 关于RAW-MIPI-SC132相机相关问题:
@veye_xumm 还是关于mcu的，SDA模式下，我猜想两种可能：一是数据先到mcu，mcu再给sensor，mcu只是做了透传。二是mcu和sensor作为i2c从设备直接挂到nx i2c总线上。请问是其中的某个情况吗？还是别的一个大致的概述呢？
后者。
@lb 当然没问题，根本用不了那么大的带宽。
你试试应该继续算下去，10801280120*8bit.
现在sensor的模式配置的是1.188Gbps/lan。
@odu 是这样的，现在opencv的这个demo主要用于演示怎样把图像导入到opencv，是个简单化的demo。不是用于实际应用的范例。
这里面，主要由于使用了纯软件的方法进行图像格式转换和搬运，因此效率比较低。
@jakobvol
Hi,
At the current time, I don't think there's a need for a complicated installation of gstreamer and opencv.
I am using the Raspberry Pi OS with desktop and recommended software version of pios downloaded from the official Raspberry Pi website.
After installing the camera driver and running sudo apt install python3-opencv, I am able to run the samples without any issues.
@lb
我们的设计是这样的：
RAW系列的，mcu不对图像做处理，mipi信号不过mcu。
mcu的存在是为了简化客户的初始化，配置等操作。
SDA模式下，客户可以认为直接掌握了整个sensor的直接控制权。mcu不做任何干预。
