The AI-14 dashcam is designed to minimize vehicle battery drain. Various features including Standby state and Low Voltage Disconnect help safeguard the vehicle’s battery to extend its life.
The AI-14 dashcam's power state and transition between power states changes according to the following circumstances:
The following process details how the AI-14 dashcam power states function with virtual ignition. For more information, see Configure virtual ignition in the AI-14 dashcam.
-
When the device accelerometer detects movement, the AI-14 is in Online state. It's fully functional at this time.
-
After movement stops, the device stays on and records for a set period before going into standby. This is configurable in the Surfsight® Portal with the dashcam setting, Idle Minutes to Enter Standby. For more information, see Configure dashcam settings.
-
After the Idle Minutes to Enter Standby period ends, the device goes into Standby mode.
-
Every 24 hours, when in standby, the device performs a watchdog reboot and connects to our network. The watchdog reboot resets the device to help prevent errors. At this time, the device goes Online again and the Idle Minutes to Enter Standby period resets. When the period ends again, the device goes back into Standby mode.
Note
If the device cannot connect to our network before reaching 25 hours in Standby, the device goes to Offline state. While offline, the device has no functionality. This can be caused by poor network connection or insufficient bandwidth. Or the device may not be connected to a sufficient power source.
-
When the device accelerometer detects movement again, the device goes back Online.
The following process details how the AI-14 dashcam power states function with conventional ignition.
-
When the vehicle has ignition ON, the AI-14 dashcam is in Online state. It's fully functional at this time.
-
After turning ignition off, the device stays on and records for a set period before going into standby. This is configurable in the Surfsight® Portal with the dashcam setting, Idle Minutes to Enter Standby. For more information, see Configure dashcam settings.
-
After the Idle Minutes to Enter Standby period ends, the device goes into Standby mode.
-
Every 24 hours, when in standby, the device performs a watchdog reboot and connects to our network. The watchdog reboot resets the device to help prevent errors. At this time, the device goes Online again and the Idle Minutes to Enter Standby period resets. When the period ends again, the device goes back into Standby mode.
Note
If the device cannot connect to our network before reaching 25 hours in Standby, the device goes to Offline state. While offline, the device has no functionality. This can be caused by poor network connection or insufficient bandwidth. Or the device may not be connected to a sufficient power source.
-
After turning ignition back on, the device goes back Online.
The Low Voltage Disconnect feature is intended to help safeguard the vehicle's battery when the AI-14 is not receiving sufficient power.
The following process details how the AI-14 dashcam power states function when there is low voltage.
-
The AI-14 dashcam needs at least 12.0v to function properly. If the device’s voltage drops to 11.0 V or less--whether it’s in Online or Standby state--the device automatically disconnects power, going to Offline state. While offline, the device has no functionality.
-
When the AI-14 reaches 12.0 V again, the device turns to Online state.
Notice
Smart Handling: Device power may drop in the course of normal use (e.g. during engine cranking). In these cases, Smart Handling helps ensure the AI-14 does not disconnect power.
|
State |
Current Draw |
|
|---|---|---|
|
Online |
225 mA |
The device has full functionality. |
|
Standby |
32 mA |
The screen turns off. While in Standby, you can wake the device remotely, bringing it back Online. This allows you to remotely retrieve video stored on the device. |
|
Offline |
NoteCurrent draw is unknown while a device is Offline, because remotely it cannot be determined if the device has no power, or a bad connection. |
The device could not connect to our backend. The device has no functionality. This can be caused by poor network connection or insufficient bandwidth. Or the device may not be connected to a sufficient power source. |