I installed Wester's chip in my 2.8 turbo. Hooked up the laptop and ran WinALDL. Drove around for about 30 minutes. Problem I'm having is...I can't seem to get the BLM table to produce any numbers. All the fields remain empty, just see a green block where the rpm is currenty at. Raw data, sensor data all seem to work fine. Just can't see anything in the BLM table or the INT table for that matter. I'm totally lost now.

Are you going into closed loop?

On the bottom left there is a drop down list, something like, greatest, least, and average values. Play with that, I think it should solve your problem

stupid question but how do i know if its in closed loop or not?

Hmm....I noticed that when I plug in the aldl cable the engine revs higher, up about 100-200 rpms. Then when I pull it out the rpms drop back to normal. This is all without having the other end connected to the laptop yet. This combined with the fact that it wont go into closed loop leads me to suspect something might possibly be wrong with the cable I purchased. Anyone else experiencing this rpm thing?

A scan should always indicate a BLM number, even if the ECM is in open loop. If you are not getting a BLM reading, I would think that you are not reading the data stream correctly.

------------------
87GT 3.4 Turbo Best 0-60 5.2 seconds
http://www.turbochargerpower.com/turbo.htm

Thanks Dennis. Problem is...I get raw data and sensor data BUT absolutely nothing in the BLM , INT and O2 tabs. Those 3 tables remain blank empty fields, except for a green colored field indicating the current rpm.

The RPM increase is perfectly normal. In order to get most ECM's to transmit data you have to put it in ALDL mode. This is done by putting a 10K Ohm resistor between pin B of the ALDL port and Ground. When you plug the cable you bought from me into the panel mount connector it will complete this circuit and your ECM will be in ALDL mode. For some reason ALDL mode increases the idle ~100 RPM.

You have gotten some good advice in this thread already. I think your main problem is probably that you are not going into closed loop.

Couple questions for you.

• What temp thermostat are you running
  
• What temp fan
  
• What is the coolant temperature in WinALDL with your car fully warmed up
  
• Do you see any BLM, INT or O2 readings at all (Dash or Sensor Data tab) in WinALDL
  
• Have you played with the box in the lower left corner of the WinALDL window that 86GT3.4DOHC refered to
  
• Have you set up WinALDL according to these instructions https://www.fiero.nl/forum/Archives/Archive-000002/HTML/20030819-1-026777.html
  
• Have you read the WinALDL readme file
  

------------------

[This message has been edited by Jefrysuko (edited 08-21-2004).]

quote Originally posted by Jefrysuko: The RPM increase is perfectly normal. In order to get most ECM's to transmit data you have to put it in ALDL mode. This is done by putting a 10K Ohm resistor between pin B of the ALDL port and Ground. When you plug the cable you bought from me into the panel mount connector it will complete this circuit and your ECM will be in ALDL mode. For some reason ALDL mode increases the idle ~100 RPM. You have gotten some good advice in this thread already. I think your main problem is probably that you are not going into closed loop. Couple questions for you. What temp thermostat are you running What temp fan What is the coolant temperature in WinALDL with your car fully warmed up Do you see any BLM, INT or O2 readings at all (Dash or Sensor Data tab) in WinALDL Have you played with the box in the lower left corner of the WinALDL window that 86GT3.4DOHC refered to Have you set up WinALDL according to these instructions https://www.fiero.nl/forum/Archives/Archive-000002/HTML/20030819-1-026777.html Have you read the WinALDL readme file

The thermostat is the stock 195 but has yet to be changed for a 160 of which the new chip is programmed for along with the appropriate fan settings.

The coolant goes up to 235 i think.

Dash displays all info and data display show blm set at a permanent 128#.

The box in the lower left corner of the WinALDL window that 86GT3.4DOHC refered to seems to actually be on the right, correct? Anyway, I played with all the narrow and widest settings and got the O2 to populate in the 02 cells but still nothing for BLM and INT.

I changed the settings for TPS according to your instuctions but of course my no-closed looping and no BLM problem exists. Can the fact i'm using a 2 bar map have anything to do with it? Could it be because of the chip Wester programmed? Here are some screen shots I took today....

Thanks to all that helped so far

quote Originally posted by LordBoOsT: The box in the lower left corner of the WinALDL window that 86GT3.4DOHC refered to seems to actually be on the right, correct? Anyway, I played with all the narrow and widest settings and got the O2 to populate in the 02 cells but still nothing for BLM and INT. I changed the settings for TPS according to your instuctions but of course my no-closed looping and no BLM problem exists. Can the fact i'm using a 2 bar map have anything to do with it? Could it be because of the chip Wester programmed? Here are some screen shots I took today....

Yeah, your right the box we were talking about is actually on the right.

I really don't know about the 2 bar map sensor. I couldn't imagine how it would cause a problem but I have been wrong before. I am curious as to what you have done to allow you to use the 2 bar though. I thought that it would take more than a reprogramed chip to use the 1227170 ecm with a 2 bar. You are using a 1227170 right?

The chip definetly could be limiting closed loop operation or it could be another parameter which is out of spec. I have always thought about putting together some information about what the exact values each sensor need meet in order to acheive closed loop. Like many other things I never got around to putting anything on paper. Obviously the most important parameter is coolant temperature which is why I was asking so many questions about it. If you have a factory service manual I would look in it to help diagnose why you are not going into closed loop. Websters should also be able to inform you of anything they would have changed in relationship to closed loop, they have obviously made some changes to allow a lower temp thermostat.

The reason I asked if you had read the WinALDL readme file was because I thought it had a note about BLM, INT and closed loop. It indicated that you won't see anything in the BLM and INT tables until closed loop operation.

quote WinALDL readme.txt: BLM INT O2 These thee tabs all look the same. It is a grid with RPM and MAP axes. When the program is started all cells are emply. As you run the engine and the engine operating point travels over the chart the cells will start to populate with engine data. O2 will start to populate right away, but INT and BLM starts when the engine is in closed loop.

------------------

After speaking to Westers again abut the closed loop problem he did discover that the 02 sensor was programmed to be ignored in the chip he burned for me...oh well. Getting a new one in a few days. I'l post the results.

Btw Jefrysuko, in an effort to troubleshoot the problem I took apart the cable you made for me and of course it was fine but I wanted to mention how impressed I was with the quality of the assembly. Great work!

quote Originally posted by LordBoOsT: Btw Jefrysuko, in an effort to troubleshoot the problem I took apart the cable you made for me and of course it was fine but I wanted to mention how impressed I was with the quality of the assembly. Great work!

Thanks for the compliment. It took me a few tries to come up with the assembly method I use now but I think it turned out well.

Let us know when you get the new chip and how it turns out.

------------------

OK got the new chip and it now goes into closed loop after warm up! Let me know what you think of the results, thanks.