Since this software is plugged into an OBDII source, would we be able to get a "dashboard" setup monitoring critical engine data as one could via a palm/logger?

Further, where is the definition to activate the low octane map? Is it possible to activate the low octane map at a certain voltage and count of knock?

 

as far as I know, the octane value is like the fuel trims, and is programmatically shifted.. Thats why I said what I said.. Its probably not something you can permimantly write into and have it stick...

 

You already can use other OBD-II loggers to do that.. What the MUT diagnostic tool does is get the sensor data directly and the stream of data is not an obd-II stream... Yes, its sent through the obd-II port.. but it might as well be morse code because its not the same type of data that OBD-II uses.

An OBD-II port is basically a data port.. the typical data is a standard communication protocol, but it doesnt mean thats the only kind of data that you can get out of the ECU. I think that is where most of the misunderstanding is coming from..

 

understood.

I guess I'm just comparing it to the Hondata Kpro Ecu that I had on my Civic Si.

It was an EM software that had logging and monitoring capability, along with the features ECUFlash currently has. I can't expect same level of refinement and polish from ECUFlash but I was thinking it would be nice to have some of the important features.

Besides, if it's going to have logging capability soon, I'm assuming it will need to start reading some of the OBDII info anyway, correct?

 

According to Jason, there is an octane value ranging from 0 to 255. The knock sensor determines this value. A value of 0 would pull from the high octane/ignition map and 255 would pull from the low octane/ignition map with fazing over as the number moves between the two.

 

Couple IX Questions

I understand the reasoning by the High Octane and Low Octane maps but what is the reasoning between Ignition map 1, 2, & 3?
Also why would the Low Octane Fuel Map be leaner than the High Octane? Just less timing?
Lastly not to slow colby "the man" down but any ETA on the IX flashing capabilities?

Thanks

 

 

Exactly, if EcuFlash can get at least to within the same ballpark as K-pro it would be the best thing to happen since Mitsu brought the evo to the states.

Hats off to Colby, Jason and the guys behind the scenes for developing and releasing a program for the evo community.

 

Honestly its only a matter of time before someone completely disassembles and then rewrites the ECU's rom to give you features that are more like the DSMLink or Hondata's offerings..

 

 

Most definitely. From what ive read they are only 45% done and project completion within 6 months or so. Can't freakin wait.

 

ok im a newb to tuning so bear with me....can I use this guy's high octane map? i mean the values are the ideal AFR for rpm x load....so this looks good for most setups? because the stock map gets as rich as 8.8 in high load and rpm....so why wouldnt it be ok to use this guy's hi octane map?

 

I believe those afr's are based off the stock car, so any changes to that would throw the stock calculations of afr off? Always tune with a wideband.

 

The values are based almost enitely off of the stock car there have been a few weird blibs in the cells that have been smothed out.

I have another tune that i have been working on that i can tune with MUCH higher octane and leaner AFR's. The car is really moving with no signs of knock.

 

The maps 1 - 2 & 3 are active under different operating conditions

You have to operate the car and observe the timing to understand when the car is in each mode

Each of the 3 modes has a high octane and low octane mapping

If you are seeing a leaner fueling in a "high octane" section it is poissible thet either your ecu has been already flashed and a mistake was made or that "definition" may be inaccurate