3.11 November 2022

This Release Notes document describes the following details for version 3.11 of the AI-12 dashcam:

Note

Firmware version 3.11 rollout is beginning in the U.S. cloud.

New features

This new release includes the following new features:

Lane weaving event

DC-90

A new event, Lane weaving, is now triggered when a vehicle crosses over a certain number of lane marking lines (dashed or solid) in a specific amount of time.

When triggered, the dashcam beeps and an icon appears on the screen. Additionally, an event is sent to the cloud. For this event to trigger, road-facing ADAS must be calibrated.

dascham_laneWeavingIcon.png

From the Surfsight Portal or through the API, you can set for individual dashcams or in bulk:

  • the number of lane marking lines the vehicle crosses to trigger the event, between two and ten. The default is three lane marking lines.

  • the amount of time during which the lane marking lines are crossed, between five and sixty seconds. The default is thirty seconds.

eventSettings_laneWeaving.png

Configurable audio and visual alerts for events

DC-103

You can now separately enable or disable the audio and visual alerts for each event in the Surfsight Portal or through the API. By default, for each event:

  • the audio alerts are dependent on whether Enable audio alerts is enabled or disabled in Settings

  • the visual alerts are enabled

Alerts can be enabled or disabled for individual dashcams, multiple dashcams, or for an entire organization. To enable audio and visual alerts:

  1. Enable audio alerts in the Settings area or in the PUT /devices/{imei}/device-config API.

  2. Enable audio and visual alerts for the desired events in the Event Settings area or in the PUT /devices/{imei}/event-config API.

eventSettings_visualAudioToggles.png

Auxiliary camera support

Support for the new auxiliary cameras has been added. Additionally, many improvements have been made to the existing auxiliary camera support.

QR code event

DC-91

A new event, QR code, is triggered when the in-cab lens scans a QR code. When the event is enabled, a QR code icon appears on the dashcam screen. When the event is disabled, the QR code icon does not appear on the dashcam screen.

To trigger this event:

  1. From the Surfsight® Portal or through the API, enable the QR code event in Event settings.

    When enabled, a QR code icon appears on the dashcam screen.

  2. Press the QR code icon at the top left of the dashcam screen.

    dashcam_mainScreenQrCode.png

    The dashcam beeps for ten seconds or until a QR code is scanned.

  3. Within ten seconds, scan the QR code using the in-cab lens.

    An event is triggered and sent to the cloud, with the QR code as metadata. A success message is displayed on the dashcam screen.

Enhancements

Visual and audio alert enhancements

  • Virtual events - DC-71

    When a virtual event is created in the cloud, there can now be a beep from the dashcam and i-exclamationWhite.png can appear on the dashcam screen.

    By default, visual alerts are enabled and audio alerts are dependent on whether Enable audio alerts is enabled or disabled in Settings.

    Alerts can be enabled or disabled for individual dashcams or in bulk. To enable audio and visual alerts:

    1. Enable audio alerts in the Settings area or in the PUT /devices/{imei}/device-config API.

    2. Enable audio and visual alerts through the POST /devices/{imei}/virtual-event API.

  • Event trigger button - DC-47

    When the event trigger button is pressed, there can now be a beep from the dashcam and i-exclamationWhite.png can appear on the dashcam screen.

    By default, visual alerts are enabled and audio alerts are dependent on whether Enable audio alerts is enabled or disabled in Settings.

    Alerts can be enabled or disabled for individual dashcams or in bulk. To enable audio and visual alerts:

    1. Enable audio alerts in the Settings area or in the PUT /devices/{imei}/device-config API.

    2. Enable audio and visual alerts for the desired events in the Event Settings area or in the PUT /devices/{imei}/event-config API.

  • Speed limit event - DC-53

    When a speed limit event is triggered, there can now be a beep from the dashcam and incabin-event-icons_0000_Tailgating.png can appear on the dashcam screen.

    By default, visual alerts are enabled and audio alerts are dependent on whether Enable audio alerts is enabled or disabled in Settings.

    Alerts can be enabled or disabled for individual dashcams or in bulk. To enable audio and visual alerts:

    1. Enable audio alerts in the Settings area or in the PUT /devices/{imei}/device-config API.

    2. Enable audio and visual alerts for the desired events in the Event Settings area or in the PUT /devices/{imei}/event-config API.

  • Tailgating event - DC-784

    When a tailgating event is triggered, a tailgating-specific icon can now appear on the dashcam screen.

    dashcam_tailgatingIcon.png

    Alerts can be enabled or disabled for individual dashcams or in bulk. To enable audio and visual alerts:

    1. Enable audio alerts in the Settings area or in the PUT /devices/{imei}/device-config API.

    2. Enable audio and visual alerts for the desired events in the Event Settings area or in the PUT /devices/{imei}/event-config API.

Certification screen update - DC-778

The certification screen has been updated with additional information:

  • the IC:25716-AI12 certification

  • the FCC ID: 2APWTAI-12 certification

  • the dashcam IMEI number

dascham_certificationScreen.png

New APNs - DC-244

Based on customer request, new access points (APNs) have been added.

Fixed items

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

Issue ID

Problem

Resolution

DC-68

Sometimes virtual events with video did not have video files attached.

All events with video have the correct video files attached.

DC-92

Some MVAI events were missed in smaller cabins when they occurred at the edges of the in-cab lens' field of view.

The in-cab lens' field of view has been improved to detect in-cab behaviors in smaller spaces.

DC-133

Too many Fence / Entered events were being created.

The correct number of Fence / Entered events are created.

DC-246

Some advanced driver assistance system (ADAS) menu items were not translated from English. Additionally, some translations didn't fit properly on the screen.

All menu items have been translated from English to Spanish and French. All translations now fit properly on the screen.

DC-681

The in-cab recordings sometimes appeared with a pinkish hue.

The colors in recordings now appear normal.

DC-693

Some events did not have an in-cab recording when the event was set to have video attached.

All events that are set to have video attached now have road-facing and in-cab recordings.

DC-733

Obstruction events were sometimes triggered when the driver's face was partially covered. Additionally, more audio alerts were received when an Obstruction event was triggered than expected.

Obstruction events have been improved to only trigger when the in-cab lens is completely blocked, and not when the driver's face is partially covered. Additionally, the number of audio alerts has been updated - the dashcam beeps once when an Obstruction event is triggered. If the trip lasts longer than an hour, and the lens is still obstructed for that duration, the dashcam beeps once an hour.

Known limitations

This section lists the current known limitations that have not yet been resolved.

Issue ID

Problem

DC-629

Entering Standby events are triggered when a vehicle with a dashcam connected to ignition power is turned on within a geofence.

This will be resolved as part of the 3.12 firmware release.

DC-640

A no internet connection icon appears on the dashcam screen for dashcams that are connected to the internet over WiFi but do not have a SIM card.

This will be resolved as part of the 3.12 firmware release.

DC-689

Sometimes there are sync issues between the in-cab lens and road-facing lens causing the in-cab lens to be one second behind the road-facing lens in recordings.

This will be resolved as part of the 3.12 firmware release.

DC-829

Smoking events are not always triggered. Additionally, seatbelt events are not always triggered when drivers wear dark clothing on their upper bodies.

This will be resolved as part of the 3.12 firmware release.

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