Evo anti-lag ECU disassembly
JB, Youngsyr was not the one who ran without the SAS hardware, the French guy with the Evo7 was. That's all I know. We'll work as a team and get this working for USDM IX Evo's. But you need to get caught up first
yep as soon as I get it running I will post a vid for ya,
SAS= Secondary Air System,
wouldnt mind but a lot of people have removed the SAS system on their evos over here as it was thought it was useless,
its been incorporated in the evo since 1994 in the Evo 4,
I am sure locating the hardware will be pretty easy,
as for the ECU I am pretty sure the USDM ECU can Handle the SAS system,
its wired into pin 53 of the 4 plug ecu,
as for the ACD its controlled by a seperate ecu, called the 4WD ECU, located behind the centre console, so changing out your USDM ecu for a JDM one should be no major issue,
some pics of the workshop manual for SAS
http://i91.photobucket.com/albums/k2...ary/EvoSAS.jpg
SAS= Secondary Air System,
wouldnt mind but a lot of people have removed the SAS system on their evos over here as it was thought it was useless,
its been incorporated in the evo since 1994 in the Evo 4,
I am sure locating the hardware will be pretty easy,
as for the ECU I am pretty sure the USDM ECU can Handle the SAS system,
its wired into pin 53 of the 4 plug ecu,
as for the ACD its controlled by a seperate ecu, called the 4WD ECU, located behind the centre console, so changing out your USDM ecu for a JDM one should be no major issue,
some pics of the workshop manual for SAS
http://i91.photobucket.com/albums/k2...ary/EvoSAS.jpg
1994 would be the Evo II. 1996 would be the Evo IV...
.
And I'll take the other! YGPM Youngsyr.
I proved (2) incorrect. I tested this by adding an another table with a random address value and the ROM's I tried to load could not use create tables with these addresses. My thinking is that the reason the XML code loaded in the first place was that these addresses are already referenced in the USDM ECU, but just not showing. I am using and edited 88590013.
I proved (2) incorrect. I tested this by adding an another table with a random address value and the ROM's I tried to load could not use create tables with these addresses. My thinking is that the reason the XML code loaded in the first place was that these addresses are already referenced in the USDM ECU, but just not showing. I am using and edited 88590013.
Actually you haven't proven anything wrong unless you get it to run. By putting the address in the xml that proves the table is there which is exactly what MrFred said. Getting it to execute while the car is running would prove him wrong...until then...
codgi, I think you misinterpret. The table can only be created if the address for it exists. It must exist since I copied the code to a T and the the proper options showed up. When I edited one of the entires to an address that was not listed, ECUFlash would load only what is there and an error would pop up for the pseudo entry. So my thought pattern tells me that these tables must exist since they can be created.
I seem to have gone back to work and come back only more confused.
SO..
Youngsyr,
To recap exactly what are the conditions that you have set to make the SAS work without the SAS hardware? No specifics if you cant share them, but I missed the connection between the SAS software and then a normal stationary rev limiter I think. .25 bar between shifts or just at a standstill with nothing else going on?
JB
SO..
Youngsyr,
To recap exactly what are the conditions that you have set to make the SAS work without the SAS hardware? No specifics if you cant share them, but I missed the connection between the SAS software and then a normal stationary rev limiter I think. .25 bar between shifts or just at a standstill with nothing else going on?
JB
Currently I only have pops and bangs when the car is stationary and I rev the car to the rev limit (set at 5,500 rpm). When the engine hits the rev limiter you get the pops and bangs and my boost gauge reads 0.25 bar whilst the car is standing still.
I haven't been able to make the car pop and bang whilst moving at all yet, either on gear change or violent lift off during WOT.
I have been sent some more aggressive parameters for the ALS settings, so I'll try those tonight/over the weekend.
It's definitely possible to get ALS working on the JDMs as there are several JDM IXs (including JohnBanks, the OP of this thread) with it running with exactly the same tables as we've now got on the JDM VIIs and VIIIs.
On another note, I'm making good progress with the SAS hardware.
Je peux pas voir ton photo mais les numeros doivent etre 0.0 pour l'ALS inactive, si tu as des "X"s par tout, le code xml pour ton ROM ID sera faux. Si tu as les Xs, il faut verifier que tu as bien copie le xml code des exemples deja donnes.
Pour avoir l'ALS il faut changer les numeros de 0.0 a 0.9 etc, mais nous sont en train d'essayer les numeros differents pour trouver les numeros exacts pour une bonne systems ALS.
Je peux pas voir ton photo mais les numeros doivent etre 0.0 pour l'ALS inactive, si tu as des "X"s par tout, le code xml pour ton ROM ID sera faux. Si tu as les Xs, il faut verifier que tu as bien copie le xml code des exemples deja donnes.
Pour avoir l'ALS il faut changer les numeros de 0.0 a 0.9 etc, mais nous sont en train d'essayer les numeros differents pour trouver les numeros exacts pour une bonne systems ALS.
Pour avoir l'ALS il faut changer les numeros de 0.0 a 0.9 etc, mais nous sont en train d'essayer les numeros differents pour trouver les numeros exacts pour une bonne systems ALS.

in English
Je peux pas voir ton photo mais les numeros doivent etre 0.0 pour l'ALS inactive, si tu as des "X"s par tout, le code xml pour ton ROM ID sera faux. Si tu as les Xs, il faut verifier que tu as bien copie le xml code des exemples deja donnes.
Pour avoir l'ALS il faut changer les numeros de 0.0 a 0.9 etc, mais nous sont en train d'essayer les numeros differents pour trouver les numeros exacts pour une bonne systems ALS.
Pour avoir l'ALS il faut changer les numeros de 0.0 a 0.9 etc, mais nous sont en train d'essayer les numeros differents pour trouver les numeros exacts pour une bonne systems ALS.

c est les RPM que j arrive pas a trouver l adresse
the time code 0.0 is good
the RPM is not good address
OK chaps, first the obligatory warning/disclaimer, which is even more relevant in this case because I am a newbie ECUFlasher and don't understand all of the basics, let alone the vast majority of this advanced stuff.
So, whatever you do to your rom/xml etc is your responsibility. Be very careful with the ALS settings as they can very easily kill your turbo and damage your car etc.
With that out of the way here's my settings that a UK tuner of my friend put together. THIS IS NOT THE ONE THAT I TESTED LAST NIGHT, in fact I haven't tested this one at all yet, but I trust the guy who put it together, and I will be trying it over the weekend.
[Edit: the tables read top row first, left to right, then bottom row, left to right]
So, whatever you do to your rom/xml etc is your responsibility. Be very careful with the ALS settings as they can very easily kill your turbo and damage your car etc.
With that out of the way here's my settings that a UK tuner of my friend put together. THIS IS NOT THE ONE THAT I TESTED LAST NIGHT, in fact I haven't tested this one at all yet, but I trust the guy who put it together, and I will be trying it over the weekend.
[Edit: the tables read top row first, left to right, then bottom row, left to right]
Last edited by Youngsyr; Mar 14, 2008 at 08:13 AM.








