OFT Openflash V4 tunes released for 2017+ with Launch/FFS

[mizzta21]

Originally Posted by Jasonb

On 91, I'd leave it at .7.

I’m on 91, when I flashed the v4 tune my IAM was set to 1.0 and every time I start my car now my IAM is at .86. Should I change it back down to .7 or just leave it? Isn’t it better to start off with a higher IAM than having to wait til it increases? Thanks in advance.

[Jasonb]

Originally Posted by mizzta21

I’m on 91, when I flashed the v4 tune my IAM was set to 1.0 and every time I start my car now my IAM is at .86. Should I change it back down to .7 or just leave it? Isn’t it better to start off with a higher IAM than having to wait til it increases? Thanks in advance.

It's safer to have it start low and increase as the ecu sees no knock being detected.

If you have it start high then there is more of a chance of it knocking.

If your IAM ever gets below where you set the initial IAM the ECU remembers that and it will start back up wherever it left off.

[Kodename47]

Originally Posted by SuperTom

Is there anything I can do or check?? I will double check all connections pipewise and 02 wise

You have a MY17 correct? I see (in EcuTek mind) that the P2270 isn't defined on older ROMs but in ZA1JK00G/01I it is and enabled. It's showing as "O2 Sensor Signal Biased/Stuck Lean B1S2". Without a V3 to compare or know what it's based on I can't comment further. If it was B01C/D then I reckon that's why.

Originally Posted by Tuxedo Tony

Also do I need to change any other table when changing just the initial IAM?

No

Originally Posted by mizzta21

I’m on 91, when I flashed the v4 tune my IAM was set to 1.0 and every time I start my car now my IAM is at .86. Should I change it back down to .7 or just leave it? Isn’t it better to start off with a higher IAM than having to wait til it increases? Thanks in advance.

Why not set it to 0.8 then? Lower would be better to start than higher IMO. It doesn't take long to increase unless you're just cruising, in which case it's not going to make much difference anyway.

[steve99]

@Kodename47
V3 tunes for usa 2017 was based on usa K00C rom

V4 on K00G

Its possible tgier is some issues with using K00G in K00C car but this is only issue thats come up with this P2270 code and a lot of guys in usa running the v4 tune on 2017. He seems to indicate he has moved the 02 sensor to differnt position.

One difference in v3 to V4 was ltft correction limits was 40% in v3 but 2% in v4 , but unlikely to cause cel just limit ltft correcrion in open loop how , seems likely its hardware issue or sensor placement install issue. Have that code before when guy put spacer in front o2 sensor got lean code and slow respose code.

Be interesting to see logs of his car might give a clue

[Lantanafrs2]

I'm running v4e85 uel tune. Today started running like shit. Poor idle, hesitation throughout power and etc. Cleaned maf, tb and reconnected and tightened intake tube on both ends. Idle immediately improved and rest of powerband is starting to come back to normal. Who knows? I am very relieved however.

[Tuxedo Tony]

Okay. I'm going to leave it as is. Thanks for the quick responses and info @ kodename47 & @ Jasonb!

[mizzta21]

anyone want to chime in on why my v4.03 drones like no other? ive had the same setup with the v2 tune with stock headers, catless front pipe and N1 catback but when I flash the v4 it just drones so much....

[NCFRS]

Has anyone had issues with the checksum not correcting itself on the ZA1JD00C tune files. I have tried all sorts of work arounds but when ever I go to load the tune into OFM I get the error code of checksum is wrong.

Any help would be awesome.

[steve99]

Originally Posted by NCFRS

Has anyone had issues with the checksum not correcting itself on the ZA1JD00C tune files. I have tried all sorts of work arounds but when ever I go to load the tune into OFM I get the error code of checksum is wrong.

Any help would be awesome.

oft/ofm automaticly corrects checksum, will be fine

it wont fix corrupted rom or editing with bad or incorrect definition, but if your using rom direct from oft guys its kust a warning that oft/ofm is correcting checksum for you just load and flash will be fine

[FT86Z]

Originally Posted by Jasonb

I have mine set at .9 on startup and it's usually at 1.00 within 2-3 minutes of driving.

How would I go about changing this? Also, I wouldn't mind getting the loud start back too if anyone can explain how to do this. Thanks

[tomm.brz]

on romraider open your map with the correct definition
change [ignition timing- knock control] Avance Multiplier (initial) from 0.7 to what you want


for cold start back:
[ignition timing - advance] ignition timing post start from 0,04 to -15 (that 's loud) or -19 (even more loud) or something less like -9 (a bit quieter)


idle speed on v4 is 1200 maximum so if you want louder cold start you should put those tables higher like 1400



but actually I think you would also change the MAF correction after start (idle)- (in gear) to offset more the maf during the cold start situations, but the Shiv's definitions on the v4 tunes have these not defined but well i think you can also not do that

[Hella Basa]

Originally Posted by tomm.brz

on romraider open your map with the correct definition
change [ignition timing- knock control] Avance Multiplier (initial) from 0.7 to what you want


for cold start back:
[ignition timing - advance] ignition timing post start from 0,04 to -15 (that 's loud) or -19 (even more loud) or something less like -9 (a bit quieter)


idle speed on v4 is 1200 maximum so if you want louder cold start you should put those tables higher like 1400



but actually I think you would also change the MAF correction after start (idle)- (in gear) to offset more the maf during the cold start situations, but the Shiv's definitions on the v4 tunes have these not defined but well i think you can also not do that

To get the loud cold start back I only need to change the ignition timing post start?

[tomm.brz]

if you only change ignition timing post start, will be louder but not like stock

stock cold start is very loud also because has higher idle so if you want it loud rise it like at 1400 rpm minimum, on the "left" zones of the idle maps

v4 tunes has max of 1200rpm that s not much to get it loud


but yes, it s basically only that, try put -15 or -19 (this one is on my17+ stock rom) and hear it



but v4 has maf correction after start a lot reduced on cold start, you should put higher values on the first 2 rows in those 2 maps, but v4 oft definitions have them not defined, you need better definitions to modify them

[steve99]

Originally Posted by tomm.brz

if you only change ignition timing post start, will be louder but not like stock

stock cold start is very loud also because has higher idle so if you want it loud rise it like at 1400 rpm minimum, on the "left" zones of the idle maps

v4 tunes has max of 1200rpm that s not much to get it loud


but yes, it s basically only that, try put -15 or -19 (this one is on my17+ stock rom) and hear it



but v4 has maf correction after start a lot reduced on cold start, you should put higher values on the first 2 rows in those 2 maps, but v4 oft definitions have them not defined, you need better definitions to modify them

defs in fist post have those tables defined if you 2012-2016