TephraMod V7
#2641
Is there a way to increase the maximum Hz value in the MAF Scaling/MAF Compensation tables? Currently the highest breakpoint is 1610hz. Changing these doesn't seem to work, typing any other value makes that point default to a Hz of 0. I've tried searching this problem but not finding any solutions. A max of 1610hz isn't nearly high enough for 95% of the cars on this forum.
#2643
I pegged my MAF scaling value to read higher if the above IS the case and it didn't read higher so I will answer my own question with a "no".
I did however figure a good math value based solely on MAF to read load, since my 1 byte logs 10+% less than actual.
It is:
Loaded = (MAF hz/RPM*0.01*81572)
as volts (which log the same):
Loaded = (MAF volt/RPM*0.01*30418251)
In my logworks math I use MC(loadedHZ) = (SSI_4_4/SSI_4_1*.01*81572)
I did however figure a good math value based solely on MAF to read load, since my 1 byte logs 10+% less than actual.
It is:
Loaded = (MAF hz/RPM*0.01*81572)
as volts (which log the same):
Loaded = (MAF volt/RPM*0.01*30418251)
In my logworks math I use MC(loadedHZ) = (SSI_4_4/SSI_4_1*.01*81572)
#2644
Change the scalling in the xml to this corrected one, you can them make any changes you wish
<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="x*64/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>
<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="x*64/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>
#2645
Thanks! That seemed to do it, along with changing the "MAFScaling" table to max=5000 (it was set to 495 for some reason).
#2646
EvocentriK,
I use the 9626 rom and have noticed that it has two 2byte to 1 byte tables...
One up the top under tephraMod-v7 which you should be using and the other one is under Mods section which you should not be using... I guess it does depend on your xml file and the addresses you use for those tables.
I had exactly the same problem with loads/ timing after reinstalling my evoscan until I changed evoscan to 1.3 to match ecuflash.
I use the 9626 rom and have noticed that it has two 2byte to 1 byte tables...
One up the top under tephraMod-v7 which you should be using and the other one is under Mods section which you should not be using... I guess it does depend on your xml file and the addresses you use for those tables.
I had exactly the same problem with loads/ timing after reinstalling my evoscan until I changed evoscan to 1.3 to match ecuflash.
#2647
I'm using 90550001 v7 and now I only get wastegate pressure but my boost goes back to normal when I got back to v5. Turbo and bcs are stock. My gear based BWGDC and BDEL load tables are zeroed out, would this be my issue, or are those table meant for those upgraded for ECU based boost control.
Last edited by nudge120; May 7, 2012 at 11:00 PM.
#2648
V7 is load and gear based boost. there is a mod/patch to make it pressure based (psi/bar).
is there any development still being done to these ROMs/XMLs?
or now that tephra is on an EvoX he has stopped all development for these?
cheers
is there any development still being done to these ROMs/XMLs?
or now that tephra is on an EvoX he has stopped all development for these?
cheers
#2649
I'm using 90550001 v7 and now I only get wastegate pressure but my boost goes back to normal when I got back to v5. Turbo and bcs are stock. My gear based BWGDC and BDEL load tables are zeroed out, would this be my issue, or are those table meant for those upgraded for ECU based boost control.
#2651
Problem with V7 88580714 running on 88840016 ECU
Hi
I have just implemented V7 to my EVO 9. It is EDM with 88840016. I have following issue with this MOD ROM.
1. M/T light does not work
2. Evoscan logging does not work (just some metric like RPM is 0)
3. Alternative maps do not work. Car is plucking and boost is without correction. I used the same maps as primary.
Do you have somebody the same experience? Is there any solution for this?
Thank you
Jaroslav
I have just implemented V7 to my EVO 9. It is EDM with 88840016. I have following issue with this MOD ROM.
1. M/T light does not work
2. Evoscan logging does not work (just some metric like RPM is 0)
3. Alternative maps do not work. Car is plucking and boost is without correction. I used the same maps as primary.
Do you have somebody the same experience? Is there any solution for this?
Thank you
Jaroslav
#2652
I'm using 90550001 v7 and now I only get wastegate pressure but my boost goes back to normal when I got back to v5. Turbo and bcs are stock. My gear based BWGDC and BDEL load tables are zeroed out, would this be my issue, or are those table meant for those upgraded for ECU based boost control.
#2655
Hi
I have just implemented V7 to my EVO 9. It is EDM with 88840016. I have following issue with this MOD ROM.
1. M/T light does not work
2. Evoscan logging does not work (just some metric like RPM is 0)
3. Alternative maps do not work. Car is plucking and boost is without correction. I used the same maps as primary.
Do you have somebody the same experience? Is there any solution for this?
Thank you
Jaroslav
I have just implemented V7 to my EVO 9. It is EDM with 88840016. I have following issue with this MOD ROM.
1. M/T light does not work
2. Evoscan logging does not work (just some metric like RPM is 0)
3. Alternative maps do not work. Car is plucking and boost is without correction. I used the same maps as primary.
Do you have somebody the same experience? Is there any solution for this?
Thank you
Jaroslav
2. you probably forgot to change the baudrate to 62500 in EvoScan
tephra mods use a faster logging baudrate. well its configurable in the rom table itself actually. only use 15625 or 62500.