@newleaf Looking at the image you sent, I do think it's an IR cut issue. Could you tell me which aespeed-related command you used to reproduce this phenomenon?

@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

@newleaf BTW, the I2C features are nice and work quite well. Was able to port the code over to Go.

Just wanted to provide a followup on this. Reached out to Seeed and they said they would order a camera and investigate further. I also had some success on the Nano by reducing the cable length between the Nano and the camera (using a CSI-HDMI adapter from Arducam). Worked sometimes on first boot. Then stopped. Regardless, we are nearing a deadline and decided to switch to the Xavier for a prototype. The Nano has been challenging due to reduced support from NVIDIA. I believe you are right about device tree. Something different from first boot compared to reboot. Even with the longer cable, it was 100% consistent with this strange behavior.

@newleaf By upgrading wordpress I think I have solved the problem, please try again.

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

@newleaf You are welcome.