ECUFlash / Evoscan / Mitsulogger Questions
#946
Evolving Member
iTrader: (3)
Joined: May 2008
Posts: 472
Likes: 0
Received 0 Likes
on
0 Posts
From: Utah
The baud rate comes standard at 15625...make sure that whatever load factor you are using in ecuflash its the same in evoscan (so since you're at 1.2 make sure your rom has 1.2 load factor)
Also, did you copy in the necessary info in your evoscan's data.xml?
Make sure you have the correct MUT address to be able to log 1 byte load too...all that is in the instructions when you download the Tephra rom.
Also, did you copy in the necessary info in your evoscan's data.xml?
Make sure you have the correct MUT address to be able to log 1 byte load too...all that is in the instructions when you download the Tephra rom.
ps baud rate was also fine in evoscan
#947
Evolved Member
iTrader: (3)
I'm new to evo tuning. I have done some tuning using my stock lancer oz ecu. My friend asked my to change his stationary rev limit from 5500 to 5000. (05 Evo) once changed, note That was the only change i did on the tune. Well after the adjustment the car would die, Every time the clutch was depressed at low rpms. I raised the limit back up and the car is now fine. Any idea's on what would cause this? Thanks sorry if its a noobish question.
#948
Hi all,
Will evoscan be able to remap the Galant VR4 (6A13TT) Ralliart edition? I know that there is no way to remap standard VR4, however, Ralliart provides different ECU? Is this correct?
Will evoscan be able to remap the Galant VR4 (6A13TT) Ralliart edition? I know that there is no way to remap standard VR4, however, Ralliart provides different ECU? Is this correct?
#949
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
Received 0 Likes
on
0 Posts
From: Connecticut / Vermont
I'm new to evo tuning. I have done some tuning using my stock lancer oz ecu. My friend asked my to change his stationary rev limit from 5500 to 5000. (05 Evo) once changed, note That was the only change i did on the tune. Well after the adjustment the car would die, Every time the clutch was depressed at low rpms. I raised the limit back up and the car is now fine. Any idea's on what would cause this? Thanks sorry if its a noobish question.
#951
Evolved Member
iTrader: (1)
you do have to connect the datalogger to actuate the SAS solenoid.
from memory, if you're on the main EVOScan screen I think its the button on the bottom right corner that brings you to another menu with a bunch of buttons. the 'acuator' button is in the top row, center, but more towards the left. When you press that you'll have to scroll over to get the EFI actuators. from there its the one all the way down the list at the very bottom. I wish I brought my car to work today, if so I would be able to tell you exactly where it is.
from memory, if you're on the main EVOScan screen I think its the button on the bottom right corner that brings you to another menu with a bunch of buttons. the 'acuator' button is in the top row, center, but more towards the left. When you press that you'll have to scroll over to get the EFI actuators. from there its the one all the way down the list at the very bottom. I wish I brought my car to work today, if so I would be able to tell you exactly where it is.
Okay, started logging, found the button...but nothing shows up when I click it? It looks as tho there should be a list of actuators to pick from in some sort of menu, but there's nothing there...just a blank menu. Is there some sort of add-on i should be installing? Or maybe an older version of evoscan...?
#952
I have a newb question..
Im pretty new at tuning and currently have ecuflash and evoscan. I have been trying to log evoscan information so I can start adjusting timing, fuel, boost, etc however the program isnt exactly user friendly and was just looking for some sort of information that would guide me through using the program. I read the sticky about how to tune your evo, the only problem is the cells in my logs dont fill correctly and dont look like any of the examples the OP posted. Im sure this is user error on my part, however like I said Im not entirely sure what options to use on the program. I have it set to EFI and I have it displaying all the parameters the OP of that thread recommended.
Also I have an evo IX if this helps clarify anything.
Im pretty new at tuning and currently have ecuflash and evoscan. I have been trying to log evoscan information so I can start adjusting timing, fuel, boost, etc however the program isnt exactly user friendly and was just looking for some sort of information that would guide me through using the program. I read the sticky about how to tune your evo, the only problem is the cells in my logs dont fill correctly and dont look like any of the examples the OP posted. Im sure this is user error on my part, however like I said Im not entirely sure what options to use on the program. I have it set to EFI and I have it displaying all the parameters the OP of that thread recommended.
Also I have an evo IX if this helps clarify anything.
#953
I have an AEM wideband serial>usb, I can log the wide band external but it only reads it for about 5 secs then it stops and freezes on the last afr reading.. evoscan still works fine, only the "external wideband" section locks up.
does anyone know how to fix this? ive tried v2.5 and v2.8 and they both do the same.
does anyone know how to fix this? ive tried v2.5 and v2.8 and they both do the same.
#955
Evolved Member
iTrader: (18)
I wired my AEM wideband directly to the ecu. I can successfully log in Evoscan with it, however i can only view the data in excel form. If i choose to view the log in a graph i can not get the AFR data to appear..very strange. Anyone have any ideas? thanks in advance!
#956
hey guys i have a mitsubishi FTO and i'm new to this ecu reading thing. i've brought the evo scan program and i've brought a OBD2 cable with a usb end to connect to my laptop. and when i connect it all up it tells me its connecting and reading but then it tells me it can note read the ecu can someone give me some guidence please i'm just trying to find the error codes so i can pass them on toget my car fixed thanks
#957
hey guys i have a mitsubishi FTO and i'm new to this ecu reading thing. i've brought the evo scan program and i've brought a OBD2 cable with a usb end to connect to my laptop. and when i connect it all up it tells me its connecting and reading but then it tells me it can note read the ecu can someone give me some guidence please i'm just trying to find the error codes so i can pass them on toget my car fixed thanks
There is an easy way to read FTO ECU error codes, using just one wire! Details are here.
If you want to go R&D-crazy, there is an FTO ECU disassembly/table-discovery session going on right now over at GeekMapped.com, here. I found that quite by accident just the other day, as luck would have it!
Hope this helps!
Rich
#958
Evolved Member
iTrader: (34)
Has anyone else had issues with evoscan 2.8 and windows 7 while logging? Usually it would give me a FID -4 error and stop logging. Lately it hasn't been doing that but now it just prints out jibberish randomly. Like I'll be idling, start the car and log, it logs fine for 5 seconds, and then random numbers come up and its like its frozen at them. Ex: it will say I'm doing 58mph, knock of 38, load 0, rpm 1031, tps 0%, timing -14....all while just idling. And once it does this the numbers stay the same for the whole log. It will do this while idling, cruising, during a pull, anytime pretty much. External wideband always reads correctly though. I need to stop and restart evoscan, and then I really don't know how much time I have until it does it again. Can be right when I start, or 2mins later. So random.
Anyways its really hard to tune my car when its doing this. Anybody else run into this problem? Is there a solution? I tried logging with/without superspeed and cpu timer fix but no difference. This is on a 1.3u cable btw.
Side note: is it just me or did 2.6 seem way more reliable? I once logged a whole 25min track session with no problems. 6mb of .csv data!
Anyways its really hard to tune my car when its doing this. Anybody else run into this problem? Is there a solution? I tried logging with/without superspeed and cpu timer fix but no difference. This is on a 1.3u cable btw.
Side note: is it just me or did 2.6 seem way more reliable? I once logged a whole 25min track session with no problems. 6mb of .csv data!
#959
Hi. That's a left-field question - esp. on an Evo-centric forum! Nevertheless...
There is an easy way to read FTO ECU error codes, using just one wire! Details are here.
If you want to go R&D-crazy, there is an FTO ECU disassembly/table-discovery session going on right now over at GeekMapped.com, here. I found that quite by accident just the other day, as luck would have it!
Hope this helps!
Rich
There is an easy way to read FTO ECU error codes, using just one wire! Details are here.
If you want to go R&D-crazy, there is an FTO ECU disassembly/table-discovery session going on right now over at GeekMapped.com, here. I found that quite by accident just the other day, as luck would have it!
Hope this helps!
Rich
#960
I think your best bet is to register on GeekMapped.com and look up RichardB's thread.
Or just hook up that special pin/wire on the link I gave you! That'll flash any stored ECU codes using the check-engine light.
Good luck keeping that FTO healthy... they are cracking good cars!
Rich