ECUFlash / Evoscan / Mitsulogger Questions
Dec 30, 2006, 07:02 PM
#61
Evolving Member
iTrader: (13)
Join Date: Jul 2006
Location: Hawaii
Posts: 460
Likes: 0
Received 0 Likes
on
0 Posts
sorry for the newb question
but how can you record or save the data logged by mitsulogger or is that a feture evoscan has?
cause i wanna record my logs to send to a tuner but cant seem to figure it out
and again sorry
but how can you record or save the data logged by mitsulogger or is that a feture evoscan has?
cause i wanna record my logs to send to a tuner but cant seem to figure it out
and again sorry
Dec 30, 2006, 07:06 PM
#62
The files are already saved to the location specified (either default where you placed the program, or you can change it)
both Mitsulogger and Evoscan save logs to disk whenever their logging
You just take the files you collected and send them with any other relevent info to your tuner.
both Mitsulogger and Evoscan save logs to disk whenever their logging
You just take the files you collected and send them with any other relevent info to your tuner.
Jan 3, 2007, 11:31 PM
#67
I have the PLX R-500 and tried to datalog with it and Mitsulogger at the same time. Well I started the PLXLogger and then tried to start Mitsulogger and Mitsulogger will not work. I stopped PLXLogger and tried again it wont recognize the cable. Ecuflash and Evoscan dont work either. I tried to reinstall Mitsulogger and Ecuflash and they wont work. The Tactrix cable is assigned COM8 and the PLX uses COM7.
I haved used both dataloggers simultaneously before with no problems, but that was with Ecuflash 1.29. I am now using 1.29a. I know the driver was updated for the Tactrix cable and I think that is the problem.
Could someone please explain to me how to fix this? Thank you in advance.
I haved used both dataloggers simultaneously before with no problems, but that was with Ecuflash 1.29. I am now using 1.29a. I know the driver was updated for the Tactrix cable and I think that is the problem.
Could someone please explain to me how to fix this? Thank you in advance.
Jan 4, 2007, 12:32 AM
#68
Its likely that the driver for the PLX (Serial port) and driver for the Tactrix cable are now the same exact version, and therefore show up in the same "Chain" when their enumerated by Evoscan/Mitsulogger/ECUFlash
As far as I know, very little error checking is done when detecting the cable (my personal program detects the first FTDI device, not checking the serial number of the device.
ECUFlash and Mitsulogger does not use serial ports, it addresses the cable directly, therefore as long as the drivers function correctly, if you unplug the PLX serial port, everything SHOULD work, if it does not, then its likely a driver problem.
Is the PLX a USB device? or does it plug into the serial port? The order it detects the devices sometimes wreaks havoc if the applications don't adequately verify the right device.
The good news is I have fixed this in a new release of Mitsulogger v1.5, the bad news is it'll be at least 2 weeks before I'll know when I will be releasing it.
My guess is PLXLogger is doing the exact same thing, as they probably developed their code from the same FTDI sample code that most of us started with.
As far as I know, very little error checking is done when detecting the cable (my personal program detects the first FTDI device, not checking the serial number of the device.
ECUFlash and Mitsulogger does not use serial ports, it addresses the cable directly, therefore as long as the drivers function correctly, if you unplug the PLX serial port, everything SHOULD work, if it does not, then its likely a driver problem.
Is the PLX a USB device? or does it plug into the serial port? The order it detects the devices sometimes wreaks havoc if the applications don't adequately verify the right device.
The good news is I have fixed this in a new release of Mitsulogger v1.5, the bad news is it'll be at least 2 weeks before I'll know when I will be releasing it.
My guess is PLXLogger is doing the exact same thing, as they probably developed their code from the same FTDI sample code that most of us started with.
Jan 15, 2007, 05:22 AM
#69
Evolving Member
iTrader: (5)
Join Date: Sep 2005
Location: Oradell, NJ
Posts: 221
Likes: 0
Received 0 Likes
on
0 Posts
First of all... Thanks to everyone for sharing your wisdom.
I'm using Mitsulogger, now that I am ready for a mail-in flash, and I hope you can answer a few questions.
1) In order to increase the recording frequency, I have removed many of the Log references, but what are the minumum references that I should measure for a good snapshot of performance before and after a Mail-in Flash?
2) When recording logs, I know to capture WOT in 3rd gear. Someone mentioned that you should start out at 2k RPMs, and take it to redline, but at 2k RPM the engine is bogged down at WOT. What is the best technique to record the best log?
Many Thanks
My-Red-RS
I'm using Mitsulogger, now that I am ready for a mail-in flash, and I hope you can answer a few questions.
1) In order to increase the recording frequency, I have removed many of the Log references, but what are the minumum references that I should measure for a good snapshot of performance before and after a Mail-in Flash?
2) When recording logs, I know to capture WOT in 3rd gear. Someone mentioned that you should start out at 2k RPMs, and take it to redline, but at 2k RPM the engine is bogged down at WOT. What is the best technique to record the best log?
Many Thanks
My-Red-RS
Jan 15, 2007, 06:31 AM
#70
The basics are what is needed to calculate load, Knock Sum, timing value, MAF, a few others. Honestly the frequency rate even with everything logging is more than adequate for the rate at which the mut values are updated.. Just uncheck stuff that you clearly don't really need. I find the more analysis I do, the more useful all the values (maybe a handful aren't useful to me) become.
In other words, leave most of it intact until you start analyzing data and can really "toss out" the things you really feel you don't need.
Generally a "Dyno Pull" is done from about 2000rpm, its actually a useless portion of the power band, but it gives an indication of the spool of the turbo under load. Its not essential, but it makes tuning the 3000rpm area where the turbo does like being easier. When I tune, I get the baseline tune doing that, but I do later pulls after my rough tune at different RPMs and loads/throttle positions so I can tune the entire map.
In other words, leave most of it intact until you start analyzing data and can really "toss out" the things you really feel you don't need.
Generally a "Dyno Pull" is done from about 2000rpm, its actually a useless portion of the power band, but it gives an indication of the spool of the turbo under load. Its not essential, but it makes tuning the 3000rpm area where the turbo does like being easier. When I tune, I get the baseline tune doing that, but I do later pulls after my rough tune at different RPMs and loads/throttle positions so I can tune the entire map.
Jan 15, 2007, 07:34 AM
#71
Evolving Member
iTrader: (5)
Join Date: Sep 2005
Location: Oradell, NJ
Posts: 221
Likes: 0
Received 0 Likes
on
0 Posts
MalibuJack... Your the man!!!
Thanks...
Thanks...
The basics are what is needed to calculate load, Knock Sum, timing value, MAF, a few others. Honestly the frequency rate even with everything logging is more than adequate for the rate at which the mut values are updated.. Just uncheck stuff that you clearly don't really need. I find the more analysis I do, the more useful all the values (maybe a handful aren't useful to me) become.
In other words, leave most of it intact until you start analyzing data and can really "toss out" the things you really feel you don't need.
Generally a "Dyno Pull" is done from about 2000rpm, its actually a useless portion of the power band, but it gives an indication of the spool of the turbo under load. Its not essential, but it makes tuning the 3000rpm area where the turbo does like being easier. When I tune, I get the baseline tune doing that, but I do later pulls after my rough tune at different RPMs and loads/throttle positions so I can tune the entire map.
In other words, leave most of it intact until you start analyzing data and can really "toss out" the things you really feel you don't need.
Generally a "Dyno Pull" is done from about 2000rpm, its actually a useless portion of the power band, but it gives an indication of the spool of the turbo under load. Its not essential, but it makes tuning the 3000rpm area where the turbo does like being easier. When I tune, I get the baseline tune doing that, but I do later pulls after my rough tune at different RPMs and loads/throttle positions so I can tune the entire map.
Jan 15, 2007, 10:11 AM
#72
i have a question,
i downloaded ecuflash from openecu.org to my laptop then i run the program and it says that i can know use my tactrix cable ok(ready to use), then i connect my tactrix cable to my laptop and inmediately it says new harware found i install it again and again and it always says that this new hardware my not work properly i then again run ecuflash and with cable connected at the end it says that tactrixcable failed to connect!
so what is wrong with my laptop? i installed it in my home computer an it works but not with my laptop? is there something iam missing here?
i downloaded ecuflash from openecu.org to my laptop then i run the program and it says that i can know use my tactrix cable ok(ready to use), then i connect my tactrix cable to my laptop and inmediately it says new harware found i install it again and again and it always says that this new hardware my not work properly i then again run ecuflash and with cable connected at the end it says that tactrixcable failed to connect!
so what is wrong with my laptop? i installed it in my home computer an it works but not with my laptop? is there something iam missing here?
Jan 15, 2007, 07:26 PM
#74
Evolving Member
iTrader: (4)
Join Date: Sep 2006
Location: Here
Posts: 247
Likes: 0
Received 0 Likes
on
0 Posts
1. Is there any benifit by using Innovate LC-1 over the Innovate LM-1 ? I allready have EcuFlash, Mitsulogger, EcuScan, ect. I am just looking for a wide band now, and have either at my disposal. thanks
Jan 15, 2007, 08:53 PM
#75
ok update: i got my laptop to work with my tactrix cable i had to repair some files on windows xp.
know my problem is that when i connect my tactrix cable to my car it says that the wizard cant help me install anything cause it doesnt recognize the rom of my ecu
my car is a jdm model evo8 rs
so what i did is i said to it to inherit it from the 2005 usdm evo8 which it did it reads out the images ok know but iam not sure if its ok what i did?
anyone else with jdm evos tried using ecuflash?
thanks
know my problem is that when i connect my tactrix cable to my car it says that the wizard cant help me install anything cause it doesnt recognize the rom of my ecu
my car is a jdm model evo8 rs
so what i did is i said to it to inherit it from the 2005 usdm evo8 which it did it reads out the images ok know but iam not sure if its ok what i did?
anyone else with jdm evos tried using ecuflash?
thanks