Understanding the different recording modes of your BlackVue dashcam helps ensure you capture all important footage—whether driving, parked, or during specific incidents. Here’s how each mode works and when it activates:
Overview of Recording Modes
| Mode | Purpose | When It Activates | What Is Recorded |
|---|---|---|---|
| Normal | Continuous driving recording | When vehicle ignition is ON/moving | All driving activity in loops |
| Event | Incident/impact/motion-based recording | Whenever an impact or trigger occurs | Clips of incidents (buffered) |
| Parking | Surveillance while parked | After 5 minutes of inactivity or ignition OFF | Motion or impact while parked |
1. Normal Recording Mode
- How it is triggered: Activates automatically the moment your vehicle's engine starts and active power is supplied to the camera's 3-pole DC input port.
- LED Indicator: The front REC LED remains Solid Red.
- How it works: The dashcam records continuously in 1-minute video segments, looping indefinitely. Once the microSD card reaches full capacity, the oldest "Normal" files are automatically overwritten to make room for new footage.
2. Event & Smart Event Recording Mode
- How it is triggered: Triggered automatically when the built-in 3-axis G-Sensor (accelerometer) detects a physical impact, sudden shock, or extreme vibration while driving. It can also be manually triggered at any time by touching the capacitive Touch Sensor on the rear face of the front camera body (replaces the proximity sensor on legacy models).
- How it works: To ensure you capture the complete picture, Event files utilize a 10-second pre-event buffer . When a shock is detected, the camera saves the 10 seconds before the trigger and 50 seconds after into a secure, dedicated 1-minute "Event" file (labeled with an 'E' suffix).
- File Protection: The ELITE Series firmware features a built-in Event File Overwrite Protection lock. Up to 50 critical impact or manual events are securely locked on the microSD card and cannot be overwritten by standard loop recording.
Expanded Event Triggers
In addition to standard impact events, the latest DR Series and the ELITE Series utilizes its 3-axis G-sensor and dual-band GPS to classify four commercial-grade Driver Performance Events:
- Overspeed: Triggered when the vehicle exceeds speed thresholds configured in the System settings menu.
- Hard Acceleration: Detected by rapid forward G-force changes.
- Hard Braking: Triggered by abrupt negative G-force changes.
- Hard Cornering: Detected by sudden lateral G-force shifts. These events are saved as distinct 'Event' files and sent as instant alerts in Fleeta cloud environments.
3. Intelligent Parking Mode
- How it is triggered: Automatically engages when the vehicle has been stationary for 5 minutes, or instantly when the ignition is switched off (requires a Hardwiring Power Cable (HWK-5FT) or a B-130A Battery Pack).
- Options available in settings:
- Power Saving Parking Mode: The ultimate long-term protection mode. The camera enters a deep sleep state (drawing ≤1mA), disabling the image sensors and Wi-Fi. If an impact is detected, the G-sensor wakes the camera up to start recording within 1 second. Note: Pre-event buffering is disabled in this mode.
- Motion & Impact Detection: Keeps the camera active. It records full-quality video whenever visual movement is detected in the lens field of view or a physical shock occurs (includes the 10-second pre-buffer).
- Time Lapse: Records continuously at 1 frame per second (1FPS), condensing 30 minutes of real-time parking surveillance into a highly compressed, silent 1-minute clip to maximize storage card space.
4. Feature Comparison Table
The following matrix outlines how each recording mode manages power, G-sensor behaviors, file locking, and cloud communication:
Feature / Metric | Normal Recording | Event Recording | Motion & Impact (Parking) | Time-Lapse (Parking) | Power Saving Parking |
|---|---|---|---|---|---|
Trigger Source | Engine Ignition ON | G-Sensor / Touch Sensor | Visual motion / G-Sensor | Time interval (1 FPS) | G-Sensor (Collision only) |
Front REC LED State | Solid Red | Solid Red | OFF (or custom stealth) | OFF (or custom stealth) | OFF (Deep Sleep) |
Pre-Event Buffer | N/A (Continuous loop) | 10 Seconds | 10 Seconds | N/A (1 FPS constant) | Disabled (Records post-impact) |
Video Segment Length | 1 Minute | 1 Minute | 1 Minute | 1 Minute (30 mins of activity) | 1 Minute |
Sub-Stream Generated? | Yes (Low-res D1 file) [3, passage 9] | Yes (For rapid cloud sync) | Yes (For quick remote preview) | Yes | Yes (Created post-wake-up) |
Overwrite Protected? | No (Overwritten when full) | Yes (Locks up to 50 files) | No (Standard loop) | No (Standard loop) | Yes (Saves as secure Event file) |
FLEETA Cloud Alert? | No | Instant Push Alert | Motion: No / Impact: Yes | Impact only: Yes | Yes (Sent post-wake-up) |
File Suffix Code | _N.mp4 | _E.mp4 | _P.mp4 (Motion) / _E.mp4 (Impact) | _P.mp4 | _E.mp4 (Saves as post-wake event) |
5. Troubleshooting & Notes
⚠️ G-Sensor Reset When Changing Speed Units
- The Issue: When you change the "Speed Unit" option (e.g., toggling from km/h to MPH) in the System Settings menu, the dashcam's firmware will trigger a visual UI warning pop-up.
- The Consequence: Accepting this change instantly resets all G-Sensor Event trigger thresholds (including impact sensitivity and your four custom commercial Driver Performance thresholds) back to their default factory values.
- Action Required: After modifying your speed unit settings, you must manually go back and re-configure your custom G-Sensor thresholds to prevent missing events or recording too many false alerts.
🔒 Why Certain Event Files Are Overwritten (The 50-File Limit)
- The Issue: Customers may contact support complaining that a critical G-sensor event recorded a week ago was overwritten, despite "Event Protection" being active.
- The Reason: The ELITE Series firmware enforces a maximum ceiling of 50 locked event files on the microSD card to prevent the storage card from filling up entirely with protected files .
- How it behaves: If the Event folder reaches 50 files and "Event Overwrite" is enabled in settings, the camera will cycle out the oldest locked event to make room for the new one. If "Event Overwrite" is disabled, the camera will refuse to protect new events once the 50-file limit is reached. Advise customers to regularly back up critical files to their smartphone or FLEETA Cloud drive.
🔌 Why Parking Mode Fails to Engage
If a customer reports that their dashcam shuts off completely instead of entering Parking Mode when they turn off their vehicle:
- Check the Wiring: Ensure they are using the official HWK-5FT Hardwiring Power Cable (or a B-130A battery). Standard accessory/cigarette lighter cables do not provide the constant, unswitched power line required to run the camera when the ignition is turned off.
- Verify the Ignition State Signal: The dashcam relies on a 3-wire physical connection (Battery, Accessory, and Ground) to detect when the engine turns off. If the installer incorrectly wired both the Battery and Accessory lines to the same unswitched fuse, the camera will never detect the ignition-off signal and will remain in Normal Mode until the car battery cutoff drops.
- Battery Protection Cut-off Active: If the vehicle's battery voltage is already close to or below the configured low-voltage cutoff threshold (e.g., 11.8V to 12.5V for passenger cars) [2, passage 10], the dashcam's smart protection algorithm will instantly shut down power upon engine-off to safeguard the car's starter battery, bypassing Parking Mode completely.