TephraMod V7
#2656
Is it really using? I have never changed baudrate from tephra roms or evoscan and all versions I have used (9055, 9626, 9653 and 8858) have worked fine. My car also had 8884 rom as original and 8858 works just fine. I have tested faster rate so I know what you mean, it does not work if these dont match (rom&evoscan).
#2657
I have never changed the evoscan rate. I will test it. But it is very strange behavior. Evoscan is connected to ECU. Some counters works fine. For example throttle position.
But much bigger problem for me is the ECU behavior. Especially the alternative map switching. I have used the same map as primary map (just for testing purpose) but on alternative car run without boost control (more than 2bar) engine is twitching. M/T Temp light on dashboard does not work. Do you have the same experience? Thank you for any help.
But much bigger problem for me is the ECU behavior. Especially the alternative map switching. I have used the same map as primary map (just for testing purpose) but on alternative car run without boost control (more than 2bar) engine is twitching. M/T Temp light on dashboard does not work. Do you have the same experience? Thank you for any help.
#2659
I'm trying to find a table for the 96530706 ROM. It would be called something like "Closed Loop Startup Delay". It's the amount of time after an engine start that the ECU waits for to enter closed loop. It's not the same as "Min Coolant Temp for Closed Loop", but the X-axis would be Coolant Temp.
The problem I'm having is the ECU is entering closed loop before the O2 sensor has started to respond, so the STFT starts going very positive to try to get the cold sensor to respond, which of course it won't until it warms up.
I found this but it's for an Evo 6 TME, any idea if there's something like this for the 96530006 or can I use it in that ROM?
<table name="Closed Loop Startup Delay" category="Fuel" address="11b5a" type="2D" level="2" scaling="DelayTime">
<table name="Engine Temp" address="2c944" type="X Axis" elements="8" scaling="Temp"/>
</table>
<scaling name="DelayTime" units="sec" toexpr="x/128*60" frexpr="x/60*128" format="%.1f" min="0" max="120" inc="1" storagetype="uint8" endian="big"/>
The problem I'm having is the ECU is entering closed loop before the O2 sensor has started to respond, so the STFT starts going very positive to try to get the cold sensor to respond, which of course it won't until it warms up.
I found this but it's for an Evo 6 TME, any idea if there's something like this for the 96530006 or can I use it in that ROM?
<table name="Closed Loop Startup Delay" category="Fuel" address="11b5a" type="2D" level="2" scaling="DelayTime">
<table name="Engine Temp" address="2c944" type="X Axis" elements="8" scaling="Temp"/>
</table>
<scaling name="DelayTime" units="sec" toexpr="x/128*60" frexpr="x/60*128" format="%.1f" min="0" max="120" inc="1" storagetype="uint8" endian="big"/>
#2660
Ok, so for some reason I can't log any fuel tables. No LTFT, STFT, etc. If I flash back to a stock rom it works fine. Any thoughts.
I'm using the 88590715 (USDM IX Rom).
Anyone have any ideas on this? Makes it impossible to try and tune with no fuel trim feedback.
I'm using the 88590715 (USDM IX Rom).
Anyone have any ideas on this? Makes it impossible to try and tune with no fuel trim feedback.
Last edited by wazzelby; Jul 17, 2012 at 03:24 PM.
#2661
Hi, I really need some help here. I am on 88590715 Tephra V7, and I can't get my "Load1Byte" to work, and I have of course made sure that the MUT41 = 0x840B and also have the correct RequestiID="41" in my Evoscan data.xml as well. But it only captures "0" all across whereas my LoadMut2Byte is working fine.
It is not a big deal since I have the Load2Byte but it really puzzles me and would like to see what could possibly be wrong or I missed something??
I also have the same issue with the "WGDC Corr" where my evoscan only captures "0" all across where I believe some correction should have happened. Again, i have double checked all the addresses (6EE3 and 6EE9), wha else could be wrong??
It is not a big deal since I have the Load2Byte but it really puzzles me and would like to see what could possibly be wrong or I missed something??
I also have the same issue with the "WGDC Corr" where my evoscan only captures "0" all across where I believe some correction should have happened. Again, i have double checked all the addresses (6EE3 and 6EE9), wha else could be wrong??
#2662
Couple of quick questions. Running this on a USDM IX,
when I open the rom in ecuflash under the ROM info it has the wrong information:
Year - 2007
Transmission: 6MT
My car is a 2006, 5spd. Does this matter?
Also, when logging in Evoscan, the "power torque car profile" section when looking at the log says the rom is for: 01_LANCER_EVO7-RalliArt_EDM_90550001.hex using ROM 90550001?? How do I change this??
when I open the rom in ecuflash under the ROM info it has the wrong information:
Year - 2007
Transmission: 6MT
My car is a 2006, 5spd. Does this matter?
Also, when logging in Evoscan, the "power torque car profile" section when looking at the log says the rom is for: 01_LANCER_EVO7-RalliArt_EDM_90550001.hex using ROM 90550001?? How do I change this??
Last edited by wazzelby; Jul 1, 2012 at 09:22 AM.
#2663
Couple of quick questions. Running this on a USDM IX,
when I open the rom in ecuflash under the ROM info it has the wrong information:
Year - 2007
Transmission: 6MT
My car is a 2006, 5spd. Does this matter?
Also, when logging in Evoscan, the "power torque car profile" section when looking at the log says the rom is for: 01_LANCER_EVO7-RalliArt_EDM_90550001.hex using ROM 90550001?? How do I change this??
when I open the rom in ecuflash under the ROM info it has the wrong information:
Year - 2007
Transmission: 6MT
My car is a 2006, 5spd. Does this matter?
Also, when logging in Evoscan, the "power torque car profile" section when looking at the log says the rom is for: 01_LANCER_EVO7-RalliArt_EDM_90550001.hex using ROM 90550001?? How do I change this??
#2664
Any tips on how I can troubleshoot these issues? I removed the PIN 9 in my OD cable and would that be the cause at all?
Hi, I really need some help here. I am on 88590715 Tephra V7, and I can't get my "Load1Byte" to work, and I have of course made sure that the MUT41 = 0x840B and also have the correct RequestiID="41" in my Evoscan data.xml as well. But it only captures "0" all across whereas my LoadMut2Byte is working fine.
It is not a big deal since I have the Load2Byte but it really puzzles me and would like to see what could possibly be wrong or I missed something??
I also have the same issue with the "WGDC Corr" where my evoscan only captures "0" all across where I believe some correction should have happened. Again, i have double checked all the addresses (6EE3 and 6EE9), wha else could be wrong??
It is not a big deal since I have the Load2Byte but it really puzzles me and would like to see what could possibly be wrong or I missed something??
I also have the same issue with the "WGDC Corr" where my evoscan only captures "0" all across where I believe some correction should have happened. Again, i have double checked all the addresses (6EE3 and 6EE9), wha else could be wrong??
#2665
You have a Rom that supports 1 byte, right? Look in your ROM and see what the 1 byte scaling factor is (if it's not there, it doesn't support it).
#2666
Hi
I'm a new member from Italy . I'd like to thanks all the people on this forum because I learned and I'm still learning a lot.
my stock map is 88840017
I'd like to try this mod but I don't know how to change this bits:
8884001X - You can use 88580714 with no problems. Just ensure you copy your immobiliser AND 0xFFA bits (yes 0xFFA) otherwise the immobiliser wont work
Can someone help me?
Thanks in advance
I'm a new member from Italy . I'd like to thanks all the people on this forum because I learned and I'm still learning a lot.
my stock map is 88840017
I'd like to try this mod but I don't know how to change this bits:
8884001X - You can use 88580714 with no problems. Just ensure you copy your immobiliser AND 0xFFA bits (yes 0xFFA) otherwise the immobiliser wont work
Can someone help me?
Thanks in advance
#2667
Anyone notice this pre patched rom is set up for OMNI 4BAR with boost control functions setup for JDM 3bar?
Option 3 - Thanks to recompile, scheides, and bigric09 88591715 (v7 + Mods + Speed Density) - Download | Mirror
Option 3 - Thanks to recompile, scheides, and bigric09 88591715 (v7 + Mods + Speed Density) - Download | Mirror
- Setup for JDM MAP and PSI based boost control (mrfred)
- WGDC Correction Interval set to 1 (Stock = 10)
- Max Total Upward WGDC Correction @ 100% TPS set to 0 (Stock = 10)
- EGR System Disabled (mrfred)
- Max Timing Retard set to -20 degrees (tephra)
- FAA bit.10 disabled ("weird unknown" timing pull at cruise)
- FAA bit.09 disabled (cat-warmup ignition retard)
- FBA bit.00 disabled (lean spool)
- FCA bit.09 disabled (EGR Test)
- OBD Inspection set to Pass all tests (acamus)
- Rear O2 Heater patch applied (mrfred)
- Fuel Cut Load Limit x2 and set to 300 (mrfred)
- Speed Density Implemented
#2668
Wow..... Well I am the dumbest guy on here and have clearly no clue how to use this on my Evo 9. I have the taxtrix cable and a new map for my break in tune on my built Evo 9 but am having issues installing it. I already connected it to my OBD2 port and got a copy of my old map to save. My issue is that when I try to use ecuflash and upload my new map it gives me errors and will not let me. My tuner stated that I need to download Tephra and install it in the Evo folder on ecuflash. Im computer savvy but there are 7 versions to what I can see. There are so many warnings that I'm scared to touch it now. My tuner stated that there is no specific version but it seems to make a difference from what I am reading. I put over $6k in this over the last 3 months and dont care to blow it up again. It blew due to overheating and damaging a piston but with my new MAP engine I need to upload this new ecu map that was sent to me. Can anyone help me???? Thanks guys
#2669
Wow..... Well I am the dumbest guy on here and have clearly no clue how to use this on my Evo 9. I have the taxtrix cable and a new map for my break in tune on my built Evo 9 but am having issues installing it. I already connected it to my OBD2 port and got a copy of my old map to save. My issue is that when I try to use ecuflash and upload my new map it gives me errors and will not let me. My tuner stated that I need to download Tephra and install it in the Evo folder on ecuflash. Im computer savvy but there are 7 versions to what I can see. There are so many warnings that I'm scared to touch it now. My tuner stated that there is no specific version but it seems to make a difference from what I am reading. I put over $6k in this over the last 3 months and dont care to blow it up again. It blew due to overheating and damaging a piston but with my new MAP engine I need to upload this new ecu map that was sent to me. Can anyone help me???? Thanks guys