Check engine light on, no noise? OBD2 scanner — it reads the code. Noise, no light? A scanner will likely show nothing; that's a sound-diagnosis job. Both at once? Both tools — the signals may be unrelated. Light is flashing and the car is shaking? That's an active-misfire emergency with its own clock — the flashing CEL guide now, this comparison after. One rule carries this whole page: a light is a code job; a noise with no light is a sound job.
Here's the sentence that sorts this entire decision: your car speaks two languages, and each needs its own translator. The electronic language — sensors, fuel trim, ignition, emissions — is spoken in trouble codes, announced by the check engine light, and read by an OBD2 scanner. The mechanical language — pads, bearings, belts, joints, shields — is spoken in sound, announced by nothing on the dashboard, and completely invisible to the scanner. Almost everything drivers get wrong about diagnosing their own car comes from hiring the wrong translator: buying a $60-$120 code reader for a grinding noise, plugging it in, reading "no codes found," and concluding either that everything's fine (it isn't) or that the problem must be mysterious and expensive (it usually isn't).
The gap is structural, not a product flaw. Your car's computer monitors what it has sensors for, and there is no sensor watching your brake pads wear down — no code for a dry wheel bearing, a glazed serpentine belt, a loose heat shield, a clicking CV joint. Those parts fail in the mechanical world, producing clear, distinctive sounds while the electronic world registers nothing. For that entire class of problems — which is most of what drivers actually hear — sound is the only at-home signal that exists.
This guide is the full sorting kit: the two-minute filter, the driveway protocol that turns your symptoms into a tool choice, verified 2026 prices for every option on the ladder (a $12 adapter with a free app, BlueDriver's $99.95 no-subscription dongle, the $69.99-to-$99.99-a-year subscription hiding inside a popular competitor, free sound diagnosis, and what shops charge when you arrive with nothing), five routes by situation, the three traps this niche runs, and the one script — the named suspect — that converts a $100-$200 open-ended diagnostic into a focused 20-minute confirmation. If you are choosing between sound tools rather than between a sound tool and a scanner, MyAutoSound vs PulsCar compares the two on price and what you get back. And if the question is simply how much a given noise tends to cost, ten noises ranked by repair bill answers it directly. Once you have chosen the sound route, every AI sound tool compared shows which of them charges what.
I built PulsCar — an AI first pass on a car noise from a 30-second recording — after a noise in Phuket in 2025 cost me a $380 "full diagnostic" and then roughly $6,000 over six months across several shops, each with a different expert diagnosis, while the sound never went away (the story is on the About page). No scanner on Earth would have helped, because there was never a code to catch. That gap is the whole reason this page exists — and I'll tell you plainly when the scanner, not PulsCar, is your right answer.
Light, noise, or both: five questions to your route
If you already know your signal — light, noise, or both — the navigator below routes you in five questions and the matching route gives you the tool, the 2026 price, and the script. If you're not sure what you're dealing with, run the filter and the protocol first; they take ten minutes and cost nothing. One rule overrides everything: identify the signal before buying the tool. The most common $60-$120 mistake in this niche is purchased in the reverse order — hardware first, symptom second — and the second most common is walking into a shop with neither.
First: is this the page you need? The 2-minute filter
The light is flashing and the car is shaking → not a comparison-shopping moment: active misfire, minutes matter — the flashing CEL emergency guide now.
You want to know what a shop diagnostic should cost → the diagnostic cost guide has the full 2026 fee map ($80-$150 independent, $120-$300 dealer, $82-$179 mobile).
You're trying to identify a specific noise right now → the complete noise index sorts by sound; this page sorts by tool.
You want app rankings and reviews → the best diagnostic app roundup compares products; this page explains the categories they belong to.
You're about to record a noise for diagnosis → the recording guide covers mic position, safety, and what 30 seconds should capture.
You're deciding between a scanner and sound diagnosis — or wondering why your scanner shows nothing → the right page. Continue.
The 10-minute signal protocol
Step 1 — Read the dashboard (30 seconds). Check engine light: off, solid, or flashing? Flashing exits to the emergency guide. Solid or off — continue.
Step 2 — Name the noise, if any (2 minutes). Is there a sound that wasn't there before? When does it live: braking, turning, accelerating, idling, cold start? A noise with a pattern is a noise with a diagnosis.
Step 3 — Record it now, not later (2 minutes). If there's any noise at all, capture 30 seconds on your phone the right way while it's happening. Intermittent noises vanish at the worst moments — the recording at onset is diagnostic gold whether you use AI, a mechanic, or a forum.
Step 4 — Get any codes read free (on your next errand). Light on? AutoZone, O'Reilly, and Advance read codes at no charge — before you buy anything. Write the exact P-numbers.
Step 5 — Run the sort. Light + no noise = code job (Route 1). Noise + no light = sound job (Route 2). Both = both (Route 3). Buying used = history job (Route 4). Neither tool satisfies = Route 5.
Ten minutes, zero dollars — and you've done the triage that decides whether the right next purchase is a $12 adapter, a free recording, both, or neither.
Eight sound-versus-scanner situations, and which is yours
"My check engine light is on but the car seems fine." → Route 1. Textbook scanner territory — the code names the system, and the free parts-store read might be all you need.
"There's a noise but no warning light at all." → Route 2, the main event. A scanner will very likely read "no codes" — the noise is your only signal, and it's a good one.
"I bought a scanner for my noise and it says no codes found." → The most common wrong-tool story in the niche. The scanner isn't broken and neither is your ear — Route 2, and the "no codes" trap below.
"The light is on AND it's making a sound." → Route 3. Two signals, possibly two problems — read the code and match the noise; don't assume they're the same fault.
"I'm buying a used car this weekend." → Route 4. Stored codes tell the car's electronic history; a test-drive listen (and the deceleration test from the knock guide) tells its mechanical present.
"The noise only happens sometimes and never at the shop." → Route 5. Intermittents are why phones exist — record at onset, or the diagnosis is a game of telephone.
"The shop wants $150 to 'run diagnostics' on my noise." → Read the traps section first. An open-ended diagnostic on an undescribed noise is the worst-value purchase in car repair — the named-suspect script fixes it.
"I just want to be set up before anything breaks." → The After section: a $10-$25 adapter in the glovebox, the recording habit, and you're covered for both languages before either speaks.
What actually determines your cost
Which language the problem speaks. The master variable: electronic faults route through codes ($0 free read to $99.95-$139.95 for a serious scanner); mechanical noises route through sound (free, no hardware). Wrong-language purchases are pure waste.
Whether you arrive named or blank. "Likely front-right wheel bearing — confirm and quote" buys a focused 20-minute confirmation; "it's making a noise" buys a $100-$200 open-ended diagnostic where the first guess can miss.
Subscription vs one-time. The 2026 scanner market splits sharply: BlueDriver's $99.95 Next-Gen is everything-forever; FIXD's $59 sensor reads engine codes free (ABS on select makes) with the useful features at $69.99 to $99.99 a year depending on the order path — a three-year cost past $250 for less depth.
Intermittency. A noise that performs on demand is cheap to diagnose anywhere; one that hides costs money everywhere except in a recording captured at onset.
Safety-criticality. Brakes and steering get hands-on inspection regardless of what any app says — sound narrows and prices the suspect; a human confirms it before you trust the pedal.
Vehicle complexity. Euro platforms bury more behind manufacturer codes (BlueDriver's enhanced coverage is make-dependent), and their dealer diagnostics run $150-$300 — which raises, not lowers, the value of arriving informed.
The price ladder: every diagnostic option, 2026 numbers
Read the ladder as insurance tiers against the red rungs: everything green costs less than one shop diagnostic, and the entire point of the green rungs is to make the red ones either unnecessary or focused — a $150 diagnostic that confirms your named suspect is money well spent; the same $150 spent on "find my noise" is a lottery ticket, because the first draw can lose.
Which tool, by what you're hearing (or seeing)
Two table rules: any safety-critical noise (brakes, steering) uses sound to narrow and price the suspect, then a hands-on inspection to confirm before you trust the pedal — the recording buys knowledge, not a skipped inspection; and any "no codes found" on a car with an audible symptom means the scanner has finished its job, not that the car is fine — the investigation moves to the mechanical language, it doesn't end.
What 3,512 NHTSA complaints about a codeless noise show
The two-languages claim is testable, so we tested it. NHTSA publishes every complaint an owner files, narrative included. We loaded 777,040 complaints received between 1 January 2015 and 8 September 2026, searched the narratives for noise words (noise, grinding, squeal, knock, rattle, clunk, whine, hum, tick, screech, growl, chirp, groan), and dropped every narrative where the only noise word was a denial — "no unusual noises," "NO WARNING LIGHTS ON DASH, NO NOISES." That leaves 55,554 complaints in which an owner describes hearing something, 7.1% of the whole file.
Inside that set we looked for the sentence this page exists for: the owner saying the dashboard stayed dark or the scan came back empty — no codes, no DTC, no check engine light, no warning light, "nothing showed up on the scan." Requiring the noise and the no-code statement to sit within 600 characters of each other, so they describe the same failure, leaves 3,512 complaints. We then read 30 of them at random in full: 29 were exactly what the query was meant to find, and one was wind noise from a door seal rather than a wear failure. Download the data and the full method.
Three things in that file are worth your attention.
The silent-dashboard noise ends on a tow truck twice as often. Across all 777,040 complaints, 5.11% say the vehicle was towed. Across the 55,554 noise complaints, 4.72%. Across the 3,512 where the owner heard something and the dashboard said nothing, 10.79% — more than double either baseline. Fire reports run 2.39% against 1.83% for noise complaints generally. These are self-reported filings, not audited repairs, and people file when something frightening happens, so read this as an association in owner reports rather than a measured risk. But the direction is the opposite of reassuring, and it is the exact population that a blank code read tends to talk people out of worrying about.
The mileage is ordinary. Median mileage at failure in those 3,512 complaints is 80,000 miles, with quartiles at 48,913 and 110,000 (2,014 of the complaints carry a usable odometer figure; we dropped zeros and anything over 400,000). This is not a story about worn-out cars at the end of their lives. It is the middle of a normal ownership, the years when a car is out of warranty and the owner is deciding between a $0 free code read and a $100-$200 shop hunt.
The parts involved are the ones with no sensor on them. Counting NHTSA's own component tags on those complaints: engine 1,633, power train 898, engine and engine cooling 324, steering 285, electrical system 252, service brakes 303, suspension 162. Counting complaints rather than tags, 1,533 of the 3,512 — 43.7% — carry at least one of the power train, brake, steering or suspension tags: four systems that the federal on-board diagnostic requirement never promised to watch.
Which models and years fill the codeless-noise file
Read that table the careful way. These are counts, not rates. The F-150 has been the best-selling vehicle in the United States for decades, so it should top almost any raw count of owner complaints; nothing here says it is less reliable than anything else, and nothing here can say that, because NHTSA publishes complaints without publishing how many vehicles are on the road to divide them by. The column that carries real information is the share: what fraction of a model's noise complaints come with an explicitly dark dashboard. Across the whole file that share is 6.3%; the Santa Fe runs 13.6%, the F-150 12.7%, the Sorento 12.1% — two to three times the average, which tells you that on those platforms the noises owners write in about are especially likely to be ones the computer never flagged.
By make, the same pattern: Ford 772 of 9,010 noise complaints (8.6%), Kia 513 of 5,319 (9.6%), Hyundai 417 of 5,957 (7.0%), Chevrolet 300 of 4,696 (6.4%). By model year, the file peaks at 2017 (370 complaints), 2016 (343), 2018 (329) and 2019 (302) — vehicles that in 2026 are six to ten years old, which is the age where wear noises arrive and factory warranties don't. The per-model CSV has the top 40 with their median mileages.
What the manufacturers' own bulletins say about codeless noises
Owner complaints are one side. The other side is what the manufacturers tell their own technicians, and NHTSA publishes that too: 187,827 distinct manufacturer communications since 2015 — service bulletins, preliminary information documents, technical journals, customer satisfaction programs.
13,868 of them (7.4%) describe a noise as the customer's complaint. Only 1,455 of those — 10.5% — mention a diagnostic trouble code, the check engine light or the MIL anywhere in NHTSA's published summary. In roughly nine out of ten noise bulletins, the factory's own description of the problem never involves a code at all. (That 10.5% is a floor, not a ceiling: the summary is NHTSA's abstract, and a bulletin could reference a code in its body without it surfacing there. The direction of the finding survives that caveat; the precision doesn't.)
Sixty-four bulletins go further and say it out loud. A sample we downloaded and read:
- Honda service bulletin 23-037, 6 July 2023, 2022-23 Civic. Symptom: a steering-effort complaint, "possible complaint of noise at slow speeds, and no MIL illuminated or DTC stored." Corrective action: replace the electric power steering gearbox. PDF
- Honda service bulletin 24-011, 3 September 2024, 2021-22 CR-V and CR-V Hybrid. A clicking noise at slow speeds while turning, "and no MIL illuminated, or DTC stored" — again a gearbox replacement. PDF
- Infiniti ITB19-003, 22 February 2019, 2019 QX50. "IF YOU CONFIRM: A spark knock or knocking type noise coming from the engine under a low RPM/high load driving pattern... AND There are no DTCs stored in the ECM and/or TCM." PDF
- Jaguar SSM74070, 6 September 2018, I-PACE. Brake-application noise where "No DTCs or warning messages are present on the instrument panel and the vehicle is otherwise behaving as expected." PDF
- GM bulletin 24-NA-095, June 2024, Buick Encore GX and Chevrolet Trailblazer. Titled, in full: "Drone Noise by Holding About 1600 RPM in Park or During Driving - No DTCs." PDF
- Ford TSB 25-2612, 18 December 2025, 2021-2025 F-150 with the electronic shift-on-the-fly transfer case. "Intermittent Grinding/Hum/Rumble Noise From The Front Wheel Area - No DTCs Stored In The TCCM," traced to integrated wheel end actuators that don't fully disengage. The parts list starts with a brass wire brush, obtained locally. PDF
Every one of those is a documented failure with a factory part number and a factory repair procedure, and in every one the entry point is a human being hearing something. A code reader plugged into any of those cars reports exactly what it should: nothing to report.
By make, the noise-bulletin counts run Chevrolet 1,220, Audi 923, Jeep 776, Land Rover 769, BMW 681, Mazda 624, Ford 604, Honda 604. That ordering says more about how many documents each manufacturer files with NHTSA and how verbose its summaries are than about how noisy its cars are — some makers publish a bulletin for every squeak, others fold the same information into service information systems NHTSA never sees. The per-make bulletin counts are published with that warning attached.
What the codeless noises turned out to be
Owners often come back and say what the shop found. Within the 3,512 complaints, 969 contain a sentence naming a diagnosis — "diagnosed with," "determined that," "replaced the," "needed a new." Categorizing the text that follows those phrases:
Two readings of that table, and both matter. The first: a quarter of the codeless noises owners bothered to report ended as engine damage. That is a selection effect as much as a finding — nobody files a federal safety complaint about a heat shield they fixed for $40, and the belt-and-pulley row sitting at 4 is the proof of it. The people who write to NHTSA are disproportionately the people whose noise ended in a $7,000 invoice. The second reading is the useful one anyway: the ten categories above are almost entirely parts with no dedicated sensor. Bearings, phasers, chains, joints, pads, shields — the computer has no opinion about any of them until the damage spreads far enough to disturb something it does monitor, which by then is late. A complaint can name more than one part, so the shares do not add to 100%; the denominator is the 969 complaints that named anything at all. The categories as a CSV.
Why the port can't hear: what the rules actually ask OBD to watch
This is the part almost nobody explains, and it turns "my scanner shows nothing" from a mystery into a specification. The federal on-board diagnostic requirement for cars is written in the emissions rules, not the safety rules. In the Code of Federal Regulations, the section covering model year 2017 and later vehicles opens by saying OBD systems must "detect malfunctions in the emission control system, store trouble codes corresponding to detected malfunctions, and alert operators appropriately" (40 CFR 86.1806-17).
Read that sentence as a job description. The port exists so that a vehicle's emission control system is continuously supervised and so that a technician anywhere can read the result through one standardized connector. Catalyst efficiency, misfire, fuel trim, oxygen sensors, evaporative leaks, EGR flow: monitored, by law, with codes and a lamp. Brake pad thickness, bearing preload, belt glazing, bushing wear, heat shield fasteners, CV joint boots: not emission control, not monitored, no code, no lamp — not because manufacturers were lazy, but because nothing ever asked the system to watch them and no sensor was fitted to do it.
That is why the sentence "the scanner says my car is fine" is a category error. The scanner said the emissions-related powertrain is not reporting a fault. It has no opinion on the grinding.
When a noise does eventually set a code — and which scanner sees it
Honesty runs both ways here, and this is where a lot of comparison pages overstate the split. Mechanical failures can reach the electronic world, usually late and usually sideways:
Wheel bearings and ABS codes. Many wheel bearings carry the ABS encoder ring. A bearing can hum for months with a clean scan, then damage the ring or the sensor and set a wheel-speed-sensor code with the ABS light. Note what that takes: a generic engine-only reader will still show nothing, because ABS codes live in a different module. Reading them takes a scanner with chassis coverage — the feature that separates a $12 adapter from a $99.95-$139.95 tool.
Spark knock and knock sensors. Engines have a knock sensor, and severe detonation can set P0325 through P0332. But the Infiniti bulletin above is the honest picture of how this usually goes: a knocking noise under load with no DTC stored, because the knock sensor's job is to retard timing, not to file a report.
Mechanical faults that disturb combustion. A collapsed lifter, a stretched timing chain, a leaking exhaust manifold gasket ahead of an oxygen sensor — each can eventually throw a misfire code (P0300-P0312) or a fuel-trim code. The noise usually arrives first by weeks or months. If you hear a noise and a light appears later, you are watching the same failure cross from one language into the other.
Mode 6 and live data. A scanner that exposes Mode 6 on-board test results, or graphs live data, can sometimes show a mechanical problem indirectly — misfire counts per cylinder climbing on the cylinder your ear picked out, a fuel trim skewing as a vacuum leak whistles. That is a real and underused capability, and it is an argument for owning a decent scanner alongside the recording habit, not instead of it.
The rule that survives all four: a code confirms; the absence of a code excludes nothing. Both statements are the same fact about a tool that was built to watch emissions.
Which sound-versus-scanner route is yours? Five questions
Question 1: Light on, car sounds and drives normal? → Route 1. Code job. Free read first, hardware second, and the code decides everything after.
Question 2: Noise present, dashboard dark? → Route 2. Sound job — the scanner would read blank. This is the route most wrong purchases were trying to find.
Question 3: Light on AND something audible? → Route 3. Both tools, treated as possibly unrelated signals until proven otherwise.
Question 4: Buying a used car? → Route 4. Stored-code history plus a listening test drive — twenty minutes that move hundreds in negotiation.
Question 5: Tried the right tool and still stumped — or the noise won't perform? → Route 5. The intermittent-and-escalation route: capture at onset, then choose the human tier deliberately.
The five sound-versus-scanner routes
Each route below is a complete answer for one situation: who it fits, what it costs in 2026, the catch nobody mentions, and the sentence to say at a service counter. Read the one your sort landed on; the others will still be here if your car changes its mind.
Route 1: The check-engine-light route — $0 to $139.95, the code decides
The scanner's home turf, and it's genuinely good here. Every car since 1996 carries the standardized OBD2 port; through it, a reader pulls the trouble codes behind the light. The 2026 buying logic runs in three tiers. Free: parts stores read codes at no charge — for a one-off light, this may be the whole answer. Budget: a generic ELM327 Bluetooth adapter ($10-$25) paired with Car Scanner ELM (free) reads basic codes and live data — the right glovebox resident for most drivers; on Android, Torque Lite or Torque Pro reads codes and live data too. Depth: BlueDriver Pro Next-Gen ($99.95, struck through from $119.95) or Pro ($139.95), both on BlueDriver's own store in September 2026, adds what generics miss — ABS, airbag, and transmission codes on major makes, plus Repair Reports built from millions of verified fixes — with no subscription, ever, which in this market is a feature worth naming twice.
Fix it yourself — the free-first sequence. Light comes on: parts-store read today, exact P-numbers written down, then the solid-light guide to translate urgency. Buy hardware only if lights are a recurring character in your car's life — and buy the tier that matches: ELM327 for engine codes, BlueDriver if you want the transmission and ABS systems speaking too.
Route 2: The noise-no-light route — free, the scanner's blind spot
The main event, and the reason this comparison matters. Belt squeal, RPM-locked knock, ticks and rattles from the engine bay — all mechanical, all codeless, all distinctive; grinding under braking and bearing hum are just as codeless but only exist on the road, so a parked-engine clip can't carry them and an inspection has to. Sound diagnosis matches the recording's fingerprint (frequency, rhythm, how it tracks RPM) against cataloged failure patterns and returns the likely cause, its urgency, and a repair-cost estimate. The honest frame from the founder of a sound-diagnosis company: it's a first pass, not a verdict — but the first pass is precisely where the money is, because it's the difference between arriving at a shop informed and arriving blank.
Fix it yourself — the recording. Thirty seconds, phone mic toward the noise, captured the right way: engine noises get idle plus a gentle rev sweep; speed-dependent noises get a safe passenger-seat recording at the speed where it sings. The recording is valuable even if you never use AI — it's evidence for the shop, the forum, and the version of you comparing quotes next week.
What to say (the named-suspect call): "I've got a [grinding when braking / hum rising with speed / knock at idle], recorded — I believe it's [the suspect]. I'd like you to confirm and quote that specifically, and call me before any work beyond the confirmation." That sentence is the entire economic point: a confirmation is 20 minutes; a hunt is $100-$200 and a coin flip.
Can an app really diagnose a car problem from sound? For the mechanical family, yes — because these failures are acoustically honest. A glazed belt slipping on a pulley, a lifter ticking, an exhaust manifold leaking, a rod knocking at idle — each produces a signature with measurable properties: dominant frequencies, rhythm locked to RPM, behavior as the revs rise and fall. AI matching compares those properties against a library of confirmed failures the way a birder's app matches songs. What makes it work is the same thing that makes scanners fail here: these parts have no electronic monitoring, so the sound isn't a supplementary clue — it's the entire signal, and a rich one. The limits are real (layered noises, safety-critical confirmation, no dealership certainty from audio alone), which is why the output is a ranked likely cause, not a decree — and a parked clip carries only engine-bay noise, not brakes or bearings. PulsCar returns that report in about ten minutes free.
Record 30 seconds of the engine running, car parked, with your phone — no dongle, no port, no hardware. PulsCar's AI screens the noise and sends a PDF with the likely cause and how urgent it is — in about 10 minutes, or says inconclusive if the clip can't support a verdict. Walk into the shop with a named suspect instead of an open checkbook. The report arrives by email as a PDF, so use the address you actually read.
Route 3: The both-signals route — code for the where, sound for the how bad
The misfire is the textbook case: the engine stumbles audibly, the light comes on, and each tool reads its half. The code names the cylinder (P0302 = cylinder 2) and preserves freeze-frame conditions; the sound grades severity and trajectory — is the roughness constant or worsening between drives? The code tells you where; the sound tells you how bad and how fast. Together they walk you into the shop with both languages translated. (If that light is flashing, stop reading comparisons — the emergency protocol has a 60-minute clock.)
The subtler version: signals that coexist without relation. A stored evaporative-emissions code from last month plus a new bearing hum are two problems wearing one visit — and a shop that bundles them into one narrative has earned scrutiny. Reading both signals yourself beforehand is how you know to push back.
What to say (the two-signal estimate): "I have code P-[number] and a separate [noise] — I want the estimate itemized by symptom: which lines address the code, which address the noise, and which address neither. Anything in the third column gets its own justification."
Why doesn't a scanner show anything when the car makes a noise? Because the computer can only report what it has senses for — and its senses are electronic. It watches oxygen levels, fuel trim, ignition events, sensor voltages; it has no ear, no touch, and no sensor bolted to your brake pads, wheel bearings, belt, CV joints, or heat shields. Those parts fail mechanically: they thin, dry, glaze and loosen — producing distinct sounds and zero data. So the scanner reports "no codes found," truthfully, about the only world it can see, while the grinding continues in the world it can't. This is the most repeated confusion in car forums, and it cuts both ways at the counter: a shop waving "no codes" at an audible symptom hasn't cleared the car — it's described the limits of one tool. For that whole mechanical class, the noise is the diagnostic signal; PulsCar's sound matching covers the engine-bay part of that gap from a parked clip, an inspection the rest.
Route 4: The used-car route — both tools, twenty minutes, hundreds in leverage
The used car is where both tools earn their keep in one afternoon. The electronic read: plug in the adapter and pull stored codes and readiness-monitor status. Stored codes are the car's confession; suspiciously blank codes with unset monitors mean someone cleared them within the last drive cycles — a tell worth more than most answers. The mechanical listen: windows down on the test drive, radio off — bearing hum at speed, clicks in tight turns, brake sounds on a firm stop, and thirty seconds of idle listening with the hood up. The knock guide's deceleration test takes thirty seconds and screens for the most expensive noise a used car can make.
What to say (the PPI request): "Before purchase I want a pre-purchase inspection — codes and readiness monitors read, a lift check, and a listen for bearing, brake, and engine noise. I'll pay the $100-$200; I want the findings itemized." A seller's reaction to that sentence is itself a diagnostic. Anything found isn't necessarily a walk-away — it's a negotiation line with a verified 2026 price attached.
Do you actually need both tools? Eventually, most drivers do — but almost never on the same day, and that timing is the budget insight. The scanner's moment is a lit dashboard: a $10-$25 adapter with a free app answers most solid lights, and the free parts-store read answers many with no purchase at all. Sound's moment is a noise on a dark dashboard — where the scanner structurally reads blank, and where a free match comes before an $80-$150 open diagnostic. The mistake is buying both preemptively as a bundle, or buying the wrong one first because a forum recommended it for the other problem. The right sequence is reactive: free reads and the recording habit today, the adapter when a light becomes recurring, sound diagnosis when a noise appears, the inspection when used-car money is on the table. Two languages, two translators, hired as each is spoken — and PulsCar covers the sound half without hardware, keeping the whole kit under one dealer diagnostic.
Route 5: The still-stumped route — intermittents and honest escalation
Some problems outlast the first pass: the intermittent squeal that never performs at the shop, the code that returns weeks apart, the layered noise matching two patterns. The escalation discipline: capture first — an intermittent noise recorded at onset is worth more than three shop visits where it stayed silent; keep the phone reachable and record the moment it sings. Then escalate with the evidence, cheapest tier first: a mobile mechanic ($82-$179) brings hands and ears to the driveway and often catches what a bay visit can't (cold-start noises die by the time you've driven to a shop); an independent diagnostic ($80-$150) with your recording and history attached is a focused purchase; the dealer tier ($120-$300) is for factory-tooling problems — intermittent electronics, manufacturer-specific systems — not for noises.
What to say (the evidence handoff): "Intermittent [noise] — here's a recording at onset, here's when it happens [cold mornings / right turns / under load], here's what's been checked. I'm paying for diagnosis against this evidence, and I'd like your findings in writing even if it's 'couldn't reproduce.'" Written findings at each tier are what keep three visits from being the same visit three times.
What arriving informed actually changes at the shop
The intake (5 min). Blank customer: "it's making a noise" → open diagnostic authorized, $100-$200, direction unknown. Informed customer: recording played, suspect named, "confirm and quote" → a bounded 20-minute task. Same counter, different transaction.
The diagnosis (20-60 min). Your named suspect gets tested first — which matters because confirmation is fast and hunting is billable. Ask: "Did the noise match, and what did you check to confirm?"
The estimate. With a suspect confirmed, the quote covers one repair with a price you've already benchmarked against this page's ladder and the linked guides. Anything additional gets its own evidence: "which symptom does that line address?"
The no-codes conversation, if it happens. A shop reporting "scanned it, no codes" on your noise gets the polite correction: "Right — it's mechanical, so it wouldn't code. The recording is the symptom; I'd like a physical inspection of [the suspect]." You've just redirected the visit from the tool that can't see to the one that can.
The verification (after). Repair done: the noise is gone or it isn't — sound problems have the courtesy of audible verdicts. Record the after-state; silence in the same conditions is your receipt.
Three sound-versus-scanner traps, dissected
Trap one: "no codes = no problem." The situation: an audible symptom, a scan, and the conclusion — sometimes a shop's, more often the driver's own — that a blank code read means the car is fine. What's real: the scanner just certified the electronic world; the noise lives in the mechanical one, where pads thin and bearings dry with no sensor watching. A blank scan on a noisy car is the expected result, not reassurance. The price: weeks of a $300 bearing becoming a bearing-plus-hub job, or thin pads becoming pads-plus-rotors — wear compounds while the dashboard stays polite. The defense: treat "no codes" as "scanner's job done," and move the investigation to the sound. If a shop uses the blank scan to wave you off while the noise persists, the request is one sentence: "physical inspection of the noise source, please — it won't code."
Trap two: the subscription quietly attached. The situation: a $59 scanner sensor looks like the budget pick — until the features you bought it for (repair costs, forecasts, the mechanic hotline) turn out to live behind a yearly plan, often entered through a free trial whose length and renewal figure differ by order page. What's real: the 2026 scanner market splits into one-time and recurring, and the sticker price hides the split: FIXD's sensor reads engine codes free, and ABS only on the makes its FAQ lists, with Premium published at $69.99 to $99.99 a year depending on the order path — past $250 over three years — while BlueDriver's $99.95 Next-Gen buys everything permanently and a $12 ELM327 with a free app covers the basics forever. The price: $200+ over a few years for less capability than a one-time tool. The defense: before any scanner purchase, two questions — "which features need a subscription?" and "does it read ABS and transmission codes, or engine only?" — and calendar the trial-cancellation date the day you start one.
Trap three: the open-ended diagnostic. The situation: the noise has you worried, so you drive in and say the six most expensive words in car repair: "it's making some kind of noise." What's real: you've authorized a hunt with no boundary — $100-$200 of exploratory time in which the first hypothesis can miss, and whatever gets found first tends to get quoted first. The shop isn't necessarily predatory; the transaction shape is bad — open scope, information asymmetry, your money metering the search. The price: the diagnostic fee, plus the occasional wrong first repair, plus the follow-up visit — the diagnostic-that-settled-nothing shape. The defense: never arrive blank. A recording plus a named suspect converts the same visit into "confirm and quote this" — bounded, checkable, and cheap. Ten free minutes of sound matching before the visit is insurance against the transaction, not just the fee.
Three sound-versus-scanner quotes, decoded
These are composite scenarios, not individual customers — typical shapes of the problem with round illustrative numbers.
Scenario 1: the "full diagnostic" that settled nothing. A noise, no warning light, and a "full diagnostic" bought at a shop for $150 — the scan portion reads no codes, a confident verdict follows anyway, a part gets replaced, and the sound stays. A second shop runs the same scan, offers a different expert diagnosis and a second bill; a third does the same. Months later the noise is still there and no part has been named with evidence. The detail that stings in hindsight: there was never a code to find, so the scan portion of every one of those diagnostics was theater — whatever answer existed lived in the sound, which the owner had been hearing for free the whole time. Lesson: for a codeless noise, what you're buying at a shop is listening time. Get the listening done free first, name a suspect, and buy the shop's time as confirmation, not exploration — because an open-ended hunt can be repeated at every shop you visit.
Scenario 2: the $60 dongle that read blank. A shape that comes up repeatedly in owner reports: grinding under braking, a forum said "get a scanner," $60 spent, "no codes found," panic upgraded — surely something invisible and serious. The eventual shop visit found what the sound had said all along: pads at metal, a routine $300-$600 axle job. The scanner wasn't defective; it was answering a different question. Lesson: match the tool to the language. Brakes speak sound, not code — and $60 of wrong hardware is the niche's most common tuition.
Scenario 3: the hum caught early. A 2019 crossover with a faint growl rising with speed — no light, no code, easy to postpone. Recorded, matched to a wheel-bearing signature, confirmed hands-on, replaced for $420 at an independent. The counterfactual is the point: bearings hum for weeks before they fail, and driven to the end, the job grows toward $700+ with hub damage — and the failure mode of a seized bearing at highway speed isn't a repair bill conversation. Lesson: sound is the early-warning channel for exactly the parts nothing electronic watches. Catching the mechanical world's whispers is cheaper than waiting for its shouts.
Four sound-versus-scanner playbooks for where you are right now
"The light just came on." Solid: free parts-store read on today's errands, exact P-numbers written, the solid-light guide for urgency. Flashing with shaking: the emergency protocol, now. Buy hardware only after the free read tells you this will be a recurring conversation.
"There's a noise and I was about to buy a scanner." Save the $60-$120 — record 30 seconds first, done right. Match it (AI, or your own ear against the noise index), then walk in with the named suspect. The scanner purchase can wait for a day when a light is actually on.
"I'm at the shop and they want $150 to find my noise." Reshape the transaction before authorizing: play the recording, name the suspect if you have one, and convert the line item — "confirm and quote [the suspect], and call me before anything beyond that." No suspect yet? Step outside, spend ten minutes getting one for free, and walk back in with the sentence that bounds the search.
"I just want to be ready before anything breaks." The two-language kit: a $10-$25 ELM327 in the glovebox (free app installed, tested once so it pairs when it matters), the recording habit for any new sound, and this page's ladder bookmarked. Total cost under $30, and both of your car's languages have a translator on retainer.
After the sort: the permanent setup
Keep the adapter resident: a paired, tested ELM327 in the glovebox turns every future warning light into a 60-second answer instead of a drive-and-worry. Keep the recording reflex: any new noise gets 30 seconds captured at onset — the sound at first appearance is the cleanest diagnostic sample it will ever produce. Keep the ladder order: free reads and recordings before hardware, hardware before shop fees, named suspects before open diagnostics. Audit any subscriptions annually: if a scanner app is billing you yearly for features a one-time tool covers, the market has moved and so should you. And keep the two-language frame: the dashboard speaks for the electronic world, your ears for the mechanical one — a car that's quiet in both languages is the goal, and now you can verify each. One disclosure for readers who would rather hold both translators in one app: PulsCar's app reads codes and live data alongside the sound check, and it works with the OBDLink MX+, so we have a commercial interest in it; nothing on this page requires it, and the free check stays free either way.
For the scanner side priced out in detail, including the four yearly figures FIXD publishes itself, see FIXD in 2026.
Read your car's own sound-versus-scanner record in ten minutes
Everything above is public, free, and searchable by your exact vehicle — and almost nobody does it before a shop visit. The sequence, in the order that saves you the most:
1. Run your VIN against open recalls. NHTSA's recall lookup takes the 17-character VIN from your windshield or door jamb and returns open, unrepaired safety recalls for that individual car. Recall work is free at a franchised dealer regardless of mileage or how many owners the car has had. If your noise matches an open recall, the rest of this page is academic — book the dealer.
2. Read the complaints for your exact year, make and model. The same site's complaints search returns other owners' narratives. Search your model, then read for your noise, not for reassurance: when did it start, what mileage, what the dealer said first, what finally fixed it. Ten minutes of that is the difference between "it's making a noise" and "a lot of 2017 owners report this at around 80,000 miles and it was the transfer case."
3. List the manufacturer communications for your car. The same lookup shows the service bulletins and other communications the manufacturer has filed with NHTSA, by title and number. You cannot always read the full text free, but you can read the title — and the titles are remarkably candid, as "Drone Noise by Holding About 1600 RPM in Park or During Driving - No DTCs" demonstrates. Write down any number whose title resembles your symptom.
4. Hand the number to the shop, don't argue it. The sentence that works at a service counter is not "I read online that..." — it is "Bulletin [number] describes this symptom on my model year. Can you check whether it applies to my VIN?" A dealer can look up bulletin applicability in seconds, and a bulletin repair is sometimes covered by a warranty extension or customer satisfaction program you were never mailed about.
5. Record the noise before any of this. The record lookup tells you what is documented; the recording tells you what your car is doing tonight. You want both in the same conversation.
Should you buy a used car that makes a noise with no codes?
Sometimes, at the right price — and the "no codes" part should not reassure you at all. This is the mirror of the question the whole page answers, and it comes up on every second test drive, so here is the decision rule.
A clean scan on a used car is worth very little on its own. Two reasons. First, everything above: the mechanical failures with the biggest bills routinely produce no codes, so a blank read is compatible with a bad bearing, a stretched chain, a failing transfer case, or pads at metal. Second, codes can be erased in thirty seconds with a $12 adapter. What cannot be erased in thirty seconds is readiness-monitor status: after a code clear, the monitors read "not ready" until the car completes a series of drive cycles. Blank codes plus unset monitors means somebody cleared something recently, and that single screen is the most informative thing a cheap scanner does at a curb.
Price the noise before you decide, not after. Our complaint file says the median codeless-noise failure arrives around 80,000 miles and lands most often in the engine, the transmission or a driveline component — categories where a repair is four figures, not three. If you can name the suspect, you can negotiate against a number: a wheel bearing is a few hundred dollars and a fair thing to split; an intermittent knock under load on a car with no warranty is a walk-away, not a discount.
What to require before money changes hands. A pre-purchase inspection at $100-$200 that explicitly includes the noise, a scan that includes ABS and transmission modules rather than engine codes only, readiness-monitor status, and a VIN recall check you run yourself. A seller who declines the inspection has answered the question. A seller who agrees and is right has just sold you a car with a documented condition.
And the cheerful case: a documented, bulletined noise on a model with a known fix is often the best used-car bargain on a lot, because the fear is priced in and the repair is a known quantity. What you are avoiding is the undocumented noise on a car nobody has looked at, sold by somebody who tells you the scan came back clean.
Your sound-versus-scanner plan: next 10 minutes, today, this week
Next 10 minutes (free):
- Run the sort: light status + noise status → your route number. Flashing + shaking exits to the emergency guide immediately.
- Any noise present: record 30 seconds now, at onset, correctly — before it becomes intermittent.
- Bookmark your noise's specific guide from the table above — the suspect list and fair prices are the negotiation prep.
Today: 4. Light on: free code read at any parts store; exact P-numbers written down, freeze-frame requested if they'll share it. 5. Noise with no light: get it matched — free AI or careful self-matching — and write the named-suspect sentence before any shop contact. 6. Check any existing scanner-app subscriptions: what's the renewal date, and does a one-time tool now cover it?
This week: 7. If lights recur in your car's life: the $10-$25 ELM327 (or a $99.95-$139.95 BlueDriver for ABS/transmission depth) — one-time tools first, subscriptions only with eyes open. 8. Any shop visit happens on your terms: recording played, suspect named, "confirm and quote," findings in writing. 9. Used-car shopping: both tools packed — stored codes + readiness monitors, the listening test drive, and the $100-$200 PPI on the finalist.
For the noise side: the complete noise index, engine knocking, grinding when braking, squealing at start-up, clicking noises, and shaking at idle. For the code side: the solid check engine light and the flashing emergency. For the money side: what diagnostics cost, the app landscape, recording a noise properly, and finding a shop worth arriving at. And our story explains why PulsCar exists — and why it will never replace your mechanic, just give you a first pass before you see one.
Sources and documents
Primary documents and data, opened and read. Our own analysis is published as CSV so you can check the arithmetic.
- 40 CFR 86.1806-17, Onboard diagnostics — the federal rule that scopes OBD to the emission control system. eCFR text
- Honda service bulletin 23-037, 6 July 2023 — 2022-23 Civic, steering noise, "no MIL illuminated or DTC stored." PDF
- Honda service bulletin 24-011, 3 September 2024 — 2021-22 CR-V, clicking while turning, no DTC stored. PDF
- Infiniti ITB19-003, 22 February 2019 — 2019 QX50 spark knock with no DTCs in the ECM or TCM. PDF
- Jaguar SSM74070, 6 September 2018 — I-PACE brake noise, no DTCs or warning messages. PDF
- GM bulletin 24-NA-095, June 2024 — Encore GX and Trailblazer drone noise, "No DTCs" in the title. PDF
- Ford TSB 25-2612, 18 December 2025 — 2021-2025 F-150 grinding/hum/rumble, no DTCs stored in the TCCM. PDF
- NHTSA complaint flat file (777,040 complaints, 1 January 2015 - 8 September 2026). Field dictionary
- NHTSA manufacturer communications flat file (187,827 distinct communications). Field dictionary
- Our analysis, published — noise complaints by make, by model with median mileage, what the codeless noises turned out to be, noise bulletins by make, and the method file with every query, exclusion and limitation. Licensed CC BY 4.0.
- NHTSA VIN recall lookup — free, per-vehicle, open recalls only. Recall search
- BlueDriver product pricing — re-read on the manufacturer's own site, 18 September 2026. BlueDriver
What we looked for and could not verify. A published, independent accuracy rate for any consumer sound-diagnosis product — there is none we can cite, ours included, which is why this page describes sound diagnosis as a first pass and never attaches a percentage to it. We also could not re-read RepairPal, AutoZone or O'Reilly this week: all three refused our requests with an HTTP 403, so the shop-fee and free-code-read figures below carry their earlier dates rather than a fresh one.
How these numbers were built: cross-checked against 2026 retail and estimator data (generic ELM327 adapters $10-$25 with free apps such as Car Scanner ELM; BlueDriver Pro $139.95 and Pro Next-Gen $99.95, struck through from $119.95, on BlueDriver's own store, re-read 17 September 2026, no subscription, ABS/SRS/transmission coverage varying by make; FIXD sensor $59-$59.99 with engine codes free and ABS on select makes, and Premium published at $69.99-$99.99/year depending on the order path, per FIXD's own pages as read for our FIXD comparison on 6 September 2026 — FIXD's site refused our request on 17 September, so those figures were not re-read that day; PulsCar sound diagnosis free; mobile mechanic diagnostics $82-$179; independent shop diagnostics $80-$150; dealer diagnostics $120-$300; pre-purchase inspections $100-$200), with shop rates at 2026 labor averages ($120-$159/hr independent). Product prices and subscription terms change; verify current terms at purchase. On 18 September 2026 we re-read BlueDriver's own site and confirmed the Pro at $139.95; the separate Next-Gen product page did not resolve for us that day, so its $99.95 and struck-through $119.95 figures keep their 17 September date, and RepairPal, AutoZone and O'Reilly refused our requests with an HTTP 403, so the shop-fee and free-read figures were not re-checked this week.
Prices verified September 2026 for the BlueDriver Pro figure only — every other price on this page carries the earlier date named above. Technical documents verified September 2026: the six manufacturer bulletins and the Code of Federal Regulations section in the sources list were downloaded and read in full on 18 September 2026, and the NHTSA complaint and communication files behind our own analysis were queried the same day. Reviewed quarterly.
Not sure which tool your situation needs? Email [email protected] with what you're seeing and hearing — we'll point you the right way, even when the answer is a scanner, not us.
