How JustAnswer Works:
  • Ask an Expert
    Experts are full of valuable knowledge and are ready to help with any question. Credentials confirmed by a Fortune 500 verification firm.
  • Get a Professional Answer
    Via email, text message, or notification as you wait on our site.
    Ask follow up questions if you need to.
  • 100% Satisfaction Guarantee
    Rate the answer you receive.
Ask Greg Your Own Question
Greg
Greg, import technician
Category: Mazda
Satisfied Customers: 6955
Experience:  17 years shop owner import
29331485
Type Your Mazda Question Here...
Greg is online now
A new question is answered every 9 seconds

I have bought a 2004 Mazda speed Miata from a dealer"

Customer Question

Hi I have bought a 2004 Mazda speed Miata from a dealer " hendrick automotive group Charlotte " and they've had it a week now and they are not able to reset the computer could it be something else
Submitted: 1 year ago.
Category: Mazda
Expert:  Greg replied 1 year ago.

What problem are you having with this car .

Are they trying to reprogram the ECU or clear codes to get the check engine light off .

Rgds Greg

Customer: replied 1 year ago.
I am assuming that when they replaced the radiator in the car they disconnected the battery and the ecu lost its memory. The car was brought in from out-of-state from South Carolina into North Carolina and North Carolina it has to pass and omissions test there aren't able to get the computer to hold any information .
Expert:  Greg replied 1 year ago.

Okay i think your problem is that they are waiting for all monitoring system to set to Ready .

Your Onboard Diagnostic System (OBD II) has NOT completed all of its self-test monitors that keep an eye on the performance of your emissions control systems.
There may be few OBD monitors that are "NOT READY" this i will prevent your vehicle from passing the emissions inspection.

You first need to check for any malfunction codes , is there any codes stored in the system .

What Causes a "Not-Ready" Report?

Causes of a "not ready" report:

Recent vehicle repairs in which diagnostic trouble codes have been cleared with a OBDII scan tool; or,
if the battery had been recently disconnected or replaced; or if the vehicle's computer requires a software update;

or a pending problem has not yet illuminated the "check engine" light.

If "NO" codes do a Generic Drive Cycle this should cause all systems ready.

The purpose of the OBDII drive cycle is to run your vehicle's onboard diagnostics.

This in turn, allows monitors to operate and detect potential malfunctions of your vehicle's emission system.

The correct drive cycle for your vehicle can vary greatly, depending on the vehicle model and the monitors that need to be reset. When a specific drive cycle is not known, or drive cycle information is not available from an owner's manual, the generic cycle described below may assist with resetting your vehicle's monitors.

However, this generic cycle may not work for all vehicles.

IMPORTANT:

If you choose to use the generic drive cycle below, you must obey all traffic laws and drive in a safe manner. Also, be sure the required preconditions are met prior to performing the drive cycle.

The OBDII drive cycle begins with a cold start (coolant temperature below 122 degrees F and the coolant and air temperature sensors within 11 degrees of each other).
The ignition key must not be left on prior to the cold start – otherwise the heated oxygen sensor diagnostic may not run.

As soon as the engine starts, idle the engine in drive for two and one-half minutes, with the air conditioning (A/C) and rear defrost turned on, if equipped.
Turn the A/C and rear defrost off, and accelerate to 55 mph under moderate, constant acceleration. Hold at a steady speed of 55 mph for three minutes.
Decelerate (coast down) to 20 mph without braking (or depressing the clutch for manual transmissions).
Accelerate again back to 55 to 60 mph.
Hold at a steady speed of 55 to 60 mph for five minutes. Decelerate (coast down) to a stop without braking.

Let me know what happens may have to try another drive cycle .

Kind regards Greg