Break-thru: Reading ACD ECU with EcuFlash
Feb 15, 2010, 05:38 PM
#91
Evolved Member
Tried logging my AUDM9 today, it connects, but nothing logs properly. (1.3 cable, v2.5).
Tried changing a request id to 14, same result as Sabin, re post #77, outside array.
I initially had all the boxes ticked, but when connection made, the pumps started activating so I quickly switched of.
I have just checked my cable, pin 1 is joined to pin 15. Pin 9 is still in the connector.
I will break it out and try again, later....
edit: removing pin 9 did not help in my case.
Tried changing a request id to 14, same result as Sabin, re post #77, outside array.
I initially had all the boxes ticked, but when connection made, the pumps started activating so I quickly switched of.
I have just checked my cable, pin 1 is joined to pin 15. Pin 9 is still in the connector.
I will break it out and try again, later....
edit: removing pin 9 did not help in my case.
Last edited by merlin.oz; Feb 15, 2010 at 06:09 PM.
Feb 16, 2010, 10:12 PM
#92
Newbie
Join Date: Feb 2010
Location: Australia
Posts: 62
Likes: 0
Received 0 Likes
on
0 Posts
Yeah I messaged the evoscan developers, they are going to do some work on the ACD stuff for you guys tonight.. fix the index bounds error, then add some openport 2.0 support for it, and then remove requestids that are doing mapping to real mut requestIDs inside the app.
Feb 17, 2010, 01:39 AM
#94
Evolved Member
Also, after I had connected to the AWD ECU via EvoScan, the CEL lit-up.
I have just checked, it threw 33 DTC's, basicly everything for AWD and an idle error for the EFI ECU. Weird.
I have just checked, it threw 33 DTC's, basicly everything for AWD and an idle error for the EFI ECU. Weird.
Feb 17, 2010, 07:32 AM
#96
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
Hamish just wrote me that anyone who wants to get Evoscan for ACD logging developer purposes shall log into EvoScan page and submit a ticket. He has a fix ready.
Last edited by acamus; Feb 17, 2010 at 09:30 PM.
Feb 17, 2010, 09:35 AM
#97
Evolving Member
Thread Starter
Feb 17, 2010, 02:46 PM
#98
Evolving Member
Join Date: Apr 2008
Location: Reading, PA
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
Anyone using the fixed EvoScan yet? I haven't got a reply...
I could make a custom MUT table with all the ADC inputs in it, so we could figure out whats connected to what. That would help in figuring out what the normal MUT Requests are.
I could make a custom MUT table with all the ADC inputs in it, so we could figure out whats connected to what. That would help in figuring out what the normal MUT Requests are.
Feb 18, 2010, 04:00 AM
#99
Evolving Member
Thread Starter
In the mean time, me and Acamus are still working on our version of MUT logger for ACD based on your MHI. So, until i really see the EvoScan, i don't believe it is ready.
But i can say, this ACD is pretty different in responses compared with the engine ECU.
Work in progress
Feb 18, 2010, 11:01 AM
#101
Newbie
iTrader: (3)
Join Date: Dec 2005
Location: Seattle, WA
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
Sorry for the late reply. If you have a spare ACD, I would be happy to pay to have you send it to me to look at and figure out what might be going wrong with the flashing. If not, I may try to find one myself...
Colby
Colby
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.
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.
Feb 19, 2010, 12:49 AM
#102
Evolved Member
colby, email Steve at
steveknightrace@optusnet.com.au
I believe he is willing help out with an AWD ECU.
We would like this issue worked out as it would enable us to flash the evo6.5, VR4 and Legnum, all with 7203 chip.
steveknightrace@optusnet.com.au
I believe he is willing help out with an AWD ECU.
We would like this issue worked out as it would enable us to flash the evo6.5, VR4 and Legnum, all with 7203 chip.
Feb 19, 2010, 05:19 AM
#103
Evolving Member
Thread Starter
We are waiting for you to find out the problem and resolv it.
But if you don't really find a ACD ECU, i think a Evo 6.5 TME or Eclipse will do also the task.
Feb 19, 2010, 05:21 AM
#104
Evolving Member
Thread Starter
Feb 19, 2010, 05:50 AM
#105
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
With the help of sba and merlin.oz we have been able to create a scanner, based on Ceddy's MHI scan. Thank you all for your participation.
Now it seems to be working to the extend of testing purposes. I know sba is currently trying to figure out the input pin request ids.
So we are now waiting to collect the MUT table meaning.
If anyone is eager to help please find logger attached.
The cable needed is OP1.3
Now it seems to be working to the extend of testing purposes. I know sba is currently trying to figure out the input pin request ids.
So we are now waiting to collect the MUT table meaning.
If anyone is eager to help please find logger attached.
The cable needed is OP1.3
Last edited by acamus; Feb 19, 2010 at 08:31 AM.