I need to bump this thread up. How do we make sure the ecu is using the fuel temp sensor?

I'm using v7 88591715.

-Acree

 

If you wanted to confirm it, put the car in openloop and see what AFR it is at idle once it's stabilized. Disconnect the fuel temp sensor wire from the ECU. This should make the fuel temp readings be pegged either very cold or very hot. Recheck the AFR at idle in openloop. They should change by a good amount.

-Jamie

 

That's going to be a problem, as I can not get the car to run at all with SD. It's not an immobilizer issue. If I keep giving the car a little bit of gas, I can get it to stay alive indefinitely, but I'm inclined to think this is due to throttle tip in enrichment. I have tried all ranges of values on the RPM VE and MAP Sensor VE and Calibration tables from 20% to 200% of the original values. Nothing seems to make a difference.

Here's the kicker, if I leave the MAF plugged in, the car is just fine. As soon as I unplug the MAF, it dies immediately. If I start the car without the MAF plugged in, then it starts up and immediately dies unless I give it gas.

I believe somehow, somewhere in one of the scaling tables, my values or scalings are off.

-Acree

 

It wont idle warm even? You have it set for Fuel temp IAT or a GM IAT?

 

Subscribed!

 

I am running 88591715 TephraMod v7. The only option to set is "SD convert MAT to IAT (0x03 -> 0x0E)." I have tried starting the car with this setting both ways, and nothing seems to make a difference.

No matter what values are in either SD table, the car does the exact same thing where it's running extremely lean and dies. The only way to keep it alive is to consistently give it tiny amounts of gas.

Another weird issue, if I give it more than 20% throttle input, the car INSTANTLY dies, until I let off, and give it 2-5% throttle again.

-Acree

 

Exh cam sensor is starting to go. When it does log it and see if the IPW drops to 0. Does it do this even with the MAF plugged in?

Aaron

 

Nope. When I run the MAF tune (which I run daily), the car runs perfectly. It has to be something in the SD rom. It's a setup issue.

-Acree

 

When you have the fuel temp sensor selected, you have NOTHING at all being used from the stock MAF plug. Saying that it changed when you unplug it leads me to believe that it's still set to the GM IAT setting.

-Jamie

 

ECU Gurus, help me out here! (Aaron, specifically calling you out )

The local temperature is 62*F.

I just checked the voltages on Pin 62 (MAF - Air Temp Signal) and Pin 96 (Fuel Temp Sensor). They both came out at 2.33 volts.

This is how my rom is setup under SD, when it dies when the MAF is pulled.



Suggestions?

-Acree

 

Update:

Tonight's temperature is 69*F.

With the MAF plugged in:With the MAF unplugged:So this shows that the wires are connected to the correct pins on the ECU. This leaves only the possibility that something is not right in the rom, or my issue is not related to the temperature sensor. My next step is to disconnect the fuel temp sensor from Pin 96 and stick it in Pin 62, replacing the MAF temp sensor. If the SD rom works after that, it proves that the rom is not properly changing the ADC address.

The hunt continues!

-Acree

 

Keeping this bumping going because I need to get my logging going correctly to make sure this is not keeping my monitors from switching to passed even after about 200 miles, not even my Heated monitor.

I Do not have Option 1 for the Speed Density IAT option, and also not sure on this part in evoscan:

In evoscan, use MUT11 to log the actual air temp readings that will be used by the ECU in all of the maps when the car is running. MUT3A is the unscaled raw air temperature directly from the sensor itself. Here is the evoscan data if you do not have them already:


Are you referring to doing a right click on the items to data log, Edit data, And then the select vehicle would I choose the MUTII option under Vehicle? Or what?

 

Is SD Convert IAT to MAT (0x03 -> 0x0E) the same as what your referring to Jamie as SD IAT?

 

For anyone following, I found out this is correct.

What I can't figure out now is what does this section refer to:

In evoscan, use MUT11 to log the actual air temp readings that will be used by the ECU in all of the maps when the car is running. MUT3A is the unscaled raw air temperature directly from the sensor itself. Here is the evoscan data if you do not have them already:
Code:
<DataListItem DataLog="Y" Color="" Display="Air Temperature" LogReference="AirTemp" RequestID="3a" Eval="1.8*x+32" Unit="deg F" MetricEval="x" MetricUnit="deg C" ResponseBytes="1" GaugeMin="0" GaugeMax="190" ChartMin="0" ChartMax="190" ScalingFactor="1" Notes=" " Priority="1" Visible="False" />

<DataListItem DataLog="N" Color="" Display="MAF Air Temp Scaled" LogReference="MAFAirTempScaled" RequestID="11" Eval="1.8*x-40" Unit="deg F" MetricEval="x-40" MetricUnit="deg C" ResponseBytes="1" GaugeMin="-40" GaugeMax="260" ChartMin="-40" ChartMax="260" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

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

Not sure where I Select MUT11 over MUT3A, and not sure where I put that code in. If it is the edits you make when you right click on an item, then I can easily update that stuff, but what about the MUT11/MUT3A part.

 

Bump... working on this now and want to try for sticker these weekend.