So today I got the OBD2 (well I think it uses the MUT protocol) to USB adapter, and an evoscan licence. I've already tried it out, but am a bit disappointed by some missing attributes. Specifically fuel flow and current selected gear.

Perhaps the standard list of attributes doesn't have them, but the ECU reports them. Anyone know of any request codes? Also any other interesting tidbits which could come in handy? For example, is there a way to ask the ECU how many kms it has done (as the dash one is independant)?

This is a 2002 model (made 2003) TJ S2 Magna. Using an Openport 1.3U cable and evoscan 2.9

Just noticed that there are different Control Units which can be accessed. Assuming I can actually access them, can they be read at the same time as the main (EFI) Control Unit? The TCU apparently has something to determine gear switch, but I don't know as yet if it will tell me the gear in drive mode (Yes, this is an Auto, I forgot to mention sooner). Still no luck on fuel flow rate.

So today I got the OBD2 (well I think it uses the MUT protocol) to USB adapter, and an evoscan licence. I've already tried it out, but am a bit disappointed by some missing attributes. Specifically fuel flow and current selected gear.

Perhaps the standard list of attributes doesn't have them, but the ECU reports them. Anyone know of any request codes? Also any other interesting tidbits which could come in handy? For example, is there a way to ask the ECU how many kms it has done (as the dash one is independant)?

This is a 2002 model (made 2003) TJ S2 Magna. Using an Openport 1.3U cable and evoscan 2.9
The MUT protocol doesn't support the same things as ODB2, however much of the same information can be extracted. Evoscan should already be configured to log most of the interesting bits.

You can compute approximate fuel flow based on the injector duty cycle (which can be logged with Evoscan) and the injector size (nominally 268cc/min as identified in the ECU code, probably around 300cc/min based on actual flow measurements). However this doesn't work well at idle because it doesn't account for injector latency, resulting in higher figures than actual flow rate.

The ECU doesn't record distance travelled, and even if it did it would only go back to the last battery disconnection as the ECU doesn't contain the EEPROM memory that would be required for what you ask.

I believe that the gear selection is available as bit fields within some MUT requests, but is not available as a simple number.

ok, I hoped that wasn't the case, but I think I can still find some use from it. I noticed the injector cut test (which I haven't completed yet) and readings from the O2 sensor(s) could come in handy. Any idea why I might not be able to talk to any of the computers other than the EFI one? I've tried the ones in the dropdown list, but none of the other ones respond (many of which I should have).

Which computers do you think you have that you can't talk to? and which protocol settings are you trying to use?

In a TJ, the ECU and TCU are the same unit (that is, both functions are handled by one micro controller, which may be why the TCU stuff doesn't respond. Older H8 auto ECUs actually had 2 microcontrollers - 1 for each function, on the same PCB - and may have had the necessary wiring.

You might find some useful MUT protocol info here (http://evoecu.logic.net/wiki/ECU_Development). The Evoscan website also has a collection of documents too. None of these are specifically for the Magna though.

Ah cool, thanks for that link. Well I only saw options to check the current gear select position under the TCU drop down menu, so I assumed that meant it was seperate.

Edit: Oh good, it explains the commands. Given my idle adjust screw has been changed, I'm going to set that right.

sorry for the threadmine..

i recently bought the 13.D
installed the software etc. but cannot for the life of me get it to sync to the ecu
tried all the settings and it's for far refusing to play or share any info

it keeps saying no response from ecu.

what settings were you using if you don't mind sharing?
as i'm trying to use it on my 96 3.0 v6 te executive

The OpenPort 1.3 option needs to be selected, the protocol must be set to Mitsubishi MUTIII, the baud rate must be set to 15625, and the EFI ECU type selected.

The ignition must be ON before the ECU will respond at all, usually works better if you wait until the engine is running before attempting to start the logger as sometimes the connection gets lost during engine start (though it should attempt to reconnect automatically and succeed once the engine is running). If you can get access to another car, see whether you can log in that in case it is a bad cable.

thanks for the info wytwyn

set it to those specs just now, i'll have a go after work.
i have been trying with the ign on or running.

cable wise. my dell laptop sees the cable as the evoscan cable
and the car does flash the cel light and flash the neutral light when plugged in. 0.5 seconds apart constant flashing

it isnt the first time this car has given issues trying to extract the codes either. as i have also tried earthing the pin out in the diag plug to use the cel light for the codes.
no dice.. even if i delibrately initiate a cel light
eg disconnect maf,cas,oxy or simply refit the maf i destroyed running on the vile bp fuel i'd used

no access to another 3rd gen unfortunately