Once the K2 gateway has been fully installed, please proceed to the following steps in order to configure the K2 gateway in the optimal manner.
Configuration Center
Open the Configuration Center platform and establish a connection to the K2 gateway via OTA connection.
Click on the “Configuration” tab >> “Communication” section >> Check that the “Sever URL” and the “Network APN” match the information you received from Galooli.
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 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 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 | If the vehicle has a buzzer installed, this is where you define how it works. Read more - 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 You create a fuel calibration table as described in the following page - My Calibration |
Manager Application
Open the “Manager” application >> “My Units”
If the unit already exists in the organization tree, then it needs to be transferred to the right cluster.
If the unit does not exist for any reason, proceed to the next step.Click on "My units" >> Create a new unit or duplicate all the configuration from another source unit. In any case, you should continue to verify the following sections.
In “My unit” >> "Overview" tab, set the appropriate "Asset Type" as and set the "Stationary Unit" as "No”.
In “My unit” >> "Overview" tab, set the destination Email and SMS. Email and phone numbers can be set at the cluster or group level as opposed to the unit level.
In “My unit” >> “Configuration” tab >> “IO’s” >>On the basis of the IO’s settings, it will be possible to define events in the system later on.
Immobilizer | Towing | Fuel |
---|---|---|
Create a new “Output” >> You should select a meaningful name and the correct output. All other options should be filled out as shown in the image. | Create a new “Digital” >> You should select a meaningful name. All other options should be filled out as shown in the image. | Create a new “Analog” >> You should select a meaningful name. All other options should be filled out as shown in the image. |
In “My unit” >> “Configuration” tab >> “Maintenance” >> Set the relevant maintenance data for you vehicle.
In “My unit” >> “Configuration” tab >> “Preferences” >> Set the “Minutes to Idle” value if necessary. As an example, if the engine continues to run for five consecutive minutes without the vehicle is moving, then the vehicle is considered to be in idle status. 5 minutes or more is the recommended value.
In “My unit” >> “Configuration” tab >> “Installation setup” >> Set the vehicle's initial working time, distance, and other parameters if necessary.
In “My unit” >> “Events” tab >> Add all relevant events and set the phone number/email to receive notifications. The events are based in part on the IO's and other configurations that you have made.
The following are some tips and suggestions for useful events.
Events Category | Event Type | Display | Severity | Notification Method | Time Before Activation | Value | Threshold |
---|---|---|---|---|---|---|---|
Common Events | Over Speed | Over Speed | Advisory | 20 sec | 120 | ||
Common Events | Status Start | Unit Disconnected | Caution | Email + SMS | 24 H | Not connected | |
Common Events | Status Start | Idle Start | Warning | Email + SMS | 10 min | Idle | |
Analog Value Events | Analog Value Below | Low Battery | Caution | Email + SMS | 5 min | Battery Voltage | 11V |
Digital Value Events | Digital State On | Towing | Warning | Email + SMS | 30 sec | Fleet Basic Towing | |
Fuel Events | Fuel Refueled | Refueled | Advisory | 0 | Analog 5 - Fleet Basic Fuel Main | ||
Fuel Events | Fuel Tank Empty | Fuel Tank Empty | Warning | Email + SMS | 0 | Analog 5 - Fleet Basic Fuel Main | |
Fuel Events | Fuel Drop | Fuel Drop | Caution | Email + SMS | 0 | Analog 5 - Fleet Basic Fuel Main | 12L |
Location Events | Location Geofence Leave | Car/Truck left the Geofence | Advisory | 0 | |||
Tips:
|
Panorama Application
After all the configurations have been completed, it is recommended that you check via the Panorama application that all the parameters are displayed correctly.
Open the “Panorama” application >> Locate the unit in the organization tree and click on it.
Your screen will display a "Fleet Unit View”.
Ensure that the unit is connected to the server (The car icon is not grey) and that the location is accurate.