This Release Notes document describes the details of version 3.12 of the AI-12 dashcam:
This new release includes the following new features:
DC-93
A new feature allows drivers to check-in and check-out directly on a dashcam via QR code or with a five digit PIN code.
Once a driver checks in, all trips, recordings, events, and data are associated with the driver. The driver may check-out through the dashcam, or be checked out through the API. If a new driver checks in while the dashcam is associated with another driver, the previous driver is checked out.
A record of the driver is available in the Surfsight portal, and relevant information is recorded in the cloud and retrievable by API. This feature can be enabled through the Surfsight portal or API.
Driver management actions, such as adding drivers, receiving a driver check-in code, or creating a QR code, are only available via API. For more information see, Drivers, in the Developer Portal.
To check-in to the dashcam:
-
When the dashcam exits standby mode, the driver check-in icon appears on the screen. There is an option to enable a driver prompt for a visual alert when the dashcam wakes up. This alert can be accompanied by an audio alert, and be configured for between 10 and 60 seconds.
If the driver does not check-in during the allotted time a No check-in event is triggered.
-
The driver presses the driver check-in icon to check-in. The Select an action menu appears.
If a driver is already checked in to the dashcam, the option to check-in or check-out appears. If a driver checks-in the previous driver is checked out automatically.
-
The driver presses check-in. The option to check-in with a five digit PIN code or a QR code appears on the screen. This option must be previously configured in theSurfsight® Portal or by API.
-
The driver enters the check-in code or presents the QR code. A confirmation of successful or failed check-in appears on the screen.
If Driver check-in failed, the home screen appears and the driver can try again.
DC-1022
A new Passenger unbelted event is triggered when it is detected that the individual seated next to the driver does not have their seatbelt fastened. If the passenger's seatbelt is not fastened, after 50 seconds there is an in-cabin alert, depending on configured audio or visual alerts. If there is no change, after ten more seconds an event is triggered and, if configured, an additional alert. This occurs once per hour, or if the trip is less than one hour it occurs once per trip.
The event is available in any API calls where events are retrieved and via webhook. Users can configure this setting for single devices, in bulk and from the Organization level using the devices/{imei}/events API endpoint.
DC-837
You can now wake up the device by pressing the event trigger button.
-
The typical Exit standby event is triggered when the device wakes up from standby mode.
-
Device maintains ability to wake up due to movement detected by the accelerometer, or via API.
DC-794
You can now refresh your ADAS calibration images by selecting the Refresh ADAS images in the dashcam settings menu or through the API. The dashcam must be online or in standby mode.
When Refresh ADAS images is selected
-
Previous ADAS calibration images are deleted from the AI-12 dashcam.
-
New calibration images are added next time the vehicle is driven at above 75 km/h.
Through the API you can:
-
Delete ADAS calibration images with the GET /devices/{imei}/adas-delete-calibration-images.
-
Retrieve new images with the GET /devices/{imei}/adas-calibration-images API call.
DC -835
Device security has been improved with the addition of device authentication. Following the upgrade to firmware 3.12, when the dashcam connects to the cloud it will be assigned a secret token. Going forward the cloud will require the token from that device to grant access to the cloud. Devices seeking access without the token will be denied. The token can be reset with a factory reset.
DC-924
Audio is now available for streaming high quality video recordings through API and the Surfsight portal. Audio is available if voiceRecording parameter is previously enabled in PUT /devices/{imei}/device-config API call, or Audio recording is enabled in the dashcam settings, and high quality video recording is selected.
The following table lists the items that we fixed for this release.
|
Issue ID |
Problem |
Resolution |
|---|---|---|
|
DC-94 |
Some event videos skipped parts of the video during playback. |
Event videos play back as expected. |
|
DC-256 |
Some recordings from the road-facing lens and the in-cab lens were not synchronized. |
Recordings from the road-facing lens and the in-cab lens are synchronized. |
|
DC-301 |
In some cases, recordings from different devices were not synchronized. |
Recordings from different devices are synchronized. |
|
DC-311 |
In some dashcams, some APNs weren't set automatically, or were lost after factory reset. |
The dashcam detects and automatically uses the appropriate APNs when a corresponding SIM is installed, and the dashcam does not stop using the APNs after a factory reset. |
|
DC-629 |
Entered events are created when a vehicle starts a trip within the defined geofence. |
Entered events are only triggered when a vehicle enters a defined geofence, not if the vehicle is already within the defined geofence. |
|
DC-772 |
On some dashcams, data usage was not calculated correctly and provided false information. |
Dashcams calculate data usage correctly and provide the correct information. |
|
DC-774 |
For some events the timestamp for the road-facing lens and the in-cab lens were not matching. |
Event timestamps for the road-facing lens and the in-cab lens match. |
|
DC-840 |
The privacy parameter in the PUT /devices/{imei}/device-config API call did not apply to all relevant events. |
The privacy parameter in PUT /devices/{imei}/device-config applies to all relevant events. |
|
DC-851 |
There were a high number of Possible accident events in some dashcams. |
The Possible accident event threshold has been properly adjusted to only trigger when appropriate. |
|
DC-863 |
Play back for recordings from some auxiliary cameras were not synchronized. |
Play back for recordings from auxiliary cameras are synchronized. |
|
DC-867 |
Data usage in the Surfsight® Portal sometimes displayed an incorrect number of events. |
Data usage in the Surfsight® Portal displays the correct number of events. |
|
DC-937 |
Some auxiliary cameras continued recording beyond configured retention time so that recordings were available from outside retention times. |
Recordings from auxiliary cameras respect the device retention configuration. |
|
DC-956 |
In privacy settings in PUT/devices/{imei}/device-config, PUT/devices/device-config, and POST/organizations/{orgId}/device-settings API calls, auxiliary cameras still had recordings during the time recordingEnabled was set to false. |
This is by design in cases where the auxiliary camera has an SD card inserted, since the dashcam settings do not control the auxiliary camera. |
|
DC-979 |
Recordings from some auxiliary cameras were not saved by the dashcam. |
Recordings from all auxiliary cameras are saved by the dashcam. |
|
DC-1026 |
Obstruction events were disabled but were still triggered. |
When obstruction events are disabled they are not triggered. |
|
DC-1158 |
Recordings were not limited to the retention time setting. |
Recordings are limited to the retention time. |
The following table lists the current known issues that have not yet been resolved:
|
Issue ID |
Problem |
|---|---|
|
DC-829 |
Smoking events are not always triggered. Additionally, seatbelt events are not always triggered when drivers wear dark clothing on their upper bodies. |
|
DC-1056 |
On rare occasions, the recording request file may skip one second in the video. |
|
DC-1081 |
Some devices report high data usage. |
|
DC-1229 |
In rare cases, event videos have a two-second time difference between the recordings from the in-cab lens and the road-facing lens. |