Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: 6201
Info: Connection successful...
Error: Index was outside the bounds of the array.
Info: Datalogger Ended.


I get this error when i try to insert a new request. Is anyone knows why?

 

I hit the corner of the table with my head...

I don't know how is that Evoscan working, or the ACD ECU, but is something devilish inside. I cannot log anything than 00, 01.....0E, (without 0F), 10, 11, 12, 13. And that's all.

All i can do is to put every requestID in the Custom Request Box and i get a 0x?? value. That all. If i try to put inside the normal requests, i get this error:

Info: ECU ID: 6201
Info: Connection successful...
Error: Index was outside the bounds of the array.
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#= qI2Bxs8jh5r0BxamKtYJJTA==()
Info: Datalogger Ended.

I tried v2.7 and i got this error, so i got back to v2.6 and....still the same error.

I'm out of ideas, bored and upset because of this slow progress. Please help to go further with this.

Maybe we can find a different program to log things with...

 

are u connecting the cable directly to the ACD ecu? do u know if the ACD ecu uses the normal MUT protocol?

if both are true maybe try using mitsulogger??? or am i going in completely different direction.

RE: AYC/ACD/SAYC.

AYC: evo4+
ACD: evo7+
SAYC: evo8MR+

that is jdm evos.... the US got a hybid evo8... more like a JDM7 but without a ACD.i am not 100% sure but i dont think the US got a 8MR... if they did it was not the same as the JDM8MR.

 

Maybe you rather use XML definition for adding requests.
I believe custom request in EvoScan works for ECU only, but I may be mistaken.

 

Ok,

This really get interesting... Today i tried to write inside the ACD a modification and ... the ECU got bricked (the error log attached)

Now i can just read the ECU with no problem, but i cannot write it anymore or even to log it. The curious thing is that the difference between the original file and what it is now inside the ECU is very small, a few bytes changed. I also attached the file that it should be inside the ECU and the file that it is now.

So:

- ACD_ECU_evo8_org - is the file that was in the ecu from the beginning and i tried to change
- i tried to write something inside. It blocked, gived me the error
- i readed again: read_error
- i tried to write again the first file, same error
- i readed again: read_error2

What is your opinion? Colby?

S.

 

I think that it's the same problem with some EVO CP9A ECU.

 

I have heard that MH7203FA and 128Kb ROM ECU has been restored using bootloader (Kashima ECU adapter + spec. soft), cannot tell the details thou.

 

What area did you change?

A map or other area?

If you changed some of the code, it will go into a bad code reset loop, and be bricked.

 

I thinked about this, so i tried to write a oem file from another ECU, identical with the test one.

What is making me curious is that, after the failed writing process, the quantity of changed data is so small. The files have very big differences between them.

So, we have to find the solutions for this 2 problem in order to get further:

- a writing process that work flawless every time
- a logger that can really log this ecu

Tomorrow i will try to repair my test ECU to have with what to play again.

 

I don't know much about how the actual ROM write works, but maybe the endian was incorrect?

 

This scaling seems to be getting closer to reality, maybe...

<scaling name="VehicleSpeed_ACD" units="kph" toexpr="x/100" frexpr="x*100" format="%.1f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/>

<scaling name="Throttle%16_ACD" units="%" toexpr="x/512*100" frexpr="x*512/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>


<table name="Main Center Dif Lockup Map" category="Lockup Maps" address="12171" type="3D" scaling="Percent (256)">
<table name="Throttle" address="12158" type="X Axis" elements="9" scaling="Throttle%16_ACD"/>
<table name="Speed" address="120ba" type="Y Axis" elements="36" scaling="VehicleSpeed_ACD"/>
</table>


edit:
looking/playing with this large map some more, and wondering if it is the map for the AYC rear diff lockup v tps v steering angle.
I did a version with a steering angle of x/60, which gives a max angle of 245 degrees, ie about 3/4 of a full wheel turn.
Is that sensible or silly?

 

I repared my ECU, and now it is working again.

I'm waiting for new ideas.

S.

 

SBA, did your ACD ecu just start working, how did you fix it?

 

I wrote the original file inside the ACD ECU with a different chip-tuning tool. Now it is working like before.

Bricked ecu in my case means: you cannot write anything inside the ecu and you cannot log the ecu, but the ecu can be readed and works normally on the car.

 

I sent a support ticket to Hamish of EvoScan, asking if there are limitations to changing the ReqestIds for the AYC.

Haven't heard back yet...