3.13 August 2024 (Beta)

This Release Notes document describes the details of version 3.13 of the AI-12 dashcam:

New features

This new release includes the following new features:

Power loss file protection

DC-1339 

The Power Loss File Protection mechanism for the dashcam protects media files during sudden power loss events, such as major accidents or theft. During the transfer of files from temporary memory to the SD card, an abrupt power loss can cause file corruption if files were not closed properly.

This new feature includes a mechanism that retries the transfer process, ensuring proper file closure and transfer. If the transfer fails repeatedly, the temporary file is deleted to maintain system efficiency. This enhancement significantly increases the likelihood of preserving crucial media files during unexpected power interruptions, enhancing the reliability of the dashcam.

Increase video protection through watermarks

DC-1287 

Our solution empowers Reseller partners and end-customers with greater protection of the video. It allows embedding customizable watermarks on captured videos and snapshots. The watermark is displayed on the bottom right of the media files. The enhancement deters unauthorized use and also facilitates tracking the video's origin and ownership even after it's downloaded and shared outside the platform. This data tracks proprietary rights embedded within the video itself.

Note

When embedding a watermark, do not include text, images, or material which violate intellectual property, privacy, or other applicable laws.

Hotspot control

DC-1277 

You can now remotely designate dashcams as hotspots. Your security posture is enhanced by controlling the enablement of dashcams as a hotspots.

Use hotspotEnabled, to designate dashcams as mobile hotspots.

This parameter is available in the PUT/devices/{imei}/event-config, PUT/devices/event-config and POST/organizations/{orgId}/event-settings API calls.

Use the cloud service to provide time zone updates

DC-1100

Some cellular providers do not provide Daylight Savings Time updates, so we developed our own service for this. Use the setTimezoneByCloud parameter to configure dashcams to retrieve time zone information from the cloud, which is based on GPS data. The connection to the cloud is subject to cellular network coverage.

When the parameter is set to false, the device uses the cellular provider to determine the time. This is the default setting.

When the parameter is set to true, the cloud will translate GPS information to location and set the timezone accordingly. Time zones on the device are updated by the cloud as necessary.

This parameter is available in the PUT/devices/{imei}/event-config, PUT/devices/event-config and POST/organizations/{orgId}/event-settings API calls.

Enhancements

Improved Audio Quality

DC-1305 

Some customers experienced audio distortions, possibly due to driving on rough roads that cause vibrations in the vehicle. To improve the user experience, we’ve updated the firmware to reduce these distortions.

Increased data security with an enhanced encryption mechanism

DC-1227 

We upgraded the level of data security by hardening the encryption mechanism on the device side with more robust encryption algorithms. You can assign a 64-character key in order to encrypt SD card recordings In both the Developer Portal and the Surfsight® Portal.

You can configure the key by using the recordingEncryption parameter, which is available in the PUT/devices/{imei}/event-config, PUT/devices/event-config and POST/organizations/{orgId}/event-settings API calls. You can also configure it in the Surfsight® Portal.

Fixed items

The following table lists the items that we fixed for this release:

Issue ID

Problem

Resolution

DC-1216

After dowloading video files in the Timeline of the Surfsight® Portal, videos stopped playing and displayed this error message: "unsupported encoding".

A new mediacore enhancement uses media file segments collected into a folder for retrieval. In most cases, complete files are returned. If the file is not completely uploaded within four minutes, the partial file is returned.

Known issues

The following table lists the current known issues:

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.

Was this article helpful?
0 out of 0 found this helpful