Break-thru: Reading ACD ECU with EcuFlash
Feb 12, 2010, 04:40 AM
#61
Evolving Member
Thread Starter
I take my words back. This ecu doesn't know the rpm.
Is there any other program that EvoScan which can log MUT request and it is free to download? I want to start logging the MUTs to see which is which, but i don't have a program.
S.
Is there any other program that EvoScan which can log MUT request and it is free to download? I want to start logging the MUTs to see which is which, but i don't have a program.
S.
Feb 12, 2010, 04:47 AM
#62
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 2 Likes
on
2 Posts
Not really every other application uses only 0x1 init sequence.
Maybe Ceddy can do something about his MHI scan
, but i am sure he will not do it without the ACD ECU.
Maybe Ceddy can do something about his MHI scan
, but i am sure he will not do it without the ACD ECU.
Feb 12, 2010, 05:06 AM
#63
Evolving Member
Thread Starter
I'm determined to finish down this bastard.
Feb 12, 2010, 08:37 AM
#65
.Can anyone give me instructions on how to pull the ACD rom from the OBD port?
Also, Ceddy... just tell me how and I should have your logs within a day. All I need are the tools to do it, and I'm only short on the knowledge part right now
. 1.3 EvoScan cable and 2.0 tactrix available on a USDM IX.
Last edited by fostytou; Feb 12, 2010 at 08:42 AM.
Feb 12, 2010, 09:05 AM
#66
Evolving Member
Join Date: Apr 2008
Location: Reading, PA
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
Under Select ECU, choose AYC.
Select all items to log, by checking them. (Log all)
Start DataLogger.
A very short log in parking lot will be fine. A hard turn and speed at least 10 mph is all I need.
This ecu doesn't know the rpm.
Wheel Freq / Wheel Time = Wheel Speed
Wheel Speed - Wheel Speed Old = Wheel Acceleration
Wheel Acceleration - Wheel Acceleration Old = Wheel Rate of Acceleration
You have all this x4 wheels, and you also have the fastest for each one.
And they go to great lengths for accuracy, and use 32 bit precision. (H8 is 16 bit ecu)
So just for the wheels there are 50+ items.
Last edited by Ceddy; Feb 12, 2010 at 09:19 AM.
Feb 12, 2010, 09:18 AM
#68
Evolving Member
Thread Starter
Ceddy, please help me here. From this morning, i'm trying to log this ecu.
All that i've got is:
Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.10.272
Info: Battery 14.007V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Error: No Response from Vehicle ECU
Info: Datalogger Ended.
I have the ecu on the bench. If i can make him work with a logger, i can see exactly where every input goes. I will put current on tps input, on all 4 wheels, all the inputs that i know.
And another question: i see in evoscan that it has already the requests for AYC ecu. Why can we take them like good directly?
S.
All that i've got is:
Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.10.272
Info: Battery 14.007V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Error: No Response from Vehicle ECU
Info: Datalogger Ended.
I have the ecu on the bench. If i can make him work with a logger, i can see exactly where every input goes. I will put current on tps input, on all 4 wheels, all the inputs that i know.
And another question: i see in evoscan that it has already the requests for AYC ecu. Why can we take them like good directly?
S.
Feb 12, 2010, 09:35 AM
#69
Evolving Member
Join Date: Apr 2008
Location: Reading, PA
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
I'm not sure how to get AYC logging to work, I never tried it. Think I read something about pin 9 needs to be removed or added.
Feb 12, 2010, 09:49 AM
#70
Mitsubishi AYC/ABS support use theEvoScan 1.3U cables without Pin9, if your 1.3U cable has pin9,
just remove it with pliers (pin9 is for subaru support, see tips and tricks below)
just remove it with pliers (pin9 is for subaru support, see tips and tricks below)
How to get Mitsubishi AYC/ABS support from an OpenPort 1.3U cable.
Step 1) Pin1 must be linked to pin15.
Early OpenPort cables did not have Pin15 linked to pin1(check with a multimeter continuity test) to see if its connected.
a) No pin1 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
b) Pin1 is connected to Pin4/5 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
c) Pin1 is connected to Pin15 on the OpenPort cable. Cable is AYC/ABS ready.
Step 2) Try logging with EvoScan v2.6 or later. Select Mitsubishi, and select ECU to "AYC" or "ABS", Press start datalogger.
If it doesn't connect, then perhaps you have pin9 interference. Goto Step 3.
Step 3) Subaru 2002 vehicles use Pin 9 for reflash support on the openport 1.3Universal cables, but it interferes with the Mitsubishi AYC/ABS ecus on some
Mitsubishi obdII ports, so you can either break pin9 off the OpenPort Cable, or put a switch on pin9 from the obdII port.
Step 1) Pin1 must be linked to pin15.
Early OpenPort cables did not have Pin15 linked to pin1(check with a multimeter continuity test) to see if its connected.
a) No pin1 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
b) Pin1 is connected to Pin4/5 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
c) Pin1 is connected to Pin15 on the OpenPort cable. Cable is AYC/ABS ready.
Step 2) Try logging with EvoScan v2.6 or later. Select Mitsubishi, and select ECU to "AYC" or "ABS", Press start datalogger.
If it doesn't connect, then perhaps you have pin9 interference. Goto Step 3.
Step 3) Subaru 2002 vehicles use Pin 9 for reflash support on the openport 1.3Universal cables, but it interferes with the Mitsubishi AYC/ABS ecus on some
Mitsubishi obdII ports, so you can either break pin9 off the OpenPort Cable, or put a switch on pin9 from the obdII port.
Feb 12, 2010, 09:58 AM
#71
Its been awhile since I looked into the ACD stuff (I deleted 2 years ago) but as I recall the major control functions will be
Lock vs Steering angle
Wheel speed (it determines slip, and allowable differences)
Engagement curve- Pump idle pressure vs time to 16bar (full pressure)
The individual tables (the 50+ wheel speed) you reference are not going to be needed since they are set, the other three tables we really need are just the mode tables really. The one big table is going to be the main table that controls when it gets to 16bar vs speed or time. The smaller three are access tables.
Lock vs Steering angle
Wheel speed (it determines slip, and allowable differences)
Engagement curve- Pump idle pressure vs time to 16bar (full pressure)
The individual tables (the 50+ wheel speed) you reference are not going to be needed since they are set, the other three tables we really need are just the mode tables really. The one big table is going to be the main table that controls when it gets to 16bar vs speed or time. The smaller three are access tables.
Feb 12, 2010, 10:13 AM
#72
Evolving Member
iTrader: (12)
Join Date: Jul 2007
Location: SoCal
Posts: 168
Likes: 0
Received 0 Likes
on
0 Posts
Don't know if this means anything or been posted previously, but Gruppe-S in Socal flashes ACD ecu's.
Here is a post on SoCalEvo:
http://www.socalevo.net/index.php?op...&topic=74905.0
-Will
Here is a post on SoCalEvo:
http://www.socalevo.net/index.php?op...&topic=74905.0
-Will
Feb 12, 2010, 10:29 AM
#73
Evolving Member
Thread Starter
Finally, i can log the mother-fu...er!!!!
It needs the L-line for the INIT signal and it is working only with OP 1.3U. This is pretty ugly, it can be read/write only with OP 2.0 and log with OP 1.3U.
It is for sure that the evoscan definitions are not good. Not even the voltage is ok.
I post a log from the ECU on the bench with nothing attached to him.
Now i will start attaching thing to see what i got.
Tell me what do you think is the most important
S.
It needs the L-line for the INIT signal and it is working only with OP 1.3U. This is pretty ugly, it can be read/write only with OP 2.0 and log with OP 1.3U.
It is for sure that the evoscan definitions are not good. Not even the voltage is ok.
I post a log from the ECU on the bench with nothing attached to him.
Now i will start attaching thing to see what i got.
Tell me what do you think is the most important
S.
Feb 12, 2010, 10:58 AM
#74
Evolving Member
Join Date: Apr 2008
Location: Reading, PA
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
That sucks that the EvoScan definitions are incorrect, I think they are for a Evo4 ACD or something.
I can try to make a definition file for it tonight, but its really hard not knowing what anything is.
You can use a AAA or watch battery to test inputs, the voltage and current are low enough that is shouldn't damage anything.
If you could correlate, a input to a RequestId, it would be very helpful.
Like Pin 9(TPS) changes RequestId 13.
I can try to make a definition file for it tonight, but its really hard not knowing what anything is.
You can use a AAA or watch battery to test inputs, the voltage and current are low enough that is shouldn't damage anything.
If you could correlate, a input to a RequestId, it would be very helpful.
Like Pin 9(TPS) changes RequestId 13.
Finally, i can log the mother-fu...er!!!!
It needs the L-line for the INIT signal and it is working only with OP 1.3U. This is pretty ugly, it can be read/write only with OP 2.0 and log with OP 1.3U.
It is for sure that the evoscan definitions are not good. Not even the voltage is ok.
I post a log from the ECU on the bench with nothing attached to him.
Now i will start attaching thing to see what i got.
Tell me what do you think is the most important
S.
It needs the L-line for the INIT signal and it is working only with OP 1.3U. This is pretty ugly, it can be read/write only with OP 2.0 and log with OP 1.3U.
It is for sure that the evoscan definitions are not good. Not even the voltage is ok.
I post a log from the ECU on the bench with nothing attached to him.
Now i will start attaching thing to see what i got.
Tell me what do you think is the most important
S.
Feb 12, 2010, 11:02 AM
#75
Evolving Member
Thread Starter
That sucks that the EvoScan definitions are incorrect, I think they are for a Evo4 ACD or something.
I can try to make a definition file for it tonight, but its really hard not knowing what anything is.
You can use a AAA or watch battery to test inputs, the voltage and current are low enough that is shouldn't damage anything.
If you could correlate, a input to a RequestId, it would be very helpful.
Like Pin 9(TPS) changes RequestId 13.
I can try to make a definition file for it tonight, but its really hard not knowing what anything is.
You can use a AAA or watch battery to test inputs, the voltage and current are low enough that is shouldn't damage anything.
If you could correlate, a input to a RequestId, it would be very helpful.
Like Pin 9(TPS) changes RequestId 13.
Also, i'm thinking how can we test outputs after.
S.
