Mitsubishi Lancer Evolution 4/5/6/7/8/9 EvoScan Project

Developer topics relating to software that logs data from ECUs

Moderator: Freon

Mitsubishi Lancer Evolution 4/5/6/7/8/9 EvoScan Project

Postby Evo4Mad » Tue May 02, 2006 8:27 pm

http://www.limitless.co.nz/evoscan

Event Log :
Sunday 5th July 2006 - EvoScan v0.8 PreRelease version released.
Sunday 26th June 2006 - EvoScan v0.7 PreRelease version released.

Project Goal:
To support all Mitsubishi MUT-II(JOBD)/MUT-III and Subaru SSM Protocol and Nissan datalogging protocol Models
Note: Only US DSMs/Eclipse and US EVO8/9 support the universal standard OBDII datalogging tools. For japanese imports, other standard OBDII dataloggers will not work. EvoScan is what you need. EvoScan still works with those US Models, although better and faster than the universal standard OBDII datalogging tools, since the Mitsubishi MUT-II(JOBD) Protocol runs 50% faster than ISO9141-2

Data Logger Features:
1) Drag, Drop, and Position any number of gauges onto the screen.
2) Custom selection of any of 10 cool looking gauges (or preconfigured dashboard)
ImageImageImageImage
3) Assign data logging item to each gauge.
4) Save/Load Gauge layout/config
5) Log data to csv (Excel) file.
6) Playback csv data log.
7) Log data to screen.
8. main EFI ecu data logging items (ABS/AYC/DTC ecu data items to follow)
9) Calculated Dyno figures and graphs: acceleration / torque / hp
10) AER A/F meter logging support
11) Realtime Graphing support
12) Alerting on data value minimum/maximum/rate of change Alerts by Background colour, and/or by custom alarm sound (wav file).

EvoScan Supported Hardware:
1) I will be putting up a cable for sale that is FT232BM USB cable for the EvoScan datalogger. ($65US) (for Evo7/8/9 I would recommend the OpenPort cable below as it supports EcuFlash factory ecu tuning)
2) OpenPort cable 1.3M uses a built in FTDI FT232BM USB-Serial adapter.
- Colby Boles - http://www.tactrix.com/ ($89US)
- advantage of this cable is that it supports ecuflash only for Evo7/8/9
3) HomeMade for Electronics minded people: beware not many OBDII cables support 15625baudrate.
What you can do is buy a FT232BM($20US+) based usb-serial adapter because this chipset supports any baudrate you like, the PC standard comport cant physically support 15625bps, with the usb adapter then convert the serial adapter voltage levels to obdII levels +0v/+12v using a optoisolater circuit like Andy Whittakers or Jeff Noxon, or use a MAX232 chipset circuit like MMCd.($20US)

EvoScan Registration:
1) EvoScan Registration will be $15US ($20NZ)
- this will allow me to purchase expensive third party charting and gauge controls to make this the best looking and best functioning datalogger around.
- with registration you will get unlimited future releases.
- if you want a new feature added, this will be added for you with priority.
- you will get emailed latest updates released every week.
- you get access to the source code (personal use only).
- Using this datalogger will allow you to successfully see what your car is doing before and after you use tools such as EcuFlash or Aftermarket Controllers such as SAFC-II to tune your car. And you can save and send your results to your openecu buddies to oggle over, and others with EvoScan can even play back your results without being plugged into a car.
- Using the alerting features of EvoScan could alert you to a bad tune or bad fuel, i.e Detonation Knock Counts, Temperatures, A/F ratios and potentially saving you your engine.

Supported Vehicles:
1) Mitsubishi Lancer Evo IV/V/VI/VII/VIII/IX (Any serial obdII adapter that will support 15625baudrate)
2) 2003 Mitsubishi Lancer OZ (thanks zlancerman) (180->200/total samples per second)
3) Other miscellaneous 1996+ Mitsubishi OBDII Vehicles (support to follow as people test it on their cars - I'm expecting a lot of these vehicles to already work with this software)
3) Subaru SSM protocol support to follow (Any serial obdII adapter that will support 4800baudrate)
4) Nissan vehicle (I have a lot of Nissan protocol information - support to follow)

Supported Operating Systems:
1) Windows XP SP2
2) Windows Server 2003 SP1
3) Windows Vista Beta 2

Source Code:
VB.NET 2003 - MS.NET Framework v1.1

Laptop Requirements:
Requires installation of USB FTDI drivers (installed with ecuflash, or download from www.FTDI.com)
Requires installation of MS.NET Framework v1.1
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=262D25E3-F589-4842-8157-034D1E7CF3A
Basically if it can run Windows XP fine, then the software should also be fine.

This tool will be specific to the initialisation and reading of data from Evos, but I will be making xml configuration files so you can load other cars also. XML file will be something like -> CarModel/ECUSytem/Mode/DataItem/
ValidMinValue/ValidMaxValue/Conversion/Units/FriendlyName/...
Last edited by Evo4Mad on Tue Jul 25, 2006 5:08 am, edited 32 times in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 02, 2006 8:29 pm

Priority data acquisition for the EvoScan:

TO DISPLAY AND RECORD
knock counter
a/f ratios
g-force sensors
rpm
speed sensor
throttle position
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 02, 2006 8:38 pm

This project will progress very rapidly as long as I can get the protocol worked out quickly.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 02, 2006 8:42 pm

Here is the initialisation sequence on the K Line:

http://forums.openecu.org/viewtopic.php?t=497
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 02, 2006 8:43 pm

Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 02, 2006 8:53 pm

EvoScan MUT-II Initial Raw Results at 10400baud

Dont forget to turn line wrap on :)

Since the baudrate was supposed to be 15,625 the log is full of garbage.

I am using the AndyWhittaker DIY Direct OBD2 ISO9141 optoisolated interface, which may or may not be suitable.
http://www.andywhittaker.com/ecu/obdii_hardware.htm
Last edited by Evo4Mad on Tue May 09, 2006 4:40 am, edited 2 times in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

About protocol

Postby YP » Tue May 02, 2006 10:34 pm

Yes, all what you write is working on MMC vehicles for US 1996+ and other markets 2001+. For example EVO5 for japan market don't understand that protocol. MMC use your own JOBD2 protocol on those vehicles with 15625 bps speed and 5 bps init with L line driving.
User avatar
YP
 
Posts: 35
Joined: Sun Feb 05, 2006 7:41 am

Postby Evo4Mad » Tue May 02, 2006 11:01 pm

No, I have a JAP mitsibishi MUT-II scan tool - ITS ALL in japanese I can only read the numbers - no english text :)
Last edited by Evo4Mad on Wed Aug 16, 2006 3:51 pm, edited 2 times in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Fri May 05, 2006 5:22 pm

There will be a problems with hardware for MMC logger because standart COM port can work on 5bps and can't work on 15625 bps. FT232 can't work on 5 bps and can work on 15625bps. I solve this dilemma by program my own interface using PIC microcontroller. If you planning to work with cars 2001+ you can use 10400bps. But Scope graph that you posted on forum reports, that the speed is 15625 bps. 0x00 is standart init byte for this speed. For 10400bps init byte is 0x33 at 5 bps.
YP
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Sun May 07, 2006 2:47 am

I spent a number of hours reading how serial ports on pcs work. I found they have a divisor setting to set the baud rate.

i.e 115,200 / x = baudrate

Divisor - Baudrate
6 - 19200
7 - 16457.14
8 - 14400
9 - 12800
10 - 11520
11 - 10472.73
12 - 9600

closest to 15625 baud is
16457 baud at 5.05% difference
14400 baud at 8.50% difference

5% difference is said to be max acceptable tolerance in most cases.
but should work ok.

I can successfully read this response from the vehicle after 0x00 5bps init now:

at 16457baud: 0x55 0xEF 0x85

also the EFI diagnostic dash light stops flashing after the init sequence
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Hitokiri » Sun May 07, 2006 8:11 am

The main piece of software for subaru select protocol has been released open source.

It would be nice to have your EVO logger and the subaru logger on the same product, and it might be wasier for you to write some code in this software rather than do your own from scratch.

http://www.tari.co.za/cgi-bin/yabb2/YaB ... 1142849753

check it out. It will already have all the storage and display done for you, you'll just have to make an option to modity the data collection for the evo init sequences and baud rate changes.
Hitokiri
 
Posts: 80
Joined: Fri Dec 31, 2004 6:55 am

Postby Evo4Mad » Mon May 08, 2006 1:24 am

ok thanks, although my first goal is to understand the protocol. And yes I can progam in c++, not very well but I can copy other functions and make them work.
Last edited by Evo4Mad on Wed Aug 16, 2006 3:51 pm, edited 2 times in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby YP » Mon May 08, 2006 3:20 am

Evo4Mad wrote:
closest to 15625 baud is
16457 baud at 5.05% difference
14400 baud at 8.50% difference

5% difference is said to be max acceptable tolerance in most cases.
but should work ok.



Port speed must be 3% or less from original baudrate to exchange with coreect data. On 16457bps will be approx. 30% errors when sending/receiving in last bit in a byte. I tried this.
Dig the FT232 DLL driver datasheet to run the chip at 5 bps. It will be correct.
User avatar
YP
 
Posts: 35
Joined: Sun Feb 05, 2006 7:41 am

Postby Evo4Mad » Mon May 08, 2006 5:18 pm

I see your point, I would prefer to program a PIC chip to do this.

do you have any schematics and assembler/hex compiled pic code to do this baud rate conversion?
Last edited by Evo4Mad on Wed Aug 16, 2006 3:52 pm, edited 1 time in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Postby Evo4Mad » Tue May 09, 2006 4:36 am

My PC Com port is reading codes 100% perfectly. (for now)

1ms send 4ms wait 1ms response
we should get abour approx. 150 samples per second
Last edited by Evo4Mad on Mon Jun 19, 2006 7:47 am, edited 2 times in total.
Evo4Mad
 
Posts: 332
Joined: Mon Jun 13, 2005 11:58 pm
Location: New Zealand

Next

Return to Data Logging Software

Who is online

Users browsing this forum: No registered users and 4 guests