Page 1 of 1

04 ROM ID 96420007 (or 96420008) 2 byte load/MAF hz logging

PostPosted: Fri May 18, 2007 4:52 am
by C6ect.ect
Hello

Has anyone dissed the 04 USDM 96420007?

If not, :) please?

If no one has the time what is required to disassemble?

Perhaps I need to buy a another evo to log 2 byte :lol:

Thanks

PostPosted: Fri May 18, 2007 6:17 pm
by Freon
It's not just a button you press, it is a manual process that may never end. Is there something specifically you are looking for? Or are you completely missing any sort of def?

PostPosted: Fri May 18, 2007 6:47 pm
by C6ect.ect
I want to log load as 2 byte (which I understand is the actual load variable the ECU uses), as well as MAF hz and RPM.

I have heard of some users running 2 byte on LogWorks which is my ultimate plan.


With these tools it will be easier to get a consistant tune and furthermore pinpoint some other on going issues

Thanks at least for responding :D

PostPosted: Fri May 18, 2007 7:01 pm
by Freon
If you can point me to where I can download the 96420007 rom I'll try to take a look. What your asking for shouldn't be very hard to get. This is a SuperH CPU, correct?

PostPosted: Fri May 18, 2007 8:35 pm
by C6ect.ect
SH7052 - I guess this stands for Super H


Here is an old download of my ROM (not stock). Back then with ECUFlash 1.79 and earlier, the ID was recognized as 96420008, several things did not display correct (stepper lookup) so when ECUFlash 1.3 came out it was recognized as 96420007, if this is important.

Thanks

http://www.aktivematrix.com/forum/dload ... file_id=15

PostPosted: Fri May 18, 2007 9:35 pm
by Freon
Try FFFF886C and FFFF8962. It's that 16bit integer *1000/256. I haven't spent much time on the non-floating point EVO ECU, but I think it is one of those two.

If one of those works I can show you a REALLY easy way to find the 2 byte just without disassembling, just using a hex editor and a working xml def.

PostPosted: Sat May 19, 2007 2:18 pm
by C6ect.ect
Still figuring....

PostPosted: Sun May 20, 2007 10:44 am
by Freon
Still figuring?

Let me know if you can add these to your logger def. It shouldn't be hard with Enguinity or Ecuedit. Just open the logger def, find your CALID, add a new line. int16, [value]*1000/256

PostPosted: Sun May 20, 2007 6:18 pm
by C6ect.ect
Yeah, still figuring

I guess I better get Enguinity or Ecuedit. To be honest, my problem lies with lack of understanding of the overall picture of what needs to be done. I thought I need to add the address you found to the ID xml which will display on ECUFlash where I would plug in a high and low decimal.

Then I add something to my LW logger to be logged

PostPosted: Sun May 20, 2007 6:40 pm
by Freon
You shouldn't need to put it in Ecuflash XML. It would go into the logger XML. Ecuedit would work.

PostPosted: Mon May 21, 2007 3:19 am
by C6ect.ect
EcuEdit is currently down, and Enginuity doesn't support Mitsu, I'll have to wait