MUT at high baudrates WORKS! 62500 tested.
Code:
<scaling name="BAUDRATE" units="units" toexpr="500000/(x+1)" frexpr="500000/x-1" format="%.0d" min="0" max="500000" inc="1" storagetype="uint8" endian="big"/>
<table name="BAUDRATE1_OBD" address="cf81" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="cfb1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="cfc1" type="1D" level="1" scaling="BAUDRATE"/>
I actually downloaded the rom that bez patched(94170014) and I do not see the options in developer mode also. If I use the 94170008 patched defintion and open a 94170008 rom it does show the new tables.
Last edited by mchuang; Apr 3, 2007 at 11:47 AM.
Huh? I thought this part from the 96940011.xml file added the baud rate tables?
Code:
<scaling name="BAUDRATE" units="units" toexpr="500000/(x+1)" frexpr="500000/x-1" format="%.0d" min="0" max="500000" inc="1" storagetype="uint8" endian="big"/>
<table name="BAUDRATE1_OBD" address="cf81" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="cfb1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="cfc1" type="1D" level="1" scaling="BAUDRATE"/>
Ok, so I totally don't get what I'm doing wrong. I put the baud rate code into the 96940011.xml but I don't get a option for the baud rate.
I know I'm using the 96940011.xml because I patched the same file for the 2byte load.
I know I'm using the 96940011.xml because I patched the same file for the 2byte load.
The definition doesnt have this stuff in it by default, you have to ADD it
Not always easy to do by editing the file directly.. My guess is you have to make sure your in developer mode, and that the rom your using is detecting the right definition. FWIW Something doesn't look quite right about the snippet you posted.
Not always easy to do by editing the file directly.. My guess is you have to make sure your in developer mode, and that the rom your using is detecting the right definition. FWIW Something doesn't look quite right about the snippet you posted.
Last edited by MalibuJack; Apr 4, 2007 at 11:42 AM.
Gah, I finally figured out what was wrong.
I had renamed my original 96940011.xml to 96940011 before mut baudrate.xml and modified the file 96940011.xml with the mut baud rate options.
Apparently ecuflash can't deal with the space in a filename, or only does it with 8 chars, so it picked up the renamed xml file as the one it used. renaming it to old 96940011.xml did the trick and I now see the MUT baudrate entries in ecuflash.
I had renamed my original 96940011.xml to 96940011 before mut baudrate.xml and modified the file 96940011.xml with the mut baud rate options.
Apparently ecuflash can't deal with the space in a filename, or only does it with 8 chars, so it picked up the renamed xml file as the one it used. renaming it to old 96940011.xml did the trick and I now see the MUT baudrate entries in ecuflash.
Hi Guys, I am working on 88580013 and 14
I found the same routine in 94170014 and 88580013 - so added the xml definition in and then changed BAUDRATE2_MUT to 62500.
Now evoscan connects and logs fine with 62500 as the baud, but I don't see any increase in samples/second???
any ideas?
I found the same routine in 94170014 and 88580013 - so added the xml definition in and then changed BAUDRATE2_MUT to 62500.
Now evoscan connects and logs fine with 62500 as the baud, but I don't see any increase in samples/second???
any ideas?
I guess I dont understand this regarding 2 byte load (even hz), increasing the baud rate is not the determining factor of log resolution.
I've been trying to find a way to log my load and hz as 2 byte but not sure if it's possible yet with 96420007 (96420008), will Bez's baud xml mod enable 2 byte logging?
I'm willing to try 94170014 (already have Bez's edit on this xml) which is close to96420007.
I've been trying to find a way to log my load and hz as 2 byte but not sure if it's possible yet with 96420007 (96420008), will Bez's baud xml mod enable 2 byte logging?
I'm willing to try 94170014 (already have Bez's edit on this xml) which is close to96420007.
You just need the RAM address of the load and airflow from the disassembly, and the address of the MUT table in your ROM. Sorry I don't have time to disasm it for you, someone else must be able to by now if it isn't done already.
bump.
Can somebody pin down the MUT/OBD baudrate address in 96420008? I don't know what i'm looking for in the rom. It's probably not a good idea to just search for 15625.
d
Can somebody pin down the MUT/OBD baudrate address in 96420008? I don't know what i'm looking for in the rom. It's probably not a good idea to just search for 15625.

d




