Vehicle diagnostics for Malta fleets. Every fault code in one list
Vehicle diagnostics, as a list you can work through
Open the page and you see the vehicles that reported something in the last 30 days. Expand a row for the detail behind it.
Codes per vehicle
Expand a row and every code that vehicle reported is listed, with the VIN it came from. One page for the fleet, instead of one conversation per van.
Occurrence counts
The most useful number on the page. A code seen once reads very differently from the same code coming back every day for a fortnight.
Four severity bands
Severe, Watch, Info and Unknown. Unknown means a manufacturer-specific code that is not in the reference list, which is no verdict on how bad the fault is.
Last 30 days by default
Widen the timeframe when you want more history. A code drops off the list once the vehicle stops reporting it.
P, B, C or U tells you which system is complaining
Every OBD fault code is five characters, and the first one names the system it came from. P0301 is a powertrain code, and the digits behind it point at a misfire on cylinder one. A code names a symptom and a circuit. What actually needs replacing is still a diagnosis, done at the vehicle by someone with the bonnet open.
- P is powertrain: engine, transmission, fuel and emissions
- B is body: airbags, seat belts, lighting, climate control
- C is chassis: ABS, traction control and steering
- U is network, the vehicle control modules talking to each other
Three limits, before you budget for this
Every telematics vendor says diagnostics. Here is exactly where ours stops, so you can check it against your own vehicles before you talk to us.
Engine data comes from two tracker models
Fault codes, coolant temperature and RPM come from the FMC003 and the FMB003, plugged into the vehicle OBD port. Those are the two models in our range that read engine data.
A fleet running FMB120, FMC130, FM11XY, Cellocator units or the Yipii Driver app gets position and trips, and no engine data. Those vehicles never appear here. Check which tracker is on your vehicles.
Yipii does not clear codes
We read codes and keep the record. Clearing happens at the vehicle with a scan tool, in the garage or at the roadside, and no button in Yipii does it for you.
A code stops appearing on the page once the vehicle stops reporting it, so a fault put right properly drops off by itself. There is no per-code status to tick and no way to dismiss a code you would rather not look at.
Nothing fires automatically on a fault code
No alert lands on your phone, no work order opens itself, nothing escalates. Yipii triggers run on distance, service dates, inspections, documents and geofences, and none of them read fault codes.
The weekly review below is the workflow that fills the gap. See what triggers can watch.
Put the review in the calendar and codes stop piling up
Because nothing alerts you, the habit is the feature. Book a slot once a week, open the last 30 days, and start with the codes that keep coming back. Most weeks there is nothing to do. The week a code starts repeating on the same van, you find out while it is still a booking rather than a recovery off the Mrieħel bypass.
- A weekly slot, the routine the Yipii docs recommend
- Start with the highest occurrence counts, then read the severity band
- Create a work order straight from the row
- The job, the cost and the parts stay on the vehicle record
Included with Yipii Mobility, the add-on that extends your IoT account. One subscription covers everything in the app, so no feature here is sold on its own. What Yipii Mobility includes
Frequently asked
No. Yipii reads fault codes and keeps the record. Clearing happens at the vehicle with a scan tool, in the garage or at the roadside. A code stops appearing on the diagnostics page once the vehicle stops reporting it, so a fault put right properly drops off on its own. There is no per-code status to tick in Yipii and no way to dismiss a code from the app.
Vehicles fitted with an FMC003 or an FMB003 and connected to the OBD port. Those two models are the only ones in our range that read engine data, which covers fault codes, coolant temperature and RPM. Everything else we fit reports position: the FMB120, the FMC130, the FM11XY, the Queclink dashcams, older Cellocator units and the Yipii Driver phone app. A vehicle without an OBD-connected tracker never appears on the diagnostics page at all.
No. Nothing fires automatically on a fault code, so there is no alert, no automatic work order and no escalation. Yipii triggers run on distance, service dates, inspections, documents and geofences, and none of them read fault codes. That is why we recommend a weekly review in the calendar rather than waiting to be told.
P0301 is a powertrain code pointing at a misfire on cylinder one. Every OBD fault code is five characters and the first one names the system: P for powertrain, B for body, C for chassis, U for the network between control modules. A code names a symptom and a circuit, so treat it as the start of a diagnosis. Yipster can look one up for you in a conversation and list the common causes.
The page opens on the last 30 days and lists every asset that reported a code in that window. Widen the timeframe if you are chasing something intermittent, or if the page looks empty because the fleet has been quiet. Each code carries its own first and last occurrence, so you can see how long it has been going on without changing the window.
From the code to the invoice
The severity bands, the troubleshooting list for a vehicle that never shows up, and the route from a row to a work order are written out in the diagnostics guide in the Yipii Mobility docs.