What Is OBD2 Specification and How Does It Work?

The Obd2 Specification is your car’s built-in diagnostic system, a standardized protocol for retrieving diagnostic trouble codes (DTCs) and real-time data. At MERCEDES-DIAGNOSTIC-TOOL.EDU.VN, we provide expert insights and tools to empower Mercedes-Benz owners and technicians to understand and utilize the OBD2 system effectively. Equip yourself with the knowledge to optimize your vehicle’s performance with diagnostic data, scan tools, and automotive technology.

1. Understanding the OBD2 Specification

OBD2, or On-Board Diagnostics II, is a vital system in modern vehicles. It acts as the car’s self-diagnostic system, reporting on the health and performance of various components.

1.1. What is OBD2?

OBD2 is a standardized protocol that allows access to diagnostic trouble codes (DTCs) and real-time data via the OBD2 connector. This system monitors various engine and vehicle parameters, alerting drivers to potential issues through the malfunction indicator light (MIL), commonly known as the “check engine light.” It helps to improve vehicle reliability and reduce emissions.

1.2. History and Evolution of OBD2

OBD2 originates from California, where the California Air Resources Board (CARB) required OBD in all new cars from 1991 onward for emission control purposes. The OBD2 standard was recommended by the Society of Automotive Engineers (SAE) and standardized DTCs and the OBD connector across manufacturers (SAE J1962). The implementation of OBD2 was phased in:

• 1996: OBD2 became mandatory in the USA for cars and light trucks.
• 2001: Required in the EU for gasoline cars.
• 2003: Required in the EU for diesel cars (EOBD).
• 2005: OBD2 required in the US for medium-duty vehicles.
• 2008: US cars must use ISO 15765-4 (CAN) as the OBD2 basis.
• 2010: OBD2 required in US heavy-duty vehicles.

1.3. Key Components of the OBD2 System

The OBD2 system consists of several key components:

• OBD2 Connector: A 16-pin connector (SAE J1962) that allows access to the vehicle’s diagnostic data.
• Sensors: Various sensors throughout the vehicle that monitor engine and emission control systems.
• Engine Control Unit (ECU): The computer that processes sensor data and triggers the MIL if a problem is detected.
• Diagnostic Trouble Codes (DTCs): Standardized codes that identify specific issues within the vehicle’s systems.

1.4. Does Your Mercedes-Benz Support OBD2?

Almost all Mercedes-Benz vehicles manufactured after 1996 support the OBD2 protocol. The easiest way to verify is to check the vehicle’s owner’s manual or locate the OBD2 connector, typically found under the dashboard near the steering wheel. This system’s widespread adoption ensures comprehensive diagnostic capabilities.

1.5. Benefits of Using OBD2

The OBD2 system offers numerous benefits for vehicle owners and technicians:

• Early Problem Detection: Allows for the early detection of potential issues, preventing costly repairs.
• Standardized Diagnostics: Provides a standardized approach to diagnosing vehicle problems across different makes and models.
• Real-Time Data: Offers access to real-time data, enabling informed decisions about vehicle maintenance.
• Emission Control: Helps to ensure that vehicles meet emission standards, contributing to environmental protection.

1.6. Understanding the OBD2 Connector (SAE J1962)

The 16-pin OBD2 connector is specified in the SAE J1962 standard (ISO 15031-3) and is used to access data from your car. It is typically located near the steering wheel, though it may be hidden. Pin 16 supplies battery power, even when the ignition is off. The OBD2 pinout depends on the communication protocol used, with CAN bus being the most common, utilizing pins 6 (CAN-H) and 14 (CAN-L).

1.7. Type A vs. Type B OBD2 Connectors

You may encounter both Type A and Type B OBD2 connectors. Type A is typically found in cars, while Type B is common in medium and heavy-duty vehicles. While they share similar pinouts, Type A provides 12V power, and Type B provides 24V. Type B OBD2 connectors have an interrupted groove in the middle, making a Type B OBD2 adapter cable compatible with both types, while a Type A cable will not fit into a Type B socket.

2. Deep Dive into the OBD2 Specification Standards

The OBD2 specification is governed by several standards that define various aspects of the system, from the physical connector to the communication protocols.

2.1. Overview of OBD2 Standards

OBD2 standards specify the OBD2 connector, lower-layer protocols, and OBD2 parameter IDs (PIDs). Several layers are covered by both SAE and ISO standards, reflecting OBD standards defined in the USA (SAE) and the EU (ISO). For example, SAE J1979 is technically equivalent to ISO 15031-5, and SAE J1962 is similar to ISO 15031-3. These standards ensure compatibility and consistency in vehicle diagnostics.

2.2. CAN Bus and OBD2 (ISO 15765-4)

Since 2008, CAN bus has been the mandatory lower-layer protocol for OBD2 in all cars sold in the US, as per ISO 15765. ISO 15765-4 (Diagnostics over CAN or DoCAN) specifies restrictions applied to the CAN standard (ISO 11898), standardizing the CAN interface for test equipment with a focus on the physical, data link, and network layers.

2.3. Key Aspects of ISO 15765-4

• The CAN bus bit-rate must be either 250K or 500K.
• The CAN IDs can be 11-bit or 29-bit.
• Specific CAN IDs are used for OBD requests and responses.
• The diagnostic CAN frame data length must be 8 bytes.
• The OBD2 adapter cable must be a maximum of 5 meters.

2.4. OBD2 CAN Identifiers (11-bit, 29-bit)

OBD2 communication involves request/response messages. In most cars, 11-bit CAN IDs are used, with the ‘Functional Addressing’ ID being 0x7DF, which asks all OBD2-compatible ECUs if they have data to report on the requested parameter. CAN IDs 0x7E0-0x7E7 can perform ‘Physical Addressing’ requests from specific ECUs. ECUs respond with 11-bit IDs 0x7E8-0x7EF, with 0x7E8 (ECM, Engine Control Module) and 0x7E9 (TCM, Transmission Control Module) being the most common response IDs.

2.5. Extended 29-bit CAN Identifiers

In some vehicles (e.g., vans and light/medium/heavy-duty vehicles), OBD2 communication uses extended 29-bit CAN identifiers instead of 11-bit CAN identifiers. The ‘Functional Addressing’ CAN ID is 0x18DB33F1. Responses are seen with CAN IDs 0x18DAF100 to 0x18DAF1FF (typically 18DAF110 and 18DAF11E). The response ID is sometimes shown in the ‘J1939 PGN’ form, specifically PGN 0xDA00 (55808), which is marked as ‘Reserved for ISO 15765-2’ in the J1939-71 standard.

2.6. OBD2 vs. Proprietary CAN Protocols

Your car’s ECUs do not rely on OBD2 to function. Each OEM implements its proprietary CAN protocols, specific to the vehicle brand, model, and year. Connecting a CAN bus data logger to your car’s OBD2 connector may reveal OEM-specific CAN data, but in many newer cars, a ‘gateway’ blocks access to this CAN data, enabling only OBD2 communication. Think of OBD2 as an ‘extra’ higher-layer protocol parallel to the OEM-specific protocol.

2.7. Bit-rate and ID Validation

OBD2 may use one of two bit-rates (250K, 500K) and one of two CAN ID lengths (11-bit, 29-bit), resulting in four potential combinations. Modern cars commonly use 500K and 11-bit IDs, but tools should verify this systematically. ISO 15765-4 provides recommendations for a systematic initialization sequence to determine the relevant combination, leveraging that OBD2-compliant vehicles must respond to a mandatory OBD2 request.

2.8. Five Lower-Layer OBD2 Protocols

CAN is the basis for OBD2 in the vast majority of cars per ISO 15765. Older cars (pre-2008) may use other protocols:

• ISO 15765 (CAN bus): Mandatory in US cars since 2008.
• ISO14230-4 (KWP2000): Common protocol for 2003+ cars in Asia.
• ISO 9141-2: Used in EU, Chrysler, and Asian cars in 2000-04.
• SAE J1850 (VPW): Mostly used in older GM cars.
• SAE J1850 (PWM): Mostly used in older Ford cars.

3. Mastering the OBD2 Diagnostic Message

The OBD2 diagnostic message is the core of the communication between a scan tool and the vehicle’s ECU, enabling the retrieval of diagnostic data and trouble codes.

3.1. Understanding the OBD2 Message Structure

An OBD2 message is comprised of an identifier, data length (PCI field), and data. The data is split into Mode, parameter ID (PID), and data bytes. Understanding this structure is key to interpreting OBD2 data.

3.2. Example: OBD2 Request/Response

Consider this example request/response for the parameter ‘Vehicle Speed’. An external tool sends a request message to the car with CAN ID 0x7DF and 2 payload bytes: Mode 0x01 and PID 0x0D. The car responds via CAN ID 0x7E8 and 3 payload bytes, including the value of Vehicle Speed in the 4th byte, 0x32 (50 in decimal form). Looking up the decoding rules for OBD2 PID 0x0D, we determine that the physical value is 50 km/h.

3.3. The 10 OBD2 Services (aka Modes)

There are 10 OBD2 diagnostic services (or modes). Mode 0x01 shows current real-time data, while others are used to show/clear diagnostic trouble codes (DTCs) or show freeze-frame data. Vehicles do not have to support all OBD2 modes and may support modes outside the 10 standardized modes (OEM-specific OBD2 modes). In OBD2 messages, the mode is in the 2nd byte. In the request, the mode is included directly (e.g., 0x01), while in the response, 0x40 is added to the mode (e.g., resulting in 0x41).

3.4. OBD2 Parameter IDs (PIDs)

Each OBD2 mode contains parameter IDs (PIDs). For example, mode 0x01 contains ~200 standardized PIDs with real-time data on speed, RPM, and fuel level. However, a vehicle does not have to support all OBD2 PIDs in a mode; most vehicles support only a small subset. If an emissions-related ECU supports any OBD2 services, it must support mode 0x01 PID 0x00. In response to this PID, the vehicle ECU informs whether it supports PIDs 0x01-0x20, making PID 0x00 useful as a fundamental ‘OBD2 compatibility test’. Further, PIDs 0x20, 0x40, …, 0xC0 can be used to determine support for the remaining mode 0x01 PIDs.

3.5. OBD2 PID Overview Tool

The appendices of SAE J1979 and ISO 15031-5 contain scaling info for standard OBD2 PIDs, which allows you to decode the data into physical values. For convenience, MERCEDES-DIAGNOSTIC-TOOL.EDU.VN provides an OBD2 PID overview tool. This helps you construct OBD2 request frames and dynamically decode the OBD2 responses. Check out our OBD2 PID overview tool.

3.6. Transporting OBD2 Messages via ISO-TP (ISO 15765-2)

All OBD2 data is communicated on the CAN bus through a transport protocol called ISO-TP (ISO 15765-2). This enables communication of payloads that exceed 8 bytes. This is necessary in OBD2 when extracting the Vehicle Identification Number (VIN) or Diagnostic Trouble Codes (DTCs). ISO 15765-2 enables segmentation, flow control, and reassembly. Often, however, the OBD2 data will fit in a single CAN frame. ISO 15765-2 specifies the use of a ‘Single Frame’ (SF), implying that the 1st data byte (aka PCI field) contains the payload length (excluding padding), leaving 7 bytes for the OBD2-related communication.

4. Practical Guide: Logging and Decoding OBD2 Data

Logging and decoding OBD2 data can provide valuable insights into your vehicle’s performance and potential issues. This section offers a practical guide on how to accomplish this effectively.

4.1. Choosing the Right Tools

To log and decode OBD2 data, you will need the following tools:

• OBD2 Scanner or Data Logger: A device that connects to your vehicle’s OBD2 port and records data.
• CAN Bus Data Logger: For more advanced data logging, a CAN bus data logger can capture all CAN bus traffic, including OBD2 data.
• Software for Data Analysis: Software tools to decode and analyze the logged data, such as asammdf.

4.2. Step-by-Step Guide to Logging OBD2 Data

1. Connect the Data Logger: Plug the OBD2 scanner or CAN bus data logger into your vehicle’s OBD2 port.
2. Configure the Device: Set up the data logger to record the specific PIDs you are interested in.
3. Start Logging: Begin recording data while driving or running the vehicle.
4. Stop Logging: End the data logging session once you have collected the necessary data.
5. Download the Data: Transfer the logged data from the device to your computer.

4.3. Decoding Raw OBD2 Data

To analyze the data, you need to decode the raw OBD2 data into physical values. The decoding information can be found in ISO 15031-5/SAE J1979. MERCEDES-DIAGNOSTIC-TOOL.EDU.VN provides a free OBD2 DBC file that makes it easy to DBC decode raw OBD2 data in most CAN bus software tools.

4.4. Decoding OBD2 with DBC Files

Decoding OBD2 data is a bit more complex than regular CAN signals because different OBD2 PIDs are transported using the same CAN ID (e.g., 0x7E8). The CAN ID is not sufficient to uniquely identify what signals are encoded in the payload. To solve this, leverage both the CAN ID, OBD2 mode, and OBD2 PID to identify the signal. This is a form of multiplexing referred to as ‘extended multiplexing,’ which can be implemented in DBC files.

5. Advanced OBD2 Communication Examples

Understanding advanced OBD2 communication techniques can provide deeper insights into vehicle diagnostics and performance.

5.1. Multi-Frame Examples (ISO-TP)

All OBD2 data is communicated using the ISO-TP (transport protocol) as per ISO 15765-2. Most examples reflect single-frame communication. Multi-frame OBD2 communication requires flow control frames.

5.2. Example 1: OBD2 Vehicle Identification Number (VIN)

To extract the Vehicle Identification Number from a vehicle using OBD2 requests, use mode 0x09 and PID 0x02. The tester tool sends a Single Frame request with the PCI field (0x02), request service identifier (0x09), and PID (0x02). The vehicle responds with a First Frame containing the PCI, length (0x014 = 20 bytes), mode (0x49, i.e., 0x09 + 0x40), and PID (0x02). Following the PID is the byte 0x01, which is the Number Of Data Items (NODI), in this case 1. The remaining 17 bytes equal the VIN and can be translated from HEX to ASC.

5.3. Example 2: OBD2 Multi-PID Request (6x)

External tools can request up to 6 mode 0x01 OBD2 PIDs in a single request frame. The ECU responds with data for supported PIDs (with unsupported PIDs left out of the response), if necessary across multiple frames as per ISO-TP.

5.4. Example 3: OBD2 Diagnostic Trouble Codes (DTCs)

You can use OBD2 to request emissions-related Diagnostic Trouble Codes (DTCs) from using mode 0x03, i.e., ‘Show stored Diagnostic Trouble Codes’. No PID is included in the request. The targeted ECU(s) will then respond with the number of DTCs they have stored (including potentially 0 if they have none), with each DTC taking up 2 data bytes.

5.5. DTC Interpretation

The 2-byte DTC value is typically split into two parts, as per ISO 15031-5/ISO 15031-6. The first 2 bits define the ‘category,’ while the remaining 14 bits define a 4-digit code (displayed in hexadecimal). The decoded DTC values can be looked up in various OBD2 DTC lookup tools like repairpal.com.

6. Real-World Use Cases for OBD2 Data Logging

OBD2 data from cars and light trucks can be used in various scenarios:

• Logging data from cars: Reduce fuel costs, improve driving habits, test prototype parts, and optimize insurance rates.
• Real-time car diagnostics: Stream human-readable OBD2 data in real-time to diagnose vehicle issues.
• Predictive maintenance: Monitor cars and light trucks via IoT OBD2 loggers in the cloud to predict and avoid breakdowns.
• Vehicle blackbox logger: Use an OBD2 logger as a ‘blackbox’ for vehicles or equipment, providing data for disputes or diagnostics.

7. OBD2 Data Logging Use Cases

OBD2 data logging has diverse applications that enhance vehicle maintenance, diagnostics, and performance monitoring.

7.1. Enhancing Vehicle Maintenance

Logging OBD2 data helps in identifying potential issues before they escalate. By monitoring parameters like engine temperature, fuel trims, and O2 sensor readings, you can proactively address minor problems, preventing major breakdowns and extending the lifespan of your vehicle. Regular data logging supports a proactive maintenance schedule.

7.2. Improving Driving Efficiency

OBD2 data provides insights into driving habits, enabling drivers to optimize their techniques for better fuel efficiency. By analyzing parameters like throttle position, speed, and RPM, drivers can identify areas for improvement, such as reducing harsh acceleration and maintaining optimal speeds. Real-time feedback helps drivers make informed decisions on the road.

7.3. Diagnostic Applications

OBD2 data is invaluable for diagnosing vehicle issues. When a check engine light appears, accessing the stored diagnostic trouble codes (DTCs) via an OBD2 scanner helps pinpoint the source of the problem. Real-time data streams can further assist in diagnosing intermittent issues, providing a comprehensive view of the vehicle’s performance under various conditions.

7.4. Performance Monitoring

Enthusiasts and professional tuners use OBD2 data logging to monitor and optimize vehicle performance. By recording parameters like boost pressure, air-fuel ratio, and ignition timing, they can fine-tune engine settings for maximum power and efficiency. Data logging is essential for validating the effects of aftermarket modifications and ensuring optimal performance.

7.5. Fleet Management

Fleet managers leverage OBD2 data to monitor vehicle health, track driver behavior, and optimize operational efficiency. Real-time tracking of parameters like fuel consumption, idle time, and speed helps in identifying areas for cost savings and improving overall fleet performance. Data-driven insights support better decision-making and streamlined operations.

8. Common OBD2 Diagnostic Trouble Codes (DTCs)

Understanding common OBD2 DTCs is crucial for effective vehicle diagnostics. Here are some frequently encountered codes and their implications:

8.1. P0171 – System Too Lean (Bank 1)

This code indicates that the engine’s air-fuel mixture is too lean, meaning there is too much air or not enough fuel. Possible causes include vacuum leaks, faulty O2 sensors, or a malfunctioning fuel pump. Addressing this issue promptly can prevent engine damage and improve fuel efficiency.

8.2. P0300 – Random Misfire Detected

A P0300 code signals that the engine is experiencing random misfires. This can be caused by worn spark plugs, faulty ignition coils, vacuum leaks, or low fuel pressure. Diagnosing and resolving misfires is essential for maintaining engine performance and preventing catalytic converter damage.

8.3. P0420 – Catalyst System Efficiency Below Threshold (Bank 1)

This code indicates that the catalytic converter is not functioning efficiently. Possible causes include a failing catalytic converter, exhaust leaks, or faulty O2 sensors. Replacing a failing catalytic converter is necessary to meet emission standards and maintain vehicle performance.

8.4. P0442 – Evaporative Emission Control System Leak Detected (Small Leak)

A P0442 code indicates a small leak in the evaporative emission control system, which prevents fuel vapors from escaping into the atmosphere. Common causes include a loose or faulty gas cap, cracked hoses, or a malfunctioning purge valve. Addressing EVAP system leaks helps reduce emissions and improve air quality.

8.5. P0505 – Idle Control System Malfunction

This code signals an issue with the idle control system, which regulates the engine’s idle speed. Possible causes include a faulty idle air control valve, vacuum leaks, or throttle body issues. Resolving idle control problems ensures smooth engine operation and prevents stalling.

8.6. Interpreting DTCs Effectively

When diagnosing vehicle issues using OBD2 DTCs, consider the following tips:

• Verify the Code: Use a reliable OBD2 scanner to confirm the accuracy of the DTC.
• Research the Code: Consult repair manuals, online forums, and diagnostic databases to understand the potential causes and solutions for the specific DTC.
• Inspect the Vehicle: Perform a thorough visual inspection of the engine and related components to identify any obvious issues, such as loose connections, damaged hoses, or worn parts.
• Test Components: Use diagnostic tools, such as multimeters and pressure gauges, to test the functionality of sensors, actuators, and other components related to the DTC.
• Address Multiple Codes: If multiple DTCs are present, prioritize the diagnosis based on the severity and potential impact on vehicle performance.

9. Future Trends in OBD Technology

OBD technology continues to evolve, driven by advancements in automotive technology and increasing demands for data-driven insights. Here are some key trends shaping the future of OBD:

9.1. OBD3 and Remote Diagnostics

OBD3 adds telematics to all cars. OBD3 adds a small radio transponder to all cars. Using this, the car vehicle identification number (VIN) and DTCs can be sent via WiFi to a central server for checks. This saves cost and is convenient, but it is also politically a challenge due to surveillance concerns.

9.2. Enhanced Data Parameters

Future OBD systems will support a broader range of data parameters, providing more detailed insights into vehicle performance and component health. This includes enhanced monitoring of safety systems, advanced driver-assistance systems (ADAS), and electric vehicle (EV) components. More comprehensive data will enable more accurate diagnostics and predictive maintenance strategies.

9.3. Integration with Mobile Apps

OBD data is increasingly accessible through mobile apps, allowing drivers to monitor their vehicle’s health and performance in real-time. These apps can provide personalized insights, maintenance reminders, and diagnostic support, empowering drivers to take proactive care of their vehicles. Seamless integration with mobile devices enhances convenience and accessibility.

9.4. Cybersecurity Measures

As OBD systems become more connected, cybersecurity becomes a critical concern. Future OBD technologies will incorporate robust security measures to protect against unauthorized access, data breaches, and malicious attacks. Secure communication protocols, encryption techniques, and authentication mechanisms will safeguard vehicle data and ensure the integrity of diagnostic systems.

9.5. Impact on Automotive Technicians

These trends will significantly impact automotive technicians, requiring them to adapt to new technologies and diagnostic methods. Technicians will need to develop expertise in data analysis, cybersecurity, and advanced diagnostic tools to effectively service future vehicles. Continuous training and skill development will be essential for staying ahead in the evolving automotive landscape.

10. Frequently Asked Questions (FAQ) About OBD2 Specification

Here are some frequently asked questions about the OBD2 specification:

10.1. What is the Best OBD2 Scanner for Mercedes-Benz?

The best OBD2 scanner for your Mercedes-Benz depends on your needs and budget. Options range from basic code readers to advanced diagnostic tools with capabilities like live data streaming and bidirectional control.

10.2. How Do I Open Hidden Features on My Mercedes-Benz?

Unlocking hidden features on your Mercedes-Benz may require specialized software and coding. Consult with a qualified technician at MERCEDES-DIAGNOSTIC-TOOL.EDU.VN with expertise in Mercedes-Benz diagnostics and programming.

10.3. How Often Should I Service My Mercedes-Benz?

The recommended service interval for your Mercedes-Benz depends on the model and driving conditions. Refer to your vehicle’s owner’s manual or consult with a certified Mercedes-Benz technician for specific recommendations.

10.4. What Does the Check Engine Light Mean?

The check engine light indicates a potential issue with your vehicle’s engine or emission control system. Use an OBD2 scanner to retrieve the diagnostic trouble code (DTC) and identify the cause of the problem.

10.5. Can I Clear the Check Engine Light Myself?

You can clear the check engine light using an OBD2 scanner, but it’s essential to address the underlying issue first. Clearing the code without fixing the problem will only result in the light reappearing.

10.6. What is the Difference Between OBD1 and OBD2?

OBD1 is an earlier version of the on-board diagnostic system, while OBD2 is the standardized protocol used in most vehicles manufactured after 1996. OBD2 offers more comprehensive diagnostic capabilities and standardized diagnostic trouble codes (DTCs).

10.7. How Can OBD2 Data Improve Fuel Efficiency?

OBD2 data provides insights into driving habits and engine performance, enabling drivers to optimize their techniques for better fuel efficiency. Monitoring parameters like throttle position, speed, and RPM can help identify areas for improvement.

10.8. What Security Risks are Associated with OBD2 Ports?

OBD2 ports can be vulnerable to security risks if not properly protected. Unauthorized access to the OBD2 port can potentially allow hackers to manipulate vehicle systems, posing a threat to vehicle safety and security.

10.9. Can I Use OBD2 for Remote Vehicle Monitoring?

Yes, OBD2 data can be used for remote vehicle monitoring through telematics systems. These systems transmit OBD2 data to a remote server, enabling fleet managers and vehicle owners to track vehicle health, location, and driver behavior.

10.10. Where Can I Find Reliable Information on OBD2 Codes?

Reliable information on OBD2 codes can be found in repair manuals, online forums, diagnostic databases, and websites like repairpal.com. Always consult multiple sources and verify the information before taking any action.

Final Thought

Understanding the OBD2 specification is crucial for anyone looking to maintain, diagnose, or enhance their Mercedes-Benz. At MERCEDES-DIAGNOSTIC-TOOL.EDU.VN, we are dedicated to providing the knowledge, tools, and support you need to make the most of your vehicle’s diagnostic capabilities. Whether you are a seasoned technician or a passionate car owner, our resources can help you unlock the full potential of your Mercedes-Benz.

Ready to take control of your Mercedes-Benz diagnostics? Contact us at MERCEDES-DIAGNOSTIC-TOOL.EDU.VN, located at 789 Oak Avenue, Miami, FL 33101, United States, or reach out via WhatsApp at +1 (641) 206-8880. Let us help you optimize your vehicle’s performance with expert advice and top-notch diagnostic tools.