Deleting the engine incident warning with Creader OBDII Scanner 3001 - Chevrolet AVEO 2002-2011

This guide only aims to give a little guidance on the option of using an OBDII connection terminal (multi-brand terminal), there are hundreds of models on the market, so the one shown in this document is neither the best, nor the worst, nor the most complete, nor the most basic, nor the most expensive, nor the cheapest, it is just one more,

To serve as guidance on the function they perform. Examples of the many on the market.

Photo 1: Model of this device, Creader 3001.

Photo 2: Location of the OBDII connector in a Chevrolet Aveo 2002 - 2011. NOTE, IN EACH CAR THIS CONNECTTOR CAN BE IN VARIOUS LOCATIONS, EVEN HIDDEN.

Photo 3: OBD II connector, on Chevrolet AVEO 2002 - 2011, BE AWARE: originally it was not where it is in the photo, it has been moved to a more accessible location under the steering wheel.

The device does not have an internal battery; it is powered by the car when connected to OBDII.

Unlike what happens with the EMM327 interface, VGATE and others,that need the engine running to operate; to perform their checks this interface type need the engine stopped with the contact activated on the first point. (Powered board).

First Function, DIAGNOSIS; press OK

Photo1: DIAGNOSIS and press the OK button.

Photo 2: The device reads the parameters.

Photo 3: After about 15 seconds it shows us the results.

Once the results are obtained, if we press the down arrow, we move on to READ ERROR CODES. We press OK.

If it has any, it will tell us the codes, if there are none stored it tells us that it does NOT have error codes.

ATTENTION, the message that it has no error codes can sometimes be false. These types of generic devices, when connected to the car, read in layers, which means that they read the surface layer, 'The main error codes that turn on the engine failure light' but there may be codes stored in the inner layer...

...or second layer, which the equipment is not able to access, these codes are read with a professional interface, 10 or 20 times more expensive than this basic interface, (This costs for example €20 or €25, the professional one costs €1000) or with the specific interface for the car make you have, for example.

We had no codes stored so it can't display any, if we had it would give us an indication of what the problem is with the car's engine. IT IS USELESS TO DELETE THE CODE WITHOUT WRITING IT DOWN FIRST AND WITHOUT REPAIRING THE VEHICLE.

Once the vehicle has been repaired, we proceed to DELETE THE ERROR CODE, in this case we did not have error codes, but as an example I'll proceed to delete them.

Down arrow, ERASE CODES, press OK.

It asks us if we also want to delete/reset the emissions diagnosis information, WE PRESS OK.

We should already have the ignition on, with the engine stopped, in any event, the computer reminds us that to clear the codes the engine must be stopped. We press OK.

I've noticed that on many occasions on the first error deletion with this interface, the device gives, DELETING FAILED, so the operation must be repeated.

To repeat a second time, we press GO BACK and repeat the operation.

ERASE CODES, press OK.

On this second case we'll see it tells us a series of checks we must perform (in fact we have already carried them out), engine stopped and contact activated. We press OK.

It tells us it is processing the ERASE CODES action.

It will give us the result again, this time it is satisfactory.

Photo 1: Other device options, language selection.

Photo 2: SEARCH DTC, It is a small summary of error codes, generic multi-brand, that the device has stored in memory.

The majority of Interfaces work more or less similarly, this is just an example so you can learn about another option for diagnosing and erasing codes from the vehicle's ECU.

I hope that this brief summary of what this interface does will help, and clarify your ideas about the function of these devices.