HOW-To 96260009 JDM8MR to 96530706
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
i tried 96532706 and it doesnt feel like what 96530706 is doing. however i cant get more than 10psi boost and 150 load...these same settings get me 255 load and around 22-23psi on 96260009 & 97250001 roms. could someone help me if i email them my evoscan log and rom? maybe im missing something basic?? im having gsc s1 cams installed monday and the car dyno tuned tuesday but i wanted to used v7, if i cant get it to work then i'll stick with 96260009 i guess 
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
im quite new to ecuflash and i hope im posting this in the right section! i dont know if anyone is having the same problem as i am but i thought i'd put it out there maybe you guy's know whats going on with this rom on my evo. i'm having trouble with boost and i find from about 3500rpm up my boost is fluctuating as i accelerate. i logged it and evoscan shows my load rising and then dropping, wgdc also going from like 90 to 0 suddenly then back up etc. i dont know whats going on i feel like im riding a rubber band, lol!! all the settings that i could change over from 9725001 are the same and even tephra 96260009 works fine. i installed my 3port (tactrix) in interrupt mode and its plugged into the grey connector (other solenoid plug isn't connected) but it did the same thing when i had both 2 ports connected. i dont know whats going on, can someone give me some advise pls, id really appreciate it!!
Evolved Member
Joined: Mar 2008
Posts: 1,392
Likes: 2
From: uk
any more known working inputs with this rom so i can log boost?
i'm already using mut 3c pin 73. it is for lc1 logging which i have setup and is working but want to log boost to so need another known working input mut and pin
i'm already using mut 3c pin 73. it is for lc1 logging which i have setup and is working but want to log boost to so need another known working input mut and pin
Last edited by leecavturbo; Jan 18, 2010 at 12:25 AM.
from another thread, following are some spare ADC inputs. i use mut 38 and 39 for boost and WBO2 on my car and i believe all 3 plug ecus this will work
ECU pin-----MUT request-------Details
92------------38-----------------Non-utilised MDP input; 5v = 255
73 ------------3C------------non utilised rear 02; havent checked input
-------------------------------but expect maybe 1v max scale
64-------------83------------spare input;5v = 255
93--------------39-------------spare input;5v = 255
96--------------87------------ spare input with pull up; 0v = 255
ECU pin-----MUT request-------Details
92------------38-----------------Non-utilised MDP input; 5v = 255
73 ------------3C------------non utilised rear 02; havent checked input
-------------------------------but expect maybe 1v max scale
64-------------83------------spare input;5v = 255
93--------------39-------------spare input;5v = 255
96--------------87------------ spare input with pull up; 0v = 255
i tried 96532706 and it doesnt feel like what 96530706 is doing. however i cant get more than 10psi boost and 150 load...these same settings get me 255 load and around 22-23psi on 96260009 & 97250001 roms. could someone help me if i email them my evoscan log and rom? maybe im missing something basic?? im having gsc s1 cams installed monday and the car dyno tuned tuesday but i wanted to used v7, if i cant get it to work then i'll stick with 96260009 i guess
the other roms were set to 1.2
either change it back to 1.2
or change the evoscan scaling for load1b to 1.3*x
Evolved Member
Joined: Mar 2008
Posts: 1,392
Likes: 2
From: uk
from another thread, following are some spare ADC inputs. i use mut 38 and 39 for boost and WBO2 on my car and i believe all 3 plug ecus this will work
ECU pin-----MUT request-------Details
92------------38-----------------Non-utilised MDP input; 5v = 255
73 ------------3C------------non utilised rear 02; havent checked input
-------------------------------but expect maybe 1v max scale
64-------------83------------spare input;5v = 255
93--------------39-------------spare input;5v = 255
96--------------87------------ spare input with pull up; 0v = 255
ECU pin-----MUT request-------Details
92------------38-----------------Non-utilised MDP input; 5v = 255
73 ------------3C------------non utilised rear 02; havent checked input
-------------------------------but expect maybe 1v max scale
64-------------83------------spare input;5v = 255
93--------------39-------------spare input;5v = 255
96--------------87------------ spare input with pull up; 0v = 255
Evolved Member
Joined: Mar 2008
Posts: 1,392
Likes: 2
From: uk
no special changes, just the normal xml... best is to put some output to the pin and see if when logging mut 39 if the value changes from 0.... if so then all good. it worked on my 9626 8MR and the guy who gave me the values had a 8GSR JDM.
just make sure u get the correct pin.
just make sure u get the correct pin.
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
not sure but I was hitting really low loads with it set at 1.2,
but yes your wdgc's would have something to do with it if you're using ecu based control, I have an AVCR do that wasn't my problem.
if you want to use psi based boost control you need to change "variable for boost control" to 0x8932. is the boost gauge or map sensor hitting the same psi?
If you have a p0500 code DEFINATELY get rid of that, there is a "max wgdc during fault setting" which is defaulted at 62.5%, so you will not hit full boost unless you either get rid of the fault OR change the wdgc fault setting to 100%. I would recommend getting rid of the fault though. Are you able to log speed? If not that would throw your gear based boost control right off also. You can turn off the fault by toggling periphery FDA bit 6.
You on the evo oz forums mate?
but yes your wdgc's would have something to do with it if you're using ecu based control, I have an AVCR do that wasn't my problem.
if you want to use psi based boost control you need to change "variable for boost control" to 0x8932. is the boost gauge or map sensor hitting the same psi?
If you have a p0500 code DEFINATELY get rid of that, there is a "max wgdc during fault setting" which is defaulted at 62.5%, so you will not hit full boost unless you either get rid of the fault OR change the wdgc fault setting to 100%. I would recommend getting rid of the fault though. Are you able to log speed? If not that would throw your gear based boost control right off also. You can turn off the fault by toggling periphery FDA bit 6.
You on the evo oz forums mate?
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
not sure but I was hitting really low loads with it set at 1.2,
but yes your wdgc's would have something to do with it if you're using ecu based control, I have an AVCR do that wasn't my problem.
if you want to use psi based boost control you need to change "variable for boost control" to 0x8932. is the boost gauge or map sensor hitting the same psi?
If you have a p0500 code DEFINATELY get rid of that, there is a "max wgdc during fault setting" which is defaulted at 62.5%, so you will not hit full boost unless you either get rid of the fault OR change the wdgc fault setting to 100%. I would recommend getting rid of the fault though. Are you able to log speed? If not that would throw your gear based boost control right off also. You can turn off the fault by toggling periphery FDA bit 6.
You on the evo oz forums mate?
but yes your wdgc's would have something to do with it if you're using ecu based control, I have an AVCR do that wasn't my problem.
if you want to use psi based boost control you need to change "variable for boost control" to 0x8932. is the boost gauge or map sensor hitting the same psi?
If you have a p0500 code DEFINATELY get rid of that, there is a "max wgdc during fault setting" which is defaulted at 62.5%, so you will not hit full boost unless you either get rid of the fault OR change the wdgc fault setting to 100%. I would recommend getting rid of the fault though. Are you able to log speed? If not that would throw your gear based boost control right off also. You can turn off the fault by toggling periphery FDA bit 6.
You on the evo oz forums mate?
No cant log speed at all mate and thats when i started investigating and found the P0500 code. Im currently using 97250001 because that works just fine (so does v5.1), even with the code, stumped! No bones about it i need to get that fixed first, then i can play with v7. Not even Mitsu dealership had any idea about what could be wrong with the speed sensor, abs, tacho, speedo, everthing seems to work and no CEL. i've had FDA bit 6 set to 0 (thats off, yes?) but still shows up in OBDII faults, even after ecu reset. hehe, hate having an abnormal problem no one has any idea about, living in Perth doesnt help either!
ps. boost gauge in v7 showed about 13-14psi, 25psi in 97250001 with same wgdc, bdel, bc, tbec...
Last edited by veszett; Jan 22, 2010 at 02:08 AM.
well mine is set to 0 also, so maybe try setting it to 1. As I said before wastegate max is 65% during fault so that could be causing your low boost. try change that to 100% if you can't get rid of the code. Even after you turn it off it'll be there for a while unless you clear it using evoscan.
you should find some local help on evo oz forums.
you should find some local help on evo oz forums.
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
well mine is set to 0 also, so maybe try setting it to 1. As I said before wastegate max is 65% during fault so that could be causing your low boost. try change that to 100% if you can't get rid of the code. Even after you turn it off it'll be there for a while unless you clear it using evoscan.
you should find some local help on evo oz forums.
you should find some local help on evo oz forums.
here's the tread https://www.evolutionm.net/forums/ec...ode-fault.html
Evolving Member
Joined: Nov 2009
Posts: 190
Likes: 1
From: WA
Stat Rev Limiter
