TephraMod V7
#1201
I just setup 88590715 on my EVO IX and am getting a code:
P0037 - Heated oxygen sensor (rear) heater circuit low
I am running a wideband o2 sensor to the rear o2 sensor input, and have the rear o2 simulator enabled in the Tephra options.
Anyone run into this before? I was running the same physical setup with 5.10 (rear o2 simulator, OBD inspection pass mods) and never got a CEL.
P0037 - Heated oxygen sensor (rear) heater circuit low
I am running a wideband o2 sensor to the rear o2 sensor input, and have the rear o2 simulator enabled in the Tephra options.
Anyone run into this before? I was running the same physical setup with 5.10 (rear o2 simulator, OBD inspection pass mods) and never got a CEL.
#1202
WTF, it turns out its not using the launch maps. The rev-limiter isnt working either set it to 6k and spun 6.5k like butter. So neither re-limiters are working, its not using the launch maps. Any ideas? Im gonna have to switch back to my old rom so i dont over rev the motor and can launch. OH AND I tryed setting the stationary rev-limiter to 5k and still didnt work
#1205
I have problem with "wgdc = 100 till load=". I can easily find throtte position when i can see boost pulsations (0.1-0.2 bar) with constant throttle position. I can change load value and boost value will change similarly. I can fix it only when zeroed load volume.
And small question yet. Why this parametr is in "global" section? I replased its address to stock xml and open stock rom and i don't see the same number (200) there.
And small question yet. Why this parametr is in "global" section? I replased its address to stock xml and open stock rom and i don't see the same number (200) there.
#1206
I think my head is going to explode! Ok so I have read through this thread, searched it, ect. Maybe I am missing something. My car has the 94170008 rom on it and I know I am to use the 96530706 Tephra rom.I have changed over all my timing/fuel maps and immobilzer code. I am seeing in various maps on the rom I am seeing values listed in hex or raw format vs. an understandable number. I also see that the address' given for value lookups are different than on my 94170008 rom. Does this matter? I have seen where other people having it work for them, but I just want to have my bases covered.
#1208
I think my head is going to explode! Ok so I have read through this thread, searched it, ect. Maybe I am missing something. My car has the 94170008 rom on it and I know I am to use the 96530706 Tephra rom.I have changed over all my timing/fuel maps and immobilzer code. I am seeing in various maps on the rom I am seeing values listed in hex or raw format vs. an understandable number. I also see that the address' given for value lookups are different than on my 94170008 rom. Does this matter? I have seen where other people having it work for them, but I just want to have my bases covered.
Paul
#1209
WTF, it turns out its not using the launch maps. The rev-limiter isnt working either set it to 6k and spun 6.5k like butter. So neither re-limiters are working, its not using the launch maps. Any ideas? Im gonna have to switch back to my old rom so i dont over rev the motor and can launch. OH AND I tryed setting the stationary rev-limiter to 5k and still didnt work
Also, to eliminate a mechanical issue, reload the ROM the worked previously to see if your launch control and NLTS still works.
#1210
I simply changed ONLY the immobilizer code in the 96530706 ROM and flashed it over my 94170014 ROM. My '03 EVO started right up, idled pretty well, and I even drove a few blocks to the shopping center and back. And that was with 1,000cc injectors on a tank of E85. Obviously, I stayed out of boost, but the car did run surprisingly well with NO changes to any settings in the ROM whatsoever.
After I had proven that the ROM would in fact work in my car, only then did I copy over my injector settings, fuel map, and timing map. I changed nothing else. Then I test drove the car again. In fact I drove it for a few days.
Then I proceeded to address the issues that that were of concern to me, documented in this post.
Start simple. Make as few changes as possible. Flash and test. Then make a few more changes. Repeat. If you change everything at once and then have a hiccup, it can be much more challenging to sort it all out.
#1211
Well my old rom doesnt have NLTS but the stationary rev limiter works fine, ive switched between the two about 6 times no lol. Ill send you the rom asap, pm your email
Last edited by 3gEclipseTurbo; Dec 10, 2009 at 09:59 PM.
#1213
Hey guys. I'm on tephra v5.10 (EVO 8 2003). I would like to upgrade to v7. I'm using the JDM 3bar map sensor to log boost but I'm not using ecu control boost, I have an MBC. Is the Option 1 96530706 (v7) download good for me??? Are the JDM 3bar map sensor included in that rom or will I have to modify the file?
#1214
I have problem with "wgdc = 100 till load=". I can easily find throtte position when i can see boost pulsations (0.1-0.2 bar) with constant throttle position. I can change load value and boost value will change similarly. I can fix it only when zeroed load volume.
And small question yet. Why this parametr is in "global" section? I replased its address to stock xml and open stock rom and i don't see the same number (200) there.
And small question yet. Why this parametr is in "global" section? I replased its address to stock xml and open stock rom and i don't see the same number (200) there.
#1215
Just as a general note once I got around to testing the direct boost control I found the scalings for the kavlico were just a bit off.
I have played around with the scaling until i found one that matches my car at least with a 5 bar sensor. I then adjusted the formula to match up with the 3.5 Bar included in this post enjoy.
Major props to MrFred for providing the knowledge to crack this piece of the puzzle.
Notes:
PSI 8 bit scaling:
The scaling seems to be derrived out of
0-255 for X where
0 = 0 volts and
255 = 5 volts.
For some odd reason the scaling seems to be HALF of the sensors range so for a 3 bar sensor you only use 1.5 bar for the range and plug it into something like excel to get the answer for the formula.
Boost error:
This scaling is about error so offsets like with the kavlico sensor aren't important here only the amount of change in psi per value of X is important. The value is derived like the psi 8 bit but the range is 8 times less, I don't know why the engineers did it this way. Essentially you just take the constant part of your equation so in x*0.177 the 0.177 from the psi 8 bit scaling and devide it by 4 to get the correct scaling here.
Hope these notes prove useful for other people looking to add sensors to this rom.
I have played around with the scaling until i found one that matches my car at least with a 5 bar sensor. I then adjusted the formula to match up with the 3.5 Bar included in this post enjoy.
Major props to MrFred for providing the knowledge to crack this piece of the puzzle.
PHP Code:
<scaling name="PSIa8 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="24.9" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa8 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="37.3" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa16 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="34.3" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="PSIa16 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="51.4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico3.5barMAP" units="psi" toexpr="(x-128)*0.031" frexpr="(x/0.031)+128" format="%.1f" min="-4" max="4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico5barMAP" units="psi" toexpr="(x-128)*0.04425" frexpr="(x/0.04425)+128" format="%.1f" min="-5.7" max="5.7" inc="0.1" storagetype="uint16" endian="big"/>
PSI 8 bit scaling:
The scaling seems to be derrived out of
0-255 for X where
0 = 0 volts and
255 = 5 volts.
For some odd reason the scaling seems to be HALF of the sensors range so for a 3 bar sensor you only use 1.5 bar for the range and plug it into something like excel to get the answer for the formula.
Boost error:
This scaling is about error so offsets like with the kavlico sensor aren't important here only the amount of change in psi per value of X is important. The value is derived like the psi 8 bit but the range is 8 times less, I don't know why the engineers did it this way. Essentially you just take the constant part of your equation so in x*0.177 the 0.177 from the psi 8 bit scaling and devide it by 4 to get the correct scaling here.
Hope these notes prove useful for other people looking to add sensors to this rom.
Last edited by RoadSpike; Dec 14, 2009 at 10:49 PM.