This Release Notes document describes the following details for version 3.10 of the AI-12 dashcam:
This new release includes the following new features:
We are now introducing road-facing ADAS alerting. For this release specifically, the dashcam now alerts on possible tailgating events - cases where you are driving too close to the vehicle in front of you.
To ensure the dashcam identifies tailgating with maximum accuracy, users first need to calibrate the dashcam. You can calibrate:
-
from the AI-12 dashcam touchscreen
-
with the API
-
with the reusable component
-
from the Partner Portal
You can prepare for calibration by taking the following measurements ahead of time, in centimeters or inches:
-
the dashcam height from the ground
-
the dashcam offset, measured from the center of the windshield
-
the width of the rear axle of the vehicle, measured from the outer edges of each tire
For more details, take a look at the ADAS calibration preparation article.
SUR-3224 and SUR-3049
The Surfsight® dashcam identifies tailgating events by estimating time-to-collision (TTC) and comparing the estimated TTC to pre-defined limits. TTC is estimated based on the distance of the vehicle in front of yours in relation to the speed of your vehicle, which the dashcam detects continuously whenever the vehicle is moving. When the driver exceeds these TTC limits, and based on our proprietary algorithms, the dashcam creates an event and sends visual and audio alerts. The pre-defined limits are calculated according to three new parameters that the user can configure.
The parameters and their default values are as in the following table:
SSUI-1873
Users can calibrate from the settings menu of the dashcam itself.
SUR-3593 and SUR-3594
Users can send API calls to manage their road-facing ADAS calibration as follows:
Users can request images to assist in calibrating tailgating events through the GET /devices/{imei}/adas-calibration-images API call. You can request between one and ten images. The default is set to ten.
Once you select an image from the options retrieved, you use that image to measure certain parameters needed in the PUT /devices/{imei}/calibrate-adas API call.
Users can set and update their ADAS calibration parameters through the PUT /devices/{imei}/calibrate-adas API call. This calibration enables tailgating events for your dashcam.
The parameters include the:
-
height of the dashcam from the ground
-
distance of the dashcam from the center of the windshield
-
rear axle width of the vehicle, from the outside of one tire to the outside of the other
-
lowest point on the y-axis of the selected image where you don't see the vehicle front or dashboard
-
four points (x, y) marking the edges of the left and right lanes in the selected image
You can integrate calibration functionality by implementing a React component. This is the same component that we use in our Partner Portal.
For more information about the React component, see our guide in the Developer Portal.
All risky driving events now include the following metadata:
-
timestamp, in Unix format
-
speed, in meters per second
-
g-force on the x, y, and z axes, in meters per second squared
The information is sampled every 100 milliseconds of an event, which is 10 seconds long (5 seconds before the event is triggered until 5 seconds after). This comes to a total of 100 measurements per event.
This metadata is included in the following events:
-
De-acceleration
-
Acceleration
-
Sharp left turn
-
Sharp right turn
-
Speed limit
-
Vibration
-
Distracted driving
-
Smoking
-
Food and drink
-
Cell phone use
-
Driver unbelted
-
G-sensor regular
-
G-sensor high
-
Possible accident
-
Tailgating
In the API, the events with this new metadata appear similar to:
"id": 215218413, "eventType": "tailgating", "metadata":[ { "x": -0.7766926884651184, "y": 1.043716311454773, "z": 0.2895919382572174, "time": 1637907799777, "speed": 13.319999694824219 }, { "x": -0.876927375793457, "y": 1.01749849319458, "z": 0.22693347930908203, "time": 1637907799881, "speed": 13.319999694824219 }, { "x": -0.9494592547416687, "y": 1.0374133586883545, "z": 0.10973739624023438, "time": 1637907799980, "speed": 13.319999694824219 }], //******** This repeats up to 100 times but is concatenated for the sake of documentation "lat": 32.17834621, "lon": 34.92789065, "speed": 47.95199890136719, "status": "new", "severity": 3, "eventComments": [], "time": "2021-11-26T06:23:24.000Z", "files":[ { "cameraId": 1, "fileId": "1637907804", "fileType": "video" }, { "cameraId": 2, "fileId": "1637907804", "fileType": "video" } ]
When viewing event videos in the Surfsight Portal, users can now see an accelerometer line chart below the video itself.
The parameters of the chart include:
-
FWD - x-axis
-
LAT - y-axis
-
GPS speed - speed
Users can now encrypt recording files on the SD cards of devices.
SUR-2374
Each recording file is independently encrypted using a password and an AES algorithm that is supported in FIPS 140-2. The password must be set by the user through the Surfsight Portal or through the API and can be 16, 24, or 32 characters in length.
Important
Encryption must be set on an empty SD card.
When first setting up encryption, it must be done from the Surfsight Portal or through the API with the PUT /devices/{imei}/device-config call.
Once enabled, the encryption can then be disabled from the dashcam, from the portal, or through the API.
The following new events are now available:
SUR-3021
Gravitational force (g-force) is a measure of acceleration and deacceleration based on the values for the x, y, and z axes. When a vehicle accelerates quickly or turns suddenly, more g-force is felt. A higher g-force can indicate risky driving.
There are now three new events that are triggered when the g-force of your vehicle is higher than it should be including:
-
G-sensor regular - indicates that the g-force is higher than normal
-
G-sensor high - indicates that the g-force is even higher than that
-
Possible accident - indicates a possible collision from very high g-force
The thresholds for these events are described in the following table:
Event |
Vehicle |
X-axis value |
Y-axis value |
Z-axis value |
---|---|---|---|---|
G-sensor regular |
Private vehicle |
750 |
750 |
2000 |
Van |
950 |
950 |
2000 |
|
Trailer |
1150 |
1150 |
2000 |
|
G-sensor high |
Private vehicle |
1050 |
1050 |
2300 |
Van |
1200 |
1200 |
2300 |
|
Trailer |
1450 |
1450 |
2000 |
|
Possible accident |
Private vehicle, van, trailer |
2500 |
2500 |
2500 |
SUR-2631
When the view from the in-cab lens is completely obstructed for more than 10 seconds, a new Obstruction event is now reported in the system.
If the lens remains obstructed, one event is created every hour for the duration of that trip or until the lens is unobstructed. If the lens is unobstructed and then gets obstructed again, a new event is created.
This section describes enhancements we've made to existing features for this release.
Additional APN support - SUR-3726
Additional Access Point Names (APNs) have been added to the firmware, enabling automatic configuration of SIM cards that originate from several leading service providers. This enables users to use their own data plan with the dashcams by simply plugging their SIM card in and powering up the device (plug and play).
More secure PIN codes - DC-23
The dashcam PIN keypad now has the numbers 0 through 9 instead of just 0 through 4. You can use these digits to create a more secure PIN code.
Improved translations - DC-49
The quality of translation in European languages in our dashcam menu has been improved.
The following table outlines known issues that we have resolved for this release.
Issue ID |
Problem |
Resolution |
---|---|---|
SUR-3727 |
Some users were receiving a bandwithAlarm event every 10 seconds, claiming that they had gone over their limit of data usage. These constant events were creating a load on the dashcam and disrupting other functions. |
The bandwithAlarm event is no longer in use. |
DC-43 |
A user was getting email notifications for old or non-existent events. |
The issue has been resolved, and the user is no longer receiving these notifications. |