Hallo to all.
For those who like soldering
License is GPL

What is it?
MUTLogger is a system (hardware and software) witch can, connected over the OBDII Connector,
view and log (logging in future releases) Data from Mitsubishi EVO Models with the MUT Protocol.

Operation
After connecting the OBDII Connector (I build my connector myself, 4 Pins only used)
Be careful ! The 12V Power line is battery, not ignition power.
Ignition on. MUTLogger on. Then press the button, and the connection will be initialized.
If connection was successful only Numbers appear.

The numbers are:
columns
0123456789012345
RRRR OOO TTT –II Line1
EEE FFFF KKK MMM Line2

R = RPM
O = octane number (0-255)
T = throttle position (0-100%)
I = ignition
E = ECU Load
F = MAF frequency
K = Knock
M = Max Knock with throttle > 30% and reset after 8 sec

Download can be found here:
http://mitglied.lycos.de/joebee/mutlogger.html

Diskussions can be found here:
http://www.aktivematrix.com/forum/vi...hp?p=1496#1496

 

Finally an potential opportunity to use LED as an indicator of ECU intrepeted knock!

 

Very cool.

 

THIS IS SUPERB!

I have experience with Atmel AVR Mega 8 using BASCOM AVR to design MAF simulator and boost controller. Although I've never learned C.

I follow your schematic and appreciate the elegance of your level conversion.

I have an AVR Butterfly which is Mega 169 based. http://www.atmel.com/dyn/products/to...p?tool_id=3146

I think this could work really well with the project despite its slightly limited display, the big bonus is most of it is ready built. There is extra memory on board, integrated LCD and 4 direction plus push switch, as well as a piezo speaker. It is battery powered and has a huge battery life. Maybe the conversion electronics could be put in the OBD II connector? It has an RS232 level converter already, would this be any use to talk to OBD?

What do you think?

 

Sorry, but the RS232 conversion is invers. What you can do, is to wire directly the TX/RX Pins of the AVR to my transistor array.
RS232(PC): -12V logical 1, +12V logical 0
AVR: 5V logical 1, 0V logical 0
OBD: 12V logical 1, 0V logical 0

Thats why I use 2 Transistor steps. Both negate the signal.

 

Thanks

 

Nice work, JoeBee! Once I'm done with a couple of current projects, I'll look into trying this out with another processor, like a PIC18.

Just out of curiosity, what schematic package did you use for this? Also, would you be able to provide a bill of materials in the zip archive?

 

What are the dimensions of the LCD and where will it fit in the EVO dashboard? Looks very promising...Nice job

 

I use the freeware Version of Eagle from cadsoft (limited Board size).
http://www.cadsoftusa.com/

I have attach a partlist. The only little more expensive parts are the ATMega168 and the LCD Module. The rest parts are "peanuts" .

 

sweet deal...

 

I use a display similar like this (in mm, divide this by 25.4 to get inches)

 

Is interest here in an alternative version?
No LCD Display, only one DUO LED that show knock Values like:
Off: Knock < 4
Yellow: Knock between 4 and 8
Red: Knock > 8
Red blinking: communication error
What about TPS threshold? Should Knock only be counted when, for example, TPS > 30% ?

Maybe we can use the smaller AVR (Atmega48) witch cost only 1.60$ (Atmega168 about 4.50$)

Comments ?

 

I would just use the knock sum without TPS limits, there are (unknown) thresholds in the ECU that limit where knock control is active.

A PWM output of 0-5V (don't need the capacitor if you drive the PWM at high frequency) for 0-36 knock sum might be useful.

Another option is an LED that illuminates when the octane value gets pulled off 100%. Knock sum 0-3 and the ECU tries to increment it, 4-5 it leaves alone, 6+ it decrements.

The bigger issue for many will be the option to buy a ready made circuit, not the price. What about basing the project on an available prototype board with LCD, perhaps not the butterfly I mentioned, but there are other AVR options... will see what I can find and post. Many could probably cope with installing a few components in an OBD II plug, then you could just send the power, ground, signal to the ready made board?

 

http://www.dontronics-shop.com/produ...cat=353&page=1

This has the keypad, nice display, power reg, RS232 all there.

What could be really nice is a little adaptor to use a Tactrix cable's USB output to put it into a ready made board? Or a few components to put into an OBD II plug to convert to the RS232 (or low voltage version of same) that many of these boards already have?

For many there is nothing as convenient as a nice ready made board with surface mount components, integrated display and controller as above. I'll find some other examples and post.

 

Some of the newer boards have USB Host addons that natively recognize RS232 and Disk devices..