Hi Sic,

How do I obtain 52360018?

 

I'm just starting to examine the maps posted on the first page a little more closely. One thing that struck me as odd was that at the 240->300 load cells @ 6000 RPM's there is a dip in timing advance of -2 degrees compared to values at 5500 and 6500 where as all the other columns have a much smoother progression at lower load cells.

This pattern shows up in the Timing High Octane Map and even earlier in the Low Octane Map. Now a stock car would never reach those load values at that RPM so it seems odd that Mitsu would bother with placing that there. It also adds a slight amount of fueling in the low and high octane maps at the same 6000 RPM range. The stock turbo starts to taper boost starting at 5500 RPM's and above so likely this wouldn't come into play unless you upgraded your turbo or had a maxxed out stock turbo setup. So what did Mitsu do here?

 

It's just failsafe in case you lose factory boost control (vacuum lines blow off the solenoids) during heavy acceleration. You'll get the safety of the maps, and then boost cut will kick in.

I think it would be nigh impossible to blow up an engine stock without downshift over-revving it.

 

Yeah my factory boost control is long gone. :P

I guess what I was asking is why the timing tables show a smooth progression from 14 degrees @ 3000 RPM's to 28 degrees @ 8000 RPM for 160% Load where as 240% Load it goes from 4 to 18 with a dip at 6000 RPM. It drops from 15 to 13 then starts climbing again to 15 and so on, just seems odd.

I'm assuming that tuners are just adjusting the values as needed based on datalogging and getting rid of that dip if the airflow is pushing you into the higher load cells. If the engine isn't knocking then what other reason would there be to put a dip in timing and adding fuel like that? Maybe on a stock car it worked out as a safety measure on top of dropping to the low octane cells if it detected knock.

 

I've had to pull timing at around that area. I actually have two 2 degree dips in my timing map. Allows for optimal timing elsewhere.

 

Ok thanks for the info, this is going to be fun tuning the car with this software. I'm going to stay on the conservative side checking often to make sure I'm not overstepping the limits. Between the Wideband, TurboXS knocklite, EvoScan datalogging, and AWD dyno available nearby I should be in pretty good shape.

 

I played with some Mivec madness today and 200-300 RPM quicker spools on top of what I had before is nutty. I used some of the max values hit on the warmup maps, JDM, and US maps as a guide then picked the best elements and smoothed them based on the likely path when going through the load cells as boost climbs. I may have to back base timing down slightly to accomodate some of the intake advance in the 2500-3000 range but overall the car feels like a torque monster now. Adding in an extra -5 exhaust retard in the 2000-4000 range is likely what really boosted the spoolup the most and was a great tip!

Starting at 2000 RPM and lifting at 20 PSI:
3rd 3200 -> 2900
4th 2800 -> 2500
5th 2550 -> 2350 (Can't get much better since you are starting at 2k)

These were approximate but there was a noticeable difference in response even without strapping it to a dyno. Tuning the Mivec for more power at WOT will be quite a bit trickier but the increased low and mid range is quite good now. It looks like 5-10 degrees of change over the US maps and 0-5 degrees of change over the JDM maps is the approximate increases I made to the MIVEC maps when advancing the Intake and retarding the Exhaust.

This should work out really well with the GT30 turbo and I can't wait to get that installed and tuned on the Dyno with EcuFlash/EvoScan!

 

i would be interested to see the maps

 

Sure thing, I'm just making a few final tweaks after a day of datalogging and testing. There were a few cells that were in the lower load cruise maps that I'm adjusting now so that the throttle isn't TOO responsive. All in all they should be safe but I'm dialing out a few degrees of timing advance to accomodate the changes because my ecutek tune was a bit aggressive in a few spots pushing it over the edge. Granted the car feels faster even with 1-3 counts of knock at 3500 and a few more hits at 6000 but I should have that remedied shortly.

Basically the test maps I made with a little too many tweaks to the 20-40% load cells made the car feel like it wanted to build boost on a hair trigger. I think that would be good for an Auto-X but for daily driving you would be too tempted to boost with the slightest press of the throttle and would burn up extra gas. I settled on stripping out most changes in the lower load cells and still kept 90% of the quick spool.

 

There was a recent post on another site where a persons warranty was voided due to having been flashed. I dont know what he was flashed with (ap, ecutek, ecuflash) but its the first i've heard of a confirmed warranty decline from flashing.

The person mentions that this was due to a counter called "CVN#"


I'm interested in the technical discussion here. Does this exist, is ecuflash detectable and other flashes not?

 

As far as I know all flashes of the ROM are detectable including dealer flashes. If someone blows their engine and it was determined that it was due to going lean or running too much timing then I'm not sure who would expect to get their own mistake covered under warranty. Failures due to a factory defect (if proven) should still be covered though assuming the tune had nothing to do with it.

 

^Agreed.


I'm looking to clarify the point though, that all flashes are detectable. I know thats always been a gray area. Some vendors say they are not, some say they are. I think it would be good for us all to know for a fact which way it is.

 

Flashes are detectable since the AFR and timing and boost tables have been altered. But the issue here is are flashes back to a STOCK rom detectable. There is a guy in that other thread that says that there is no flash counter and the dealer could not find that his car was flashed back to stock even though they tried.

 

what logging software is out there for the X?

 

PCMScan, Cobb AP, EvoScan, tephra's logger. But they are all pretty rough. I haven't used tephra's logger yet but I'm planning to try it today.

https://www.evolutionm.net/forums/ev...x-logging.html