View Poll Results: Overall, who do you think is the best at mail in/e-mail flashes?
Dynoflash



77
16.45%
Jestr



168
35.90%
TTP Engineering



160
34.19%
Vishnu



36
7.69%
WORKS



27
5.77%
Voters: 468. You may not vote on this poll
VOTE please - e-mail/mail in flash POLL
I haven't tried one of those e-mail tunes but was custom road tuned by scott @ ttp and my car is running so much better and faster than before without going too aggresive on the tune.
I have also seen cars tuned by jester and he really does a great job tuning these cars as well.
Whichever tuner you choose I bet the results will be great and don't forget to let them know about any problem you may encounter okay!
I have also seen cars tuned by jester and he really does a great job tuning these cars as well.
Whichever tuner you choose I bet the results will be great and don't forget to let them know about any problem you may encounter okay!
1. Max out the turbo limit tables effectively preventing the ECU from cutting boost in case of boost surge
2. Remove the boost delay timer which means that the ECU does not have the stock 1000 ms to cutoff boost in case of a surge
3. Max out the BDEL tables which lead to a lack of control over how the boost behaves under different load conditions
4. Max out the WGDC tables which means that the wastegate is supposed to stay shut all the time. This is not really possible, so why do it.
I have seen 3-4 Jestr maps and they all have the same boost tune. These are dangerous practices IMO. If you get any form of a boost surge then your engine is toast.
Good points
1) No block tuning - Block tuning can be very effective. I utilized this method several years ago when I was flashing on a much more primative HEX editor which did not allow for as much precision as the current tuning applications afford. I not longer utilize the block method in any of my tuning calibrations (for well over a year)
1) No block tuning - Block tuning can be very effective. I utilized this method several years ago when I was flashing on a much more primative HEX editor which did not allow for as much precision as the current tuning applications afford. I not longer utilize the block method in any of my tuning calibrations (for well over a year)
You used to block tune before the widespread availability of ECUflash. When Ecuflash became widely available and people started seeing your block tuning you stopped doing it.
(2) Boost limits set - setting a boost limit usualy winds up with a frustrated customer when they go to the track on race fuel and try to run high boost levels. Most of my pump gas maps will work very well on race gas at up to 30 psi (stock turbo spike). Customers are suggested to watch the boost guage and not over boost - or get a ebc with overboost warning cut off. I will provide a lower boost limit to any customer upon request - no problem. I stopped putting one in after a lot of customers would run into the limit when they went racing.
Telling you customers to watch the boost gauge might be too little too late in case of a boost surge or a malfunctioning wastegate.
(4) Different Fuel and Timing maps for High / Low (Knock) This is NOT needed - BUT I have been doing this also for a year now as I found most customers wanted this additional protection.
Last edited by nj1266; May 10, 2007 at 08:27 AM.
Block tuning is troublesome. It should not be done. The stock ECU is a model of tuning style (not content) and it is to be emulated when tuning. Does the stock ROM block tune in the WOT sections. NO, and neither should the tuner. There is a reason why the timing is lower when the load gets higher under WOT conditions and tuners are advised to follow the same style szet by Mitsu in the stock rom. Block tuning prevents the ECU from finding the lower timing cell as load increases. Block tuning is for the tuner who does not want to put the time to match the load and rpms logged to the load and rpm in the timing and fuel maps.
You used to block tune before the widespread availability of ECUflash. When Ecuflash became widely available and people started seeing your block tuning you stopped doing it.
Again that practice is very dangerous. Jestr does this and it seems you do too. Rather than remove the limits you should tell your customers to get TWO maps one for racing and one for daily driving. I know that might might hurt your business, but it is the right thing to do.
Telling you customers to watch the boost gauge might be too little too late in case of a boost surge or a malfunctioning wastegate.
It is VERY much needed. It is a safety feature that Mitsu built in the ECU for a reason. These maps are there to protect the engine in case of a bad gas tank or severe knock problems. As a general rule the lower octane ignition and timing maps should be left untouched. There is no reason to mess with them. A well tuned car should not use the low octane maps anyway.
You used to block tune before the widespread availability of ECUflash. When Ecuflash became widely available and people started seeing your block tuning you stopped doing it.
Again that practice is very dangerous. Jestr does this and it seems you do too. Rather than remove the limits you should tell your customers to get TWO maps one for racing and one for daily driving. I know that might might hurt your business, but it is the right thing to do.
Telling you customers to watch the boost gauge might be too little too late in case of a boost surge or a malfunctioning wastegate.
It is VERY much needed. It is a safety feature that Mitsu built in the ECU for a reason. These maps are there to protect the engine in case of a bad gas tank or severe knock problems. As a general rule the lower octane ignition and timing maps should be left untouched. There is no reason to mess with them. A well tuned car should not use the low octane maps anyway.
In most cases the so called block areas which people have complained about are in map areas the car never operates in
For example 1000 rpms full load - the car will never run full load at 1000
In any event, as I suggested the Tech Tom equipment was not as condusive to fine precise ignition mapping so that was why I adopted the block method - which I may add produced really good results while I did it - with zero problems of engine failure.
Its really a moot issue as I no longer employ the block method - (expect on my own vehicle) as the new tools are much easier to work about and pin point the load zones the car is in.
I will also point out that your argument is moot for a car which runs at the last collum of the load on the maps (which many cars do) as when its on WOT it runs down the highest load cells.
As for boost limits - I stated why I do it above
I have tuned more than 4,000 evos (I stopped counting)
To this date we have not lost any motors that I know of from over boosting
100% of customers are advised that the fuel cut over bost protection is removed - if they want a lower limit then I can provide that at no extra charge but if they go to the track and try to run higher boost on race gas (which my maps are designed to accomidate) then they will hit the fuel cut.
I concur that a well tuned car will never tough the low octane maps and before it does the ecu will have already pulled the timing down to negative values which renders those maps virtualy moot.
Back in the day I set them the same for a specific reason which related to check sum calculations in the ecu and cars which ran very high boost levels off the end of the load.
Its really a moot issue as I have explained - for the past year and change I have been setting the low octane maps lower (I dont use stock ones - I make up custom ones for the particular car)
I appreciate your arm chair tuning advice and suggestions - however - in the real world in which I have tuned thousands of cars with very reliable and safe results it seems that the practice has worked very well - this despite your theoretical concerns.
Regardless, most of these points are moot as I have adopted many of these changes as my customers were concerned about these type of comments so I just started to do some of these style of maps to make my customers happy.
Its no longer an issue in my product at least.
AL
Last edited by DynoFlash; May 10, 2007 at 04:22 PM.
Its really a moot issue as I no longer employ the block method - (expect on my own vehicle) as the new tools are much easier to work about and pin point the load zones the car is in.
I will also point out that your argument is moot for a car which runs at the last collum of the load on the maps (which many cars do) as when its on WOT it runs down the highest load cells.
As for boost limits - I stated why I do it above I have tuned more than 4,000 evos (I stopped counting) To this date we have not lost any motors that I know of from over boosting
I concur that a well tuned car will never tough the low octane maps and before it does the ecu will have already pulled the timing down to negative values which renders those maps virtualy moot.
I appreciate your arm chair tuning advice and suggestions - however - in the real world in which I have tuned thousands of cars with very reliable and safe results it seems that the practice has worked very well - this despite your theoretical concerns.
It has been well documented that you ran as of 88888888 degrees of timing in the lower rpm WOT sections of the map. This has been well documented. It is not in the sections of the map that the car never sees.
I am glad that you stopped using this method, but you only did that AFTER you were flamed heavily for using it. Go ahead and blame it on the tuning tools if you want.
There are many more EVO 8s that run in the 200-240 load range than those that run in the 260 load range. And if a car maxes out the load column, then a tuner should re-scale the iginition and fuel maps. Allowing a car to run in the highest load column for multiple rpm rowas is not good tuning practice IMO.
You know very well that it is almost impossible to pin point the blowing up of an engine to the tune especially on the EVO that has an extremely stout engine.
I do not agree. The low octane maps are not moot. When the engine knock 6 counts or more continuously, then the octane flag starts to decrements. The more the flag decrements that more the ECU starts seeking the low octane fuel/iginition maps. If they are the same, then the ECU cannot find these safe maps. It is well known that the ECU will pull timing even if the maps were made the same.
No need to be arrogant with me Al. I am more than willing to engage in a civil debate with you, but these little digs are not called for. I tune my own car and a friend's car that was left high and dry by a pro tuner here in SoCal. I tune his car since I recommended that worthless tuner in the first place. These are the only cars I tune since I do NOT want the liability and the headaches involved with tuning other people's cars. That does not mean that I do not know how to tune, just that I do not want to tune.
I am glad that you stopped using this method, but you only did that AFTER you were flamed heavily for using it. Go ahead and blame it on the tuning tools if you want.
There are many more EVO 8s that run in the 200-240 load range than those that run in the 260 load range. And if a car maxes out the load column, then a tuner should re-scale the iginition and fuel maps. Allowing a car to run in the highest load column for multiple rpm rowas is not good tuning practice IMO.
You know very well that it is almost impossible to pin point the blowing up of an engine to the tune especially on the EVO that has an extremely stout engine.
I do not agree. The low octane maps are not moot. When the engine knock 6 counts or more continuously, then the octane flag starts to decrements. The more the flag decrements that more the ECU starts seeking the low octane fuel/iginition maps. If they are the same, then the ECU cannot find these safe maps. It is well known that the ECU will pull timing even if the maps were made the same.
No need to be arrogant with me Al. I am more than willing to engage in a civil debate with you, but these little digs are not called for. I tune my own car and a friend's car that was left high and dry by a pro tuner here in SoCal. I tune his car since I recommended that worthless tuner in the first place. These are the only cars I tune since I do NOT want the liability and the headaches involved with tuning other people's cars. That does not mean that I do not know how to tune, just that I do not want to tune.
My point is that Jestr and I combined have tuned many thousands of vehicles and I have spend thousands of hours on the dyno tuning evos
None of these dire predictions you suggested ever occured - my tunes have been as safe as stock roms - in practice over 4 years and some cars well over 100,000 miles
Most of these points are now irrelevant in any event as I have as of the last year included all of these features in the maping that I do
I am sorry if you feel I was taking a dig at you - I also enjoy a civl debate
However, the fact remains that I tuned several thousand evo ecus using the same methods you claim are dangerous and there are no reports of any problems what so ever.
To conclude, with the new software's friendly grapohical intephase - vs the raw hex editor I used to use - I have adopted many of the methods which you have referenced. The maps I have been selling for over a year all have these features.
Responding to the concerns and wishes of my customers and being flexable in how I set up my maps is a sign of flexability and an open mind.
While I disagree with your suggestions - it was much easier to just include - for example - a very low timing low octane timing map for the customer's peace of mind even if the properly tuned car will never see that map in any event.
Thus - the point is a moot issue for me to discusss as my maps have these features and have had them for over a year now.
Its like saying that Ford cars used to have carberators - well they dont have them any more.
Al
Tune for tune, a Mellon tuned Evo without cams is keeping up with my cammed Vishnu Evo locally.
Mellon is a good guy and has been practicing on his 3000GT for awhile.
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
that's probably eating him up.

