Which logger has the dynograph feature.
Thread Starter
Former Sponsor
iTrader: (73)
Joined: Dec 2005
Posts: 4,668
Likes: 1
From: Ft. Lauderdale, Fl
Which logger has the dynograph feature.
i wanted to compare my old map with my new map and i thought evoscan had it but i cant find it...
what other logger is there?
what other logger is there?
Thread Starter
Former Sponsor
iTrader: (73)
Joined: Dec 2005
Posts: 4,668
Likes: 1
From: Ft. Lauderdale, Fl
Trending Topics
I see you talking about ECU+ all the time..... but what does it really offer the average poor evo owner (not the spoiled brat).
Say I have:
ECUFlash
EVOScan
LC1
What is the cost benefit of ECU+ in this situation?
Say I have:
ECUFlash
EVOScan
LC1
What is the cost benefit of ECU+ in this situation?
the stock ECU will never be capable of giving you data in an unclipped manner, plus the values are interpolated and therefore not accurate as if it were output without any modification.
The ECU+ shows you IPW, IDC, MAF reading, Timing, Knock sensor voltage, RPM, all this data as an actual value, not an interpolated value.
What does this mean? Well, RPM is a good example of the interpolation of data, the output of the logger (Evoscan or Mitsulogger, or any MUT logger) is a value from 0-254, which has to represent an RPM value to 8000 or so (any higher and its clipped) so each step in RPM is not the actual RPM value, but some interpolation of what it is.
It gets more interesting, ECU has a load value, and its determined internally, which is what we should be using, only it has a value from 0-254, representing load from 0-160 So, when you hit 160 your at maybe 7psi of boost, what happens at higher boost levels.
Now, take the MAF frequency, it clips completely at 1609.. So a value of 0-254 has to represent a value of 0-1609hz, Not only is it interpolated innacurately, but it clips at 1609hz (way lower than the evo typically hits with a boost controller and minor mods)
Internally to the ECU, the values are not clipped, and used to accurately work within the Rom, but when the data is output, its output is a single byte, and that single byte has to represent a ton of different things as scaling values, but if you take any of those formulas, and calculate a value for 1, 2, 3 ... 254, you'll see the steps involved.
The ECU+ does not have this limitation (neither does the UTEC, XEDE, etc, but the ECU+ has by far the best and most complete logging)
It doesn't mean you cannot do what you need to with just a wideband, and Tactrix cable and the software involved, but you'd be missing key bits of useful data that could help you more.
Most people don't understand that its OKAY to have several different logging tools running at the same time, as long as data can be correlated, either by time offset, RPM, etc.. Its just difficult for some to look at different graphs and put that data together in their mind.
The additional cost benefit of the ECU+ is being able to overcome things that are typically difficult to do with the ECU..
Getting your MAF frequency right at idle, to prevent stalling, altering the MAF curve to get your fuel trims in check after you have everything scaled as close as possible in the ECU, Removing the stock MAF and putting a blowthrough setup in its place, having an OBD-II scantool built into the hardware (not as critical with the Tactrix cable now that I found OBD-II software that works with it)
So.. If you add the great logger (logs wideband AFR, boost and EGT)($300-$400 for the Innovate equivalent), the built in scan tool ($100), the MAF Translator ($200-$300), the rear O2 simulator ($70), Idle stabilizer ($120), MAF and Timing fine-tuning, among other features, you can see how it replaces many additional tools/software/hardware that if you bought seperately would be more expensive and harder to work with as seperate components.
The ECU+ shows you IPW, IDC, MAF reading, Timing, Knock sensor voltage, RPM, all this data as an actual value, not an interpolated value.
What does this mean? Well, RPM is a good example of the interpolation of data, the output of the logger (Evoscan or Mitsulogger, or any MUT logger) is a value from 0-254, which has to represent an RPM value to 8000 or so (any higher and its clipped) so each step in RPM is not the actual RPM value, but some interpolation of what it is.
It gets more interesting, ECU has a load value, and its determined internally, which is what we should be using, only it has a value from 0-254, representing load from 0-160 So, when you hit 160 your at maybe 7psi of boost, what happens at higher boost levels.
Now, take the MAF frequency, it clips completely at 1609.. So a value of 0-254 has to represent a value of 0-1609hz, Not only is it interpolated innacurately, but it clips at 1609hz (way lower than the evo typically hits with a boost controller and minor mods)
Internally to the ECU, the values are not clipped, and used to accurately work within the Rom, but when the data is output, its output is a single byte, and that single byte has to represent a ton of different things as scaling values, but if you take any of those formulas, and calculate a value for 1, 2, 3 ... 254, you'll see the steps involved.
The ECU+ does not have this limitation (neither does the UTEC, XEDE, etc, but the ECU+ has by far the best and most complete logging)
It doesn't mean you cannot do what you need to with just a wideband, and Tactrix cable and the software involved, but you'd be missing key bits of useful data that could help you more.
Most people don't understand that its OKAY to have several different logging tools running at the same time, as long as data can be correlated, either by time offset, RPM, etc.. Its just difficult for some to look at different graphs and put that data together in their mind.
The additional cost benefit of the ECU+ is being able to overcome things that are typically difficult to do with the ECU..
Getting your MAF frequency right at idle, to prevent stalling, altering the MAF curve to get your fuel trims in check after you have everything scaled as close as possible in the ECU, Removing the stock MAF and putting a blowthrough setup in its place, having an OBD-II scantool built into the hardware (not as critical with the Tactrix cable now that I found OBD-II software that works with it)
So.. If you add the great logger (logs wideband AFR, boost and EGT)($300-$400 for the Innovate equivalent), the built in scan tool ($100), the MAF Translator ($200-$300), the rear O2 simulator ($70), Idle stabilizer ($120), MAF and Timing fine-tuning, among other features, you can see how it replaces many additional tools/software/hardware that if you bought seperately would be more expensive and harder to work with as seperate components.
Not true. EcuEdit has HP/TQ graphing built in. However, I didn't have much success with it at the standard MUT rate. The graph was very jagged. I haven't tried it at the modified data rate. I don't really think the increased rate will help much. I think the problem is the quantization error of the RPM reading. If we could get a 2-byte RPM reading, then it might work better.
I don't think ECU+ is limited by RPM quantization error. It probably works pretty good.
I don't think ECU+ is limited by RPM quantization error. It probably works pretty good.