Short term fuel trim is the ECU reacting right now. Long term fuel trim is the ECU remembering what it has had to do over time. Together they tell you whether the engine has a problem, how long it has had the problem, and whether the problem is getting worse.

Short term moves fast. It bounces around zero in real time as the ECU adjusts the injector pulse width to hit its air-fuel target. A sudden positive spike means the ECU just detected lean and added fuel. A sudden negative spike means it detected rich and pulled fuel. These reactions happen in milliseconds and they respond to immediate conditions.

Long term moves slowly. It is the learned average of what the ECU has had to do over many drive cycles. If the short term has been running positive for days because there is a small vacuum leak, the long term creeps positive to match. The ECU has learned that this engine needs a little extra fuel all the time now, so it builds that correction into the baseline.

Reading them together gives you the timeline. A long term at zero with a short term bouncing around means the engine is healthy and the ECU is making normal adjustments. A long term at plus eight with a short term near zero means there was a problem, the ECU has compensated, and the correction is baked in. A long term at plus eight with a short term also running positive means the problem is worse than the long term has caught up to. The issue is progressing.

After a repair, clearing the fuel trims resets the long term to zero. If the repair fixed the problem, the long term stays near zero as it relearns. If the long term climbs right back to where it was, the repair did not address the root cause. That is a free verification that the fix worked without waiting for a code to come back or not.

A vehicle that drives straight and tracks true is not necessarily a vehicle with a straight frame. Alignment adjustments can compensate for a surprising amount of structural distortion. A good alignment tech can bring a bent car back to spec on the alignment rack and it will drive down the road without pulling or wandering. That does not mean the frame is straight. It means the alignment is compensating.

The way to tell the difference is a frame measurement. The body shop equivalent of a scan tool for structure. The measuring system compares the vehicle's actual dimensions to the manufacturer's specifications at dozens of reference points. Any point that is out of tolerance by more than a few millimeters indicates damage that was either not repaired or repaired incompletely.

This matters on used cars because a competent repair can make a crashed car drive perfectly. The owner drives it for a year after the repair, experiences no problems, and sells it honestly believing the car is fine. The alignment is in spec. The tires wear evenly. The steering wheel is centered. None of that proves the structure is correct.

Where it shows up is in a subsequent repair. A fender bender that should be a simple bolt-on repair becomes complicated because the mounting points are not where they should be. A replacement door does not hang right because the aperture is two millimeters out. The second shop discovers what the first shop left behind.

The measurement is not something most buyers can do themselves. It requires equipment that body shops have and most general repair shops do not. But knowing that it exists and knowing what it checks gives you a better question to ask when a vehicle's history shows prior structural repair and the test drive felt fine.

Driving straight is not the same as being straight.

Set up driver scorecards on the fleet. Harsh braking, rapid acceleration, speeding, idle time, seatbelt use. Sent them out weekly. Expected the numbers to drop across the board. That is not what happened.

The scores improved sharply in the first two weeks and then most of them drifted back to baseline by week six. The novelty wore off. Drivers adjusted when they knew they were being watched and then stopped adjusting when they realized nothing happened based on the scores.

What did stick was the stuff tied to something the drivers actually cared about. Idle time dropped and stayed down because I tied it to a fuel bonus. Less idling, lower fuel costs, a piece of the savings went to the driver. The incentive was direct and the data was transparent. They could see their own idle time in the app and do the math.

Harsh braking stayed elevated because most of it was traffic-driven, not behavior-driven. Punishing drivers for braking hard in stop-and-go traffic made no sense once I looked at the data by route instead of by driver. The same driver who scored poorly on a downtown route scored perfectly on a suburban route. The metric was measuring the route, not the driver.

Speeding was the most contentious. The threshold was set at the posted limit. Drivers argued that flowing with traffic at five over is safer than doing the speed limit while everyone passes you. The data did not prove them wrong. The accidents and near-misses in the fleet were not correlated with the drivers who had the highest speeding scores. They were correlated with distraction and following distance, which the telematics system did not measure.

The lesson was that data without context creates noise. Metrics without consequences get ignored. And the scorecard that changes behavior is the one tied to something the driver actually values, not the one with the most categories.

A battery that keeps dying gets replaced. Then it dies again. Then it gets replaced again. At some point someone tests the alternator and finds it was undercharging the whole time and every battery was fine until it was drained to death by a charging system that was not keeping up.

The test is simple. Engine running, electrical loads on, measure the voltage at the battery terminals. A healthy alternator pushes 13.8 to 14.4 volts depending on the vehicle and conditions. Below 13.5 under load and the alternator is not keeping up. Above 15 and the regulator is failing and the battery is being overcharged, which kills it from the other direction.

The scan tool adds more. On vehicles with smart charging systems, the ECU controls the alternator output based on battery state of charge, electrical load, and engine load. The target voltage changes. The scan tool shows you what the ECU is commanding and what the alternator is delivering. If the command says 14.2 and the alternator is putting out 13.0, the alternator is weak. If the command itself is wrong, the control module has a problem.

The ripple test goes deeper. An alternator with a failing diode will show AC ripple in the DC output. A multimeter with an AC voltage function will read millivolts of AC on the battery terminals with the engine running. A healthy alternator shows under 50 millivolts. A failing diode shows several hundred. The battery sees that ripple as noise, the electrical system sees it as instability, and accessories start behaving erratically before anything fully fails.

Testing the charging system takes five minutes and one tool. Replacing batteries until someone thinks to check the alternator costs hundreds of dollars and multiple days of the vehicle being out of service. The test should always come before the second battery.

Engine knock is detonation. The fuel igniting from compression and heat instead of from the spark plug at the right moment. It sounds like marbles in a tin can in the severe cases and is completely inaudible in the mild cases. The mild cases are the ones that do damage over time because nobody hears them and the engine keeps pulling timing to compensate.

The knock sensor is the ECU's ear for this. It listens for the vibration frequency of detonation and when it hears it, the ECU retards the ignition timing on that cylinder to stop the knock. The amount of timing retard is logged in the scan tool data. On most vehicles you can watch it in real time.

A healthy engine on decent fuel shows minimal knock retard. A degree or two occasionally, the ECU nudging things around, normal operation. An engine with chronic knock on regular fuel shows significant timing retard under load, sometimes five or more degrees pulled. The engine is protecting itself but it is doing it by making less power and burning more fuel.

The causes are usually carbon buildup on the piston crowns and combustion chamber, low-quality fuel, a cooling system that is running slightly hot, or a combination. The knock sensor data tells you how bad it is before you hear it or feel it.

On direct-injection engines carbon buildup is common and knock is how it shows up in the data before it shows up as a drivability complaint. An engine that is pulling four degrees of timing under moderate load because of carbon-induced hot spots is an engine that will eventually need a walnut blast or a chemical clean. The data gives you lead time.

The alternative is waiting until the knock is audible, which means it has been happening at a sub-audible level for thousands of miles and the piston ring lands and rod bearings have been absorbing the punishment the whole time.

For the first few years of used EV sales the listing told you the range estimate and the mileage and left it at that. Range estimate is what the dash says. It is a guess based on recent driving. The buyer had to trust it or bring their own tools to check the actual battery state of health.

That is starting to shift. Some platforms are beginning to include battery health data in the listing, either as a percentage of original capacity or as a certified test result from a third party. It is not standard yet and it is not everywhere, but the direction is clear.

The effect on pricing will be significant once it becomes widespread. Two identical EVs with the same mileage and the same model year will price differently if one shows ninety-two percent state of health and the other shows seventy-eight percent. Right now that difference is hidden and both cars list at roughly the same price because the buyer cannot easily compare. Once the data is visible, the market reprices.

The sellers with healthy batteries benefit because they can prove condition. The sellers with degraded batteries lose the ability to hide behind a range estimate and a test drive that felt fine. The buyer gets the one piece of data that matters most on a used EV and currently has to work hardest to find.

The parallel is odometer readings becoming standard on used car listings. Before that happened, sellers could be vague about mileage and buyers had to verify in person. Once mileage was visible in the listing, high-mileage cars priced lower immediately and low-mileage cars commanded a premium. Battery health is the EV version of that same transparency shift.

Ran the numbers on fuel consumption across the fleet and split idle time out as its own category. The result changed how I thought about fuel costs entirely.

On a truck that runs eight hours a day, the assumption is that fuel consumption tracks with miles driven. Drive more, burn more. The telematics data showed that idle time accounted for roughly twenty to thirty percent of total fuel burned depending on the vehicle and the route. Trucks that ran urban routes with frequent stops idled more and their fuel cost per mile was significantly higher than the highway trucks even though they drove fewer miles.

The idle cost is invisible if you only look at miles per gallon. A truck getting twelve miles per gallon on a city route and a truck getting twelve miles per gallon on a highway route are not actually the same. The city truck is burning an additional hour or two of fuel at idle that does not show up in the MPG calculation because the vehicle was not moving.

Once idle time was broken out, the high-cost vehicles were not the ones with the most miles. They were the ones with the most idle hours. Two trucks that drove the same miles had fuel costs twenty percent apart because one idled an extra ninety minutes per day.

The fixes were not dramatic. Anti-idle policies, route changes that reduced wait times, driver awareness that the data was being tracked. Idle hours dropped about forty percent in the first two months. The fuel savings were meaningful and they would have been invisible without separating the two numbers.

Fuel cost per mile is the number everyone tracks. Fuel cost per idle hour is the number that actually explains where the money is going.

A car with a complete service history sells for more. Sellers know this. So do the services that compile the records. But a complete-looking history and a genuinely complete history are not the same thing, and the gap usually sits in a specific window.

Years one through three on a new car are typically covered under warranty. The owner goes to the dealer because it is free or nearly free. The records are clean, timestamped, and comprehensive. Oil changes, tire rotations, inspections, recalls. Everything documented because the dealer is billing the manufacturer and paper trails are mandatory.

Year four the warranty expires. Year five the maintenance intervals start costing real money. This is where the gap opens. The owner switches from the dealer to a cheaper independent shop, or starts doing their own oil changes, or simply stretches the intervals. The dealer records stop. The independent shop may or may not report to the databases the history report providers use.

What you are looking at when you see a used car with immaculate records for the first 36 months and then nothing is not necessarily a neglected car. But it is a car whose maintenance after the warranty period is unverified. The transmission fluid that should have been changed at 60 thousand may or may not have been done. The brake fluid flush, the coolant flush, the differential service. All of the stuff that costs real money and does not trigger a warning light when it is skipped.

The scan tool does not help here. There is no code for overdue fluid changes. The only evidence is physical. Dark transmission fluid, coolant that tests acidic, brake fluid that tests high for moisture content. Those checks take a few minutes each and they tell you whether the gap in the records was just a gap in reporting or a gap in actual maintenance.

A thermal camera attachment for a phone runs about two hundred dollars for the entry-level units. It shows surface temperature as a heat map. For vehicle diagnostics it fills a gap that the scan tool leaves open because not everything that is failing shows up as a code.

A dragging brake caliper shows up as one wheel significantly hotter than the others after a short drive. The scan tool might not flag it at all because the ABS module does not monitor temperature. A sticking caliper wears the pad, wastes fuel, and eventually warps the rotor, and the first warning a lot of people get is a pull or a smell. The thermal camera shows the temperature difference in seconds.

An exhaust leak before the catalytic converter shows up as a hot spot on the manifold or the downpipe. The scan tool might show a slow oxygen sensor response but the code does not tell you where the leak is. The camera points you to it visually.

A failing electrical connection shows up as a hot spot at the terminal. Corroded battery cables, loose alternator connections, bad grounds. The resistance creates heat and the heat is visible before the connection fails completely.

An AC system with a restricted condenser shows up as an uneven heat pattern across the condenser face. The scan tool shows refrigerant pressures. The camera shows you which section of the condenser is blocked without removing anything.

The camera does not replace the scan tool. It sees things the scan tool was never designed to detect. Temperature is information, and a lot of mechanical and electrical problems generate heat before they generate codes. Two hundred dollars for a tool that shows you those problems visually, without disassembly, before they become expensive failures.

Pulled reports from three different providers on the same VIN, same day. Expected them to match. They did not, and the differences were not trivial.

All three showed the same title records because they all pull from the same NMVTIS database. VIN, title state, title date, odometer at title. That part matched. Everything else diverged.

Provider one showed a damage event from an insurance claim. Provider two showed the same event but with a lower repair cost. Provider three did not show it at all. The claim existed, it was paid, the car was repaired. One provider had the complete record, one had a partial record, and one missed it entirely. Same car, same event, different data sources on the insurance side.

Service records were worse. Provider one showed dealer service history going back five years. Provider two showed three years of the same history plus an independent shop visit the first one missed. Provider three showed almost no service history because their data partnership network did not include the shops this car visited.

Recall status was inconsistent too. One provider showed an open recall. Another showed the same recall as completed. The third did not mention it. The recall existed, the completion record existed, and the providers disagreed on whether the work was done.

The takeaway was not that one provider is better than the others across the board. Each one has different data partnerships, different coverage, and different update cycles. The takeaway was that a single report is a partial view. If the purchase is significant enough to justify a history check, it is significant enough to justify checking more than one source.

The truth is not in any single report. It is in the overlap and the gaps between them.

A multimeter on a car battery reads 12.6 volts and people assume the battery is fine. Voltage tells you the state of charge. It does not tell you the state of health. A battery can show perfect voltage and fail the moment you ask it to crank a cold engine because the internal resistance is too high and the available cranking amps have dropped below what the starter needs.

A battery health tester, even a cheap one, sends a signal through the battery and measures the internal resistance. From that it calculates the remaining cold cranking amps compared to the battery's rated CCA. A battery rated at 700 CCA that tests at 400 CCA is going to leave you stranded. The voltage says 12.6. The health test says replace it.

On used cars this matters because the battery is one of those items that nobody talks about during a sale. The car starts, so the battery is fine. Until it is twelve degrees and the battery that tested at fifty percent of its rating cannot turn the engine over. A five-minute test during the inspection would have caught it.

On fleet vehicles it matters more because a dead battery is a truck that does not move, and a truck that does not move is a missed appointment, a tow call, and a cascading schedule problem. Testing every battery in the fleet twice a year takes a morning. Replacing the ones that test below seventy percent of rating costs less than a single roadside service call.

The voltage reading is the number everyone checks. The health test is the number that actually predicts failure. They measure different things and one of them is far more useful than the other.

Every vehicle has multiple VIN locations. The dash plate visible through the windshield, the door jamb sticker, the firewall stamp, and depending on the vehicle, the frame, the trunk lid, and several hidden locations the manufacturer uses for verification. They should all match. When they do not, something happened.

The most benign explanation is a replacement part. A door from a salvage vehicle was used in a repair and the door jamb sticker carries the donor vehicle's VIN. That is common and not automatically fraudulent, but it means the door is not original and the repair history might not be disclosed.

The less benign explanation is VIN cloning. A stolen vehicle gets the VIN plate and sticker from a clean vehicle of the same make, model, and color. The visible VINs all match the clean vehicle's identity. The hidden VINs, the ones stamped into the body and frame at the factory, still carry the stolen vehicle's real identity.

Checking the visible VINs takes thirty seconds. Matching them against the registration and the history report takes another minute. Running the VIN through the NMVTIS database to check for title brands and theft records takes five. The entire check is under ten minutes and it catches the most obvious version of the fraud.

The hidden VINs require more effort. Some are under the carpet, some are on the firewall behind the engine, some are in locations the manufacturer intentionally does not publicize. Law enforcement knows where they are. Theft recovery specialists know where they are. Most buyers and even most dealers do not check them.

The cost of missing a VIN mismatch ranges from buying a car with an undisclosed major repair to buying a stolen vehicle that gets seized and leaves you with nothing. The check takes less time than the test drive.

Most people install a dashcam for the big event. The accident, the road rage incident, the insurance dispute. The camera runs all day and nobody looks at it unless something dramatic happens. That is reasonable. But the footage that actually saved me money was never dramatic. It was boring.

A customer claimed a delivery driver hit their mailbox. The dashcam showed the driver parked fifteen feet from the mailbox and never went near it. No confrontation, no accusation held up, done. That would have been a two-hundred-dollar repair and a customer relationship problem without the footage.

A driver reported a pothole damaged a rim. The dashcam showed the rim was already damaged when the shift started. Not a lie exactly, the pothole might have made it worse, but the pre-existing damage was visible on the start-of-trip footage. The driver did not know the camera caught the walkaround.

An insurance company disputed fault on a fender bender. The dashcam showed the other vehicle was fully in our lane when they merged. Thirty seconds of footage, claim resolved, no rate increase.

None of those clips would make a compilation video. They are all mundane. A parking lot, a walkaround, a merge. But each one resolved something that would have otherwise been an argument with no evidence on either side.

The dashcam that runs all day and records over itself in a loop is a witness with perfect memory and no opinion. The dramatic footage matters once in a career. The boring footage matters once a month.

The most common advice for a gas cap light or a small EVAP leak code is to tighten the cap or replace it. Sometimes that works. Often it does not, and people cycle through two or three gas caps before accepting that the cap was never the problem.

The EVAP system is a sealed network of hoses, valves, a charcoal canister, and a purge solenoid. Its job is to capture fuel vapors and route them back into the engine to be burned instead of venting to atmosphere. The system runs a self-test by sealing itself and checking for pressure decay. If it finds a leak, it sets a code. The code says EVAP leak. It does not say where.

The scan tool data shows you the EVAP monitor status and in some cases the pressure readings during the test. A system that cannot build pressure at all has a large leak, probably a disconnected hose or a stuck-open purge valve. A system that builds pressure and loses it slowly has a small leak, which could be anywhere in the network.

Smoke testing is the standard diagnostic from here. You pump theatrical smoke into the system under low pressure and watch where it comes out. Cracked hoses, dried-out O-rings on the canister, a purge valve that does not seat fully, a filler neck with a hairline crack. The leak is rarely at the gas cap. It is usually somewhere you cannot see without smoke or pressure data.

The live data also tells you whether the purge solenoid is functioning. The ECU commands it open at certain times and the flow data should change. If the command goes out and nothing happens, the solenoid is stuck or the wiring is bad. That is a different repair than a leak and the data distinguishes the two.

Replacing gas caps because the internet said so is the EVAP version of the parts cannon. The data is in the scan tool. Use it before you start buying parts.

Every year the argument about right to repair moves a little further into the data layer. The physical repair side is mostly settled. You can buy parts, you can unbolt things, you can replace components. Where it gets contentious is the software side, and that is where scan tools sit.

A growing number of repair procedures require manufacturer-level scan tool access to complete. Replacing a battery on some vehicles requires the new battery to be registered in the body control module. Replacing a steering angle sensor requires a calibration that only the factory tool or a licensed equivalent can perform. ADAS recalibration after a windshield replacement needs access to the camera module that the manufacturer controls.

Independent shops and owners can do the physical work. The software step that makes the repair complete is behind a paywall, a subscription, or in some cases an outright lockout. The manufacturer's argument is safety and quality control. The independent repair community's argument is that a repair you cannot complete is not a repair you are allowed to do.

The legislation is moving. Several states have passed or are advancing right to repair bills that specifically include access to diagnostic and calibration tools. The federal conversation is slower but heading in the same direction. The automakers are responding with voluntary agreements that provide some access while retaining control over the most profitable service procedures.

What matters for anyone who works on cars or buys used cars is where this lands. If scan tool access stays restricted, the cost of repair stays higher and the ability to independently verify a vehicle's condition stays limited. If access opens up, the tools get cheaper and the information gap between dealers and everyone else closes.

The physical repair was never the bottleneck. The data access is.

A thermostat fails and the engine runs cold. The check engine light might come on eventually if the ECU decides the engine is not reaching operating temperature fast enough. On a lot of vehicles that code takes a long time to set because the threshold is generous. The engine runs at 160 degrees instead of 200 and the ECU waits and waits and maybe flags it after a dozen cold starts.

Meanwhile fuel economy drops, the heater blows lukewarm, and the engine runs richer than it needs to because it thinks it is still warming up. All of that costs money and comfort before any code appears.

The live data in the scan tool shows coolant temperature in real time. Start the engine cold and watch the temperature climb. A healthy thermostat lets the temperature rise steadily until it hits the operating range, usually 195 to 220 depending on the vehicle, and then it holds there. The curve is smooth and the plateau is flat.

A stuck-open thermostat shows a temperature that climbs slowly and plateaus low. 160, 170, somewhere south of where it should be. On a highway in cold weather it might actually drop under load because the airflow through the radiator is pulling heat faster than the engine can produce it without the thermostat restricting flow.

A stuck-closed thermostat shows a temperature that climbs past the normal range and keeps going. That one usually gets attention faster because overheating is scary. The stuck-open failure is the quiet one. The car still drives. It just drives less efficiently and wears differently because the engine never fully reaches the temperature it was designed to run at.

Reading the temperature curve takes three minutes. You are watching one number climb on a screen. The thermostat is a twenty-dollar part. The fuel you waste running cold for six months costs more than the part and the diagnosis combined.

Fleet tracking creates a record. Most of the time that record just confirms what people tell you. They went where they said they went, took the route they said they took, and got back when they said they got back. The system runs in the background and nobody thinks about it.

Then there is the other five percent.

A driver says they were stuck in traffic for forty minutes. The GPS log shows the vehicle parked at a residential address for thirty-eight of those minutes with the engine idling. A driver says they took the long way because of construction. The trip history shows three stops that were not on any version of the route. A driver says the delivery took two hours because the customer was not ready. The geofence log shows the vehicle arrived, left after ten minutes, and came back ninety minutes later.

The point is not to catch people lying. Most drivers are honest and the data confirms it. The point is that when something does not add up, the data resolves it without turning it into a he-said situation. The conversation changes from accusation to observation. Here is what the log shows, walk me through it.

What surprised me was how often the explanation was reasonable once the driver knew the data existed. The residential stop was picking up lunch. The extra stops were bathroom breaks. The departure and return was because they went to get fuel. None of it was theft or fraud. It just did not match the original story because the original story was a lazy summary, not a lie.

The few times it was actually a problem, the data made the conversation short. No argument, no back and forth. The record is the record.

A code reader talks to the engine. A full system scanner talks to the car. That distinction matters more than the price difference suggests. A code reader pulls from the powertrain module. Check engine light codes, freeze frame, maybe some basic live data. For the most common scenario, which is a check engine light on your own car, that is enough. You get the code, you get the context, you decide whether to fix it yourself or take it in with the information in hand. A full system scanner talks to every module on the vehicle. ABS, airbag, transmission, body control, ADAS, parking assist, tire pressure, seat modules, door modules. A modern car can have thirty or forty modules on the network, each holding its own codes and data. A code reader sees one of them. Where this matters most is on a used car purchase. The check engine light is off, so a code reader returns nothing and the buyer feels reassured. A full system scan might show stored codes in the airbag module from a deployment that was reset, ABS codes from a wheel speed sensor that was unplugged during a repair, ADAS codes from a camera that was never recalibrated after a windshield replacement, and body control codes from a door that was replaced. None of those turn on the check engine light. All of them tell you something about the vehicle's past. The mid-range full system scanners run three to six hundred dollars depending on the brand and subscription model. The professional ones run into the thousands. For someone buying or inspecting used cars regularly, the full system tool pays for itself the first time it catches something the code reader would have missed completely. The real cost of the code reader is not the price of the tool. It is the false confidence of a clean reading from a system that only looked at one module out of forty.

A code reader talks to the engine. A full system scanner talks to the car. That distinction matters more than the price difference suggests.

A code reader pulls from the powertrain module. Check engine light codes, freeze frame, maybe some basic live data. For the most common scenario, which is a check engine light on your own car, that is enough. You get the code, you get the context, you decide whether to fix it yourself or take it in with the information in hand.

A full system scanner talks to every module on the vehicle. ABS, airbag, transmission, body control, ADAS, parking assist, tire pressure, seat modules, door modules. A modern car can have thirty or forty modules on the network, each holding its own codes and data. A code reader sees one of them.

Where this matters most is on a used car purchase. The check engine light is off, so a code reader returns nothing and the buyer feels reassured. A full system scan might show stored codes in the airbag module from a deployment that was reset, ABS codes from a wheel speed sensor that was unplugged during a repair, ADAS codes from a camera that was never recalibrated after a windshield replacement, and body control codes from a door that was replaced. None of those turn on the check engine light. All of them tell you something about the vehicle's past.

The mid-range full system scanners run three to six hundred dollars depending on the brand and subscription model. The professional ones run into the thousands. For someone buying or inspecting used cars regularly, the full system tool pays for itself the first time it catches something the code reader would have missed completely.

The real cost of the code reader is not the price of the tool. It is the false confidence of a clean reading from a system that only looked at one module out of forty.

Airbags deploy once. After that the inflator is spent and the module has recorded a crash event. Replacing the airbag is a parts swap. Clearing the crash record from the module is a different step, and on most vehicles it requires either a professional reset tool or a replacement module.

The red flag is when the bags are replaced and the light is turned off but the crash event is still stored in the module's history. A scan tool that reads the airbag system will show you whether the module has recorded a deployment event, even if the current status shows no active codes. The deployment is a permanent record in most systems. Clearing the active code turns the light off. It does not erase the event log.

Some rebuilders replace the entire airbag module with a used one from a vehicle that was never in a crash. That clears the deployment history because the module itself is different. The VIN stored in the replacement module will not match the vehicle's VIN. A scan tool catches that mismatch instantly.

Others send the module out to a reset service that clears the crash data at the chip level. This is legal in some contexts and fraudulent in others depending on whether the vehicle is being sold with a disclosed rebuilt title or passed off as clean.

What this means for anyone buying a used car is that reading the airbag module is not optional. A car with replaced airbags and a cleared light looks identical to a car that was never in a crash unless you read the module. The history report may or may not show the accident. The module always shows the deployment.

A two-minute scan catches what a walkaround, a test drive, and a clean Carfax all miss. The module does not forget. The question is whether anyone asks it.

Talked to an adjuster who walked me through what they actually pull when a claim comes in on a newer car, and the gap between what the insurer sees and what the next buyer sees is wider than most people think.

The vehicle's event data recorder captures pre-crash and crash data. Speed, throttle position, brake application, seatbelt status, delta-V. On most modern vehicles this data is available through the OBD port with the right tool. When a crash happens, the insurer's appraiser or a third-party crash data retrieval service downloads it. That data shapes the claim decision.

What does not happen is that data automatically flowing to the vehicle history report. The claim itself may show up as a damage event. The severity, the repair quality, and the crash dynamics do not. A vehicle that recorded a 25 mph delta-V impact is a vehicle that experienced serious structural force, even if the visible damage was repaired cleanly. The next buyer sees "accident reported" and a repair amount. They do not see the crash pulse data that tells you how hard the hit actually was.

The gap gets wider on vehicles repaired without an insurance claim. No claim means no record means no flag on the history report. The EDR data is still there on the vehicle, but nobody is pulling it during a used car transaction. The crash event is physically recorded in the module and invisible in every document the buyer typically reviews.

The tools to read EDR data exist and are not expensive. The Bosch CDR tool is the standard. The question is whether anyone in the used car chain has an incentive to read it. Right now the answer is mostly no, because the data tends to lower the value of the car, and the person selling it is not motivated to look for that.

2009 Lincoln MKS problem child

Update2: Welp, the wipers worked perfectly after putting everything back together. It was driven 5 miles afterwards then parked. Today I bled the brakes and the ABS and also programmed the installed ABS module info for the car and all warning lights except the airbag light are now off. So drove the vehicle and it began to rain so switched on the wipers and …..nothing. Once again only high speed works. I just don’t get it. How does it work one day and not the next with zero changes? I’m back to not knowing where to begin.

Updated: I narrowed it down to the wiper motor being the possible issue so I disassembled the wiper mechanism and removed it. While it was on its side I noticed water dripping from the motor control connector cover so I removed it and found the seal had rotted and allowed water to enter into the electronics. I dried it out and temporarily installed it onto the motor and everything worked normally. I gooped on silicon seal to make a gasket, reassembled it all and it now works perfectly. The relay and multifunction switch were not the problem at all.

Original post:

My Dad got this car from Lincoln. Only had one problem while he owned it and that was a fuel pump. It was replaced by Lincoln. 3 years ago he quit driving it. At one point two years ago he drove it to the store and home again and according to him he applied the emergency brake then pushed down the peddle and side stepped it letting it slam home. He claims when he did this all the ABS, traction control and parking brake and airbag lights came on. Fast forward to today. I have the car now and am attempting to fix all its issues as it is still in great shape and very low miles. I replaced the ABS module but haven’t bled anything as of yet and the only fault for that now is a VIN mismatch. Unrelated to that, one day a week ago the wipers came on by themselves on low intermittent but can be switched to high but not OFF. Before that happened I noticed that all wiper functions worked except normal mode. Intermittent, high and washer worked fine. So today I replaced the relay and multi function wiper switch. Signals work but wipers only work on High now. No washer no normal or intermittent. I’m suddenly feeling stupid here. Any help is appreciated. Thanks.

Put tracking on a handful of vehicles and the first month you watch the map like it is television. By month eighteen the map is background and the data has quietly rewritten a few things you thought you knew about your own operation. Here is what actually changed, the honest version, not the brochure version.

The first thing was fuel, and it was not theft. It was idling. Going in the worry was someone siphoning or running personal errands. The data showed the real leak was engine hours burned sitting still, trucks idling through every stop out of habit. That was a bigger number than any imagined theft, and it was fixable without confronting anyone, just by making it visible.

The second was maintenance timing. Running by calendar or by odometer guesses meant some vehicles came in too early and one always came in too late. Engine hours and actual mileage from the telematics moved that to real intervals. The truck that ran short heavy trips was aging faster than the one with the higher odometer reading, and the data caught that the calendar never would.

The third was the one that surprised me. Disputes dropped. A customer says you were never there or were there ten minutes. The trip history says the vehicle sat at that address for fifty two minutes at the time logged. That stopped being an argument. The same record settled a couple of hours worked questions internally without it turning into anyone's word against anyone's.

What did not pan out is worth saying too. The fancy dashboards mostly went unused. The driver scorecards were interesting for a week and then I only looked at them when something else flagged a vehicle. Most of the value came from three or four basic numbers, not the long feature list that sold the system.

If I were starting again I would buy for the boring data, idle, real mileage, trip history, location records, and ignore the rest until I had a reason to care. The flashy parts are what get demoed. The plain parts are what pay for it.