Trip & Idle with parking report
This guide explains how to use a more advanced Trip & Idle report which contains the possibility to handle the Parking state.
In this report:
- Idling: Engine On / No movement
- Parking: Engine Off / No movement
- Configure a trip definition for your device type (if you have multiple device brands, apply a trip definition to each of them).
- Configure the driver ID (if you want to display Driver information).
1. Download TripIdleParkingWithEventRule.zip.
- Trip & Idle & Parking (Detailed).xml > the report.
- Trip & Idle parking rule.xml > Event Rule that collects data.
2. Import the Trip & Idle & Parking (Detailed) Example.xml report.
Read how to import a report template guide.
3. Enable the report Trip & Idle & Parking (Detailed) Example into your application.
Read how to enable a report into an application guide.
4. In the application, import the Trip & Idle parking rule.
Read how to import an event rule guide.
5. Create an instance of the Trip & Idle & Parking (Detailed) report.
Read how to create an instance of a report.
The new Trip & Idle & Parking (Detailed) Example instance should have selected the event rule by default.
Adding more columns to your reports
You can add more columns using Report Arguments. For the full list of variables you can add using report arguments click here.
Reprocess the report after you have made any change to the Event Rule for the changes to take effect.
- Problem 1: 'I only see Run and Parked trip state and I never see Idle'.
Solution: Verify the content of variable used as a trip definition (you can do this by adding columns in your track points panel to verify its content). If you have used another variable rather than Ignition, change it in the script, or check if it is mapped correctly using the Device Mapper.
- Problem 2: 'I customized the event rule, but I do not see the changes I made when rendering a new report'.
Solution: Reprocess the report.