| Message |
All of the Maps are contained on the Eprom chip.
JWT starts with new Eprom chip. They spent their time creating one set of maps which have been tried and proven to be better (safer) at higher levels of boost than the stock maps. Not optimal, but better. Instead of burning two seperate sets of maps on to the chip, they just double copied their one set maps that they put all their efforts into. Why?
Easier or did they just not realize the difference? Maybe they have some reason we just haven't stumbled over. I think there is a lot to learn from all the work JWT has done but I don't think they are the gods of ECU tuning. In my experiences with them they are close minded and very monopolistic, not to mention overpriced. None of which I blame them for from a business perspective, but I don't think it's impossible to develop a better product for a more reasonable cost.
It isn't that JWT was so malicious that they went in and removed the secondary maps from the computer. They just started with a blank Eprom and neglected to use the more conservative secondary maps. Yes during detonation, The JWT ECU still goes through the subroutine of retarding timing but that loss of power you feel is temporary and isn't the same thing as the secondary (low octane) maps that stock or Ash's ECU's revert to. I understand almost everything Ash is saying and it does all make sense, it is just very complicated. I have spent hours on the phone with him listening for my personal knowledge. I am an engineer but he blows me away sometimes. It is possible that Ash understands the theory behind all of this stuff better than the folks at JWT. I will agree that he doesn't know as much as they do about how it all works in real world situations, but we plan on working with him to help get there. Ash does this stuff because he loves it, making money at it doesn't even seem that important to him, and I respect that. I don't see that he has any reason to lie about the fact that both sets of their maps are the same. He has been telling me about that problem for months. In lieu of all of this JWT may get wind of it and correct it, unless they have some unknown explanation.
|
 |
