Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Make sure that the vehicle is on a flat surface, that the engine is on, and that it is not moving.

  2. Open the Configuration Centerplatform and establish a connection to the K2 gateway via OTA connection.

  3. Click on the “Configuration tab >> “Communication” section >> Check that the “Sever URL” and the “Network APN” match the information you received from Galooli.

...

  1. Click on the “Configuration” tab >> "On-Board Accelerometer Calibration" and complete the process.

    This action is used to detect several following events: severe/high acceleration, severe/high brake, severe/high turn, crash detection

    5. The user can indicate the thresholds for vehicle accelerations and braking events. The threshold will determine how the unit will indicate the driver passed the accepted parameters to indicate a violation has occurred. 
    Each event's threshold can be configured by selecting the vehicle type. Click on the "Configuration" tab and scroll to “Driver Behavior”. Open the “Vehicle Type” dropdown menu and select the desired vehicle type.

    Alternatively, the thresholds can be entered manually by clicking “Manual Settings”. This will require that a threshold (in units of g) will be configured per event.

6. Click on the “Configuration tab >> If there are different devices connected to the K2 gateway, such as an immobilizer, buzzer, or keypad, you should configure them now.

Here are some suggestions for devices.

Driver Identification & Immobilizer Section

Driver Identification & Immobilizer Section

Buzzer Control Section

Fuel Section

It's recommended to use this option if you want the driver to identify himself before the trip starts.

Read more - Configuration Center Configuration https://galooli.atlassian.net/wiki/spaces/KP/pages/2435022858/Mobile+Gateway+Configuration+Configuration+Center#Configuration

If you choose to have the driver identify himself before the trip begins, and the identification is performed using the Dallas Key, then the relevant information must be included here.

Read more - Configuration Center Configuration https://galooli.atlassian.net/wiki/spaces/KP/pages/2435022858/Mobile+Gateway+Configuration+Configuration+Center#Configuration

In the event that you decide to monitor the drivers' activities and link the vehicle to driver, you must perform another step in the system as described in the following page - My Contacts

If the vehicle has an immobilizer, this is where you define how it works.

Read more - Configuration Center Configuration https://galooli.atlassian.net/wiki/spaces/KP/pages/2435022858/Mobile+Gateway+Configuration+Configuration+Center#Configuration

If the vehicle has a buzzer installed, this is where you define how it works.

Read more - Configuration Center Configuration https://galooli.atlassian.net/wiki/spaces/KP/pages/2435022858/Mobile+Gateway+Configuration+Configuration+Center#Configuration

In the case of an external fuel sensor, this is how you define its operation.

It is recommended that the "Noise Factor" be set at "Standard".

Read more - Configuration Center Configuration https://galooli.atlassian.net/wiki/spaces/KP/pages/2435022858/Mobile+Gateway+Configuration+Configuration+Center#Configuration

You create a fuel calibration table as described in the following page - My Calibration

...

After all the configurations have been completed, it is recommended that you check via the Panorama application that all the parameters are displayed correctly.

  1. Open the “Panorama” application >> Locate the unit in the organization tree and click on it.

  2. Your screen will display a "Fleet Unit View”.

  3. Ensure that the unit is connected to the server (The car icon is not grey) and that the location is accurate.

...