Timeline for What is ~delay after picamera2.capture_file code until sensor data is captured on Pi Camera Module 3?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2023 at 10:12 | comment | added | Vadim | Sounds like you need some more sophisticated way to trigger your cameras or even a different hardware concept. With Raspberry Pi you are controlling the cameras with software and Linux is not a real-time operating system, meaning getting timing below 10ms will be a challenge if possible at all... | |
| Mar 22, 2023 at 19:05 | comment | added | Tree Sesame | Thank you. The reason I'm asking is I'm building an array of cameras for photogrammetry and synchronization is important. My trigger is a falling edge that arrives at all cameras synchronously. In a little test of two cameras viewing the default Android stop watch on a Pixel 7 phone (perhaps 90 Hz update; I know the screen update rate is an issue), I observe delays in the two captured images of at minimum about 10 to 20 ms (perhaps! given the phone screen). In one instance the delay between images was a whopping 5 seconds! I'll post a more targeted question about how to minimize this delay. | |
| Mar 19, 2023 at 19:12 | comment | added | Vadim |
I guess the time it take is roughly exposure time + readout time + file IO
|
|
| Mar 18, 2023 at 4:01 | history | asked | Tree Sesame | CC BY-SA 4.0 |