Using Mode 6 to Catch Failing Components Before They Set Codes

Using Mode 6 Data to Catch Failing Components Before They Set a Code

Most technicians are comfortable reading DTCs and checking monitor status. But there is a whole layer of diagnostic data sitting inside the PCM that most shops never touch — and it can tell you a component is dying weeks or months before it ever sets a fault code. That layer is Mode 6, and if you are not using it, you are leaving real diagnostic information on the table.

This is not an advanced concept reserved for factory scan tools and dealership technicians. Mode 6 data is available on any OBD-II compliant vehicle — which covers virtually every car and light truck sold in the United States since 1996 — and you can pull it with a generic scan tool or even a mid-grade code reader that supports enhanced OBD-II modes. Once you understand what you are looking at, it becomes one of the most powerful predictive tools in your arsenal.

What Mode 6 Actually Is

OBD-II communication is broken into nine standard service modes, sometimes called service information modes. Mode 1 gives you live data. Mode 2 gives you freeze frame. Mode 3 gives you stored codes. Mode 6 is the one that gets skipped over in most shops, and it is also the most underrated.

Mode 6 contains the results of non-continuous monitor tests stored by the PCM. Think of it this way: the PCM is constantly running self-checks on specific components and systems. Continuous monitors like the misfire monitor and the comprehensive component monitor run all the time. Non-continuous monitors — catalytic converter efficiency, oxygen sensor response, EVAP system integrity, oxygen sensor heater — only run under specific drive conditions. Every time one of those tests runs to completion, the PCM records the result. That result is what Mode 6 exposes.

The data is not just a pass or fail flag. Mode 6 stores the actual measured test value alongside the minimum and maximum threshold values the PCM uses to judge whether the component passed or failed. That is where the real power is. A component can be sitting at 95 percent of the failure threshold, still technically passing, and the PCM will never set a code. But Mode 6 will show you exactly how close to the edge that component is.

How to Access Mode 6 Data

To pull Mode 6 data, your scan tool needs to support generic OBD-II Mode 6 requests. Many mid-range tools do this under a menu option labeled something like On-Board Monitoring, OBD-II Tests, or Non-Continuous Monitor Results. High-end factory tools and professional aftermarket tools like Snap-on, Autel, and Launch all support it. Even some sub-$200 generic scan tools will pull raw Mode 6 data if they support the full OBD-II mode set.

The challenge is interpretation. A raw Mode 6 screen on a generic tool will show you hexadecimal Test IDs and Component IDs, raw numeric values, and threshold limits. It looks like noise until you know what each test ID maps to on a given vehicle. Factory tools and better aftermarket tools will translate those IDs into plain English descriptions. If you are working with a generic tool that only shows raw hex values, you will need the vehicle-specific Mode 6 test ID definitions, which can usually be found in service information or in OBD-II documentation for that manufacturer.

Understanding Test IDs and Component IDs

Mode 6 data is organized using two identifiers: the Test ID, commonly abbreviated TID, and the Component ID, commonly abbreviated CID. Together they pinpoint exactly which test result you are looking at.

The Test ID identifies the type of test being performed. For example, TID $21 on many vehicles refers to the catalytic converter efficiency test. TID $01 might refer to oxygen sensor response time. The exact meaning of each TID is not universal across all manufacturers — which is one of the important limitations of Mode 6 — but within a given manufacturer family, these IDs tend to be consistent across model years.

The Component ID further specifies which component the test applies to. For oxygen sensors, the CID will tell you whether you are looking at Bank 1 Sensor 1, Bank 1 Sensor 2, Bank 2 Sensor 1, and so on. For misfire data, the CID identifies the cylinder. Understanding both identifiers together lets you pinpoint exactly what the PCM tested and what it found.

Each Mode 6 record contains four pieces of information you need to pay attention to:

• TID — Which test ran
• CID — Which component was tested
• Test Value — The actual measured result from the last completed test
• Min/Max Thresholds — The limits the PCM uses to determine pass or fail

A value within the threshold range means the component passed that test. A value outside the range means it failed — and if it failed, you should already have a DTC. The diagnostic gold is in the values that are inside the threshold but drifting toward the limit. That is your early warning system.

Catching a Failing Catalytic Converter Before P0420 Sets

This is the most common practical use of Mode 6 in a shop environment, and it is where the tool earns its keep. P0420 — catalyst system efficiency below threshold — is a code that sets after the PCM has already determined the converter has degraded past the point of acceptable function. By that point, the customer already has a check engine light, and the conversation becomes reactive.

Mode 6 lets you have that conversation proactively. The catalytic converter efficiency test compares oxygen storage activity between the upstream and downstream oxygen sensors. The PCM measures how quickly the downstream sensor oscillates compared to the upstream sensor. A healthy converter buffers the downstream sensor — it barely moves. A worn converter passes exhaust through with minimal processing, causing the downstream sensor to mirror the upstream sensor more closely.

The Mode 6 test value for converter efficiency reflects this relationship as a ratio or a counts-based measurement depending on the manufacturer. What you are looking for is how close that value is sitting to the threshold limit. If the spec is a maximum of 0.75 and the converter is currently testing at 0.71, that converter has maybe 10,000 to 20,000 miles of life left before P0420 sets. The PCM has not flagged it yet. The customer has no warning light. But Mode 6 is telling you the story.

That is a legitimate, data-backed upsell opportunity. You are not speculating based on mileage or age. You are showing the customer a number that proves the converter is on its way out. That conversation lands differently than saying the converter looks old and should be replaced soon.

Weak Oxygen Sensors Before They Set Codes

Oxygen sensor response time tests are another area where Mode 6 earns its keep. The PCM tests how fast the upstream oxygen sensor switches between rich and lean, typically measuring response time in milliseconds. It also tests the downstream sensor's activity level for converter monitoring purposes.

A fresh oxygen sensor switches fast and cleanly. As the sensor ages, the electrochemical cell inside the sensor begins to degrade. Response slows. The PCM measures this during the oxygen sensor response time test and stores the result in Mode 6. The threshold for a typical upstream sensor might be a maximum switch time of 100 milliseconds. A sensor reading 85 milliseconds is technically passing but already showing degradation. A sensor reading 97 milliseconds is almost at the line.

What makes this particularly useful is that oxygen sensor degradation often shows up in Mode 6 long before it causes noticeable driveability symptoms or sets a P013x or P014x diagnostic trouble code. By the time those codes set, the sensor has been degraded for a while and may have already caused fuel trim corrections, efficiency losses, and potentially contributed to other issues. Catching it early through Mode 6 is better for the customer and better for your diagnostic accuracy.

Misfire Counters in Mode 6

On many GM and Ford vehicles in particular, Mode 6 includes cylinder-specific misfire data. This is separate from the P030x misfire fault codes. The PCM tracks misfires per cylinder continuously and stores running counts. Mode 6 exposes those counts, and they can be extraordinarily useful.

A customer comes in with a rough idle complaint but no misfire codes set. You pull Mode 6 and find cylinder 4 is showing 47 misfires while every other cylinder is showing zero or single digits. That is your problem cylinder identified without ever inducing a fault code or doing an injector kill test. The PCM told you everything.

This also helps when a misfire code has been erased by a previous scan and the customer says the light came on once but went out. The misfire counters in Mode 6 may still show elevated counts on a specific cylinder even after the code was cleared, giving you documentation that the event happened and which cylinder was involved.

EVAP System Test Results

The EVAP system is notorious for generating codes based on marginal conditions — a loose gas cap, humidity, temperature extremes. Mode 6 EVAP test data helps you separate a genuine system integrity problem from a one-time anomaly.

EVAP tests in Mode 6 typically include results for the leak detection test, the purge flow test, and the vent valve operation test. The leak detection test value reflects the measured decay rate of pressure or vacuum in the EVAP system. If the PCM pulled the system to a target pressure and measured how long it held, Mode 6 will show you that time value and the minimum time required to pass. A system barely squeaking by on the minimum tells you there is a real but small leak present — probably not a gas cap, probably a deteriorating hose or a purge valve that is not sealing completely.

On vehicles that use a vacuum decay EVAP test strategy, Mode 6 can show you the exact vacuum level reached and how much it decayed during the test window. That is a level of detail that goes well beyond what a simple pass/fail flag tells you.

Using Mode 6 for Pre-Purchase Inspections

Mode 6 is one of the best tools available during a pre-purchase inspection, and almost no one uses it for that purpose. By the time a vehicle goes through inspection, whoever detailed it for sale has often cleared codes. Monitor readiness flags are a start, but they only tell you whether a monitor has run to completion — not how the component performed when it ran.

Mode 6 survives a code clear. The PCM resets the monitor status but the test result data updates as monitors run. If you do a pre-purchase inspection and have the customer or you drive the vehicle through a drive cycle, Mode 6 will show you exactly how every non-continuous monitor component tested. A catalytic converter sitting at 90 percent of the failure threshold. An oxygen sensor response time right at the limit. An EVAP system barely passing the leak test. None of those generate a check engine light, but they all represent near-term repair expenses the buyer should know about before they sign papers.

From a shop standpoint, this makes your inspection report more credible and more detailed than the competition. You are not saying the exhaust system looks worn. You are showing a number from inside the vehicle's own computer.

Manufacturer Differences in Mode 6 Implementation

This is where Mode 6 gets complicated, and you need to understand the variability before you rely on it heavily.

The OBD-II standard requires manufacturers to support Mode 6, but it does not mandate what specific tests must be included or how test results must be scaled. As a result, Mode 6 implementations vary significantly across manufacturers and even across model lines within the same manufacturer.

Manufacturer	Mode 6 Characteristics
GM	Generally excellent Mode 6 support. Test IDs are well-documented and consistent across platforms. Cylinder misfire counts are readily available. Catalyst and O2 sensor data is detailed. Generic scan tools often interpret GM Mode 6 data accurately.
Ford	Strong Mode 6 implementation, particularly on EcoBoost and larger engine families. Ford includes detailed EVAP test data and misfire information. Some older Ford applications use proprietary scaling that can confuse generic tools. IDS and FORScan provide the best interpretation.
Toyota	Toyota Mode 6 data is present but can be sparse compared to domestic vehicles. The catalyst efficiency test data is typically available and reliable. Response time data for oxygen sensors is included but Toyota often uses different scaling factors. Factory Techstream provides the most complete picture.
Honda	Honda has historically been one of the more challenging manufacturers for Mode 6 interpretation. Some Honda platforms provide limited non-continuous monitor test detail through generic Mode 6 requests. Honda's factory scan tool (HDS) provides far more diagnostic detail than any generic Mode 6 request will reveal on these vehicles.

The practical takeaway is this: Mode 6 is most reliable and most readable on GM and Ford products using a quality scan tool that has vehicle-specific Mode 6 interpretation built in. On Asian nameplate vehicles, Mode 6 is still useful, but you may need to cross-reference raw values against manufacturer documentation to understand what you are looking at. A generic tool showing Mode 6 hex data on a Honda does not mean the data is wrong — it means the tool is not translating it for you.

Using Mode 6 Data to Upsell Legitimate Maintenance

There is a right way and a wrong way to use this data with customers. The wrong way is to cherry-pick a number that looks bad and scare someone into an unnecessary repair. Do not do that — it destroys trust and it is not what this data is for.

The right way is to show customers the trend and let the data speak. Print the Mode 6 results or show them on a tablet. Explain in plain terms: Your catalytic converter is still passing its test right now, but this number shows it is 85 percent of the way to the point where it will fail and trigger a check engine light. Based on what I am seeing, you have probably one more year before that becomes a code and a repair.

That kind of conversation does several things. It positions your shop as thorough and transparent. It gives the customer time to plan financially for a repair rather than being hit with an unexpected bill. And it builds the kind of trust that makes customers come back. They know you are not making things up — you are reading the car's own internal test data.

Common Mode 6 based maintenance conversations that are backed by real data include:

• Catalytic converter replacement when efficiency test values are consistently trending toward the failure threshold over multiple visits
• Oxygen sensor replacement when response time is degraded but not yet at the code-setting limit
• EVAP hose and purge valve inspection when the leak test is barely passing
• Ignition system service when cylinder-specific misfire counts show one cylinder consistently elevated
• Fuel injector service when misfire data correlates with a specific cylinder showing no obvious mechanical cause

Limitations of Mode 6

Mode 6 is a powerful tool, but you need to understand what it cannot do so you do not over-rely on it or misinterpret what you are seeing.

It only updates when the test runs to completion. If a vehicle comes in and the monitors have not completed their drive cycle, the Mode 6 data may be stale or absent for some tests. A customer who just had their battery replaced and has not completed a full drive cycle will show incomplete or cleared Mode 6 data. Always verify monitor completion status before drawing conclusions from Mode 6 results.

It does not directly tell you what is causing a borderline value. If the catalyst efficiency test is showing a value near the threshold, Mode 6 confirms the converter is underperforming — but it does not tell you if the converter is mechanically degraded, or if there is an upstream fuel trim issue skewing the test, or if an exhaust leak is contaminating the readings. Mode 6 is the starting point for a conversation, not the final diagnosis.

Test ID definitions are not universal. The same TID number can mean completely different things on a GM versus a Toyota versus a Chrysler product. Never assume a test ID definition from one manufacturer applies to another. Use vehicle-specific documentation or a scan tool with proper mode 6 interpretation for the specific vehicle you are working on.

Not all manufacturers implement all tests. Some manufacturers provide very limited Mode 6 data, and some tests that you might expect to see simply are not implemented for a given vehicle. Absence of data is not the same as a passing result — it may just mean the manufacturer did not include that test in their Mode 6 implementation.

Generic scan tools vary in their ability to interpret Mode 6 data. A tool that shows raw hex values is still giving you real data — but without interpretation, it is easy to misread. Invest in a tool or software that has documented Mode 6 interpretation for the vehicles you work on most frequently.

Making Mode 6 Part of Your Standard Process

The biggest obstacle to using Mode 6 regularly is habit. Most technicians were trained to pull codes, check PIDs, and refer to service information. Mode 6 was never emphasized in ASE training or in most dealership technical training programs. It feels unfamiliar, and unfamiliar tools get skipped.

The fix is to make it a routine step during every diagnostic and every maintenance inspection. Every time you hook up a scan tool, pull Mode 6 along with codes and monitor status. It takes thirty seconds. You will not find something useful on every vehicle. But on the ones where you do, the payoff is significant — in diagnostic accuracy, in legitimate repair revenue, and in the kind of credibility that turns a one-time customer into a long-term shop relationship.

Mode 6 is the PCM telling you what it already knows about how its own components are performing. All you have to do is listen to it.