Vehicle Maintenance is a module available in the Summary menu where you can find information about the DTCs (Diagnostic Trouble Codes) collected from your vehicles:
To be able to access this module, you must be granted the following permission:
Once you access the module, you will see the following table:
This table shows the vehicles of your fleet and information regarding their DTCs.
It contains the following columns:
Column | Description |
Vehicle |
The license plate of the vehicle |
Odometer | The current Odometer's reading |
Service |
For vehicles that supply it, Service is the estimated distance to the next scheduled maintenance (same as displayed in the Intranet - CANBus data view). It's calculated as currentDate + serviceDate / avgKmsPerDay. Please note that this is vehicle dependent and we actually don't know what each vehicle is supplying. |
Avg mileage/day | Average mileage per day |
Service expected date |
Expected date for the next scheduled maintenance |
Total of DTCs reported |
Number of DTCs reported for the vehicle |
Number of active DTCs |
Number of active DTCs reported for the vehicle |
Last DTC code |
The code of the last reported DTC |
Date |
Date of the last reported DTC |
Description | Description of the last reported DTC. This description is always displayed in English |
Above the table, you will find a Search box and a Vehicle filter, that you can use to filter the table:
You may click on the License plate of a vehicle with reported DTCs to open its details:
Here, you can find all the DTCs reported for the selected vehicle. DTCs displayed in red are currently active.
It contains the following columns:
Column | Description |
Start date | The start date of the reported DTC |
Odometer | Odometer at the moment of the report |
End date | The end date of the reported DTC |
DTC | DTC's code |
Description | DTC's description. This description is always displayed in English |
About the DTCs
Interpreting the DTC Code
There is a defined logic behind the format of the DTC error codes:
- The first character is always a letter. It indicates which control system has an issue, and has the following possible values and meanings e.g. Powertrain (P), Network (U)
- The second character is a digit, typically 0 or 1, and shows whether or not the code is standardized or OEM-specific. e.g. Standard (0), OEM specific (1)
- The third character is also a digit, ranging from 1 to 8. This reveals the subsystem at fault. e.g. 1 refers to the fuel or air metering system, 2 refers to the fuel or air metering injection system
- The fourth and fifth characters are read together as a two-digit number between 0 and 99 known and is an index designed to better define the specific fault.
How critical is the code?
- There can be a lot of DTC codes generated and not all of them are important or critical. Unfortunately, the code gives no indication of the relative importance of the issue.
- The more important codes should trigger a warning light on the vehicle dashboard and drivers should report these to the fleet manager so the fleet manager can provide guidance on the appropriate course of action based on the DTC code.
Acting on the DTC Code:
- The DTC code will identify the area of the problem. However, engineers are still encouraged to think like detectives before jumping to a conclusion about a repair based on the DTC code.
Service requirements
With the OBD2 service activated (only C4OBD v8, available soon), beside DTCs, you can also see Service requirements information.
-
Vehicle Maintenance
- Distance and Service Expected date using AVG Mileage/Day (last 30 days average mileage),
- Next service (month/year)
-
Engine oil Maintenance
- Distance and Service Expected date using AVG Mileage/Day (last 30 days average mileage),
- Next service (month/year)
-
Brake Maintenance (These dates may present excessive values until the vehicle detects brakes usage)
- Front brake distance and Service Expected date using AVG Mileage/Day (last 30 days average mileage),
- Rear brake distance and Service Expected date using AVG Mileage/Day (last 30 days average mileage).
-
Brake fluid Maintenance
- Service Expected date (month/year)
NOTE: Some vehicles may not report all this fields. Please, check with your Frotcom Certified Partner.
Service requirements details
Also, automatic appointments are created and updated everyday using the vehicle data received, you can see when was the last updated from the vehicle on top right corner, and you can access the appointments alarms created by clicking the Appointments button (top right corner)
Automatic appointments alarms
you can updated the warnings, periodicity, and other alarm settings, but remember that Next occurrence will be updated daily, when your vehicle travels or execute a maintenance distances and/or dates are automatic updated.
The date presented in the Vehicle Maintenance > Service expected date column is the closer date of all collected values (above images)
and by clicking the Service expected date you can see the Service requirements details.
Comments