shogun
04-20-2009, 10:45 PM
I am asking for your help on behalf of Ellen. :)
I have a check engine light that goes on intermittently; when I checked for a code with the peak tool I got "A0"--Lambda Control. Is this the same as the Lambda sensor/02 sensor, or is the lambda control referring to something else?
I think that the 02 sensor is alright , as it is relatively new and was checked at a smog shop very recently; they said that it was responding well.
Thanks. 1988 735i Ellen
Have searched a bit but cannot find more details, what I found/know:
online user manual:
http://www.sixtek.fi/pdf/B100_Manual.pdf
no further explanations there too.
In general, 1988 model has the problem that the PEAKE or also other diagnostic tools do not give much information. Just 25 only codes, a 1994 model has more info to offer. But that was in 1987/8 still in the early days of OBD.
Could be also some prob with MAF? Faulse Air?
BTW, I just found the manual also on Peake's website for the
http://www.peakeresearch.com/manuals/FCX3-manual%201.0%20NA.pdf
and this just also copied from Peake's site, just for info to make life with the tool easier:
Technical Issues: the R5/FCX code tool
Problem 1: Error message "E" or E-10 /E-11
Occasionally the R5/FCX will flash "E" when an attempt is made to read codes or reset the check engine light. "E" means the car is not responding to the tool: This happens when the data line (also called "diagnostic bus") in the car is "hung" or disabled. In order for the tool to access information from the car it must first "hand shake," like your computer modem does with your ISP. To properly handshake there must be a clear data line to communicate on. Imagine a household with multiple phones or modems all sharing the same phone line, well, the BMW is similar; it has multiple control units (transmission, ABS, traction control, etc...) If one of these units is tying up the communication line (like a teenage girl on the household phone) all other devices on the line are unable to communicate. This happens quite often, but try the following procedures in the order given to determine the nature of your problem.
Things To Try:
1.) Insertion Depth
Check the insertion depth of the R5/fcx. If it is not fully inserted the unit will not work. See page 11 of the user manual.
2.) Reversing the power-up sequence
Plug in the R5/FCX in first, THEN turning on the ignition key. This is the opposite of the routine specified by the manual and the tool label. This procedure has proven very effective on some cars.
3.) Pin 19
Observe that pin 19 of your diagnostic connector is not recessed. A number of models had pin 19 improperly installed. BMW service bulletin 12 05 94. (Please do not Contact Peake Research for service bulletins. Contact Central Letter Shop, BMWs authorized publication vendor 1-800-695-0079 9:00am - 4:30pm EST) While you're looking at the diag port go ahead and check out all the pins.
4.) Cycle power
Plug in tool
Cycle the ignition key on and off two or three times (do not start engine)
5.) Other warning lights
Observe that no other malfunction indicator lights are on. Often a malfunctioning module (i.e. transmission, ABS traction control, etc...) can hang the diagnostic bus (see above)
6.) Power resetting of all modules
a.) Disconnect the main car battery.
b.) Activate the emergency flasher lights (this will fully drain all power from all ECUs) wait 5 minutes
c.) Reconnect the main battery and try the tool again.
7.) Module Troubleshooting
If you suspect a particular module is malfunctioning or damaged, you may wish to consult repair documentation for the car and attempt to isolate the problem by removing the module from the diagnostic bus. WARNING: This procedure is for qualified mechanics only.
ABS service bulletin 34 01 96: BMW circulated a service bulletin and low cost repair advice detailing the malfunction of the ABS unit wiring which caused diagnostic bus problems on a large number of BMWs. This is often the problem on BMWs built prior to 10/1994 that are getting the "E" message on the R5/fcx code tool. (Please do not Contact Peake Research for service bulletins. Contact Central Letter Shop, BMWs authorized publication vendor 1-800-695-0079, or 973-808-8339, 9:00am - 4:30pm EST)
8.) The Dealer
Visit your local BMW dealership. The R5/Fcx will not serve it's intended purpose if the diagnostic bus is impaired by a malfunctioning control module. If one of the modules is inhibiting communications it is necessary to visit a BMW dealer or qualified repair facility to diagnose and fix/replace the bad module.
Problem 2: Check Engine light is on but no code found.
Transient errors in other controllers (i.e. transmission control, ABS traction control, etc...) can cause the check-engine light to come on and stay on until reset. There are also situations where the Check Engine light circuit is bad, causing it to come on in the absence of faults. The R5/FCX is only capable of reading and resetting codes in the DME (the engine control unit.) If the check engine light stays off after you reset it you can be reasonably sure that it was caused by a transient ECU fault. If you have a recurring problem that the R5/fcx will not display a code for, it may be necessary to visit a BMW service center.
Problem 3: Display is not working.
Every unit goes through two display tests before being shipped to you, so it is unlikely that the display is dead. The display on the R5/FCX is not bright enough to be read in direct sunlight or strong indirect sunlight. Cup your hand around the display or move the vehicle to a darker area. It is also possible that the tool is not recieving power powered due to a.) blown fuse, or b.) insufficient insertion into the diagnostic connector (see page 11 of users manual) or recessed pins in the BMW diagnostic connector port. See above problem 1, section 3 "Pin 19".
Problem 4: Not working on 1999 or 2000 V8 BMW.
Your tool is probably the old R5/FCX, the predecessor to the R5/FCX-II. The R5/FCX (Built from December 1999 to August 2003) is not capable of supporting the 1999/2000 V8 BMWs (740, 540). For compatibility with these cars you must purchase the R5/FCX-II.
I have a check engine light that goes on intermittently; when I checked for a code with the peak tool I got "A0"--Lambda Control. Is this the same as the Lambda sensor/02 sensor, or is the lambda control referring to something else?
I think that the 02 sensor is alright , as it is relatively new and was checked at a smog shop very recently; they said that it was responding well.
Thanks. 1988 735i Ellen
Have searched a bit but cannot find more details, what I found/know:
online user manual:
http://www.sixtek.fi/pdf/B100_Manual.pdf
no further explanations there too.
In general, 1988 model has the problem that the PEAKE or also other diagnostic tools do not give much information. Just 25 only codes, a 1994 model has more info to offer. But that was in 1987/8 still in the early days of OBD.
Could be also some prob with MAF? Faulse Air?
BTW, I just found the manual also on Peake's website for the
http://www.peakeresearch.com/manuals/FCX3-manual%201.0%20NA.pdf
and this just also copied from Peake's site, just for info to make life with the tool easier:
Technical Issues: the R5/FCX code tool
Problem 1: Error message "E" or E-10 /E-11
Occasionally the R5/FCX will flash "E" when an attempt is made to read codes or reset the check engine light. "E" means the car is not responding to the tool: This happens when the data line (also called "diagnostic bus") in the car is "hung" or disabled. In order for the tool to access information from the car it must first "hand shake," like your computer modem does with your ISP. To properly handshake there must be a clear data line to communicate on. Imagine a household with multiple phones or modems all sharing the same phone line, well, the BMW is similar; it has multiple control units (transmission, ABS, traction control, etc...) If one of these units is tying up the communication line (like a teenage girl on the household phone) all other devices on the line are unable to communicate. This happens quite often, but try the following procedures in the order given to determine the nature of your problem.
Things To Try:
1.) Insertion Depth
Check the insertion depth of the R5/fcx. If it is not fully inserted the unit will not work. See page 11 of the user manual.
2.) Reversing the power-up sequence
Plug in the R5/FCX in first, THEN turning on the ignition key. This is the opposite of the routine specified by the manual and the tool label. This procedure has proven very effective on some cars.
3.) Pin 19
Observe that pin 19 of your diagnostic connector is not recessed. A number of models had pin 19 improperly installed. BMW service bulletin 12 05 94. (Please do not Contact Peake Research for service bulletins. Contact Central Letter Shop, BMWs authorized publication vendor 1-800-695-0079 9:00am - 4:30pm EST) While you're looking at the diag port go ahead and check out all the pins.
4.) Cycle power
Plug in tool
Cycle the ignition key on and off two or three times (do not start engine)
5.) Other warning lights
Observe that no other malfunction indicator lights are on. Often a malfunctioning module (i.e. transmission, ABS traction control, etc...) can hang the diagnostic bus (see above)
6.) Power resetting of all modules
a.) Disconnect the main car battery.
b.) Activate the emergency flasher lights (this will fully drain all power from all ECUs) wait 5 minutes
c.) Reconnect the main battery and try the tool again.
7.) Module Troubleshooting
If you suspect a particular module is malfunctioning or damaged, you may wish to consult repair documentation for the car and attempt to isolate the problem by removing the module from the diagnostic bus. WARNING: This procedure is for qualified mechanics only.
ABS service bulletin 34 01 96: BMW circulated a service bulletin and low cost repair advice detailing the malfunction of the ABS unit wiring which caused diagnostic bus problems on a large number of BMWs. This is often the problem on BMWs built prior to 10/1994 that are getting the "E" message on the R5/fcx code tool. (Please do not Contact Peake Research for service bulletins. Contact Central Letter Shop, BMWs authorized publication vendor 1-800-695-0079, or 973-808-8339, 9:00am - 4:30pm EST)
8.) The Dealer
Visit your local BMW dealership. The R5/Fcx will not serve it's intended purpose if the diagnostic bus is impaired by a malfunctioning control module. If one of the modules is inhibiting communications it is necessary to visit a BMW dealer or qualified repair facility to diagnose and fix/replace the bad module.
Problem 2: Check Engine light is on but no code found.
Transient errors in other controllers (i.e. transmission control, ABS traction control, etc...) can cause the check-engine light to come on and stay on until reset. There are also situations where the Check Engine light circuit is bad, causing it to come on in the absence of faults. The R5/FCX is only capable of reading and resetting codes in the DME (the engine control unit.) If the check engine light stays off after you reset it you can be reasonably sure that it was caused by a transient ECU fault. If you have a recurring problem that the R5/fcx will not display a code for, it may be necessary to visit a BMW service center.
Problem 3: Display is not working.
Every unit goes through two display tests before being shipped to you, so it is unlikely that the display is dead. The display on the R5/FCX is not bright enough to be read in direct sunlight or strong indirect sunlight. Cup your hand around the display or move the vehicle to a darker area. It is also possible that the tool is not recieving power powered due to a.) blown fuse, or b.) insufficient insertion into the diagnostic connector (see page 11 of users manual) or recessed pins in the BMW diagnostic connector port. See above problem 1, section 3 "Pin 19".
Problem 4: Not working on 1999 or 2000 V8 BMW.
Your tool is probably the old R5/FCX, the predecessor to the R5/FCX-II. The R5/FCX (Built from December 1999 to August 2003) is not capable of supporting the 1999/2000 V8 BMWs (740, 540). For compatibility with these cars you must purchase the R5/FCX-II.