Hi,

i have access to a mut2 and mut3 (mitsubishi diag tool). is there a sniffer app out there for openport 1.3 cable?

I would like to try sniffing all acuators and all logging items.

problem:
i can't write my own app. i tried, but my knowledge isn't big enough.

my idea is that i connect the openport cable and the mitsutool both to the obd plug on the car.

maybe someone can write a simple tool that displays all data sent from mitsu tool to the ecu and back.

like sniffing a network with a lan-adapter in listen mode.

i tried using hyperterminal but i couldn't get it workring.


any ideas?

 

I try something similar a while ago.
The problem I ran into was because two things were talking on the same line I got a lot of corrupt and miss aligned data. I had better luck with the with my FTDI cable pretending to be the ecu.

Can the MUT3 tool flash using .RPG files?

 

all genuine mitsi mut 3 reflash's and software upgrades are .rpg files

 

i dont know much about serial protocols, but isn't it possible to monitor only?

or to wire something between sniffer and the mut <-> ecu connection, that no data is sent from the sniffer.

 

The MUT Tool and ECU both talk on the K-Line, so its hard for for the Sniffer to know which one is sending/receiving and its easy to get alignment problems. I was looking mostly at the 5 Baud Init Sequences that switch to 10400 or 15625 Baud when done. You might have better luck if you just monitor the MUT 15625 stuff.

I wired a spare OBD2 plug to my existing one and hooked a 1.3 cable to that.
I used Visual Basic and the FTDI Library to make a "sniffer". I couldn't get HyperTeminal to work, don't think it can do 15625 baud or something, so I used another terminal program. I have source code for a MUT/Hybrid Logger project I never finished if you would like to see how the FTDI stuff works.

 

i think i can get the communication sorted out by hand.

if i monitor logging for one item, i get only one request value and different response values.

of cause i like to see some code, maybe i understand it and can modify it to work for me.

 

http://ceddy.us/wp-content/uploads/MHIScanner_FTDI.rar

Code isn't clean, but might help getting you to started with the FTDI/MUT comms.

 

what I would do is take 2 x MC33290, female, male OBD plugs and serial sniffer in-between

 

it's working.

i found a arduino board with a ftdi chip onboad. i used this chip as a sniffer with a 15625 baud compatiple terminal. i just connected the receive line.

the 12v->5v translation i have done with some resistors.

its a dirty thing but it works great.

now i am going to squeese out the last bit of information from the oem mut3.

i just need to build a more robust wiring for in car use.

thanks for you good thought, i have a lot of new ideas now.

 

This thread has been dead for a year, but here's a quick suggestion for the archives: on a Linux host system, with Windows running as a guest in a VM (on any virtualization platform that allows you to pass through USB devices to the guest system), use Wireshark on the Linux side to capture the raw USB traffic on a given bus, then kick off whatever activity you want to capture on the WIndows guest.

You may need to do a little protocol analysis to get the data you're looking for depending on the device you're sniffing, but this got me 90% of the way there for what I was trying to do (and wireshark's awesome filtering got me the rest).

 

Hi Deepnine,

I am interested to know more about how you used arduino to communicate with ECU in MUT protocol. Currently, I have MUT ODBII cable but i do not have FTDI serial cable.

Just not to bother you with many question from me, can i have the sample of the arduino programming to communicate with ECU and how you make the wiring?

Thank you.