How to use the Cameras setting in Fleet Vision mode

How to use the Cameras setting in Fleet Vision mode

1. Overview

This feature, much like the Vehicles feature, has all your purchased cameras for your fleet with all their related information, you can customize your camera alerts and events from this feature, It is by far one of the most important features to be familiar with.
To access the Camera feature, open the navigation drawer by clicking on the three-dashed button located at the upper left corner of the page, then under Settings, click on Cameras, a similar window appears.
Fig.01

You'll find the cameras names, register codes, AI-Engine types, groups they're included in if any, the status of the camera, whether it's on silent mode (i.e. doesn't alert the driver to events, only the owner), the last command updates (where this shows the date and time of the last command sent by the camera). To see more details, scroll right, a similar window is shown.
Fig.02
There you'll find the last AI update (which is the date and time of the last AI update made to the camera), the location of the camera, the installation date of the camera and the version of the AI software installed on the camera.

2. Add/Edit Camera

If you need to edit an existing camera, click on the pencil shaped button under actions next to the camera's name, a window will pop up with all the editable information present, after you're done editing click on save and you're done. To add a new camera, click on the "New Camera" button located at the upper right corner of the page, the following window appears.
Fig.03


Fill in the information required and click on save first before moving on to the settings tab.
If you don't click on save first, you won't be able to access the camera customizations that will follow below.
The Settings tab has a lot of customizations, they're all set to default values, If you wish to customize a few, here's a breakdown of all the functions.
The functions are divided into blocks where each feature is represented in a block of consecutive keys with values, their priorities are classified into dangerous, high, medium and low.

1. Harsh Acceleration

This feature is provided by the ADAS camera, it records any harsh acceleration done by the driver, and according to both their speed and the inter-distance between the driver's vehicle and the surrounding vehicles, one of four priorities is set for the event. The key features are as follows:
Fig.05
Fig.04


  1. g_activation: This sets the minimum distance (calculated in centimeters) between your fleet's unit and the vehicle or barrier in front of it, of activating an event and/or sounding the in-cabin alarm. The default is 500 centimeters for dangerous, 500 centimeters for high, 700 centimeters for medium and 1000 centimeters for low.
  2. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  3. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 0 milliseconds for all priorities.
  4. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority, 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  5. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

2. Harsh Braking

This feature is provided by the ADAS camera, it records any harsh braking done by the driver, and according to both their speed and the inter-distance between the driver's vehicle and the surrounding vehicles, one of four priorities is set for the event. The key features are as follows:
Fig.07
Fig.06
  1. g_activation: This sets the minimum distance (calculated in centimeters) between your fleet's unit and the vehicle or barrier in front of it, of activating an event and/or sounding the in-cabin alarm. The default is 500 centimeters for dangerous, 500 centimeters for high, 700 centimeters for medium and 1000 centimeters for low.
  2. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  3. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 0 milliseconds for all priorities.
  4. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority, 70 km/hr for the high priority, 50 km/hr for the medium priority and 0 km/hr for the low priority.
  5. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

3. Unsafe Distance

This feature is provided by the ADAS camera, it records any unsafe distances (between your unit and the vehicle in front of it) made by the driver, and according to both their speed and the inter-distance between the driver's vehicle and the surrounding vehicles, one of four priorities is set for the event. The key features are as follows:
Fig.09
Fig.08
  1. distance_activation: This sets the minimum distance (calculated in meters) between your fleet's unit and the vehicle or barrier in front of it, of activating an event and/or sounding the in-cabin alarm. The default is 100 meters for dangerous, 30 meters for high, 50 meters for medium, and 10 meters for low.
  2. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  3. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 1000 milliseconds for all priorities.
  4. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority, 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  5. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.
  6. auto_mute_alerts_after_x_times: This feature helps you silent the alerts after a specific number (x) is reached

4. Blinded

This feature records the presence of any object binding the main camera in the driver's cabin, and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:

Fig.11
Fig.10
  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to True for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 1000 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority, 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

5. Cellphone

This feature is triggered by stalking on the cellphone, if the driver starts using a cellphone and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:

Fig.13
Fig.12

  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to True for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 0 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

6. Cigarettes

This feature is triggered by smoking cigarettes, if the driver starts smoking and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.14
  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to True for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 0 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

7. Distracted Driving

This feature records the distracted driving behavior of the driver, and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.16
Fig.15

  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to True for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 3000 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

8. Drowsy Fatigue

This feature records the drowsiness (or the tiredness/sleepiness) of the driver, and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.18
Fig.17
  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to True for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 3000 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

9. Fatigue

This feature records the fatigue like symptoms by monitoring the eyes of the driver, and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.20
Fig.19

  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 1500 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

10. Head Fatigue

This feature records the fatigue like symptoms by monitoring the head of the driver, and according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.22
Fig.21

  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 3000 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.

11. No Face Detection

This feature alerts the driver and/or the employer that it cannot detect the driver's face, that usually happens because of wrong mounting of the camera, according to the unit's speed, one of four priorities is set for the event. The key features are as follows:
Fig.23
Fig.24

  1. silent: This feature, if written to True, stops the in-cabin alarm from going off when the event is activated. The default is set to False for all priorities.
  2. start_duration_activation: This sets the time taken to report the event in milliseconds, if set to zero, this means the event is reported right away. The default is 5000 milliseconds for all priorities.
  3. start_speed_activation: This sets the minimum speed (in kilometers per hour) for each priority for which the event is activated. The default is 80 km/hr for the dangerous priority and 70 km/hr for the high priority, 50 km/hr for the medium priority and 25 km/hr for the low priority.
  4. upload_event: This feature if set to True, it activates the event (and hence uploading it to the platform) and if set to False, turns off the reporting or uploading of said event for each priority. The default is set to True to all priorities.
  5. play_welcome_message: This feature, if set to True, makes the camera play a welcome message at the beginning of each trip. The default is set to True.
If you have any more questions, please email us, call or simply start a ticket!

    • Related Articles

    • How to use the Vehicles setting in Fleet Vision mode

      this feature allows you to view and control your fleet in the form of units, each unit is called a vehicle in the Fleet Vision service. you can view, add, or edit vehicles or details about previously registered ones. to access Vehicles, go to the ...

    • How to use the Parking Types setting in Fleet Vision mode

      The Parking Types setting helps you control your fleet through the Fleet Performance feature we have on our platform, the idea is to add kinds or types of parking by simply listing the reason for it, for instance, if a unit stops for scheduled ...

    • How to use the Groups setting in Fleet Vision mode

      This feature helps you organize your fleet by sorting your vehicles into groups relevant to your business. To access the Groups feature, open the navigation drawer by clicking on the three-dashed button in the far left corner of the screen, under ...

    • How to use the Drivers setting in Fleet Vision mode

      The Drivers feature is where you add your fleet's drivers names', license information and much more. to access Drivers, open the navigation drawer by clicking on the three-dashed button on the left side upper corner of the page, under Settings, click ...

    • How to use the Camera-Vehicle setting in Fleet Vision mode

      This feature links your camera device to a certain vehicle on the platform. After mounting the camera unto the dashboard in your vehicle, a software link must be created, that is where you link your vehicle to your new camera. Make sure you have ...