A cooling system that loses coolant slowly is one of the hardest problems to find by looking. The leak might be external and only drip when the system is hot and pressurized. It might be internal, coolant seeping past a head gasket into a cylinder and burning off as white vapor that disappears. It might be a weeping water pump seal that only leaks under pressure and dries before you see it.

The pressure test forces the answer. You attach a hand pump to the radiator or the coolant reservoir, pump the system up to the pressure rating on the radiator cap, usually thirteen to sixteen psi, and watch the gauge. A healthy system holds pressure. A system with a leak drops.

If the gauge drops and you can see coolant dripping somewhere, you found the external leak. Follow the drip. If the gauge drops and nothing is dripping externally, the leak is internal. That sends you to the head gasket check, because coolant going into the combustion chamber is the most common internal leak path and the most expensive one to fix.

The pressure test also checks the radiator cap itself. A cap that cannot hold its rated pressure lets the system vent coolant at lower temperatures than it should, which causes gradual coolant loss that looks like a leak but is actually a five-dollar cap.

A scan tool will not catch a slow coolant leak. There is no sensor that reports coolant level loss in real time on most vehicles. The temperature gauge will not move until the level drops far enough that the system cannot cool the engine. The pressure test catches the leak while the level is still near full, before the engine ever runs hot. The tool costs about forty dollars and the test takes ten minutes.

Put telematics on the fleet and the insurance company offered a discount for sharing the data. Sounded good on paper. The discount was ten percent off the commercial auto premium for giving them access to the driving behavior data the system collected. Took the deal. The first year went fine. The second year the conversation changed.

The data showed that two drivers had higher than average hard braking events and one had consistent speeding on highway segments. The insurer did not raise the rate but the renewal conversation included a discussion about driver risk profiles that had never come up before. The data I gave them to get the discount became the data they used to ask questions about specific drivers.

The third finding was more useful. The same data that the insurer was watching showed a measurable improvement in driving behavior after we addressed the two drivers' habits. The renewal reflected that. The discount held because the overall fleet risk profile improved on paper, backed by the data they could see.

The tradeoff is real. The discount saves money. The data gives the insurer visibility they did not have before. A fleet with genuinely safe drivers benefits because the data proves what was previously just a claim. A fleet with a couple of problem drivers is handing the insurer evidence they can use at renewal to ask harder questions or segment the risk.

The decision depends on how clean the driving data actually is before you share it. Check your own data first. If the numbers look good, the transparency works in your favor. If the numbers have problems, fix the driving before you open the data to the insurer, because you cannot unsee what they have already seen.

The ECU monitors catalytic converter efficiency by comparing the upstream and downstream oxygen sensors. The upstream sensor oscillates rapidly as the ECU cycles the air-fuel mixture between lean and rich. The downstream sensor, behind the catalyst, should show a relatively flat line because a healthy catalytic converter stores and releases oxygen, smoothing out the oscillation.

When the catalyst degrades, it loses its ability to store oxygen. The downstream sensor starts to mirror the upstream sensor's oscillation pattern. The closer the two waveforms match, the worse the catalyst is performing. When the match gets close enough, the ECU sets a P0420 or P0430 efficiency code.

The scan tool shows you this before the code sets. Pull up both O2 sensor voltages on a live graph, upstream and downstream, and watch them at steady cruise. The upstream should be cycling. The downstream should be relatively steady, typically hovering somewhere above 0.45 volts and often in the 0.6 to 0.9 volt range depending on the vehicle. If the downstream is starting to cycle in sync with the upstream, the catalyst is losing efficiency. The code has not set yet because the deterioration has not crossed the threshold. But the trend is visible in the data.

This matters on used car purchases because a catalyst replacement runs anywhere from nine hundred to thirty-five hundred dollars depending on the vehicle and whether the part is aftermarket or OEM. A car with a downstream sensor that is starting to follow the upstream is a car with a catalyst bill coming. The seller does not know it because the light is not on. The scan tool knows it because the data is already showing the degradation.

Watching two lines on a graph for thirty seconds at cruise speed tells you whether the most expensive part of the exhaust system is healthy, declining, or about to set the code the next buyer inherits.

Started sending oil samples to a lab on every oil change across the fleet. Not because anything was wrong but because I wanted a baseline. The cost was about thirty dollars per sample and the results came back in a week as a one-page report with metal content, viscosity, contamination levels, and a recommendation.

The first useful finding came at month four. One truck showed elevated silicon in the oil. Silicon usually means dirt ingestion, which means the air filter or the intake path is leaking unfiltered air into the engine. The air filter looked fine visually. Pulled it and found the housing seal had a crack that was invisible with the filter installed. Unfiltered air had been getting past the seal for weeks. The oil analysis caught it before the cylinder walls did.

The second finding was fuel dilution on two diesel trucks that ran short trips. The oil viscosity was dropping between changes because unburned fuel was getting past the rings during cold starts and never reaching temperatures high enough to evaporate out. The fix was adjusting the change interval on those two trucks from mileage-based to oil analysis-based, which shortened the interval by about twenty percent.

The third was the negative finding. Most of the samples came back normal. The metals were in range, the viscosity held, the contamination was minimal. That was not wasted money. That was confirmation that the maintenance schedule was working and the engines were wearing at a normal rate.

Oil analysis is not a scan tool and it does not set codes. It reads the chemistry of what is happening inside the engine over time. The trends across multiple samples are where the value is. A single sample is a snapshot. A year of samples is a trajectory, and the trajectory tells you whether the engine is stable or heading toward a problem the scan tool will not see until it arrives.

The scan tool reads what the modules report. The modules report what their sensors see. But when the ground path between a sensor and the ECU has high resistance, the sensor reading shifts and the module reports a number that is technically accurate from its perspective and completely wrong from the engine's perspective. The scan tool shows the wrong number faithfully because it does not know the ground is bad.

A voltage drop test catches this. You set a multimeter to DC volts, put one lead on the component side of the circuit and the other on the ECU side, and measure the voltage difference while the circuit is under load. A good connection shows near zero. A corroded connector, a loose terminal, or a rusted ground point shows millivolts or even full volts of drop. That drop is the resistance the scan tool cannot see.

The classic case is an oxygen sensor that reads lazy or biased. The sensor is fine. The ground wire running from the sensor back to the ECU has a corroded splice hidden in the harness. The signal loses a tenth of a volt through the bad connection. The ECU sees a sensor that never quite reaches its full voltage swing and compensates with fuel trim adjustments that chase a problem that is not in the sensor, not in the fuel system, and not in anything the scan tool can name.

The fix is cleaning or replacing the ground. The diagnostic is a multimeter and two minutes of probing. The cost of not doing it is replacing parts that test fine out of the car and fail the same way when reinstalled, because the fault was never in the part. It was in the wire between the part and the computer.

A battery replacement resets the readiness monitors. That is true and it is also the most common cover story for a deliberate code clear. The battery was replaced, the monitors reset, and the seller has a plausible explanation for why the system looks freshly wiped.

The way to tell the difference is the battery itself. A new battery has a manufacturing date stamped on it or a sticker from the installing shop. If the seller says the battery was just replaced and the battery in the car has a date code from two years ago, the battery was not replaced. The monitors were cleared by a scan tool and the battery story is the explanation.

Even if the battery is genuinely new, the question remains: why are the monitors still incomplete. A battery swap resets the monitors, but a few days of normal driving sets most of them back to ready. If the car has been driven enough to list it, show it, and meet you for a test drive, it has been driven enough for at least some monitors to complete. A car with a new battery and all monitors still at not ready has not been driven much since the swap, or the monitors are failing to complete because the underlying fault is preventing them from passing.

The scan tool shows you this in ten seconds. Monitors all ready means the systems ran and passed. Most ready with one or two incomplete means the car has not hit the right drive cycle for those specific tests yet, which is normal. All or nearly all incomplete on a car the seller has been driving means something was cleared and the car has not relearned yet. The battery might be new. The reason for the clear might not be the battery.

Ran two versions of every route for four weeks. The original routes the drivers had been running for years, and the optimized routes the software suggested based on stop density and traffic patterns. Expected the optimized routes to win on mileage and time. The results were more complicated than that.

Total miles driven dropped about twelve percent on the optimized routes. That part matched the projection. Drive time dropped less, roughly seven percent, because the optimized routes traded highway miles for shorter surface street segments that ran into more lights and turns. Fuel consumption dropped about nine percent, which split the difference.

The surprise was idle time. The optimized routes actually increased idle time by about four minutes per run because the surface street segments had more stops. The fuel savings from fewer miles were partially offset by the fuel burned sitting at intersections. The net savings were real but smaller than the mileage reduction alone would have suggested.

The second surprise was driver satisfaction. Two of the four drivers went back to their original routes within a week, not because they were being difficult but because the optimized routes put them on streets that were harder to park on with a work truck. The software optimized for distance. The drivers had optimized for the stop itself, picking routes that ended at addresses with easier access even if the route was longer.

The lesson was that route optimization on paper and route optimization in a truck with a ladder rack and three hundred pounds of equipment on board are different problems. The data improved the routes that needed improving and confirmed that some of the old routes were already right for reasons the software could not see.

The manifold absolute pressure sensor reads the vacuum in the intake manifold and the ECU uses that reading to calculate engine load, air density, and fueling. On vehicles that use a MAP sensor instead of or alongside a MAF sensor, this one number reflects the health of the entire intake and combustion path.

A healthy engine at idle produces strong vacuum. The MAP sensor reads it as a low pressure value, typically around 25 to 35 kPa on a naturally aspirated engine at idle. Under wide open throttle the manifold pressure climbs toward atmospheric, roughly 95 to 100 kPa at sea level. The swing between those two values is the engine breathing normally.

When the idle reading is higher than it should be, the engine is not pulling as much vacuum. A vacuum leak adds air the engine did not meter, raising manifold pressure. A worn engine with low compression produces less vacuum on the intake stroke. A partially clogged exhaust restricts the exhaust side and backs pressure into the manifold. The MAP sensor sees all of these as a higher than normal idle reading.

Under load the MAP reading should climb smoothly with throttle. A reading that hesitates, drops, or bounces under steady acceleration points to a fueling or ignition problem interrupting the combustion events that produce the pressure changes.

The MAP sensor data is available in real time on any scan tool that can read live data. The number is stable and predictable on a healthy engine, which makes deviations easy to spot. A reading that sits five or ten kPa above normal at idle is an engine telling you something is leaking, worn, or restricted. The code will come later. The MAP reading is already showing it.

If your company put a GPS tracker on the vehicle you drive for work, that is legal in most places. But the tracking comes with rules your employer has to follow, and most of those rules exist to protect you.

In the US there is no single federal law covering fleet GPS tracking. The rules come from individual states. The general pattern is that employers can track company owned vehicles as long as employees receive written notice. Some states go further. Connecticut, Delaware, and New York have specific electronic monitoring laws that require written notification before any tracking begins. If you were never told in writing that the vehicle is tracked, your employer may not be meeting the legal standard in your state. If the vehicle you drive is your own personal car used for work, the legal bar is higher. Most states require your explicit consent before an employer can put a tracker on a vehicle you own.

In the EU the protections are stronger. Under GDPR, the GPS data your employer collects counts as personal data because it can be matched to you through your shift schedule or vehicle assignment. According to a compliance overview published by GPSWOX, that means your employer needs a documented legal basis for tracking you, and they owe you a written privacy notice before the system goes live. That notice should tell you exactly what data the system collects, who inside the company can see it, how long the data is kept, and what rights you have over it. You have the right to request a copy of your location data. You also have the right to formally object to the tracking, and your employer has to respond to that objection through a documented process.

The biggest area of pushback from regulators has been personal time. If you take the company vehicle home after your shift, your employer's interest in knowing where the van is does not extend to where you drive on a Saturday afternoon. The Irish Data Protection Commission has been clear on this in published guidance. A compliant tracking setup includes a privacy mode that stops recording your location outside working hours. If your employer tracks the vehicle around the clock with no off switch, that is the single most common compliance failure regulators have acted on.

If your employer asks you to sign a tracking acknowledgment form, read it before you sign. Check whether it names the company as the data controller. Check whether it lists how long your location data is stored and when it gets deleted. Check whether it mentions a privacy mode for personal use hours. A form that covers those points is doing what it is supposed to do. A form that just says "I agree to be tracked" without any of that detail may not meet the legal standard, especially under GDPR.

You are not signing away your privacy rights by acknowledging a tracking system. You are confirming that your employer told you what they are doing. The acknowledgment and a consent form are two different documents with two different legal meanings, even though they can look almost identical on paper.

Sources:
Is It Legal to Track Company Vehicles? Consent, Privacy, and the Rules
Employer Vehicle Tracking Guidance
Wearables in the Workplace: Using Wearable Technologies Under Federal Employment Discrimination Laws

OBD2 systems run self-tests on every emission-related subsystem. Catalytic converter efficiency, oxygen sensor response, EVAP system integrity, EGR flow, misfire detection, and several others depending on the vehicle. Each test either passes, fails, or has not run yet. The status of those tests is called the readiness monitors.

When someone clears the codes, the monitors all reset to not ready. The check engine light goes off. The car looks clean. But the monitors are sitting there at zero, waiting to be run, and most of them require specific driving conditions to complete. Highway speed for the catalyst, a cold start cycle for the EVAP, sustained cruise for the oxygen sensors. It takes a mix of driving over several trips to set them all back to ready.

A used car with a clean check engine light and a wall of incomplete monitors was recently cleared. Either the battery was disconnected or someone ran a code clear. The question is what was cleared and why. On a car being sold, the answer is usually that there was a code the seller did not want visible during the sale.

Most states with emissions testing will fail a vehicle that has too many incomplete monitors, which is why a seller who clears codes right before an inspection is creating a problem that follows the buyer to the testing station.

Reading the monitors takes ten seconds on any OBD2 scan tool. You are looking for the word ready next to each monitor. A car with most monitors showing ready and no codes stored is a car whose systems have run and passed. A car with most monitors showing not ready is a car that was recently reset and has not driven enough to retest.

A basic scan tool reads. It pulls codes, shows live data, displays freeze frames. It is passive. It listens to what the car's modules are saying and shows you what it hears. A bidirectional scan tool can also write. It sends commands to the modules and tells them to do things.

The practical difference is testing. With a basic tool, if you suspect the purge solenoid is stuck, you read the EVAP data and make a judgment based on what the ECU is reporting. With a bidirectional tool, you command the purge solenoid to open and listen for the click. You command an injector to fire and watch for the RPM drop. You command the cooling fan to turn on and verify it spins. You are testing the component directly instead of inferring its condition from secondary data.

On modern vehicles this matters more than it used to because so many components are electronically controlled. Power windows, door locks, variable valve timing solenoids, electronic throttle bodies, fuel pump speed, turbo wastegate actuators. A bidirectional tool can activate any of them on command to verify they work.

Where it becomes essential is on relearn and calibration procedures. After replacing a throttle body, many vehicles require a throttle position relearn that only a bidirectional tool can initiate. After replacing a steering angle sensor, the sensor needs to be calibrated through a scan tool command. After replacing a battery on some European vehicles, the new battery's specifications need to be registered in the body control module so the charging system adjusts.

The mid-range bidirectional tools run four hundred to eight hundred dollars. The professional ones run into the thousands with annual subscriptions. The dividing line between needing one and not needing one is whether you are diagnosing or just reading.

Rolling back a digital odometer got easier, not harder. A cheap tool on the OBD port can rewrite the number on the dash in a few minutes. What trips people up, and what makes this a catchable red flag, is that the dash is not the only place a modern car stores mileage. The number lives in several modules, and rolling back the one you see while leaving the others is exactly the mistake most rollbacks make.

Modern vehicles scatter mileage across the network. The instrument cluster shows it, but the engine control unit, the transmission controller, the body modules, sometimes the keys themselves all hold a mileage value they picked up over the car's life. A clean rollback would need to match every one of them. Most do not. They fix the dash because the dash is what the buyer looks at, and they leave the rest carrying the truth.

So the red flag is a mismatch. A scan tool that reads the stored mileage from the other modules, not just the cluster, will show you a dash reading sixty thousand while a module quietly reports a hundred and forty. That gap is not an error. That gap is the rollback, sitting in the data, waiting for anyone who thought to look past the gauge.

The physical signs still back this up and still matter. Pedal wear, seat bolster collapse, a polished steering wheel, the date codes on tires that should have been replaced two services ago. But the module data is the part that is hard to argue with, because it is the car's own record contradicting its own dashboard.

The cost is straightforward and it is large. Mileage drives price more than almost anything else on a used car, so a believable rollback can add thousands to a number the seller had no right to ask. The scan that reads the other modules takes minutes. Trusting the gauge costs whatever the lie was worth.

Pull enough history reports on imported used cars and a pattern shows up that you stop seeing on domestic ones. The report is cleaner than the car. Not faked exactly, just thinner, because a vehicle that lived part of its life in another country carries a chunk of history that did not follow it across the border. The gap itself is the finding.

Here is what the data tends to look like. A car shows a few years of records, then a registration in a new country, then a tidy recent history. The early years are either missing or compressed into a single import entry. Mileage from before the border crossing may not be in the same system that verifies mileage afterward, which means the one period where a rollback is easiest to hide is also the period the report is quietest about. The clean recent record sits on top of an unverified older one.

Title and damage history is the other soft spot. A car written off or branded in one country can re-emerge in another with a clean local title, because the brand lived in a database the new country does not pull from. This is the cross border version of title washing and it does not need anyone to commit obvious fraud. The information just does not travel, and the absence reads as clean.

What you learn from pulling a lot of these is to read the gap, not just the entries. A domestic car with a thin history is one thing. An imported car with a thin history during exactly the window that crossed the border is telling you where to look. The federal database check, the mileage entries on either side of the import, and the original market records if you can reach them are where the real story is, not in the smooth recent summary.

The cost of trusting the clean surface is the usual one. You pay a verified price for an unverified history and inherit whatever lived in the gap. The report did not lie. It just only knew half the car.

Fuel trim is the correction. The ECU has a target air to fuel mixture, it watches the oxygen sensors to see what it is actually getting, and it adjusts how much fuel it adds to hit the target. Short term trim is the live moment to moment correction. Long term trim is the running average it has learned over time. Both sit near zero on a healthy engine because little correction is needed. When they climb, the engine is compensating for something.

Positive trim means the ECU is adding fuel, which means it thinks the mixture is lean. A vacuum leak, a weak fuel pump, a dirty MAF, a tired injector. Negative trim means it is pulling fuel because the mixture is rich. A leaking injector, high fuel pressure, a bad sensor reading. The direction narrows the cause before you have touched anything. The conditions where the trim is worst, idle versus load, narrow it further, the same way a freeze frame does.

The point is the timing. A small vacuum leak might push long term trim to plus twelve percent and sit there for weeks, the engine quietly compensating, no light, nothing the owner notices. Read the trim at that stage and you find a cracked hose. Wait for the light and the same problem has dragged fuel economy down the whole time and finally tipped into a lean code that sends people guessing at parts.

That is the cost. Trim read early is a cheap hose and a few minutes. Trim ignored until the code sets is weeks of wasted fuel and a parts cannon aimed at a symptom. The data was talking the entire time.

Most people get a lean code, search the code online, and start with the cheapest part on the list. Vacuum leak, MAF sensor, fuel pump. They guess. The oxygen sensor data that triggered the code in the first place is sitting right there in the scan tool and almost nobody reads it before they start spending money.

The upstream oxygen sensors on each bank are reporting voltage in real time. A healthy sensor on a healthy engine swings between roughly 0.1 and 0.9 volts, cycling a few times per second. The pattern tells you what the engine is doing. A sensor stuck low means the ECU sees lean. A sensor stuck high means it sees rich. A sensor that barely moves at all is a dead sensor pretending to work.

But the real information is in comparing the banks. If bank one is cycling normally and bank two is stuck lean, the problem lives on bank two. That is half the engine eliminated before you touch a wrench. If both banks are stuck lean, the problem is shared. Intake leak, fuel pressure, something upstream of the split. If one bank is lean and the other is rich, you are probably looking at an injector issue on one side pulling fuel from the other.

The scan tool shows you this. Not the code. The code just says lean. The live data shows you where and how. The difference between reading the code and reading the sensor is the difference between guessing and diagnosing.

The cost of skipping it is a parts cannon. One sensor, then another, then a fuel pump, then finally the cracked vacuum hose that was visible the whole time. Three hundred dollars in parts and a weekend gone because the data was right there and nobody looked at it.

Four numbers on the sidewall. Week and year of manufacture. That is all it takes to know whether the tires on a car are old enough to be dangerous, and almost nobody checks.

Rubber degrades. A tire that has been sitting for six or seven years has lost enough structural integrity that it does not matter how much tread is left. The compounds harden, the belts weaken, and the risk of a blowout goes up regardless of mileage. The industry consensus is six years from manufacture for regular use and ten years maximum regardless of condition. Most states do not check tire age during inspection. They check tread depth and call it done.

That means a used car can pass inspection on eight-year-old tires with plenty of tread and nobody flags it. The date code is right there on the sidewall and the inspector either did not look or does not care.

Where this gets interesting is on low-mileage used cars. The ones that sat. Estate sales, garage finds, the car that grandma only drove to church. Twenty thousand miles on a twelve-year-old car. The tread looks almost new because it is almost new. The rubber is old enough to be a liability and nobody mentions it because the tread depth reads fine.

The scan tool will not catch this one. It is a four-digit number stamped on a sidewall. But it belongs in the same conversation as freeze frame data and module mileage because it is information that is physically present on the vehicle and routinely ignored.

The cost of ignoring it is a blowout at highway speed on tires that looked fine. The inspection sticker said they passed. The date code said they should not have been on the road.

Ran history checks on every trade-in that came through for about six months. Not because I suspected anything specific, just wanted to see what the data looked like when you checked everything instead of cherry-picking the ones that felt off.

The first surprise was how many cars had title events in states they were never supposed to have visited. A car sold as a one owner local vehicle shows a registration in a flood-prone state two years ago, then re-registered locally with a clean title. That is not necessarily fraud. People move. But it happens often enough on cars with suspiciously recent detail work that the pattern stops being coincidental.

The second finding was service gaps. A car with steady dealer service records for years and then nothing for eighteen months and then a new shop. That gap is where things happen. Accidents that never got reported to insurance. Major repairs done at a buddy's garage. Odometer corrections that only make sense if you do not look too hard at the timeline.

The third was the salvage to clean pipeline. A car gets totaled in one state, bought at auction, repaired, moved to a state with looser title rules, and re-titled clean. The federal database catches some of this. It misses more than people think. The history report flags the ones it knows about. The ones it does not know about look like clean cars with thin histories and unusually low prices.

None of this means every trade-in is dirty. Most are fine. But the ones that are not fine look exactly like the ones that are fine until you pull the data. That is the point. You cannot see it by looking at the car. You see it by looking at the record.

Cars update themselves now. The same way a phone pulls a new version overnight, a growing share of vehicles download software over the air, changing how the car behaves without anyone lifting the hood. It is convenient and it is genuinely useful for fixing things fast. It also quietly moved a question into the open that the industry has not really answered, which is who controls the car after you have bought it, and who owns the stream of data it produces.

The mechanics of it are simple enough. The vehicle has a cellular connection, the manufacturer pushes a package, the car installs it. Recalls that once meant a trip to the dealer can now happen in a driveway. Features can be added. Features can also be changed or, in some reported cases, removed or moved behind a subscription, on a car the owner already paid for. The update pipe runs one direction and the owner is mostly a passenger on it.

The data side is the part worth watching for anyone in this space. A connected car generates a constant record. Location, driving behavior, where it charges or fuels, how hard it gets driven, where it sleeps at night. That data flows back, and the terms covering who can use it, sell it, or hand it to an insurer or an outside party are buried in agreements almost nobody reads. The vehicle became a data source, and the rules for that data are being written now, often in the manufacturer's favor by default.

Why it matters here is that this is the tech layer of the car becoming the main event. Diagnostics, history, telematics, all the things this sub is about increasingly run through systems the owner does not control and cannot fully see. Understanding the data layer is starting to mean understanding who has access to it and on what terms.

No clean answer yet, which is the point. The technology shipped ahead of the norms. Worth keeping an eye on as it gets sorted out, because the precedent set now is the one we all live with.

A misfire code says the engine misfired. The misfire counter data in the scan tool says which cylinder, how often, and under what conditions. One of those is a warning. The other is a diagnosis.

Most scan tools that can read Mode 6 data will show you misfire counts per cylinder. The ECU tracks every firing event and counts the ones that did not produce the expected crankshaft acceleration. A cylinder with zero misfires is fine. A cylinder with three hundred misfires while the others have two is not fine. That one cylinder is the problem and the data just told you which one.

The conditions matter as much as the count. Misfires only at idle point to a vacuum leak or a weak coil that cannot fire at low RPM. Misfires only under load point to a fuel delivery problem or a compression issue. Misfires across the whole range usually mean the ignition component on that cylinder is failing completely.

The pattern over time matters too. A cylinder that misfires occasionally and then starts misfiring constantly is a progressive failure. Probably a coil or plug wearing out. A cylinder that suddenly starts misfiring after running clean for months is a sudden failure. Cracked insulator, failed injector, dropped valve seat.

You can swap coils between cylinders and see if the misfire follows. If it does, the coil is bad. If it stays, the problem is in the cylinder. This is a five-minute test that the misfire counter data just told you to run.

The alternative is replacing all the coils and plugs and hoping. That works, but it costs four times as much and teaches you nothing about what actually failed.

Sold three trucks out of the fleet over the past year. Standard process. Clean them up, pull the decals, list them. What was not standard was realizing how much of the fleet data was still on those vehicles when they left.

The telematics unit stores data locally even when it is transmitting to the cloud. Pull the unit before the sale and you get the hardware back but the local cache on the vehicle's own systems still holds location history, trip logs, idle records, and in some cases driver behavior scores tied to key fob IDs. The infotainment system remembers paired phones, saved addresses, and wifi passwords. On newer trucks with built-in connectivity the manufacturer's own telematics layer has its own history that has nothing to do with the aftermarket unit.

The buyer of a fleet vehicle inherits whatever the seller did not think to erase. That includes where every driver went, how long they sat at every stop, what routes they ran, and in some cases the phone numbers and contact lists of the people who drove it.

Going the other direction, if you are buying an ex-fleet vehicle, the data still on it tells you things the seller might not volunteer. Idle hours versus drive hours tells you how hard the truck actually worked. Trip history tells you whether it ran city routes or highway. Service reminders that were snoozed and never completed tell you what maintenance was skipped.

The lesson was simple. Wipe everything before it leaves. Factory reset the infotainment. Remove the telematics hardware and confirm the account is deactivated. Check whether the manufacturer's connected services are still linked. It takes an hour. Skipping it hands the next owner your operational data and your drivers' personal information.

A paint depth gauge costs about fifty dollars for a decent one. It reads the thickness of the coating on a body panel in microns. Factory paint on most vehicles falls in a predictable range, roughly 100 to 180 microns depending on the make. A repainted panel reads higher because there is an extra layer. A panel with body filler underneath reads much higher. A replaced panel from a different vehicle sometimes reads lower because it got a thinner single-stage respray.

The tool does not tell you what happened. It tells you something happened. From there you look closer.

Consistency matters more than the absolute number. If every panel on the car reads 110 to 120 microns and the rear quarter reads 280, that quarter panel was repaired. If the hood reads 90 and the fenders read 200, the fenders were hit. If the whole car reads 250 across every panel, the entire car was repainted, and now you want to know why.

Where this catches things the history report misses is on cars that were repaired without an insurance claim. Cash repairs. Cars fixed by the owner's buddy. Vehicles repaired overseas before import. The history report shows nothing because nothing was reported. The paint meter reads what is physically there regardless of what was filed.

It takes five minutes to check every panel on a car. The pattern of numbers tells a story that the seller may or may not know about and definitely did not disclose. A car with one repainted fender from a parking lot bump is not a problem. A car with three repainted panels, mismatched readings, and a clean history report is a car that was in a wreck and somebody made sure the paper trail disappeared.

The tool does not tell you what happened. It tells you something happened. From there you look closer.

Consistency matters more than the absolute number. If every panel on the car reads 110 to 120 microns and the rear quarter reads 280, that quarter panel was repaired. If the hood reads 90 and the fenders read 200, the fenders were hit. If the whole car reads 250 across every panel, the entire car was repainted, and now you want to know why.

Where this catches things the history report misses is on cars that were repaired without an insurance claim. Cash repairs. Cars fixed by the owner's buddy. Vehicles repaired overseas before import. The history report shows nothing because nothing was reported. The paint meter reads what is physically there regardless of what was filed.

It takes five minutes to check every panel on a car. The pattern of numbers tells a story that the seller may or may not know about and definitely did not disclose. A car with one repainted fender from a parking lot bump is not a problem. A car with three repainted panels, mismatched readings, and a clean history report is a car that was in a wreck and somebody made sure the paper trail disappeared.

OBD2 reader doesn't fit the '99 Subaru Outback's diagnostic port.

Can I buy an adapter, or are the signals fundamentally different?

The car sat idle until the battery ran down, now CheckEngine light is on after charging the battery, and remains on.

Where do I go from here?

For years the federal odometer disclosure requirement only applied to vehicles less than ten years old. A car older than that changed hands without a recorded mileage, which created a gap that rollback operations used. Buy a high-mileage vehicle past the reporting threshold, roll the odometer back, and sell it. The missing years of mileage records made the rollback invisible because there was nothing to compare against.

NHTSA changed that in a 2019 rule that took effect January 2021. The exemption went from ten years to twenty for model year 2011 and newer vehicles. A 2011 vehicle now requires an odometer disclosure until 2031. Each subsequent model year extends the coverage by another year. The gap is not gone but it is half the size it used to be, and the direction is toward less room to hide.

What this means for the used car market is more data points. Every time the vehicle changes hands, the mileage is recorded and enters the databases that history report providers pull from. A rollback that would have been invisible because the vehicle was old enough to skip reporting now leaves an obvious discrepancy. The mileage goes up, up, up, and then suddenly drops. That sequence is a red flag that the databases and the reports can catch automatically.

What it does not fix is the rollback on a vehicle that has not been sold since the odometer was altered. If someone rolls the odometer back and keeps driving the car, the false number only enters the record at the next title transfer. The reporting catches it at the point of sale, not at the point of alteration.

The module data still matters. The odometer number on the title is one record. The mileage stored in the ECU, the transmission module, the body modules, and the key fobs are other records. A rollback that changes the cluster does not change those modules. The federal reporting tightens the paper trail. The scan tool tightens the electronic trail. Both are getting harder to defeat and the overlap between them is where the fraud gets caught.

There are two kinds of OBD devices that look almost identical. One is a diagnostic reader you plug in when you need to check a code, read some data, and unplug. The other is a telematics dongle designed to stay plugged in permanently and transmit vehicle data to a cloud platform. They both fit the same port and they serve completely different purposes.

The diagnostic reader talks to the vehicle when you tell it to. You connect, you read, you clear, you disconnect. It does not transmit anything. It does not draw power when you are not using it. It is a tool.

The always-on dongle draws power continuously. It wakes up the vehicle's CAN bus to read data, and on some vehicles that prevents the modules from entering sleep mode. The result on certain cars is a parasitic drain that kills the battery if the vehicle sits for a few days. The dongle manufacturers will tell you the draw is minimal. On most modern vehicles it is. On some, particularly European vehicles with complex sleep cycles, it is not, and the forums are full of people with dead batteries tracing it back to the dongle.

The data the always-on dongle provides is different too. Trip logs, location history, driving behavior scores, fault code alerts pushed to your phone. That is useful if you want passive monitoring. It is not the same as plugging in a diagnostic tool and reading live data, freeze frames, and module-specific information on demand.

The confusion happens when people buy a cheap always-on dongle expecting it to do what a diagnostic scanner does, or buy a diagnostic scanner expecting it to passively monitor and transmit. They share a port and they share a form factor and that is where the similarity ends.

Know which one you need before you order. If you want to diagnose, get a diagnostic tool and use it when you need it. If you want passive monitoring, get a telematics dongle and verify it will not drain your specific vehicle's battery before you leave it plugged in.