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.
@mca312
Hello, I'm glad to receive your request.
To be honest, we currently don't have plans for these two sensors. Their high frame rates exert significant pressure on the computational speed of embedded platforms.
Regarding the IMX273, if we decide to proceed, we should be able to develop it quite quickly. The primary concern remains the demand.
I'd be happy to discuss this further with you.
@natzguk We've already obtained the Raspberry Pi 5, and we estimate that the driver will be released next week.
@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.
@mca312
Hello, we haven't provided precompiled files for this version yet. Please follow our instructions in the documentation to compile it yourself.
https://github.com/veyeimaging/raspberrypi_v4l2
@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
@vitob
I've posted the drivers for Orin nano and Orin NX for Jetpack 6.0 as well as the supporting materials. Please refer to the following link.
https://wiki.veye.cc/index.php/Nvidia_Jetson_Application_Note_Index
@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.
@vitob said in NVidia Jetson Jetpack 6 support?:
In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.
These driver changes add support for RAW8 RAW10 RAW12 data types on the one hand, and externally triggered modes on the other.
Their code reference:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/kernel_patch_4_mv/l4t-r36.3
Compile step by step reference:：
https://wiki.veye.cc/index.php/VEYE_CS_Camera_source_for_Jetson
@ess
Our company discussed and decided to bring this forward. It is expected that the version will be available to you within 10 days.