Skip to content
Safee Documentation

6-3-2

Release 6.3.2

In this release, we introduce a new report, 2 new alarm conditions, and an enhancement to some alarm conditions.

  1. Wasl Violations Report

We are excited to launch the new Wasl report “Wasl volition report”. The report is targeted to show the number of each violation considered by Wasl policy over the selected period.

The report input enables you of selecting:

  • a level/multiple level
  • the date range
  • The columns to be displayed for the vehicle’s info
  • The instance of the “load weight limit” alarm conditions to be considered when counting the number of “load weight limit exceeded” violations.
  1. Reverse Movement Alarm:

We are glad to announce the new alarm condition that monitors the direction of the vehicle movement. This alarm condition is dedicated —for now- for GalileoSky devices only. it depends on the “user data 2” programed on the device. The logic behind firing this alar is as follow:

When “user data 2” equals 1, this means the vehicle has been moving backward for more than 10 sec; Which is considered as a violation.

The alarm condition wizard consists of 6 steps:

  1. Alarm condition name
  2. Target level
  3. Target geofence; the options are inside/outside a geofence or everywhere.
  4. The day times where the conditions should be applied
  5. Types of notifications needed upon firing an alarm
  6. And finally, revision and confirmation

Once the value of the received “user data 2” equals 1, and all the above-mentioned conditions are met, an alarm will be fired and the system will keep accumulating the duration of the violation as long as “user data 2” = 1. Once it’s received as 0, the system closes the alarm, and you can get the final violation duration.

  1. Movement without Lights at Night

We are also glad to announce the new alarm condition that monitors the state of the front light of the vehicle. This alarm condition is dedicated —for now- for GalileoSky devices only. it depends on the “user data 4” programed on the device. The logic behind firing this alar is as follow:

When “user data 4” equals 0, this means the vehicle is moving with speed greater than 5 km/h at night without turning on the lights; Which is considered as a violation.

The alarm condition wizard consists of 6 steps:

  1. Alarm condition name
  2. Target level
  3. Target geofence; the options are inside/outside a geofence or everywhere.
  4. The day times where the conditions should be applied
  5. Types of notifications needed upon firing an alarm
  6. And finally, revision and confirmation

Once the value of the received “user data 4” equals 0, and all the above-mentioned conditions are met, an alarm will be fired and the system will keep accumulating the duration of the violation as long as “user data 4” = 0. Once it’s received as 1, the system closes the alarm, and you can get the final violation duration.

  1. Consider chiller status in alarm conditions:

It’s now available to you to add a condition on the chiller status when creating conditions in the following alarm conditions:

Temperature Range Alarm Condition:

At the fourth step in the “temperature range” alarm condition, you can set a new condition to check the chiller status before deciding on firing the alarm. The chiller status can be provided by a digital input in the tracking device, and you are asked to select the corresponding digital input.

Fridge Door Alarm Condition:

At the fourth step in the “Fridge Door” alarm condition, you can set a new condition to check the chiller status before deciding on firing the alarm. The chiller status can be provided by a digital input in the tracking device, and you are asked to select the corresponding digital input.