First off, I fully understand that changing any values on the ROM can be dangerous to the engine so I do not intend to do so! I do intend to have my car remote tuned when I finish my 2.4LR build. However, I bought my car with quite a few mods on it from a dealer and I had no idea if it was tuned.

I just got my tactrix 2.0 cable in the mail and after some reading figured out how to copy my ROM and read it with EcuFlash. Obviously I have no idea what I am looking at, I found a stock ROM to compare it to and here is what I found.

#1. The two high/low octane and ignition maps are EXACTALLY the same, is that normal?
#2. Other than the fuel and ignition maps, everything else is EXACTALLY the same as the stock map, is that normal?

Mods I have are intake, exhaust, cams, lightweight pulley, fuel pump

 

The high and low octane ignition maps should not be the same. Your low octane should be 3* less than high octane. It is not uncommon for those to be the only maps changed, although I am surprised the WGDC, BDEL, and Adder tables were left alone.

 

Someone correct me if I'm wrong but the high/low maps should not be the same. They're a sign of a bad tune. A bad tuner will do this so that if the engine detects knock the ECU doesn't (or minimizes the amount) pull timing.

As for the rest of the map, I'm not that knowledgable about tuning but it does seem like a lazy tuner to me. Post up pictures of your ignition and fuel maps and that will tell us if they're any good or not.

 

Matching low & hi oct tables is wrong.. period, it's kind of a common practice by some tuners especially for track cars.
I suggest that you re-insert stock or near-stock lo-oct tables, I also suggest that you purchase & start using evoscan & data log you car for knock and other vital data, it would greatly improve your tuning knowledge, plus you're gonna need it anyway for your remote tune process.

 

This is the maps I pulled off my car today. I also run 91 octane fuel if thats any help.

I intend to learn how to use evoscan and data log I just don't feel comfortable enough with the program yet.

 

Are you using 93 fuel? Ignition looks a bit aggressive, I don't mind an aggressive tune but you should definitely fix that lo-oct issue to be on the safe side. Your tables have the same load/rpm scaling as a stock map, so you could copy the lo-oct tables from the stock file & paste them into your lo-oct tables.

What kind of turbo do you have? Judging from the fuel table, it looks like a fast spooler, an RS turbo perhaps?

Evoscan is easy to use & it's just for data logging, you'd also need an external wideband kit to log AFR


Edit: I just read that you're using 91 fuel, I think that ignition is too aggressive for 91, it wasn't tuned with 91 oct in mind!

 

I got a copy of his rom and made it alot safer for him. He was running timing above what I can do on e85 with an efficient combo of parts, and he is on 91 lol Fuel cut was maxed out, load based targets were all over the place, ign & fuel maps were identical and so on..

 

Thanks to boosted91t I think my engine will be safe on the 91 octane. I also will be installing a wideband sooner than later. I just got it in the mail, I just need to put it in!