If that ralliart program was leaked it would be KILLER. It looks incredibly capable and informative.

 

I saw Motec ACD ECU and GEMS ACD ECU. None of this has more than 2 maps for every program. What is in that movie is a log session for a rally car where you have logging on every sensor, Gs, steering angle, every ABS wheel sensor. So you can see how the car is acting on that surface and what do you have to change inside the map to make the car work like you like.

I play with some Motec Evo IX for high climbing and it is a different story than OEM ECU. First of all, you know every aspect of what is the ecu doing.

Inside the ACD ECU you have to find 6 maps regarding the pressure inside the ACD system. The axle variants are: rpm, throttle position and load. Also the breaking moments get there. Everything else we should find out.

 

Here is that KAPs ACD controller from that video:

http://eng.kaps.cz/news-kaps/acd_com...ancer-934.html

(and in not-english)
http://www.kaps-transmissions.com/ne...ancer-921.html

Looks pretty badass. I can't find any info on pricing anywhere...

 

VERY cool. I was pretty interested in what software that actually was, thanks for checking it out

 

Late to discussion...read first couple pages and last couple
If you guys are trying to read/ write this through the OBDII port, it will result in failure. The tool is mitsubishi propriety type tool that can do the read write. if you are looking to flash the ACD then a completely separate device is needed. IMO it looks similar to what Garage HRS uses to do the custom flashes on your stock ACD ecu.

for the AYC guys. Most if not all ACD flashes just turn off the AYC.

I have 3 acd ecus. Ralliart gravel, Garage HRS tarmac/circuit and another which will be nameless. I have driven with the AP boss one as well...

me and a buddy have looked extensively at this and really we can barely even read the tunes...even found this japanese guy online who created a device to hack the evo 6 acd. I cant remember the extensive searches we did...but Renasas and a bunh of other shiz came up.

in response to the Do luck unit. I dont believe that unit adjusts for steering input, brake, hand brake etc...
It is a piggy back unit which I dont believe is a good thing...
and yes the idea seems good but personally I wouldnt want to eff with it. maybe for drag it would be good.

I will be watching this thread, in case something comes up. But the ACD is the bread and butter of the evo...it is quite amazing how that little box can alter how the car feels.

I would check out Gruppe-S offering.

 

very interesting

any news?

 

I have done quick disassembly

processor H8/500
loading offset 0x10000
interrupt vectors 0x10000-0x10140
data segment 0x12000-0x14000
code segment 0x14000-0x1B13c

ADC Read subroutine @ 0x1a190
ADC Poll subroutine @ 0x14EC3

 

someone please figure this one out, its the next level! i would love to get a disassembly of the hole thing, cause if there was a way the flash it i would!

 

Nice to hear this. And you will go further deep with your research?
I'd love to have a xml for the ACD ecu.

 

It is kind of hard without the ECU itself.
I can probably find communication protocol from disassembly only.

 

 

It seams thatit has the same ecu like the evo 6.5. Do you think it worth trying to read it with EcuFlash like the Evo 6.5?

Can i break something?

 

I would try it with engine ECU unplugged and 5-6 protocol
I believe Init code 3 will pick the ACD ECU.

 

For the moment i will try directly on the bench. After that i will try on the car. The problem on the car is that i don't know if the read/write voltage goes to this ecu also.

 

I tried to read it with evo 5,6 and evo 6.5 and i got these:

[15:22:39.203] EcuFlash Version 1.42.2720
[15:22:39.203] OS Version Windows XP
[15:22:39.203] Qt Version 4.5.2
[15:22:39.234] 57 memory models read.
[15:22:39.234] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[15:22:39.515] 344 ROM metadata models scanned.
[15:22:39.515] checksum module "subarudbw" loaded.
[15:22:39.515] checksum module "mitsucan" loaded.
[15:22:39.515] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[15:22:39.515] flashing tool "wrx02" loaded.
[15:22:39.515] flashing tool "wrx04" loaded.
[15:22:39.515] flashing tool "sti04" loaded.
[15:22:39.515] flashing tool "sti05" loaded.
[15:22:39.515] flashing tool "mitsukernel" loaded.
[15:22:39.515] flashing tool "mitsukernelocp" loaded.
[15:22:39.515] flashing tool "mitsubootloader" loaded.
[15:22:39.515] flashing tool "shbootmode" loaded.
[15:22:39.515] flashing tool "shaudmode" loaded.
[15:22:39.515] flashing tool "subarucan" loaded.
[15:22:39.515] flashing tool "mitsucan" loaded.
[15:22:42.656] Using interface OpenPort 1.3 Universal TX277cOF8999f4d5b4eb04dea66501e857acafd543097b09
[15:22:44.187] sending init sequence 2
[15:22:44.187] got 0x13 response instead of 0x11
[15:22:44.203] sending init sequence 3
[15:22:44.578] entering bootloader
[15:22:44.593] sending kernel size (2027)
[15:22:44.609] sending kernel load address (0x0000F000)
[15:22:44.625] uploading kernel
[15:22:44.953] verifying kernel checksum response
[15:22:44.953] kernel valid
[15:22:45.156] kernel get version
[15:22:45.171] kernel version is : OpenEcu Mitsubishi H8/539FA Kernel V1.06
[15:22:45.171] reading kernel comm buffer size
[15:22:45.187] comm buffer size set to 256
[15:22:45.187] reading kernel flash buffer size
[15:22:45.203] flash buffer size set to 1024
[15:22:45.218] interface close


Anyone can tell me what i should do?