Page 1 of 1
98640014 2Byte Load?

Posted:
Tue Jan 15, 2008 2:13 am
by R. Mutt
Anyone know the address for it?
only thing I've seen is :
- Code: Select all
<table name="00 2 byte load" address="38062" type="1D" level="1" scaling="uint16" />
<table name="01 2 byte load" address="38066" type="1D" level="1" scaling="uint16" />
but this is for 94170008 (USDM Evo VIII) and I don't know if it's correct for JDM VII ecus.

Posted:
Tue Jan 15, 2008 3:40 am
by R. Mutt
So I looked at burgers definition file and see the following:
- Code: Select all
<table name="RequestID00" category="MUT" address="2e9e2" type="1D" level="1" scaling="uint16"/>
<table name="RequestID01" category="MUT" address="2e9e6" type="1D" level="1" scaling="uint16"/>
<table name="MUT8A" category="MUT" address="2ea6e" type="1D" level="1" scaling="Hex16"/>
<table name="MUT8B" category="MUT" address="2ea72" type="1D" level="1" scaling="Hex16"/>
Which 2 MUT parameters are these address for? I take it that the first one is 2 Byte Load while the other is


Posted:
Sat Feb 02, 2008 3:12 pm
by burgers
Hi
Request ID 0 and 1 are for 2 byte load. MUT8A and 8B are for boost error and WGD correction, unfortunatly I haven't found the correct addresses for those. To log 2 byte load you need to change Request ID 0 to 34908 and Request ID 1 to 34909 This information was originally supplied by John Banks, S54fan on here.
MB

Posted:
Tue Feb 19, 2008 1:58 pm
by R. Mutt
kind of late to reply, but thanks burgers.

Posted:
Sat Mar 22, 2008 11:22 pm
by sub7
My ROM address using 2e9e6 value is 135 and 34738 doesn't look right. But if I change it to 34908 and 34909, the value is 255 and 65535. Does this look right to you?