Page 1 of 2
Mitsubishi Lancer Evolution 4/5/6/7/8 MUT-II Initialisation
Posted:
Tue May 02, 2006 5:58 pmby Evo4Mad
Keywords: Evo4 Evo5 Evo6 Evo7 Evo8 Evo9 IV V VI VII VIII IX OBD2 OBDII ELM323 ISO9141 SCANTOOL DATALOGGER MUT-II MUT-III
http://www.limitless.co.nz/evoscan
Posted:
Tue May 02, 2006 10:55 pmby Evo4Mad
what baud rate and byte could I send to mimic that initialisation signal? could I try with no stop bit?
Posted:
Wed May 03, 2006 1:09 amby YP
Init byte is 0x00 at 5bps with stop bit. After that bps rate changed.
Posted:
Wed May 03, 2006 10:19 amby Evo4Mad
oh yeah thanks.
Posted:
Sat May 06, 2006 10:35 pmby Evo4Mad
I ahve got it working for the Evo4
Posted:
Sat May 06, 2006 10:43 pmby Evo4Mad
The MUT-II scantool firstly tries this initialization at 10,400bps its probably for different model EVOs
Packet structure:
0x44 0x10 0xF0 0x3F 0x83
(Settings byte/EFI ecu ID/Scantool ID/Data Request/CheckSum)
Log @ 10,400bps
[0][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83][44][10][F0][3F][83]
Jumbled data cause the MUTII starts talking at a different bps
[0][0][0][0][E6][FB][F2][FF][FA][FF][FB][FF][FA]
Posted:
Wed Jul 26, 2006 7:29 pmby donour
Does anybody have working VCP code to do this (D2XX drivers are not available for my platform) ? All I'm getting are echos of my requests. I get nothing from the setting break for 1800ms.
d
Posted:
Wed Aug 30, 2006 6:30 pmby fotis_rs2
with what cable you connect it to an evo6???
the openport1.3 dosn't seems to work... no connection at all...
Posted:
Thu Aug 31, 2006 4:01 pmby fotis_rs2
anyone????
Posted:
Fri Sep 01, 2006 5:13 amby Evo4Mad
yep it works, does the obdII connector have pins 1 & 4? join them with a paperclip in the back.
Posted:
Fri Sep 01, 2006 6:12 amby fotis_rs2
so i'm missing a ground signal right? the pin 4 is ground..
Posted:
Sun Sep 03, 2006 3:53 amby S54fan
I've found the initial setup routine for the 5 comm ports in the SH7055 of my Evo IX. The VII is similar...
It sets port 0 & 1 to 1953 bps, and port 2 to 15625 bps. 3 and 4 seem unused, but are initialised to 1953 bps.
The above rates are based on 8MHz CPU crystal which is multiplied by 4 for the CPU clock and then divided by 2 for the peripheral clock. Then various prescalers are selectable and then a trim for the actual rate.
There are also baud rate switching routines which I'll look at.
I have several other serial routines to go through to find the area where it processes the byte requestIDs that Evoscan sends.
We could consider a custom ROM to increase the logging rate as I want to start changing pointers for the fuel and timing maps to be selectable by an Evoscan requestID to be the original ROM site or a RAM copy. I want live adjustment of that RAM area, and a nice Windows app to use an agreed protocol to change these bytes. I also want to send the load value I've found back down the serial to Evoscan.
Posted:
Sun Sep 03, 2006 4:00 amby S54fan
The SH7055 can manage 500K baud = 32 times faster than 15625 baud. About half as fast as my broadband internet connection. It could shift a lot of data if we needed it to...
Posted:
Sun Sep 03, 2006 4:03 amby S54fan
Might not have much time to run the engine though at that speed LOL.
Posted:
Sun Sep 03, 2006 6:00 pmby Evo4Mad
LOL, yeah, might want to give the engine a chance
colby and I had discussed this scenario once before, but were concerned about the factory tools still being able to connect.. good for power users though.