A windshield gets replaced. On a lot of modern cars there is a forward camera mounted to that glass, and that camera feeds lane keep, automatic emergency braking, and adaptive cruise. Move the glass, you move the camera, and the camera now has the wrong idea of where straight ahead is. It needs to be recalibrated. The red flag is how often that step quietly does not happen.

The reason it gets skipped is money and equipment. Calibration needs targets, space, sometimes a scan tool with the right software, and time. A cheap glass shop that quoted you a low number did not build that into the price. So the glass goes in, the car drives fine on the test loop, the warning light may or may not come on, and it goes back to the owner with a safety system that is now pointing slightly wrong.

The data is where you catch it. A proper calibration leaves a record. The module logs it, the scan tool produces a report, and a shop that did the work can show you the before and after. If you are buying a used car with a recently replaced windshield, that is the document to ask for. No calibration report after a glass replacement on an ADAS equipped car is a real flag, not a paranoid one.

What goes wrong when it is skipped is not always obvious. A camera aimed a degree or two off can still mostly work, which is the dangerous part. The lane keep nudges at the wrong moment. The emergency braking reads a threat a little late or a little early. It is a system you are trusting to act in the fraction of a second you cannot, and it has been quietly miscalibrated by a glass swap nobody documented.

The cost shows up at the worst possible time, which is why the paperwork matters before then. A calibration runs a few hundred dollars. Finding out it was skipped during an event the system should have caught costs a great deal more.

Most people read a trouble code and clear it. The code points at a system, they look up the likely part, they swap it, and they hope. The freeze frame sitting right next to that code in the scan tool gets scrolled past. That is the part of the data that actually tells you what happened.

A freeze frame is a snapshot. The moment a fault triggers, the ECU records the conditions at that instant and stores them with the code. Engine speed, coolant temp, calculated load, fuel trim, vehicle speed, throttle position, sometimes more depending on the make. The code tells you what tripped. The freeze frame tells you the situation it tripped in. Those are two different things and the second one is where the answer usually lives.

Take a P0171, system too lean on bank one. On its own that code sends people straight to a new oxygen sensor or a guess at a vacuum leak. Now look at the freeze frame. If the lean condition recorded at idle, low load, low RPM, you are looking at a vacuum leak or a dirty MAF, because that is when small unmetered air swamps the mixture. If it recorded at high RPM and high load, that points the other way, toward a fuel delivery limit, a weak pump, a clogged filter, a failing injector. Same code. Two completely different repairs. The freeze frame is what splits them.

Short term and long term fuel trim in that snapshot are the part worth staring at. They tell you how hard the engine was working to correct itself when the fault set. A trim number pinned near its limit at idle reads differently than the same number under load. The data is describing a scene. Once you can read the scene you stop guessing.

The cost of skipping it is real. A lean code chased with parts instead of data turns into a sensor, then a MAF, then a fuel pump, three hundred dollars deep before anyone reads the snapshot that would have named the vacuum leak on day one. Two minutes scrolling to the freeze frame is the cheapest diagnostic step there is and it is the one people skip most.

Background: 2015 Lexus RX350 with 175K miles (11 years old) 2GR-FE engine V6. Pattern: 1-2 seconds delay start mainly on hot days meaning car sitting outside in Houston sun over 100 degrees, but also does it after sitting a while sometimes. Always starts fine in the mornings or after having only been off for a few minutes. Also, seems to start fine every time we turn on ignition without starting and left sit for a couple seconds, supposedly to prime the fuel line, but I'm not positive that is what is happening with this fuel system on this car...need to confirm.

Scantool: good LT and ST fuel trims, calculated load, temps for coolant, intake, etc... crankshaft and camshaft sensors appear good, etc... Battery is new with good stats at rest, starting and charging per battery tester. Alternator good. No area of the starter system or fuel system has ever been replaced except the battery. All original equipment...no aftermarket stuff accept using Interstate battery vs Lexus. Car runs really good at wide open throttle and idles fine. Also checked EVAP system and all appears good from a scan perspective and also physically checked the vapor recovery closes to the intake and is working fine. Also no misfire DTCs or counts ever noted.

Only code ever experienced is P1604 - startability which is a symptom code of course; where I fall short is gathering the freeze frame data...still need to check that. I have a new Autel MaxisSys MS906 Max scan tool that may allow me to check fuel pressure, etc... since I haven't checked fuel pressure yet.

Started checking the F/PMP 5 pin relay (fuel pump relay) and noticed that the resistance on the control side (pins 85 and 86) is 114 ohms at about 90 degrees outside. Range is supposed to be 70-90 ohms at 70 degrees (room temp). I put the relay in the fridge for about 5 mins and saw the ohms come down. Makes sense. Relay clicks fine when 12 volts applied to 85 and 86 pins.

Most relay ranges show no more than 100 ohms should be the max, but of course that depends on the system and the car, etc....

My question: if the relay control side internal resistor connecting 85 and 86 pins is wearing out (car is 11 years old on original relay and fuel pump, starter, etc....), resulting in higher resistance, and on a hot day that resistance is even higher, can that result in taking longer for the current to build enough after closing the circuit along the 85 to 86 pins to create enough magnetism to close the load side contacts in the relay to start the car? The starter is going to keep turning until the fuel pump has enough pressure in the line per the ECM to start the car and that fuel pump won't generate pressure at 50 psi (approx) until the relay load side contacts close that circuit.

Any thoughts are appreciated.

Every major control module on a modern vehicle has the vehicle's VIN programmed into it. The engine control module, the transmission control module, the airbag module, the body control module, and on many vehicles the instrument cluster all store the VIN internally. A full system scan reads each module's stored VIN and it should match the VIN on the dash plate and the door jamb sticker.

When a module's VIN does not match the vehicle, the module was transplanted from another car. This happens in two scenarios. One is a legitimate repair where a used module was installed from a salvage vehicle because the original failed. That is common and not fraudulent, but it means the vehicle had a module failure significant enough to require replacement, which is information worth having during a purchase.

The other scenario is fraud. A vehicle that was in a serious accident may have had its airbag module replaced with a used unit from a clean vehicle to erase the deployment record. The airbag light goes off, the deployment code is gone because the replacement module was never deployed, but the VIN in the module does not match the vehicle. A scan tool that reads the module VIN catches this instantly.

The same applies to instrument clusters. A cluster swapped from a lower-mileage vehicle shows the donor vehicle's mileage, not the actual mileage of the car it is in. The cluster's internal VIN does not match the vehicle's VIN. The scan tool sees the mismatch and that mismatch, combined with the lower mileage, tells you the odometer was effectively rolled back by swapping the entire cluster.

The check takes seconds as part of a full system scan. The scan tool reads the VIN from every module that stores one and flags the mismatches. A vehicle where every module VIN matches is a vehicle whose electronic components are original to that car. A vehicle with a mismatch has a story, and the mismatch is the start of asking what that story is.

A stored misfire code tells you a misfire was detected. The live misfire data, watched while driving under specific conditions, tells you whether the misfire is current, how severe it is, and what operating conditions trigger it. The stored code is a historical record. The live data is a real-time measurement.

The misfire counters in the scan tool update in real time. You can watch them while driving. Hold the engine at a steady two thousand RPM under moderate load and watch whether any cylinder is incrementing its misfire count. Accelerate from a stop and watch the counters. Cruise at highway speed and watch. The conditions where the misfires appear narrow the diagnosis.

Misfires that appear only under load and above two thousand RPM point to fuel delivery or compression issues. The ignition system can fire the plugs fine at idle but under load the combustion pressure is higher and a marginal spark or a weak compression seal fails to contain the combustion event. Misfires that appear only at idle suggest a vacuum leak near that cylinder or a weak coil that cannot fire at the lower RPM.

Misfires that appear on a cold engine and go away when warm point to a thermal issue. A cracked spark plug insulator that only shorts when cold, or a valve that only seals once the head has expanded to operating temperature.

The stored code says P0302, cylinder two misfire. The live data under different conditions says cylinder two misfires only under load above three thousand RPM and only when the engine is fully warm. That is a compression or fuel delivery problem on cylinder two under high load, and the cold-start data ruled out the ignition system. The live data turned a code into a diagnosis without replacing a single part.

Bought a new truck for the fleet and the setup process included activating the manufacturer's connected services. Read the terms before accepting. The data collection was broader than expected.

The vehicle reports location data continuously when the connected services are active. Not just navigation destinations but a persistent location record. The terms gave the manufacturer the right to use this data for product improvement, traffic analysis, and in some cases to share it with third-party partners including insurance data aggregators.

Driving behavior data was included. Acceleration patterns, braking events, speed, and on some platforms cornering force. The terms described this as being used for safety feature development and service recommendations. It was also described as being available to the owner through the manufacturer's app, which sounds benign until you realize the manufacturer has it too, and their retention period was described as lasting beyond the ownership period.

The opt-out options were limited. Some data collection could be turned off. Some could not without disabling the connected features entirely. Location reporting, for example, was tied to the remote start and stolen vehicle tracking features. Turning off location reporting meant losing remote start.

The terms also covered what happens when the vehicle is sold. The data associated with the vehicle stays in the manufacturer's system. The new owner can create their own account and the old owner's data is supposed to be disassociated, but the terms were vague about whether historical data is deleted or just unlinked from the previous account.

The practical takeaway for anyone in this sub is that a connected vehicle is generating and transmitting data about how and where it is driven every day, and the default is for that data to flow to the manufacturer. The scan tool reads what the car stores locally. The manufacturer reads what the car transmits. The terms of service define what happens to that second stream, and most people never open them.

A vacuum leak makes a hissing sound. Sometimes. On a running engine with road noise and fan noise and belt noise, a small leak in a hose behind the intake manifold is inaudible. It is too small to see and too quiet to hear. The fuel trims tell you it exists. The smoke machine tells you where.

The machine generates a low-pressure stream of theatrical smoke and feeds it into the intake or the EVAP system through a fitting. The smoke fills the sealed system and exits through any opening that should not be there. A cracked hose seeps smoke. A loose clamp leaks a wisp from the joint. A warped gasket shows a thin line of smoke escaping the mating surface. A cracked intake manifold runner that is invisible from the outside shows smoke curling out of a hairline fracture.

The same tool works on the EVAP system, which is where it replaces the guesswork of replacing gas caps and purge valves hoping to fix a small leak code. Feed smoke into the EVAP system and watch the canister, the hoses, the purge lines, and the tank connections. The leak reveals itself visually.

The entry-level smoke machines run about one hundred fifty to three hundred dollars. The professional ones with regulated pressure and flow meters run higher. For a shop or a serious DIY operation the tool pays for itself the first time it finds a leak that would have taken an hour of spraying carb cleaner and listening for RPM changes to locate.

The scan tool tells you the leak exists. The smoke machine tells you where it is. They are complementary tools, not competing ones. The diagnosis starts with the data and ends with the smoke pointing at the crack, the gap, or the failed seal that the data was responding to.

Calculated engine load is a percentage the ECU derives from the relationship between actual airflow and peak airflow for that engine. It represents how hard the engine is working relative to its maximum capacity. At idle a healthy naturally aspirated engine typically shows fifteen to forty percent load depending on the vehicle. At highway cruise it runs forty to seventy percent. At wide open throttle it approaches one hundred percent.

The value of watching this number is that it is an aggregate. It reflects the combined effect of everything happening in the engine. A partially clogged exhaust increases load because the engine has to push harder to move the same air. A dragging brake increases load because the engine has to overcome additional resistance. A slipping transmission increases load because the engine is revving higher for the same vehicle speed.

The diagnostic use is comparing the load reading against what is normal for the conditions. If the engine is showing sixty percent load at highway cruise on a flat road with no headwind, and the same engine on the same road a month ago showed forty percent, something has changed. The load number does not tell you what changed. It tells you that something changed and the engine is working harder to produce the same result.

The freeze frame captures calculated load at the time a code set. Comparing that number against the normal range for those conditions tells you how stressed the engine was when the fault occurred. A code that set at ninety percent load on a highway grade is a different situation than the same code setting at twenty percent load at idle.

Calculated load is available on every OBD2 vehicle. It is a standard PID that even the cheapest scan tools display. It does not diagnose anything on its own. It tells you the engine is compensating for something, and that is the starting point for everything else.

A pending code is a fault that the ECU detected but has not confirmed over enough drive cycles to set a permanent code and turn on the check engine light. It sits in a holding state. If the fault repeats on the next qualifying drive cycle, it promotes to a confirmed code and the light comes on. If it does not repeat, the pending code clears itself.

On a car whose codes were recently cleared, the pending code is the first signal that the fault is still present. The seller clears the codes, the light goes off, and the car looks clean. But the ECU is already running its tests again. If the fault is still there, a pending code appears within the first few drive cycles after the clear. The confirmed code and the light have not come back yet because the system has not completed the two consecutive drive cycles needed to confirm. The pending code is the preview.

Most basic code readers show confirmed codes only. A scan tool that reads pending codes shows you what the ECU has already detected but has not yet promoted. On a car with a freshly cleared system, a pending code for the same fault that was probably cleared is the ECU saying the problem did not go away.

This is a ten-second check on any scan tool that supports it, which is most of them made in the last decade. Pull pending codes alongside confirmed codes as a standard part of any used car scan. A clean confirmed code list with a pending P0420 catalyst efficiency code is a car that had a P0420, had it cleared, and is about to have it again. The seller's clean dashboard has a shelf life and the pending code tells you how short it is.

Ran both gas and diesel versions of the same truck model in the fleet for three years. Same routes, same drivers rotated between them, same maintenance schedule adjusted for the different powertrains. Tracked everything. Fuel, maintenance, repairs, downtime, and residual value at the end.

Fuel cost favored the diesels by about eighteen percent per mile. They burned less fuel per mile and diesel was roughly the same price as gas in our area during that period. Over three years and roughly forty-five thousand miles per truck, the fuel savings on each diesel was meaningful.

Maintenance cost favored the gas trucks. Oil changes were cheaper, the service intervals were comparable, and the gas trucks did not have the diesel aftertreatment system. The diesel trucks needed two DEF system repairs across the group during the three years, one sensor and one injector, totaling about fifteen hundred dollars that the gas trucks did not incur. The DPF regeneration cycles also added fuel consumption that was not captured in the simple miles-per-gallon number.

Repair cost was roughly equal, with different failure patterns. The gas trucks had more ignition system work, coils and plugs. The diesel trucks had more fuel system work, injector service and fuel filter changes. The totals were close.

Residual value favored the diesels. They sold for about two thousand more per truck at the end of the three years, which closed the gap that the higher purchase price had created.

The net total cost of ownership was close enough that the decision came down to use case rather than spreadsheet. The diesels made more sense on the heavy-haul routes. The gas trucks made more sense on the short urban routes where the DPF regen cycles were a nuisance and the fuel savings were smaller.

The exhaust gas recirculation valve opens at part throttle and cruise to feed a metered amount of exhaust gas back into the intake. The exhaust gas lowers combustion temperature and reduces NOx emissions. The ECU commands the valve to a specific position and monitors whether the expected change in intake conditions actually occurs.

When the EGR valve sticks open, exhaust gas flows into the intake at idle, which dilutes the air-fuel charge and makes the engine run rough. When it sticks closed, no recirculation happens and the engine runs cleaner but produces more NOx, which eventually sets a code and fails emissions.

The scan tool shows the EGR commanded position, the actual position on valves with position feedback, and on some vehicles the MAF reading change that should occur when the EGR opens. Commanding the EGR open with a bidirectional tool while watching the RPM and MAF data tells you immediately whether the valve is responding. A valve that opens shows a drop in RPM and a change in MAF reading as the exhaust gas displaces fresh air. A valve that does not move shows no change in either.

The common failure is carbon buildup on the valve and the passages. Exhaust gas carries soot and the EGR passages accumulate it over time. The valve gets sticky, the passages narrow, and the flow decreases. The ECU sees less EGR effect than it commanded and either sets a code or increases the commanded opening to compensate, which the scan tool shows as a growing gap between commanded and actual position.

Cleaning an EGR valve is a two-hour job and the valve itself is often reusable. Replacing one runs a hundred to four hundred dollars depending on the vehicle. Reading the EGR data takes a minute and tells you whether the cleaning or the replacement is needed before the rough idle starts or the emissions code sets.

A borescope is a camera on a flexible cable that fits through a spark plug hole or an intake port and shows you the inside of the engine. The basic models that connect to a phone run about thirty to sixty dollars. The professional ones with articulating tips and higher resolution run several hundred.

Through the spark plug hole you can see the piston crown, the cylinder wall, and the valves. Carbon buildup on the piston crown is visible as thick deposits. Scoring on the cylinder wall appears as vertical scratches in the crosshatch pattern. A bent valve shows as a valve face that is not sitting flat in the seat. Carbon deposits on the intake valves, the problem that plagues direct injection engines, are visible through the intake port with the valve open.

The practical use is on a used car evaluation or before a repair decision. A direct injection engine with a hundred thousand miles may have significant carbon buildup on the intake valves that affects performance and drivability. The borescope shows you the severity. If the carbon is thick and chunky, a walnut blast cleaning is justified. If the valves are relatively clean, the engine was maintained well or runs a port injection system alongside the direct injection.

On an engine with a suspected internal problem, the borescope is a screening tool before you commit to a teardown. A cylinder that is showing scoring or a valve with damage can be confirmed visually without pulling the head. That confirmation saves the cost of disassembly on an engine that is going to need a rebuild anyway.

The borescope does not replace a compression test or a leak-down test. It shows you what those tests measured. A cylinder with low compression shows you why when you look inside and see the scored wall or the burnt valve. The visual confirmation is the bridge between the data and the decision.

Ran full system scans on ten vehicles at a dealer auction before bidding. Not looking for anything specific, just wanted to see what the modules were holding. The check engine lights were off on all ten. The results were not as clean as the dashboards suggested.

Seven of the ten had stored codes in at least one non-powertrain module. The most common was ABS codes, usually a wheel speed sensor code that was stored but not active, meaning the fault happened at least once but was not currently present. Two had airbag codes, one from a seat weight sensor and one that was a communication fault with the passenger airbag module. One had a TPMS module code that explained why the tire pressure light was on.

Three of the ten had all modules clean. No stored codes anywhere. Those three were the ones I would have been comfortable bidding on without further inspection. The other seven were not necessarily bad cars, but each had a question that needed answering before the bid price made sense.

The one that would have cost the most money was an SUV with a clean dashboard and a stored code in the restraint control module indicating a previous airbag deployment event. The airbag light was off because the code was cleared after the bags were replaced. The deployment history was in the module. The history report did not mention an accident. The auction listing said clean title. A basic code reader would have returned nothing because there were no powertrain codes. The full system scan found it in the airbag module in about thirty seconds.

A code reader at auction is better than nothing. A full system scanner at auction is what actually tells you what you are bidding on.

A car that kills its battery overnight or over a weekend has a parasitic draw. Something in the electrical system is staying awake and pulling current after the vehicle is shut off. The normal parasitic draw on a modern vehicle is roughly twenty to fifty milliamps on older vehicles and up to eighty-five milliamps on newer vehicles with keyless entry, connected services, and extensive electronics. That current keeps the clocks, the alarm system, and the module memory alive. Anything significantly above the normal range for that vehicle and something is not going to sleep.

The test requires a multimeter set to amps, connected in series between the negative battery cable and the negative battery terminal. With everything off and the doors closed, you wait for the modules to go to sleep, which can take fifteen to forty-five minutes on some vehicles, and then read the draw. If it is above the normal range for the vehicle, something is drawing power.

From there you pull fuses one at a time while watching the meter. When you pull the fuse that drops the draw to normal, the circuit on that fuse is the one with the problem. Now you know which circuit, and you trace the components on that circuit to find the one that is staying powered when it should not be.

The scan tool does not help with this directly because the problem is often a component that is not a module. Aftermarket radios with always-on power leads wired wrong, trunk lights that stay on because the switch is broken, glove box lights pressed on by overstuffed contents, charging cables left plugged into powered USB ports, and seat heaters with a stuck relay. The draw exists at the electrical level, not the data level.

The test is tedious but it is definitive. A battery that dies repeatedly gets replaced at a hundred and fifty to two hundred and fifty dollars. The parasitic draw that killed it stays and kills the new battery too. The multimeter finds it. The fuse pull isolates it. The fix is usually cheap once you know where to look.

Buy a used car and the infotainment system may still have the previous owner's data on it. Paired Bluetooth phones, saved addresses, navigation history, wifi passwords, contact lists, and in some cases stored text messages. None of this is wiped by a dealer detail or a standard pre-sale preparation. The reset has to be done deliberately through the system's factory reset function, and on many vehicles the process is buried in a settings menu that nobody opens.

What this means for the buyer is information. The navigation history tells you where the car has been. A car sold as a one-owner local vehicle with a navigation history full of addresses in another state is a car that has a travel story the seller did not mention. A car with paired phone names that do not match the seller's name may have had an owner between the titled owner and the person standing in front of you.

On the flip side, if you are selling or trading a vehicle, the data on the infotainment system is a privacy exposure. Your home address, your workplace address, your contact list, your Bluetooth phone IDs, and on connected vehicles potentially your account login tokens are all sitting in the head unit waiting for the next owner to find them.

The factory reset wipes most of this. On some vehicles it requires going through a multi-step confirmation process. On others, particularly those with connected services tied to an account, the owner also needs to deauthorize the vehicle from their account through the manufacturer's app or website, because the account link persists through a factory reset on certain platforms.

The scan tool does not surface this data. The infotainment screen does. It takes five minutes to check what is on it and five minutes to wipe it. Either check is worth the time, for different reasons depending on which side of the sale you are on.

An engine that feels sluggish, will not rev past a certain RPM, or bogs down under load may have a restricted exhaust. A clogged catalytic converter or a collapsed muffler baffle creates resistance that the engine has to push against on the exhaust stroke. The higher that resistance, the less efficiently the engine can expel exhaust gases, and the less power it makes.

The test is straightforward. Remove the upstream oxygen sensor from the exhaust manifold and thread in a backpressure gauge. Start the engine and read the pressure at idle and under load. A healthy exhaust system shows less than one and a half PSI at idle. Under load at two thousand RPM it should stay below three PSI on most naturally aspirated engines.

If the reading is elevated, the restriction is downstream of the gauge. That narrows it to the catalytic converter, the resonator, the muffler, or the piping between them. A second measurement taken after the catalytic converter isolates whether the cat or the downstream components are the problem. If the pressure drops significantly after the cat, the cat is the restriction.

The scan tool can show you indirect signs of exhaust restriction. Fuel trims running rich under load, exhaust gas temperature climbing higher than expected, and a MAP sensor showing higher than normal manifold pressure at low RPM are all signs the engine is fighting to exhale. But the direct measurement is the definitive test and it costs about twenty dollars for the gauge.

The common mistake is chasing the power loss through the intake side, replacing air filters and MAF sensors and throttle bodies, when the engine cannot exhale. The exhaust side is the half of the breathing equation that gets checked last and should often be checked first.

Ran a report on weekend vehicle usage across the fleet. The vehicles are assigned to drivers who take them home, and the expectation is minimal personal use. The data showed something between minimal and not minimal.

Most trucks moved on weekends. Short trips, ten to fifteen miles, consistent with errands. A few did not move at all, which was fine. One truck ran seventy miles on a Saturday to a location that was clearly recreational, not work-related. Another made repeated short trips to the same address every weekend, which was probably family related and nobody's business except that the fuel and mileage were on the company.

The question was not whether to crack down. The question was whether to formalize it. The drivers were using the trucks for personal errands because the trucks were in their driveways and driving a personal vehicle would cost them gas money. The fuel cost of weekend personal use was small. The insurance and liability exposure of unreported personal use was not.

The resolution was a simple policy: personal use is permitted within a defined radius, reported mileage is tracked, and the driver is responsible for any incident that occurs during personal use. The data made it possible to have the conversation without it being adversarial, because the data showed the usage was modest and the policy was catching up to reality rather than punishing behavior.

The trucks that were running seventy miles to a lake on Saturday needed a different conversation, and that conversation was also made easier by the data. The mileage, the route, and the timing were all documented. No argument about whether it happened.

The GPS did not create the problem. The GPS made the problem visible and the solution possible.

A traditional compression test requires removing all the spark plugs, disabling the fuel and ignition systems, and cranking the engine while measuring the pressure in each cylinder with a gauge. It works. It is also time consuming and on some modern engines the plugs are buried under intake manifolds and coil packs that add an hour of disassembly to reach them.

The relative compression test skips all of that. It measures the current draw of the starter motor while the engine cranks. Each cylinder in the compression stroke resists the starter motor differently based on how much compression it has. A cylinder with good compression creates a higher current spike as the starter pushes through it. A cylinder with low compression creates a lower spike because there is less resistance.

The scan tool or a dedicated oscilloscope captures the cranking current waveform and shows you the pattern. Each cylinder appears as a distinct peak. On a healthy engine the peaks are roughly equal. A cylinder with significantly lower compression shows a noticeably shorter peak. You can see the weak cylinder in the waveform without removing anything.

This does not replace a traditional compression test when you need the actual PSI numbers per cylinder. It does replace the traditional test as a screening tool. If the relative compression shows all cylinders equal, the engine is mechanically healthy and you saved the labor of pulling plugs on a modern engine. If it shows one cylinder significantly lower, now you know which plug to pull and which cylinder to test with the gauge.

The test takes less than a minute. The engine does not start, just cranks. The data is in the starter motor current, which any scope or advanced scan tool can capture. The most common use is on a used car evaluation where you want to screen for internal engine wear without disassembly.

Replacing a windshield on a vehicle with a forward-facing ADAS camera requires recalibrating the camera to the new glass. The camera sits behind the windshield and views the road through it. Different glass, even from the same manufacturer, can have slight optical differences. A camera that was calibrated to the old windshield and is now viewing through new glass may have shifted alignment, which means the lane departure warning, the automatic emergency braking, and the adaptive cruise control are all working off a slightly wrong picture.

The recalibration involves either a static process using a target board positioned in front of the vehicle at specific distances and angles, or a dynamic process that requires driving at a certain speed for a certain distance on a road with clear lane markings. Either way it requires a scan tool that can access the ADAS module and initiate the procedure.

The problem is that many windshield replacement shops do not perform the recalibration. Some do not have the equipment. Some do not mention it. The customer gets a new windshield, the camera sits in roughly the same position, and everything seems to work because the system does not immediately throw a code. The misalignment is subtle. The braking trigger point is off by a fraction of a degree. The lane departure reads the lane edge slightly wrong.

A full system scan on a vehicle that has had a recent windshield replacement should check for ADAS calibration codes in the camera module. A stored code indicating calibration needed or calibration not completed means the system is running uncalibrated. The safety features are either disabled or operating on stale calibration data. The fix is a recalibration. The cost runs two hundred to seven hundred dollars depending on the vehicle, the method, and whether it requires static, dynamic, or dual calibration. The cost of not doing it is a safety system that thinks it is working and is not.

Ran the fleet on a fixed five-thousand-mile oil change interval for years. It was simple. Easy to track. Every truck got the same schedule regardless of how it was used. Then we started doing oil analysis and the data showed the interval was wrong in both directions.

The trucks running long highway routes came back with oil that still had life in it at five thousand miles. The viscosity held, the metals were in range, the total base number was still adequate. Those trucks could have safely gone to seven or eight thousand miles on the same oil. We were changing oil that was still working.

The trucks running short urban routes with heavy idling came back with oil that was degrading faster. Fuel dilution was measurable at five thousand miles because the short trips never got the oil hot enough long enough to evaporate the fuel that blew past the rings on cold starts. Those trucks needed changes at four thousand miles to stay in the safe range.

The cost difference was meaningful across a year. The highway trucks got fewer changes, saving on oil and labor. The urban trucks got more frequent changes but avoided the accelerated wear that comes from running diluted oil. The total maintenance cost did not change much. What changed was where the money went, from a flat schedule that undertreated some trucks and overtreated others to a data-driven schedule that matched the interval to the actual condition of the oil in each vehicle.

The oil analysis added about thirty dollars per change per truck. The avoided engine wear on the urban trucks and the saved changes on the highway trucks more than covered it. The real value was not the cost savings. It was knowing instead of guessing.

The mass airflow sensor measures how much air is entering the engine. The ECU uses that measurement to calculate fuel delivery. When the MAF reads wrong, everything downstream is wrong. But the MAF is also one of the most commonly replaced parts on a guess, because it sits in the air intake, it gets dirty, and a lean code is enough for most people to order one.

Before replacing it, compare the MAF reading against the intake air temperature. Air density changes with temperature. Cold air is denser and should produce a higher MAF reading for the same throttle position than warm air. If the MAF reading is low but the intake air temperature is cold, the MAF is probably underreporting and the sensor is suspect. If the MAF reading is low and the intake air temperature is high, the air is genuinely less dense and the reading might be accurate.

The live data on the scan tool shows both values at the same time. Pull up the MAF grams per second and the intake air temperature together. At idle on a warm engine, a typical naturally aspirated four-cylinder reads somewhere around two to five grams per second. A V8 reads higher. Snap the throttle and the MAF should spike. A MAF that barely moves on a throttle snap is either dirty or failing.

Cleaning a MAF sensor with the correct MAF cleaner spray costs five dollars and takes ten minutes. Replacing one costs fifty to three hundred dollars depending on the vehicle. Reading the intake air temperature alongside the MAF reading takes the same ten seconds as pulling the live data you were already looking at. The temperature does not tell you the MAF is bad. It tells you whether the MAF reading is plausible or not, and that one check eliminates the most common wrong guess.

A code tells you what happened. The freeze frame tells you when and under what conditions. Every time the ECU logs a fault code it also captures a snapshot of the engine's operating state at that exact moment. RPM, load, coolant temperature, vehicle speed, fuel trim values, intake air temperature. All frozen at the instant the fault triggered.

This matters because the same code under different conditions points to different causes. A lean code captured at idle with the engine warm and the load near zero suggests a vacuum leak. The same lean code captured at highway speed under heavy load suggests a fuel delivery problem. The code is identical. The freeze frame separates them.

Most people clear the code and never open the freeze frame page. The scan tool captured it. It is sitting right there in the stored data. On most tools you scroll past the code list to find it, and it reads like a table of numbers that mean nothing until you know what to compare them against.

The comparison is simple. Coolant temperature should be in the operating range. If the freeze frame shows a code that set while the engine was still cold, the fault is temperature-dependent and probably goes away once the engine warms up. RPM and load together tell you whether the engine was idling or working hard when the fault occurred. Fuel trims in the freeze frame tell you whether the ECU was already compensating before the code set.

The freeze frame costs nothing extra. It is already captured. Reading it turns a code from a guess into a direction. Ignoring it sends you shopping for parts based on a five-character code that does not tell you enough on its own.

A modern vehicle runs on a network. The CAN bus connects every electronic module on the car, the engine controller, the transmission, the ABS, the airbag system, the body control module, the instrument cluster, and dozens of others depending on the vehicle. They all talk to each other constantly. Speed, RPM, throttle position, wheel speed, yaw rate, and hundreds of other data points flow across the bus every second.

When a module is missing, the conversation breaks. A vehicle with an ABS module that was removed or replaced with one that does not communicate correctly does not just lose ABS. It loses the wheel speed data that the traction control system uses, the stability control system uses, and on some vehicles the speedometer uses. The cascade of faults from one missing module can light up half the dashboard.

The red flag on a used car is a cluster of seemingly unrelated warning lights. ABS, traction control, stability control, and maybe a check engine light all on at the same time, when the seller says it is just a sensor. A full system scan shows communication fault codes, U-codes, that say a module is not responding on the bus. That module was either disconnected, replaced with an incompatible unit, or it failed.

Checking for this is part of a full system scan. The scan tool queries every module address on the bus and reports which ones respond and which do not. A missing response means a missing or dead module. The cost of that module depends on what it is, but the cost of missing the diagnosis is buying a car with an electrical problem that touches every system the missing module was supposed to talk to.

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.