Hi,
I just want to know: Does anybody know where and how to mod the tables to make this work?
I want to used the "intercooler-waterlevelsensor-" or map sensor input to log my oiltemp.

I just relalized that the stock coolant sensor does fit perfectly in my oilfilterhousing, so I`m planing of using it.

My ecu have the 96530706-v7 tephra rom on it.
So I guess there is a map for translating the sensor input (of stock coolant sensor) into x (in °C because evoscan doesn`t need to convert it any more)

Where to find the stock coolant sensor map, duplicate it and link it to the right sensor and logger input?

Hope you guys can help me, its my first try to do something like this, so please don`t laugh... I`m sure tephra would do such a sing faster than I wrote this question

Thank you

 

i wouldn't do that if i were you.
a whopping load of functions is using coolant temperature for different actions, it's hard to predict how it turns out.

 

Sorry maybe it wasn`t clear enough what I tried to say (english isn`t exactly my kind of language )

I want to keep the stock coolanttempsensor as it is.
But install a second one in the oilfilterhousing and connect it to an unused input of the ecu.

just to be able to log watertemp and Oiltemp.

so I don`t want to mess with the orginal sensormaps in the ecu, just copy them to a free area and link the new sensorinput to the new map.

 

ah, if that's the case then as long as i remember most of the gauges temperature sensors are dual use, for both oil and coolant. so it might work for you. don't see why not.

 

You could probably use the fuel temp input or IAT (if using fuel temp for MAT on speed density).

You need to use a channel that is setup correctly for RTDs.

I like the idea. If you are on speed density, you could use the baro input to log a pressure sensor too. A little patch work and you could fire off a dash light for low oil pressure or overtemp.

 

I like the fuel temp input idea!
I`m not using speed destiny.

Is the fueltemp the same as the coolant temp? or is it needed to edit a map to get the signal converted right?

Nice that I`m not the only one who would like to log oiltemp

 

Haha not destiny, just density

Mmm maybe You mean the speed is Your destiny, so it's mine too

 

Ok, not only my english is bad, I`m also to dumb to type right.

I know the differents between both, it was just a simple typo

But thx for mention my misstake, so I maybe can work on not making it again

 

It was only joke. Your mistake has funny meaning, that's all

BTW. my english is not so good, I am from Poland so I can say, You are my neighbour

 

The engine coolant temp (ECT) is handled differently then the fuel temp. On the ECT, it first converts the raw ADC voltage into a linearized, non-signed value (index). It takes that value and then uses a second table to convert it into a signed value (0 to 0x7E are positive values, 0x80 to 0xFF are negative values). It is pretty much ECT in the ecu at that point, although a few other checks are made before it is written to the ECT ram variable.

On the fuel temp channel, on 96530006, the raw ADC value is written to FFFF8938 (can be logged through MUT87) and FFFF893A. The only other hit I got for either of those channels was in the ECU initialization section where the variables get copied over to other channels. The ram address it gets copied to isn't getting any hits either. As far as I can tell, on 96530006, no code changes would need to happen and the channel should be fine to log with just connecting the sensor to the fuel temp input. That assumes however that the pull-up resistor for the fuel temp channel is the same as the ECT channel.

Without writing a patch, you could use a scaling formula in Evoscan. Although, it is a parabolic and I'm not sure if EVOscan can handle non-linear equations? If it can, the following equation is a reasonably good curve fit.
y = -5E-07*x^3 + 0.0008*x^2 - 0.5132*x + 138.42


Another option is to linearize a small portion of the output. Using -0.5394*x + 145.75 will give you pretty good values from 80C to 125C, it will be WAY off below 80C though. Also, if you linearize the input as mentioned, you can log it on MUT87 as a 1-byte value. If you want to try and use the non-linear scaling, to read below 53C, you'll need to change the MUT table so you can log 2-byte values.

 

For anybody else interested, if you are on speed density, it would work better to use the original IAT input for MAT. Other wise some of the changes made in the SD patch will prevent this from working and you'll have to change some addresses.


Actually, this may have just given me an idea on how to handle some of the start up issues on the speed density patch.

 

Thank you very much 03whitegsr that should help alot

Are 96530006 and 96530706 identical?
But it will take me some time until I can say if that works or not... engine is still not ready to go in the car soon.

@TJung
I got the joke neighbour
I allready saw that you`r from Poland, PPL from america will never criticize us for using bad english. (they are to kind to do that)... so the first thing I did was having a look on your location details