Luckfox Forums

Current Flow:
MCU(PIR trigger) → 5V_ON → Pico Pi A W boots → MIS5001 photo → SD card → 5V_OFF → MCU sleep

GOAL: PHOTO CAPTURE within 200ms from PIR detect
t=0ms: PIR motion detected
t=50ms: Pico Pi A W 5V enabled, booting
t=200ms: Photo captured + SD stored

Hardware:
- Luckfox Pico Pi A W RV1106G3(256MB RAM, 8GB eMMC, WiFi6)
- MIS5001 CSI camera
- 12V 1A power supply → MCU controls 5V rail for Pico Pi A W
- SD card always inserted

Questions

1. Can Pico Pi A W RV1106G3 boot + MIS5001 photo complete in 200ms total?
2. Fastest measured boot-to-first-frame time on Pico Pi A W?
3. GPIO input pin → immediately triggers camera pipeline?
4. ISP/Camera initialization - typical startup time to first JPEG?

Priority: Photo capture timing ≤ 200ms from PIR trigger is requirement.

Anyone measured Pico Pi A W RV1106G3 boot + MIS5001 first frame time?

Hi,
Your question falls under the category of secondary development. It requires independent design and verification. We have not conducted any relevant tests.
From what we can share:
1 Achieving full boot + MIS5001 initialization + first frame capture within 200 ms is very challenging. It would require a dedicated fast-boot image with optimized camera initialization. Even then, it is marginal and not guaranteed.
2 In such a short time window, the ISP (e.g., AE) may not be fully initialized, so the captured frame could be very dark or unusable.
3 A more practical approach is to keep the camera pipeline running continuously, and use the PIR trigger only to save a frame. In this case, capturing and storing an image within 200 ms is achievable.

Currently, we are using AOV (Always-On Vision) mode, which gives us a boot time of about 6–8 seconds.
In sleep mode, the board consumes approximately 0.3 W.

Our target is to reduce the sleep-mode power consumption to below 0.2 W.

Any suggestions or recommended configurations to achieve lower power consumption would be appreciated.

We have no experience or development plans regarding AOV and suspend-wakeup functions. Issues related to these areas are not covered by our technical support, as we have clearly informed you in previous topics