We have these new kids on the block so I decided to make one thread that gathers all the information about them in one place. As of now, the latest version of EvoScan (EvoScan OBDII Mitsubishi MUTII DataLogger Scantool) is 2.5, and the latest version of EcuFlash (EcuFlash - OpenECU) is 1.38 Lets look at the EvoScan first EvoScan is a dataloging software that you can buy for around 30$. It was used mostly by Evo and Impreza crowd, but it has also been verified to work on some DSMs. The 97 (metal) and 98/99 (plastic) DSM ECUs can be logged with a sample rate of 70-110 samples/sec using Mitsubishi/EFI settings, with timeout@1000 and baudrate@15625. Both 97 and 98/99 ECUs can be logged with Hybrid settings as well, with timeout@1000 and baudrate@15625. Dsm-onster reports (http://www.dsmtuners.com/forums/tun...-evoscan-ecuflash-tuning-3.html#post151651614) that some of the pre-97 ECUs can be logged at sample rates of ~100 samples/sec as well I had trouble achieving acceptable data rates or connect to older ECUs though, so Im still investigating. You can also log ABS ECU with EvoScan, but in order for it to work you need to get a cable without pin 9 from Limitless. Im not sure about how accurate the data from the ABS ECU is on DSMs though. I know I can connect to ABS ECU, but so far values were wrong for my 98/99 ECU, 96 ABS combination. Might be that my ABS ECU is fried though, because ABS light is on all the time. In order to use EvoScan, you need to connect your laptop to the car via the black large OBD2 plug only, if you have two plugs on your cable, the second one is for EcuFlash. EvoScan can also read and clear Diagnostic Trouble Codes and it has Actuators for injectors, fuel pump, some solenoids etc. Now the EcuFlash EcuFlash is free flashing software that allows you to read, modify and write ROMs to ECUs. So far mainly used by Evo and Impreza crowd, seems it has finally gained ability to flash 98/99 ECUs as well. GSXDNA in (http://www.dsmtuners.com/forums/tuning-engine-management/307561-new-ecuflash-1-38-2g.html) thread reports that he has managed to successfully flash the 99 ECU. Unfortunately, as it turns out, only the stock ROM can be flashed back for now (http://www.dsmtuners.com/forums/tun...14-evoscan-ecuflash-tuning.html#post151637356), there is probably a checksum that doesn't allow to flash back modified ROM easily. It also seems that there are problems with (early)98 ECUs, so you need a 98(late)/99 ECU to be able to read it. In order to read or write the ROM you will have to connect to your car using both plugs on the diagnostic cable, OBD2 and the Flash plug. Flash plug socket is only available on 98/99 cars as far as I know. If you swap the plastic ECU to an older car, you can add the socket or connect to ECU directly via pin 79 as reported by Ceddy in (http://www.dsmtuners.com/forums/tun...561-new-ecuflash-1-38-2g-2.html#post151634961) thread, but you still need an 98/99 ECU!!! So far I don't have information that would say that 97 ECUs are flashable. Pinouts for 2G can be found here: (http://www.dsmtuners.com/forums/articles-tuning-ecu/281763-2g-turbo-ecu-pinout-w-wire-colors.html) The 98/99 ECUs are based on H8 processors. Based on EcuFlash output GSXDNA posted (http://www.dsmtuners.com/forums/tun...07561-new-ecuflash-1-38-2g.html#post151604992), it must be H8/539F model. Here is the datasheet of the actual processor (http://www.xtreme3s.net/H8500/H8 539F.pdf) Ceddy in (http://www.dsmtuners.com/forums/tuning-engine-management/307561-new-ecuflash-1-38-2g.html) thread said, that Evo crowd has been learning the ROM contents of their ECUs using IDA disassembler (Hex-Rays IDA Pro Disassembler: What's new Page - version 5.3) which can be downloaded for free if you use it for noncommercial purposes. So it might be possible to learn what DSM ECUs do, the same way. I dont know if disassembling a ROM is legal though, and if you need additional data to do so. If you know something more, let me know. You can also learn a lot from ROM if you just look at it via HEX editor like (Freeware Hex Editor XVI32) A word of warning, if you are going to swap 96 ECU to 98/99 then you need to compensate for the CAS. 97/98/99 CAS is on the opposite side of the engine head, so signal is inverted, you have to swap plug wires and injector pins to compensate, here is what I did (http://www.dsmtuners.com/forums/tun...07561-new-ecuflash-1-38-2g.html#post151631922). I'm not 100% sure I didn't messed up, but the car runs fine so 99% that it's OK I'm also posting this link about all (most) available DSM ECUs for a reference (Eclipse Talon Laser Galant 3000GT Stealth ECU ID Reference). Additional information and uncertainties regarding data logging with EvoScan I am only starting to learn the datalogging so I will try to list all the options you can log with the EvoScan and what I think they do. So please send me PMs and/or post here if you know that the description is wrong, that option doesnt work on DSM ECUs or is calculated incorrectly. I hope we will be able to gather the ultimate tuning list this way real fast. Injector sizing One of the things that EvoScan doesn't detect automatically is injector sizing. By default it leaves it at 513. From discussion at (http://www.dsmtuners.com/forums/tun...561-new-ecuflash-1-38-2g-2.html#post151634961) it seams that it's best to enter the real value of the injectors you are running. Stock 2G-T and 1G-T/MT would need 450, stock 1G-T/AT would need 380. But please look at the dsm-onster warning below (http://www.dsmtuners.com/forums/tun...14-evoscan-ecuflash-tuning.html#post151635786), and do report back if you find out anything more. Logging options The EvoScan allows you to log following options: Throttle position sensor: Logs how open or shut the throttle valve is. I have yet to see a DSM where it displays less than 12% with accelerator fully released, so values of 12-100 seems to be normal. You can tweak the formula so that it starts from 0% if it bugs you. Engine RPM: Self explanatory. Battery level: Displays how much juice the ECU is getting, 13-15 is OK, anything below or above is probably bad. Airflow/Rev: ------no idea------ Coolant Temp: The temperature of the coolant, not sure from which sensor, I have a feeling that its from the one in engine block, although EvoScan says its from radiator. Air Temperature: Seems to display temperature of the air under the hood, but not after Turbo and intercooler MAF Air Temperature Scaled: Usually around 2 deg higher than air temp, could be under the hood temp as well Coolant Temperature Scaled: ------no idea------ Timing Advance: The timing advance in degrees, some guidelines of what to expect would be great. If someone knows the stock maps they could be a good reference point. As far as I know there are different maps for high octane and low octane operations and ECU can interpolate between them depending on knock. *my speculation* Air Flow: ------no idea------ Barometer: The barometric pressure that ECU sees. Target Idle RPM: ------no idea------ Fuel Trim Low: ------no idea------ Fuel Trim Mid: ------no idea------ Fuel Trim High: ------no idea------ O2 Feedback Trim: Supposedly the percent of fuel that ECU adds or subtracts from standard fuel map depending on O2 sensor response in closed loop. O2 Sensor: First O2 sensor, useless for tuning as its a narrowband and is used only during closed loop. Displays voltage that should be floating on idle and get saturated under heavy acceleration. O2 Sensor 2: Sensor behind the cat, shows constant 0v on my car all the time, although its there. Speed: Doesnt seem to work on (late)97 and floats even when car is standing still on my 96 car with 98/99 ECU. Still, 98GSXtreme07 reports that he had no trouble logging this parameter and that it's pretty accurate. He used Mitsubishi setting. Injector Pulse Width: ------no idea------ Injector Duty Cycle: ------no idea------ Fuel Consumption: Calculated value. Depends on duty cycle, rpm, injector pulse width, speed and other variables. If one of them is wrong, this one is wrong. Gear: Calculated value from speed and RPMs Air Volume: ------no idea------ (Boost) MAP: Boost pressure, I dont know how accurate it is. JDM MAP: Same as above but for JDMs? Wide Band AF: Data from external wideband attached to serial port of your laptop. Knock Sum: * ISC Steps: ------no idea------ Crank Signal Switch: ------no idea------ Idle Position Switch: Probably the sensor that tells the ECU that you have fully released the accelerator. Power Steering Switch: * AC Switch: * AC Relay Switch: ------no idea------ Inhibitor Switch: ------no idea------ AFRMAP: ------no idea------ Load Calculated: ------no idea------ Load11bit4: ------no idea------ ECU Load: Variable that displays the load of your engine, required for most graphs Injector Latency: ------no idea------ Load MUT 2 Byte Mod: ------no idea------ RPM MUT 2 Byte Mod: ------no idea------ Air Flow MUT 2 Byte: ------no idea------ Estimated g/Rev: ------no idea------ Estimated Lbs/Min ------no idea------ Estimated HP: Calculated HP, could be pretty accurate if you set up all the params like vehicle weight, gear ratios, etc, etc. Estimated TQ: Same as above, but torque E1 RAM: ------no idea------ E4 RAM: ------no idea------ Knock Voltage: On DSM you should look at Knock sum, this is meaningless Octane Level: This might indicate if youe ECU is switching to lower octane fuel map because of excessive knocking. knock_adc: ------no idea------ knock_base: ------no idea------ knock_var: ------no idea------ knock_change: ------no idea------ knock_dynamics: ------no idea------ knock_flag: ------no idea------ EGR Temp: ------no idea------ Wastegate Duty Cycle: ------no idea------ Load Error: ------no idea------ WGDC Correction: ------no idea------ ZTX /LC1 : External wideband data Custom: Custom requests to ECU As you see there are ton of things that I dont know yet, so if you know something, let me know. I will update the post so that we can have one place where to look for settings and formulas that are correct for our cars. I will update the post as soon as I discover something new as well.