ECUFlash / Evoscan / Mitsulogger Questions
Anyways.. am having a problem.. everytime I try to read.. I get this message..
UNABLE TO CONNECT TO VEHICLE INTERFACE
I just recently installed the new Ecuflash version.. could this be it.. my dumb *** deleted the older version as per recommendation on the new startup wizard..
I demodified the evo a bit and wish to run a map more suitable for my mods..
Same with the calculatedload for the timing map which should not be confused with the load160 which tops out at 160.
The only way to get a completely accurate value is to get it from the Rom, there are ways to do that, but its documented elsewhere on this forum and aktivematrix.
Also, this was quoted from a much older post, as Mitsulogger does currently support most of the popular widebands. The currently released version does have a glitch in the LC-1 LM-1 support if you have multiple channels, I will be releasing a new version with that and several other fixes in the near future.
1) The application is being launched from the zip file, and has no support files for it to run. You need to extract all of the files to a directory and run it from there.
2) There are no tactrix drivers (or any FTDI Compatible drivers) installed whatsoever and therefore it can't initialize the driver component and fails. (If you never installed the cable, or drivers, this is the most common problem) I used to include an FTD2xx.dll file with mitsulogger, but discovered as there were driver updates and minor changes, that it sometimes would either conflict or not work, so I removed it. Since I did that, users who don't have any drivers installed have been experiencing the error.
How does one expand their base maps out to 300 load level? My stock maps stop at 260 and I would like to grow them to 300.
EDIT FOUND IT: https://www.evolutionm.net/forums/sh...d.php?t=211022
EDIT FOUND IT: https://www.evolutionm.net/forums/sh...d.php?t=211022
Last edited by EVIL_EV0; Apr 26, 2007 at 09:24 AM.
I missed this question, but most of the time its for two reasons... This really has been discussed quite a few times before..
1) The application is being launched from the zip file, and has no support files for it to run. You need to extract all of the files to a directory and run it from there.
2) There are no tactrix drivers (or any FTDI Compatible drivers) installed whatsoever and therefore it can't initialize the driver component and fails. (If you never installed the cable, or drivers, this is the most common problem) I used to include an FTD2xx.dll file with mitsulogger, but discovered as there were driver updates and minor changes, that it sometimes would either conflict or not work, so I removed it. Since I did that, users who don't have any drivers installed have been experiencing the error.
1) The application is being launched from the zip file, and has no support files for it to run. You need to extract all of the files to a directory and run it from there.
2) There are no tactrix drivers (or any FTDI Compatible drivers) installed whatsoever and therefore it can't initialize the driver component and fails. (If you never installed the cable, or drivers, this is the most common problem) I used to include an FTD2xx.dll file with mitsulogger, but discovered as there were driver updates and minor changes, that it sometimes would either conflict or not work, so I removed it. Since I did that, users who don't have any drivers installed have been experiencing the error.
Once you have your cable's drivers installed and sucessfully work with ECUFlash, you don't actually need the cable plugged in for the app to work. It just happens that without any drivers installed, its missing a required file for it to start up, and I inadvertantly forgot to put an error check for it at the beginning.
Once you have your cable's drivers installed and sucessfully work with ECUFlash, you don't actually need the cable plugged in for the app to work. It just happens that without any drivers installed, its missing a required file for it to start up, and I inadvertantly forgot to put an error check for it at the beginning.
I was experimenting with ECUFlash 1.3 in the hopes of being to mess with mitsulogger, but it is giving me the same message. Do I need to have ECUFlash running in order to run mitsulogger? I thought I read somewhere that you have to close ECUFlash in order to run mitsulogger.
I recently purchased a lap top for logging. What do you guys use to view the logs? I have used Excel in the past, Kinda hard to follow. Any imput on Data Log Lab? What do you guys suggest?
iam hitting at peak boost load calculation of 228 this is at 3900rpms by 6000rpms iam 185 and by 7000rpms it falls to 167 ive been reading and seeing people sustain higher load calculations then what my car does what causes this?
could it be that its cause iam at a higher altitude at 3300' above sea level i see my my boost drops to 17-18psi by redline?
thanks
could it be that its cause iam at a higher altitude at 3300' above sea level i see my my boost drops to 17-18psi by redline?
thanks
ok i think my problem is that the formula in evoscan has injectors scaled to 513 my jdm ecu has them scaled to 543 so how do i change the formula in evoscan?
also does my injector scailing which is 543 have an effect on knock sums and timing?
thanks
also does my injector scailing which is 543 have an effect on knock sums and timing?
thanks








