Break-thru: Reading ACD ECU with EcuFlash
Hmm, post #459 drawing is actually different what I have used, see link in post #458 as it works for sure. Maybe it is the same as sba's drawing but there is two of these floating around and other one does not work. Sorry I did not notice that earlier. If you need tuned acd rom, ask sba, he can help you.
With L-line what pin you mean as I have always used post #458 schema and seems to work?
K1 is rally, yes, but it is tarmac rally (http://www.ralliart.com/GRN/parts/vii.html, search: RA553831K1). It seems to be widely used also in cars equipped with ayc but you might be right that it does not control ayc, anyway that would be easy to proove by datalogging ayc solenoid current, have to do that later when I get possibility.
There is difference in ecu hardware between evo 7 and evo 8&9 so I have to disagree that you can run any ecu in any car, ayc is not only problem in my opinion. Or have you tested by running 7 ecu in later or vice versa? One known difference is related to ABS signal which is done via different pin in these ecu's, this difference is also in car wiring (check workshop manuals for both) so one signal will be missing if ecu does not match. This signal is readen/generated by using different processor pin so there has to be some difference also in firmware unless it is built so that both pins are used in sofware point of view for same purpose. I suspect it is not like that but no evidences for that
. Here is picture with highlights, picture from evo 9 ecu and these black rounded marks are differences seen with eyes compared to evo 7 ecu:
In my opinion, you are missing a wire from your drawings. You should find mine drawings in the first post. YOu need also L-line.
About ralliart files. C1 is also controlling AYC (only ralliart file doing this), K1 and K2 are for gravel rally and no AYC (group N car with mechanical rear diff). You can put any ecu in any car, but the AYC will run evenly like 50:50 or like a weak mechanical one.
But take care. K1 and K2 is very bad for streets and C1 gives you a very dangerous handling if you don't have lots of grip. With stock tires, stock suspension or close to stock, the car will enter in a drift when you will try to take a hard corner and stay there, completly differently that you would expect and when you lift you foot, it will go in other direction pretty aggresive. You should take caution. When i first tested C1, i was very close to smash the car twice in the same evening!!!
This is the reason i went in the pursuit of a better acd file.
About ralliart files. C1 is also controlling AYC (only ralliart file doing this), K1 and K2 are for gravel rally and no AYC (group N car with mechanical rear diff). You can put any ecu in any car, but the AYC will run evenly like 50:50 or like a weak mechanical one.
But take care. K1 and K2 is very bad for streets and C1 gives you a very dangerous handling if you don't have lots of grip. With stock tires, stock suspension or close to stock, the car will enter in a drift when you will try to take a hard corner and stay there, completly differently that you would expect and when you lift you foot, it will go in other direction pretty aggresive. You should take caution. When i first tested C1, i was very close to smash the car twice in the same evening!!!
This is the reason i went in the pursuit of a better acd file.
K1 is rally, yes, but it is tarmac rally (http://www.ralliart.com/GRN/parts/vii.html, search: RA553831K1). It seems to be widely used also in cars equipped with ayc but you might be right that it does not control ayc, anyway that would be easy to proove by datalogging ayc solenoid current, have to do that later when I get possibility.
There is difference in ecu hardware between evo 7 and evo 8&9 so I have to disagree that you can run any ecu in any car, ayc is not only problem in my opinion. Or have you tested by running 7 ecu in later or vice versa? One known difference is related to ABS signal which is done via different pin in these ecu's, this difference is also in car wiring (check workshop manuals for both) so one signal will be missing if ecu does not match. This signal is readen/generated by using different processor pin so there has to be some difference also in firmware unless it is built so that both pins are used in sofware point of view for same purpose. I suspect it is not like that but no evidences for that
. Here is picture with highlights, picture from evo 9 ecu and these black rounded marks are differences seen with eyes compared to evo 7 ecu:
schem in #458 and the the one i put up, is the exact same scheme.......
its just reverse, depending what way you look at the plug but its the same....
look again...
This is why i dont understand what ur saying....
And what line am i missing ??? as this is the only scheme i can see in the whole thread...
3x ground wires from the CIG LIGHTER ------- 2x wires to pins 4 &5 of the OBD2 Connector
1x wire to pin 22 of SMALL ACD CONNECTOR
3x power wires from the CIG LIGHTER --------- 1x wires to pin 16 of the OBD2 connector
1x wire to pin 11 of the SMALL ACD CONNECTOR
1x wire to pin 1 of the LARGE ACD CONNECTOR
1x green wire from pin 7 of the OBD2 Female connector to small ACD conenctor (pin 7)
1 x yellow wire from pin 15 of the LARGE ACD CONNECTOR to pin 6 of the TACTRIX 2.0 Flashing connector.......
What am i msising?
i cant log, or can read the ACD ECU?

its just reverse, depending what way you look at the plug but its the same....
look again...
This is why i dont understand what ur saying....
And what line am i missing ??? as this is the only scheme i can see in the whole thread...
3x ground wires from the CIG LIGHTER ------- 2x wires to pins 4 &5 of the OBD2 Connector
1x wire to pin 22 of SMALL ACD CONNECTOR
3x power wires from the CIG LIGHTER --------- 1x wires to pin 16 of the OBD2 connector
1x wire to pin 11 of the SMALL ACD CONNECTOR
1x wire to pin 1 of the LARGE ACD CONNECTOR
1x green wire from pin 7 of the OBD2 Female connector to small ACD conenctor (pin 7)
1 x yellow wire from pin 15 of the LARGE ACD CONNECTOR to pin 6 of the TACTRIX 2.0 Flashing connector.......
What am i msising?
i cant log, or can read the ACD ECU?

Last edited by Prolifik; Dec 16, 2011 at 06:21 PM.
^^^, yes it is the exact same schema, I copied it from Prolifik's original and flipped it over as I thought it was easier to see that way when making a harness up.
BTW thanks Prolifik for posting the original, very helpful.
BTW thanks Prolifik for posting the original, very helpful.
https://www.evolutionm.net/forums/8219274-post10.html
this is the picture.
Now, unfortunately, i don't have in my country to much Evo 7.
With K1 and K2, because they are for rally, rally cars doesn't have ABS (at least in my country) so you can use any kind of ecu with a rally car.
I never tried with a street Evo 7 to see if it is working or not.
L-line is for looging only! reading should be possible with just Vcc, ground, K-line and Flash voltage.
this is the picture.
Now, unfortunately, i don't have in my country to much Evo 7.
With K1 and K2, because they are for rally, rally cars doesn't have ABS (at least in my country) so you can use any kind of ecu with a rally car.
I never tried with a street Evo 7 to see if it is working or not.
L-line is for looging only! reading should be possible with just Vcc, ground, K-line and Flash voltage.
Last edited by sba; Dec 15, 2011 at 05:27 AM. Reason: i overlooked my internal notes once again
https://www.evolutionm.net/forums/8219274-post10.html
this is the picture.
Now, unfortunately, i don't have in my country to much Evo 7.
With K1 and K2, because they are for rally, rally cars doesn't have ABS (at least in my country) so you can use any kind of ecu with a rally car.
I never tried with a street Evo 7 to see if it is working or not.
L-line is for looging only! reading should be possible with just Vcc, ground, K-line and Flash voltage.
this is the picture.
Now, unfortunately, i don't have in my country to much Evo 7.
With K1 and K2, because they are for rally, rally cars doesn't have ABS (at least in my country) so you can use any kind of ecu with a rally car.
I never tried with a street Evo 7 to see if it is working or not.
L-line is for looging only! reading should be possible with just Vcc, ground, K-line and Flash voltage.

It is true that ABS is removed, maybe K1&K2 works because of that in rally cars but not for us street guys. Or maybe it "works" but will cause trouble in co-operation with abs system? Hmm, lots of those used in street cars, what is the truth...
i understand this stuff, i learn fast.... but id dare say half the reason this is taking so long to work out is because theres only a few people working on it....
Reason being --- Poor instructions most likely.
In my case all i need to do is read the rom off one ECU and transfer it to anothe seperate ECU....
Yet another question that needs to be clarified if someone that HAS DONE IT could confirm...
Step 1:
Make your harness following the scheme in post #468.
Step 2:
Remove your ACD ECU from the car
Step 3:
Connect your large and small ECU connectors from the harness u made to the ACD ECU
Step 4:
Connect your OBD2 FEMALE connector from the harness u made to the OPENPORT cable..... (1.3 or 2.0)
Step 5:
Connect the small plug off your OPENPORT cable to the flashing voltage wire from the harness u made.
Step 6:
Connect your OPENPORT CABLE USB conenction to your laptop.
step 7:
Provide 12volts to the harness (via cig lighter)
Now this is where i get confused... as nothing happens..... what is it im doing wrong?
step 8:
Open up ECU FLASH 1.43 beta
Step 9:
click read ROM
Then i get an error saying it cant read or something in the task info log section.
I use a tactrix 2.0 OP cable. All i want to do is read my rom, Back it up so i have a spare STOCK OEM map copy (incase something goes wrong)
Then go to my buddys car with a modified ralliart map and take his to put on mine.....
If someone could fill in where i have gone wrong it would be good.
Thankyou.
Reason being --- Poor instructions most likely.
In my case all i need to do is read the rom off one ECU and transfer it to anothe seperate ECU....
Yet another question that needs to be clarified if someone that HAS DONE IT could confirm...
Step 1:
Make your harness following the scheme in post #468.
Step 2:
Remove your ACD ECU from the car
Step 3:
Connect your large and small ECU connectors from the harness u made to the ACD ECU
Step 4:
Connect your OBD2 FEMALE connector from the harness u made to the OPENPORT cable..... (1.3 or 2.0)
Step 5:
Connect the small plug off your OPENPORT cable to the flashing voltage wire from the harness u made.
Step 6:
Connect your OPENPORT CABLE USB conenction to your laptop.
step 7:
Provide 12volts to the harness (via cig lighter)
Now this is where i get confused... as nothing happens..... what is it im doing wrong?
step 8:
Open up ECU FLASH 1.43 beta
Step 9:
click read ROM
Then i get an error saying it cant read or something in the task info log section.
I use a tactrix 2.0 OP cable. All i want to do is read my rom, Back it up so i have a spare STOCK OEM map copy (incase something goes wrong)
Then go to my buddys car with a modified ralliart map and take his to put on mine.....
If someone could fill in where i have gone wrong it would be good.
Thankyou.
Last edited by Prolifik; Dec 16, 2011 at 05:22 PM.
Prolifik, don't use pin15 in your picture.. that is for subaru L-Line
please update all your pictures to use Mitsubishi's OpenPort 1.3U/2.0 pin1.
its generally not called L-Line in Mitsubishi terms.. its called Diagnostics Init Line.
and its only used for EvoScan to datalog and read/clear ACD dtc.
pin1 Diagnostics line is not required for read/flash ACD using ecuflash.
yep use the latest Ecuflash version from the evoscan site. thats what we are all using. the version on evoscan site has no bluescreens. any older ecuflash and you run risks of blue screens. All tuners I know are using ecuflash v1.42.3252
please update all your pictures to use Mitsubishi's OpenPort 1.3U/2.0 pin1.
its generally not called L-Line in Mitsubishi terms.. its called Diagnostics Init Line.
and its only used for EvoScan to datalog and read/clear ACD dtc.
pin1 Diagnostics line is not required for read/flash ACD using ecuflash.
yep use the latest Ecuflash version from the evoscan site. thats what we are all using. the version on evoscan site has no bluescreens. any older ecuflash and you run risks of blue screens. All tuners I know are using ecuflash v1.42.3252




