This report provides a comprehensive overview of all event types supported by our platform. These events can be categorized into general, location-based events, hardware events, and service notifications. The report will display when and where each event took place on the device, illustrate the distribution of events over time through a graph, and present an aggregate summary of all events for the specified period.
In order to log these events, it's necessary to create rules for the device.
Additionally, each event has an associated driver column in the report. If a driver was assigned at the time the event was received, their name will be indicated in the report.
Report Parameters
This report utilizes not only general parameters but also some additional ones:
- Group by event type: if this option is selected, events will be organized into tables based on their type. If it's not enabled, all events will be displayed in the order they were logged by the device.
- Event type: refers to all potential event types, which are divided into four groups. A quick name search feature is available for your convenience. The search function will highlight the text you're looking for within the event names.
Possible event types
Let's delve a little deeper into the different types of events you might encounter in this report. They typically fall into one of three categories:
- Hardware events: these are processed by the device itself, using its built-in algorithms and settings. Once processed, an event is then sent to the platform.
- Software events: these are logged based on data from the platform side.
- Always running events: these are continuously triggered and don't correspond to any specific rules.
Now, let's examine which rules are associated with different events. Simply click on any of the groups to view the respective list.
- Inside auto-created geofence: refers to the 'Unauthorized movement (by coordinates)' hardware rule. It triggers if the device moves back inside an automatically created geofence.
- Outside auto-created geofence: also pertains to the 'Unauthorized movement (by coordinates)' hardware rule. It activates when the device exits an automatically generated geofence.
- Cruise control ON/OFF: events are associated with the 'Cruise control On/Off' hardware rule.
- Tracker attach: corresponds to the 'Tracker detach from the object' hardware rule and is activated when the tracker is attached to an object.
- Opening doors/trunk: This event is linked to the 'Door opening in alarm mode' rule.
- Forward collision warning: is tied to the 'Advanced Driver Assistance Systems (ADAS)' hardware rule. The ADAS tracker system triggers it when there's a potential collision with a vehicle ahead.
- GPS signal lost and recovered: pertains to the 'GPS signal lost/Recovered' hardware rule, activating when the tracker's internal systems detect a loss or recovery of GPS satellite connection.
- GSM jamming: is related to the 'GSM jamming' hardware rule. It triggers if the tracker's internal systems identify an attempt to jam the GSM signal.
- GPS jamming: corresponds to the 'GPS jamming' hardware rule, activating when the tracker's internal systems detect a jamming attempt on the GPS satellite connection.
- Harsh driving: is tied to the 'Harsh driving' hardware rule, triggering when sudden acceleration, braking, or turning is detected by the tracker's accelerometer.
- Headway warning: is associated with the 'Advanced Driver Assistance Systems (ADAS)' hardware rule. It triggers when the ADAS tracker system identifies continuous movement close to the vehicle ahead.
- Opening hood: is linked with the 'Hood opening in alarm mode' hardware rule.
- Idle period start/end: corresponds to both the hardware and software rules for 'Excessive idling'.
- Ignition activation while alarm mode is ON: is related to the 'Ignition start in alarm mode' hardware rule.
- Return to the route and deviation from the route: are tied to the 'Deviation from the route' software rule.
- Lane Departure: is associated with the 'Advanced Driver Assistance Systems (ADAS)' hardware rule. It triggers when the ADAS tracker system detects a lane departure.
- Connecting/Disconnecting with vehicle through OBDII interface: pertains to the 'Connection/Disconnection to the OBDII port' hardware rule.
- Mileage counter value change: doesn't correspond to any specific rule, but the platform always logs manual odometer value changes made by users.
- Connection restored: is tied to the 'Tracker switched OFF or lost connection' software rule.
- Speeding (hardware related): corresponds to the 'Speeding (by hardware speed)' rule, which the tracker's internal systems determine.
- Change of state of output: refers to the hardware data about the output state change.
- Pedestrian collision warning: is linked to the 'Advanced Driver Assistance Systems (ADAS)' hardware rule. It triggers when the tracker's ADAS system detects pedestrians under suitable conditions.
- Alarm mode change: is associated with the AutoControl related rules.
- Object renaming: doesn't apply to rules but always triggers if the tracker's name is changed.
- Parking start and end: correspond to the 'Parking state detection' software rule and trigger when the platform identifies the start and end of a trip according to parking detection settings.
- Traffic sign recognition: is tied to the 'Advanced Driver Assistance Systems (ADAS)' hardware rule.
- Sensor value in range/Out of range: are related to a software rule 'Parameter in range'.
- Status change: corresponds to the 'Work status change' software rule, triggering when the tracker's operating status changes.
- Call button pressed: is associated with the 'Call Button pressed' hardware rule and triggers when the device's voice call button is pressed.
- Driver change: is linked to the 'Driver change' software rule, triggering each time there's a driver change on the device.
- Driver identified and Driver not identified: correspond to the 'Identification via RFID/iButton/Camera' hardware rule.
- Drastic fuel level increase and decrease: are associated with the 'Fuel level change' software rule, triggering based on fuel sensor settings.
- Check-in: is always logged when a mark is sent from the X-GPS tracker application.
- Notifications on tachograph data download: triggers when a tachograph data download is requested from the Device Management panel.
- GPS antenna disconnected: is tied to the 'GPS antenna disconnected' hardware rule.
- Check engine light (MIL) is ON: corresponds to the 'Check Engine (MIL)' hardware rule.
- Responding to location request: is associated with the 'Location report on demand' hardware rule.
- Low battery: is linked to the 'Low battery' hardware rule.
- Distance breached/restored: refers to the 'Distance between objects' software rule.
- Excessive parking and excessive parking finished: correspond to the 'Parking time' software rule.
- Excessive driving and excessive driving finished: are tied to the 'Driving time' software rule.
- Driver left cabin and driver entered cabin: are associated with the 'Driver absence' hardware rule.
- Expected value detected: corresponds to the 'State field value' software rule, triggering each time the set value for the rule is received in the state field.
- Entry geofence: corresponds to the software rule 'Geofence entrance or exit'. It triggers when a device enters a predefined geographical area.
- Exit geofence: similarly, this event also refers to the software rule for 'Geofence entrance or exit', but it activates when a device leaves a predefined geographical area.
- Speeding (platform related): is tied to the software rule 'Speeding (by hardware speed), which is based on the speed data received from the device by the platform. It triggers when the device's speed surpasses a specified limit.
- Car alarm: corresponds to the 'Car alarm triggered' hardware rule.
- Power Supply off: is linked to the 'External power cut' hardware rule.
- Bracelet close and bracelet open: refer to the 'Bracelet sensor' hardware rule.
- Case is closed and case is opened: are connected to the 'Case intrusion' hardware rule.
- Crash: corresponds to the 'Car crash' hardware rule.
- Tracker detach: refers to the 'Tracker detach from the object' hardware rule.
- Fall detection: is tied to the 'Fall detection' hardware rule.
- Ignition and inputs change: relates to the 'Inputs triggering' hardware rule.
- Bright environment and dark environment: are associated with the 'Light sensor' hardware rule.
- Lock is closed and lock is opened: correspond to the 'Locking/unlocking (padlock)' hardware rule.
- Low battery: is linked to the 'Low battery' hardware rule.
- Connection loss: pertains to the 'Tracker switched OFF or lost connection' hardware rule, which is triggered when the device loses server connection and remains offline for a specified length of time.
- Unauthorized movement: is tied to the 'Unauthorised movement (by Motion Sensor)' hardware rule.
- Device switch off and device switch on: correspond to the 'Tracker switch ON/OFF' hardware rule.
- Panic button pressed (SOS): is associated with the 'Pressing SOS button' hardware rule.
- Strap (bolt) is cut and strap (bolt) is inserted: refer to the 'Padlock tampering' hardware rule.
- Vibration start and vibration end: are linked to the 'Vibration sensor' hardware rule.
- Fatigue driving detected and fatigue driving finished: correspond to the 'Fatigue driving' hardware rule.
- The driver is distracted and the driver is not distracted: are tied to the 'Driver distraction' hardware rule.
- External device connected and external device disconnected: refer to the 'External device connection' hardware rule.
- Safety distance breached and safety distance restored: are associated with the 'Social distancing monitoring' hardware rule.
- No Movement event occured: corresponds to the 'No movement' hardware rule.
- SMS location requests: works when the location request is sent from the widget, when the device is offline.
- Information notices: works when different informational messages appear in account.
Events table
It offers details about all events, including their triggering times, locations, and the employees assigned to the respective devices. The report also organizes this information by day, specifying the day of the week and providing a total count of events for each day.
The information is structured into the following columns:
- Time: indicates when an event took place.
- Event: provides the name of an event.
- Address: specifies the location where the event occurred.
- Employee: identifies the employee who was assigned to the device at the time the event was received.
The information can be understood in this way:
On Wednesday, July 12th, there were a total of six events logged. At 12:51:35 PM, the device was turned off. The last known location at the time of this event was recorded as 'address'. Notably, no employee was assigned to the device when this event took place.
Distribution of events in time
The graph provides a visual representation of all rules that were triggered during the specified period.
Number of events by type
This table displays the total count of each type of event that occurred on the device during the specified period. You can select all types of events to be tallied in the report settings. If a certain type of event did not occur on the device during this period, a dash will appear next to that event type's name.
Conclusion
This report is valuable for monitoring all activity on the device over a given period. It's particularly beneficial if you're tracking multiple groups of events or if you want to document specific events to analyze the circumstances that transpired.