Events

Navigate to the "Events" tab on the main page, and select "Add Trigger", as Events are created by things happening to objects, those particulars need to be set. You define the Name, the Type and the parameters first. An Event is created only if the state changes to these conditions. (This means, creating an overspeed trigger will not continually fire for a tracker travelling too fast, it will fire once when the speed is first seen above the filter).

Event config window:

Give your event a Name, this will be used in alerts, emails and other templates.

Set the type of action that should trigger this event. Many are dependant on the type of device you have, it's available sensors/inputs, and may or may not work depending on that. Basic ones like "geofencing" should work fine by using the Zone In and Zone Out actions. You then need to pick the objects this trigger should fire for. (We encourage you to select All of your objects per Trigger, rather than creating a Trigger per object/rule).

• If your event is route specific (route must be defined before trigger created), you can select it here. (For example if you are only interested in Speeding when driving a specific Route etc, the condition of the Trigger outside the selected Route will not create an Event at all. It is important to understand that the filters are designed to prevent excessive Events from being generated).
• If your event is zone specific, you can select it here, and specify it's requirement. However it can be used to filter any other Event Type, eg: I am only interested in overspeeding inside Victoria, send an alert to [email protected], then you can define different events for each region, apply it to all of your objects etc.
• The time period filter ensures that conditions must be set for an amount of time. For example, only create an Event when the "Stopped" condition is set for more than 10 minutes.
• Parameters and Sensors: This is used to customize the Parameters and Sensors - Event Types. For example, if you want to know when your vehicle is turned on, you could create a Sensor Type Event Trigger, and specify the Source as "ACC Status" and then select the value "= 1" This will create an Event when the tracker transitions from anything else to 1. (Eg: The car turns on). You can add a few sensors at once combined into patters, for example: When the vehicle is moving > kmph and the ACC Status = 0, that would mean the car is being towed or is inside a truck being stolen etc. You can only select the sensors when you have changed the Type to Sensor, and the parameters when the type is set to Parameter. (Parameters are essentially raw Sensors, we encourage you to use the Sensors instead).

Other Event types:

• Low Battery - Most should use a Sensor instead, this Type is not supported on all hardware.
• Connection: Yes - This fires an Event when the hardware changes from having no Mobile signal to having a mobile signal.
• Connection: No - The opposite of "Connection: Yes".
• GPS: Yes - This fires an Event when the hardware changes from having no GPS signal to having a GPS signal.
• GPS: No - The opposite of "GPS: Yes".
• Stopped - This fires when the vehicle changes to the state "stopped". Eg, it is no longer Moving.
• Moving - Fire an Event when a tracker changes from not-moving to moving.
• Engine Idle - Fires an Event when the tracker changes state to "idle", eg, the engine is on, but it isn't moving.
• Overspeed - Fires an event when the tracker reports it's velocity has changed to be higher than the entered "Speed limit" in kmph. .Reset's when the speed is reported to be lower than that.
• Underspeed - Basically the opposite of Overspeed. Think the movie "Speed"
• Harsh Acceleration - Not all hardware supports this, we recommend using a Sensor and specifying the Sensor "Driver Behaviour" instead. If your hardware does not support this sensor, you will not be able to make this Trigger.
• Harsh braking - Not all hardware supports this, we recommend using a Sensor and specifying the Sensor "Driver Behaviour" instead. If your hardware does not support this sensor, you will not be able to make this Trigger.
• Harsh Cornering - Not all hardware supports this, we recommend using a Sensor and specifying the Sensor "Driver Behaviour" instead. If your hardware does not support this sensor, you will not be able to make this Trigger.
• Parameter - Trigger an event based on the raw parameters received from the hardware. Requires in-depth knowledge of the parameters values, meanings and magnitudes. You can read the current parameters from the Info tab of an Object, or in the History. It is recommended to use a Sensor instead of a raw Parameter. The actual parameters that the device sends are dependant on the hardware and it's configuration.
• Sensor - The premier Event Type, this allows you to construct a custom trigger based on many simultaneous parameters, depending on the hardware you have. Refer to the Sensors tab of your object to see the sensors and how they are defined. We recommend installing the Gator Defaults. You can always delete your sensors and reload the Gator defaults if you wish to reset them.
• Service - Subscribers can access Service Events, which are configured via the Service properties of Object Editing.
• Route In - Fires an Event when a tracker enters a defined Route. You must define the Route first, a bit like a Zone In trigger, but for a Route, instead of a Zone.
• Route Out - Fires an Event when a tracker leaves a defined Route.
• Zone In - Fires an Event when a Tracker enters a Defined Zone.
  You must define the Zone first. If you create this trigger in the App then it will guide you through this process.
• Zone Out - Fires an Event when a Tracker leaves a Defined Zone. This is commonly referred to as "Geofencing", you define a Fence (Zone) and when the Tracker departs the fence (Zone) we call that a "Zone Out" condition, and this Trigger would generate an Event for that condition.
  You must define the Zone first. If you create this trigger in the App then it will guide you through this process.