I can indeed attest to this.. I was on the phone a few nights back discussing which of new parameters would be most useful..

 

Funny you mention that, some of these parameters require more deep decoding of how the CEL functions worked but they also came up in conversation since the rear 02 sensor, and P0300 code are two that people seem to have the most problem with.

 

I'm actually looking forward to this part, since I have the ability to write code, but no patience to disassemble things, once there's some documented reverse engineered code, I'd be more than willing to contribute some of my ideas for "Program segments"

Have you had the chance to look at the code for the MUT Diagnostic output stream? Figuring out how its formatted and how its triggered would help Donour alot in his quest to build a logger that can sample much faster than OBD-II..

 

one idea I had for example was adding code that can trigger a 0 or 255 value in the long term octane value cell, so you can forcibly switch between maps.. On the 03 and 04 ECU, that could be done with the switched input for the Intercooler sprayer..

 

That is what I use... MUT III to help develop the datalogger, and getting th axis scaling factors for the maps.

 

I know al can make dual maps?

 

Also If anyone can write up just a tutorial of disassembling 1 evo subroutine i can get a jumpstart into the rest.

I code in c# daily, have made things in c++/c and dealt with a little bit of low level memory location / reversing type stuff. My only lacking skill is not knowing the actual assembly language.

 

If I recall, thats different, I think he's rescaling the sensor so the higher boost has a few columns for tuning, and then he tunes a low boost map in a lower column.. so you have a 23psi tune in a set of lower boost cells, and the high boost map in a higher set of columns.. Its actually pretty common to see this type of tuning in other cars and using standalones where you might run different boost levels and not have the luxury of easily switching maps.

 

Not really. He just sets the maps up with differnt tunes dependant on what load range the engine is running. Lower boost will run in a lower load range... turn up the boost and you're running the tables in a differnent area/range. So, it's not really duel maps. No offense Al, I hear it works great.

 

that should be a two way street. how about you share some of your info...

 

Al uses EcuTek. I don't think its his info to share? and as far as i know he's been good about sharing what he can.

 

He uses both Techtom and EcuTek, but there may be a nondisclosure clause in his license to use EcuTek or Techtom so he might not be able to share.. I'm sure he will if he can.

 

I believe that Al uses Techtom more frequently than EcuTek. Mine was done twice with Techtom...as far as my probing eyes could tell.

 

I am sharing info every day on these forums on a whole host of subjects

 

It would be perfectly understandable if Al did not share ANY info on the subject of ECU flashing. Unlike most of us, this is how he makes his living.

I do think that he is smart enough to realize that with EcuFlash the price barrier that exsisted before with the TechToms EcuTecs, etc. is now gone and that he has to embrace the new business paradigm.