Posts made by veye_xumm

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

@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驱动的基础的话，不建议做这个工作。有一定的门槛和难度。
你的主板是什么型号的？
需要首先编译你主板的系统，然后在系统中增加我们摄像头模组的驱动，做出新的系统。

@nian 好的

@golden0514 你可以进一步将fps设置小，相应的最大曝光时间也会拉长。

@golden0514 这篇文章没有修改曝光时间的东西吧？ 有设置格式，分辨率，帧率，取图相关的内容。

@golden0514
可以参考这篇文章进行取图。
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi/zh

@golden0514 你的嵌入式平台是什么？

@nian
你说的对，我们现在还没有那么高的ADC精度的产品。
你的使用场景，动态范围很宽？ 用长短曝光时间来辅助解决可否？

@nian
12bit模式，相机是支持的。但是你现在只可以将其保存为文件，并手动转换为可以方便用软件读取的格式。你可以看一下这个文章part7，尤其是part7.5的部分

14bit这个，我们现在相机还不支持。sensor是有的，我们没有做这个格式。

@nian 不客气

@nian

@nian said in 有一些错误 ，大神们 请指教啊raspi5 +imx78:

但是veye_vbyone不能用 是不是可以忽视往下进行？

是的。
请更新一下最新的github上的media_setting_rpi5.sh，应该就可以解决你现在的问题。

@linoooooo
你好，fps参数是可以修改的。但是需要先停止取图。曝光时间是被限制到1/fps的。 你可以先设置合适的fps，然后在范围内进行曝光时间的修改。

在这个脚本中，带星号的命令，都是取图中写保护的。
你也可以参考寄存器清单中的part1.3来理解这个设置规则。

@fumyang 请问您用的是哪个相机模组？

@stiwana

1. The MV-MIPI-GMAX4002M model was missing on this page and has now been added. Both Jetpack 5.1 and 6.2 are supported. However, we currently only provide the 4-lane mode DTB for Orin NX and Orin Nano under JP6.2 mode, as only these two boards have official baseboards that expose the 4-lane interface.
3. You're right. Just place the order using that link. We will ship ADP-MV1-V2.
4. For Jetson Xavier NX, since the official baseboard only exposes 2 lanes, the DTB in our provided driver remains configured for 2-lane mode, which limits the maximum frame rate.
   As for Orin NX, there is no such restriction. You can refer to the 4 How to Use 4-Lane Modesection to enable 4-lane mode.
5. yes.
6. The MV series products feature ISP (Image Signal Processor) capabilities, including typical functions such as auto-exposure, LUT (Look-Up Table), and more.

@israel_bolo Actually, for the development of new projects, I would recommend using the V4L2 mode, which is the material from the link below.
https://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi

@israel_bolo

May I ask which version of piOS you are currently using? The libdmipicam mode is only suitable for the 32-bit legacy mode of piOS.

@dragos You are welcome.