TephraMOD V6 - testing!
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
cool 
not sure on the fuel consumption... what are the details?
do you have a MAT sensor? wired upto the fueltemp/sparetemp sensor input?
its not for SD, but hopefully jcsbanks can use it somehow...

not sure on the fuel consumption... what are the details?
do you have a MAT sensor? wired upto the fueltemp/sparetemp sensor input?
its not for SD, but hopefully jcsbanks can use it somehow...
Not easy to say. I'm monitoring the fuel consumption since a long time.
Before I had a mean value of 10.8l/100km.
Now I have around 9-9.5l/100km
Obviuosly this can depend on a lot of factors, but I also feel that the spooling come sooner than before: 2500rpm vs. 2900rpm.
so I though it might be because of the WGDC setting.
By the way, do you see any risk that the solenoid will break sooner because of that? If I understood correctly in a normal ECU SW the value is 0% until a certain load.
P.S: I have no special MAT sensor
Before I had a mean value of 10.8l/100km.
Now I have around 9-9.5l/100km
Obviuosly this can depend on a lot of factors, but I also feel that the spooling come sooner than before: 2500rpm vs. 2900rpm.
so I though it might be because of the WGDC setting.
By the way, do you see any risk that the solenoid will break sooner because of that? If I understood correctly in a normal ECU SW the value is 0% until a certain load.
P.S: I have no special MAT sensor
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
so your fuel eco got BETTER?
ie LESS litres per 100km
yeah boost will come on sooner as the WGDC is kept closed longer... but you need to give it enough TPS to really get boost anyways
'min load for boost control' is still in effect, so for <90load you will have 0WGDC anyways...
do you have any MAT sensor?
ie LESS litres per 100km
yeah boost will come on sooner as the WGDC is kept closed longer... but you need to give it enough TPS to really get boost anyways

'min load for boost control' is still in effect, so for <90load you will have 0WGDC anyways...
do you have any MAT sensor?
so your fuel eco got BETTER?
ie LESS litres per 100km
yeah boost will come on sooner as the WGDC is kept closed longer... but you need to give it enough TPS to really get boost anyways
'min load for boost control' is still in effect, so for <90load you will have 0WGDC anyways...
do you have any MAT sensor?
ie LESS litres per 100km
yeah boost will come on sooner as the WGDC is kept closed longer... but you need to give it enough TPS to really get boost anyways

'min load for boost control' is still in effect, so for <90load you will have 0WGDC anyways...
do you have any MAT sensor?
I usually monitor the fuel economy on a standard trip I do every weekend (~160km) to drive home. I'm also driving with the same style, so it's comparable.
I don't have any MAT sensor, although the car has the value for "air temperature". But I don't know where the sensor is.
BR
mlocatel
I will double check everything tonight. It was late, so I might have missed somethin. I noticed that there was 1 perihery bit change. I believe it was fde aa bit 14. was disabled (my rom), but enabled in the tephra rom. what is this bit? I have no idea whats what w/ the periphery bits, except a few the mrfred had pointed out. those were the faa bits... I know mrfred has updated his findings, but I couldnt open up the zip file...
TIA
No, I didnt pull the code. I Should have! Is there another method of pulling the code, besides going to autozone? This was my very first cell. I believe I read somewhere, that we have this function in evoscan, but wasnt functioning... has this been fixed? and if so, how do I go about it?
I will double check everything tonight. It was late, so I might have missed somethin. I noticed that there was 1 perihery bit change. I believe it was fde aa bit 14. was disabled (my rom), but enabled in the tephra rom. what is this bit? I have no idea whats what w/ the periphery bits, except a few the mrfred had pointed out. those were the faa bits... I know mrfred has updated his findings, but I couldnt open up the zip file...
TIA
I will double check everything tonight. It was late, so I might have missed somethin. I noticed that there was 1 perihery bit change. I believe it was fde aa bit 14. was disabled (my rom), but enabled in the tephra rom. what is this bit? I have no idea whats what w/ the periphery bits, except a few the mrfred had pointed out. those were the faa bits... I know mrfred has updated his findings, but I couldnt open up the zip file...
TIA
there is an no FDE - not sure which one you mean, I can see what is set on mine.
can you link me up to this "scantech" Seems like it would come in handy! I will verify which bit section it was, when I have my laptop infront of me. I'll try to search scantech...
Last edited by nonschlont; Mar 9, 2009 at 03:55 PM.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
apparently evoscan does DTC now... although I still use scantech.
its on aktivematrix.com
its pretty basic - and the initial connect is hard to get right (just ask if u need too)
its on aktivematrix.com
its pretty basic - and the initial connect is hard to get right (just ask if u need too)
Well jumped in the car after work, and cell... again, on my rom... weird??? The only thing I know I changed were the MUT's for the new logging parameters. 40, 41, 42, 43, 44 (which I cant get these new parameters to log) i added to the .xml and added new data items...
And the bit I was referring to earlier was (fea) bit. 14
I copy/pasted my old MUT table, and changed (fea) bit. 14 back to "0", and flashed the car, and the cell went away... IDK
wait: just thought of something... I only copy/pasted (00,01,02,03,04,05) into the (tephra) MUT table
Last edited by nonschlont; Mar 9, 2009 at 09:27 PM.



