oh are you saying that by sending "0xA0<MUTID>" over CAN you can access the MUT TABLE??

or are you talking about still using serial MUT (not CAN)?

 

where did you get the 0xA0 number from?

 

Dave, I have just spitted out what I have found in 7-9 ECU's, hoping someone with standard tool (e.g. ELM327 based) will try it out. If the translation from OBDII to CAN
is straight forward and they have kept the functionality in CAN processing then X guys could benefit from my finding. I only hope they have retained the functionality with CAN, but I cannot test it, nor confirm it via disassembly.

 

no thats ok. I am just trying to understand what you are saying

Where did you get the 0xA0 address/byte from?

 

e.g. 88590015:

0003A6D8 mov.w @(h'130,pc), r11 ; h'A0

but this is present in any ROM

 

ok.

well MUT technically isn't OBD - as far as I know (Hamish told me) the sequence for CT9A is:

send 1byte "0x00" init code @ 5bps
set baudrate to 15625bps
receive 3 bytes - just make sure you get 3
send 1byte request which is the MUTID - ie 0x26
receive 1byte response for that ID

Now 0x00 doesn't work on the X. 0x33 which is the REAL OBD init code doesn't work either, 0x10 DOES work but that's something different again (repeating sequence of key info @ 10400bps)

I spent a LOT of time looking at the disasm trying to uncover the new init code. But I can't find it.

Also the MUT_TABLE is refernced ONLY in the serial parts of the code, No CAN routines are associated with the MUT_TABLE.. So I think its unlikely that MUTTABLE over CAN works...

I will try some more init codes, but apart from that we are up a dirty creak without a paddle...

 

Actually those 3 bytes are sync and keywords.....

If I am not mistaken standard CAN uses OBD protocol i.e. Mode, PID to retrieve operational parameters. If I should test this one out, I would connect any CAN standard device to CAN ECU, and I would send Mode A0 PID 07 request to ECU
which is responsible for engine at the bus to see if it fits with MUT request 07.

 

yeh on the 3 bytes - Hamish ignores them, just ensures he gets 3 back...


ok so YOUR saying that a mode of 0xA0 should allow access to the MUT TABLE.

well I can test that out - HOWEVER like I said I find ZERO links between the MUT_TABLE and the CAN routines.

I have found the main CAN routine which handles all the different MODES, ie 0x01 (current), 0x21 (by ID)... etc etc

 

Yes EvoScan has already done this for the 12 months. its called Hybrid Mode. MUT over OBDII. I use it Mostly for datalogging on the 1996 3000GT vehicles.

 

I looked back at January 2008 and we already know how to do MUT over OBDII using 0xA0. Here is the information from my website from last year:

Hybrid 95-99 DSM/3000GT/Eclipse (16Pin) Supported Vehicles:
EvoScan is the first to support these vehicles. Select "Hybrid" and select ECU "EFI" in EvoScan.
EvoScan software is confirmed working with these vehicles, using the EvoScan 1.3U Datalogger/Reprogramming cable.
34) Mitsubishi Eclipse/DSM (1995 and 1996 support Hybrid MUT Protocol)
35) Mitsubishi 3000GT (Hybrid MUT Protocol)
36) Mitsubishi Eclipse (Hybrid MUT Protocol)

 

We already tried that the Hybrid mode doesn't work on EvoX.

 

EvoScan supports OpenPort2 cables and the main CAN protocol, and it has everything we need for the EvoX, including knocksum.

 

Normal for the ACD/ABS lights to come on/flicker once logging when set for E8/9?

 

ya. I freaked out for a sec till I figured out it was the 2.0 cable

 

Does this new version, or any of the older versions of EVOSCAN support the innovative LM2 wideband just as it did the LM1??