Break-thru: Reading ACD ECU with EcuFlash
Evolved Member
Joined: Jun 2008
Posts: 824
Likes: 24
From: Sydney
ceddy or logic, any progress with the disassembly and map investigations?
acamus, can the baud rate / sample rate of your scanner be increased?
It all seems to work OK, just a bit slow, or can I change some setting?
and finally, does anyone know if Hamish has fixed the out of range error in v2.7 beta?
acamus, can the baud rate / sample rate of your scanner be increased?
It all seems to work OK, just a bit slow, or can I change some setting?
and finally, does anyone know if Hamish has fixed the out of range error in v2.7 beta?
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
After looking at the Technical Manual, it appears that the x-axis for Table Main and Table C is most likely Steering Angle.
A optical wheel is used, with three outputs. I think they time the difference between leading edges of the waveforms. Zero difference would be steering wheel neutral, and a large time difference would be the steering wheel turned a lot.
Some real world data will be needed to find the scaling, as I have no idea what the frequency of the waveforms and the ecu timer is.
Definition Update
Main -> Steering Angle x Vehicle Speed
Table A -> Throttle Position x Vehicle Speed
Table B -> Front/Rear Speed Difference x Vehicle Speed
Table C -> Steering Angle x Vehicle Speed
Just need to find what .1, .2, .3 correspond to, Snow, Gravel, Tarmac.
And the definition will be fairly complete.
A optical wheel is used, with three outputs. I think they time the difference between leading edges of the waveforms. Zero difference would be steering wheel neutral, and a large time difference would be the steering wheel turned a lot.
Some real world data will be needed to find the scaling, as I have no idea what the frequency of the waveforms and the ecu timer is.
Definition Update
Main -> Steering Angle x Vehicle Speed
Table A -> Throttle Position x Vehicle Speed
Table B -> Front/Rear Speed Difference x Vehicle Speed
Table C -> Steering Angle x Vehicle Speed
Just need to find what .1, .2, .3 correspond to, Snow, Gravel, Tarmac.
And the definition will be fairly complete.
-> no, it is just testing application
Originally Posted by _Speedy_;
Yeah v2.7 now has ACD and AYC and TCU in the dropdown.
http://en.wikipedia.org/wiki/Rotary_encoder
Last edited by griceiv; Mar 11, 2010 at 06:26 AM.
Evolving Member
Joined: Apr 2008
Posts: 265
Likes: 1
From: Reading, PA
Then we can log items from a custom MUT table. This will enable us to figure out which maps are Tarmac, Gravel, Snow, etc.
My disassembly has hit a wall until I can get some logs with custom items from someone.
I think we are waiting for a update to EcuFlash so it can flash all the blocks in the ACD.
Then we can log items from a custom MUT table. This will enable us to figure out which maps are Tarmac, Gravel, Snow, etc.
My disassembly has hit a wall until I can get some logs with custom items from someone.
Then we can log items from a custom MUT table. This will enable us to figure out which maps are Tarmac, Gravel, Snow, etc.
My disassembly has hit a wall until I can get some logs with custom items from someone.
Colby
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Can someone give me some specifics of what blocks / data they are having trouble flashing? I have done some test writes in various empty areas of the ROM on a Evo8 ACD and haven't run into any problems. If someone can send me some ROM images with changes that they are having trouble flashing, that would be helpful. (support@tactrix.com).
Colby
Colby
Maybe we just do not know what shall be in xml def header?
We have been using
Code:
<flashmethod>mitsukernel</flashmethod>
<memmodel>H8539FA</memmodel>
Last edited by acamus; Mar 25, 2010 at 10:59 PM.
Thread Starter
Evolving Member
Joined: Nov 2007
Posts: 153
Likes: 2
From: East Europe
Hello boys,
It is some time of being absent from here but i was very very busy.
I can post some files with 2 readings of a blocked ecu and a file that i tried to right it and blocked the ecu. I got ecu blocked when i tried to modify mut table also.
So, in the zip you will find the original file from the ecu, the file that i wanted to right and the 2 readings with errors.
It is some time of being absent from here but i was very very busy.
I can post some files with 2 readings of a blocked ecu and a file that i tried to right it and blocked the ecu. I got ecu blocked when i tried to modify mut table also.
So, in the zip you will find the original file from the ecu, the file that i wanted to right and the 2 readings with errors.
OK. I have the kernel problem fixed now. I will be releasing a new beta version on www.tactrix.com later today that will have the fix. H8539FA is the correct memory model. Let me know if you have some reasonable definitions for the ACD, and I will add those XMLs to EcuFlash if you would like. I have already added the ACD as a read option.
Colby
Colby
That is a great news as we were not able to flash anything with OP2.0.
Maybe we just do not know what shall be in xml def header?
We have been using
Could you make a dropdown list of kernels/processors/memory models when creating definition in EcuFlash?
Maybe we just do not know what shall be in xml def header?
We have been using
Code:
<flashmethod>mitsukernel</flashmethod>
<memmodel>H8539FA</memmodel>