My 1997 gmc sonoma truck,it has a V6,4.3 liter V-Tec failed the MIL/Check Engine Light Test due to a Warning Lamp Failure. Due to a OBD Fault Code:P1406 manufacturer specific code

Disconnect your battery. Touch the two battery cables together. (make sure they are not in contact while hooked to the battery). Then leave the battery disconnected for 10mins. Connect battery again. This should reset the computer. Sometimes lights my be on until you drive the vehicle a short distance, then it resets.

Have the fault codes read and that will point to the faults that caused the problem

google toyota avalon forums go there and join forum than post question
or just google youre question like you did here

Blow it up and buy a real car.

Basically, it means the check engine warning light didn't light up when it should. Perhaps a burned out bulb?

Every vehicle has a "system check" that happens every time you turn the key on. Most people don't know it is happening right before thier eyes. So if you go out and get into your car in the morning and you turn the key to "on" but then don't go the rest of the way to the "start" position there are several warning lights on. The check engine light is one of them. All the system is doing is running power through the light to show it is functional.

It doesn't mean there is something wrong, it is just showing that an error "can" be displayed if an error existed by the light being on. Try it next time. Turn the key on but dont start the engine. If your check engine light is off, then that is what they stated in the report.

The person running the test is an idiot. The OBDII test instrument is not capable of determining if there is a warning lamp failure. It is probably guessing based on voltage level, but lamp resistance does normally vary. The test is supposed to be done visually. Take it to someone else, and they will probably be more competent and pass your car.

Hello
Does the light ever come on while you are driving the vehicle? It is possible that the vehicle does not trigger the code on the key cycle when vehicle is connected to the OBDII scan tool (a cycle is the time from when a vehicle is started to the time the vehicle is turned off) you should however most of the time be able to check a vehicles trouble code history to see what may be turning the light on
Good luck
Chris

A SCAN TOOL WILL TELL YOU WHAT CYLINDERS MISFIRING.THATS QUICK WAY TO CHECK.CHANGE FUEL FILTER AND CLEAN FUEL INJECTORS BY FILLING GAS TANK AND PUTTING A BOTTLE SEA FOAM IN TANK.MISFIRING LACK OF POWER AND STUMBLING ON ACCELERATION MOST TIME CLOGGED FUEL INJECTORS WILL CAUSE THOSE PROBLEMS.

First the fault codes,
U110C is No Fuel Level Bus Message
U0155 is No Cluster Bus Message.
Unfortunatly you have to be able to communicate with the instrument cluster with your scanner to diagnoise and I do not think an aftermarket scanner can do this.

Some vehicles require very specific drive cycles (called "drive traces" if you perform them on a road simulator or dyno) to activate certain self-checks like the catalyst and EVAP monitors. As a general rule, doing some stop-and-go driving around town at speeds up to about 30 mph followed by five to seven minutes of steady 55 mph highway speed driving will usually set most or all of the monitors. Consequently, if you're checking an OBD II system and discover that one or more of the monitors have not run, it may be necessary to test drive the vehicle to set the remaining monitors.

You should talk to a good emission tec, if this is not throwing a code, it is hard to say if that one of the components could be bad. O2,pump,convert, HeO2, every part of the emission system.

With a 1000 miles, and doing what is says above just before the test, and ending driving at the test
should be plenty. If it is not, you will have to have each emission part checked, or when the computer
is plugged in it might show a code that did not trip dash light.