MUT at high baudrates WORKS! 62500 tested.
It would be interesting to see an obscenely fast OBD-II baud rate..
Although this works, and I do intend to play with it.. You guys will notice many of the logged items don't update as frequently as they are sampled..
Although this works, and I do intend to play with it.. You guys will notice many of the logged items don't update as frequently as they are sampled..
Originally Posted by dryad001
Can someone try this out with a Palm? Im just curious to see if the sample rate will also increase. Since there is a table to switch the OBD baudrate also.
d
Originally Posted by bez_bashni
It can fit the other ecus of this family - to try this with your ecu add this lines to your ecu definition after the include <evo7base> ;
<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="d59d" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="d5d1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="d5e1" type="1D" level="1" scaling="BAUDRATE"/>
If you see after reloading your hex that baudrate3_unknown=62500 and BAUDRATE2_MUT=15625 and BAUDRATE1_OBD=10416 than it will work with your ecu.
<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="d59d" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="d5d1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="d5e1" type="1D" level="1" scaling="BAUDRATE"/>
If you see after reloading your hex that baudrate3_unknown=62500 and BAUDRATE2_MUT=15625 and BAUDRATE1_OBD=10416 than it will work with your ecu.
I had planned on testing my OBDII logger with a doulbled rate. Since I was having troubles and had to get to work, I did not flash the increased rate. I'll try it this afternoon if no one beats me too it.
I still cannot get the scaled value to increment/decrement or change in any way. So, I changed the OBDII rate from an int8 value of 47 to 23. This in theory should have double the rate. I could not get my OBDII datalogger(AutoTap) to connect at the higher rate. I'd still like to see faster OBDII logging rates.
Originally Posted by bez_bashni
About 2 weeks of my free time at office 
and home I devoted to evo ecu disassembling. The first goal was to discover load pid and writing patch for "correct" launch control.But by the way i found some interesting. Heres one of the first usefull achievements - found OBD and MUT baudrates. Heres the definition for the most popular 94170008 ecu - sometime I'll make definitions for other ecus.
How to use. If your flash is 94170008 -unzip my definition to ecuflash mitsu folder (dont forget to backup the original) , open your rom and u'll see new params under MISC. Change the BAUDRATE2_MUT and reflash the ecu.
Then start evoscan and put this value in baudrate window (15625 by default)
I tested 62500 baudrate logging - all Ok -engine runs - no errors.
Enjoy highs speed logging
copy sent to openecu.org ,aktivematrix.com
and home I devoted to evo ecu disassembling. The first goal was to discover load pid and writing patch for "correct" launch control.But by the way i found some interesting. Heres one of the first usefull achievements - found OBD and MUT baudrates. Heres the definition for the most popular 94170008 ecu - sometime I'll make definitions for other ecus. How to use. If your flash is 94170008 -unzip my definition to ecuflash mitsu folder (dont forget to backup the original) , open your rom and u'll see new params under MISC. Change the BAUDRATE2_MUT and reflash the ecu.
Then start evoscan and put this value in baudrate window (15625 by default)
I tested 62500 baudrate logging - all Ok -engine runs - no errors.
Enjoy highs speed logging
copy sent to openecu.org ,aktivematrix.com
Originally Posted by Spec'd
What would be nice is having the capability to run the ACD pumps
for 05+ Evos. This would mean not requiring the MUT tool to change
your own ACD fluid.
for 05+ Evos. This would mean not requiring the MUT tool to change
your own ACD fluid.
Originally Posted by TTP Engineering
Will this affect the dealer's ability to communicate with the ECU via the MUT-III scantool with the baudrate change?
There are two other baud rate values, not sure what they are yet, but if anything the MUT Tool does using those, it will still work..
Its the primary reason I don't tell everyone to change it..
HONESTLY, I don't see any benefit at this time in logging since the baud rate isn't the limiting factor in logging..
I have enough data sampled at 10 lines per second (15-20 samples per line) to show that the data itself in most of the requests dont get updated that often anyway..
The baud rate might help for issues like dropped data or missing data in the buffer, but I don't know that you'll get any more information.. Just more data (items with repeating values)
Newbie
Joined: Jan 2005
Posts: 62
Likes: 0
I downloaded and replaced the definition file for rom 96940011 in the above post, switched the ecuflash in developer mode, but don't see the baud rate option under misc in ecuflash. I've gotten the 2 byte load status working correctly for my rom, so I'm not sure what the problem is. I'm currently using ecuflash 1.3
I've tried closing and reopening ecuflash to no avail.
I've tried closing and reopening ecuflash to no avail.
