View Single Post
Old 07-13-2016, 06:57 AM   #1353
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,996
Thanks: 1,035
Thanked 4,994 Times in 2,984 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
Quote:
Originally Posted by dtek View Post
Much as I respect your work on tune refinements round here, you're no stranger to a petty smart arse snipe, so I thought you of all would take it with a grain of salt.

FYI it's an A00I and yes Im in 'straya like you. Why those two factors are really a relevant concern escapes me though.

The Defs used were the most up to date available at the time, but I'll make a point to go revisit the tune comparison with the current most recent defs and see if I can find any new tables. I've even done side by side comparisons between Shiv's OTS tune (91RON C ROM to his ESC 91RON C ROM) and I can't see any clear differential that speaks to where he adds/tweaks specifically for boost. Yes there's some differences but certainly not intuitive or logical.

I was hoping that one of the forced induction tuning guys would weigh in here with actual experience with that aspect of tuning. Since the one common denominator in the problematic AFRs is only when boost is applied.
You might want to try a guy called @KoolBRZ from memory he has an auto trans and an phantom esc, i think he had similar issues hes in usa/canada so yu will have to port changes to your rom.

If porting changes between rom calid i usually do this

1. compare say a stock A01C or whatever the source rom is with the modded source rom of same calid say A01C. Note the names of all the tables changed. dont try to directly copy from say a C to G series as you dont know which tables to change and which to leave alone

2. Then open the destination and source roms with compatible definitions ie make sure ones not metric and one imperial and carefully copy across ONLY those tables you noted different in step 1. Carefully check both the source and destination tables BEFORE you copy to see the x and y axis are consistent in both the source and destination tables , the x and y axis should be same only the contents of the table should differ there are some errors in defs.

Traps and pitfalls

Do NOT copy tables if the x and y axis dont match between source and destination tables either weird stuff will happen or ecu may be bricked.

Other traps are tables can be named slightly differenty between roms of different calid.

Their will be differences in say a stock C series and G series rom due country specific changes to roms DO NOT copy these over, this is the purpose of step 1 ,to find what the tuner changes from stock on the same rom calid.

If you cannot match table names or the tables look different then be exceedingly careful and research why this is.
steve99 is offline   Reply With Quote
The Following User Says Thank You to steve99 For This Useful Post:
dtek (07-13-2016)