@newleaf said in Recommendation to reduce startup latency for IMX327S:

For our system, we utilize 940nm IR lighting at night that is triggered by motion. I noticed that there is a 1-3 second period for the camera to adjust each time if we start streaming when the lighting is activated. The first few images are washed out until AE kicks in. What's the recommended approach to eliminate this latency and the initial washout? Should we explore manual exposure and gain? Thx!

You can try configuring aespeed first, and then try manual mode if that doesn't meet your needs.
https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#aespeed

@zoldaten Approve

@lin said in 编译veye_mvcam.ko报错:

RKMODULE_CSI_INPUT

forlinx的kernel源码不支持RKMODULE_GET_CSI_DSI_INFO这个宏定义，可以注掉代码。

@lin 是的。
不过你要是用视频流模式当然可以咯。

@joe The software part of the work seems fine. Next, we need to check if the hardware connections are correct, paying particular attention to the orientation of the FFC cable.

@lukapercic The number of pins and the spacing of the connectors are different, so I believe they cannot be directly connected together.

@veye_xumm ok thank you. We'll try generating an external trigger and seeing how things sync up. We will follow up with more questions if we have any.

@veye_xumm 感谢感谢

针对RTSP这个，一般只需要一个rtspd服务器就行，可以移植live555，或者直接用gstreamer的rtsp服务器插件，甚至可以直接用ffmpeg进行rtsp推流，接收的时候，用vlc即可。

@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

@liubo1999

读取0x0424寄存器地址的数据全是0x00,请问是不是我设置的报文发送的不正确？举个例子，数据类型是bool的数据，我可以发一个字节作为设置值吗？还是说必须一次设置4个字节？

所有数据类型，都是必须使用4个字节的。

还有一个问题，就是说，如果成功设置成为“MCU bypass mode”模式后，是不是仍然在当前的I2C总线上与传感器通讯？MCU只是作为透传功能是吗？

设置之后，电路上外部与sensor的i2c通信不经过mcu，是直接联系的。i2c地址也是各自sensor的地址了。

@国电富通 可以找一下网上开源的rtsp， 在板子实现一个rtsp server 然后电脑用vlc访问

@veye_xumm

The feedback from this link below is the same as your problem, and although it is in Chinese, the images in it are informative.
https://forum.veye.cc/topic/187/veye-mipi-imx385在新版raspberry-pi-zero-2-w上无法使用

I'll list the points to use:

Use a separate 5V supply. On the raspberry pi zero 2w, the power on enable pin for camera, needs to be executed separately: raspi-gpio set 40 dh

Once this is done, the camera can be detected on the i2c-10 bus.

i2cdetect -y 10

The 0x3b device can be detected and the script can read and write camera parameters now.
After completing the above steps, you can use the veye_raspicam series software normally.

@mca312 You are welcome.

@jose5000
Please run the commands from part3.7 of this link and post the results here.
https://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2#Are_Image_and_DTB_upgrade_successful_.3F

@veye_xumm Thank you. And agreed, it's heat transfer. Everything is stable and works great. Good to know it's normal.

@nimble99 Hi, this board won't work for you. It's a IR lamp running a full duty cycle.

@lizi 你好，我们这个相机本身是黑白的，只有一个通道。 驱动输出的数据也是单通道的。 你的意思是进入opencv现在是三通道模式的？ 不好意思，这个我们对opencv的确不太熟，这方面需要再研究。

@canglin 默认是discontinues模式。

@vaa said in New Raspberry pi 5 support:

@veye_xumm
In case I try to set pixel_format to any other value is cause VIDIOC_STREAMON fail. I suppose this is a bug in the driver.
Some other applications like gstreamer only set pixel_format if you directly point to do this, this is why it works, but many others (e.g. trying to set default pixel_format) are not.

Will you going to fix the issue?