Official OpenFlash Tablet FA20 Tuning Tech Discussion Thread

[steve99]

Originally Posted by jamesm

Open loop has nothing at all to do with any O2 sensor (aside from the high ltft bucket calculated in closed loop, if it's even enabled). The stock tune really is quite rich, but remember the map is scaled past what the stock car will ever see on the load axis (out to 1.4g/rev).

Deliberately jacking up the airflow model to achieve an AFR target would be very odd, and I can't imagine why anyone would do that.

Thanks @jamesm

I realize the O2 sensor is not use in the fuel calculation for open loop just that its use to measure the AFR you see in you logs which you compare with the commanded AFR ?

Are their any other tables used for OL fueling ?

As the OFT tunes almost always run richer top end than the values in the OL fueling tables even though you LTFT may be 1% or less.

The table says 12.4 but your usually running 11.5 to 12 measured AFR, untill you scale maf then it matches up.

[jamesm]

Originally Posted by Td-d

One very specific reason to shift the entire O2 scaling around, actually, but nothing to do with open loop as mentioned.

If you want to run higher than stoich AFRs in closed loop, it is not possible within the limitation of the OEM code. 14.7 is the leanest you can reach. To achieve leaner mixtures (for fuel economy), you have to manipulate the O2 sensor scaling.

I was referring to deliberately introducing error into the airflow model.. Ie targeting a leaner afr then countering that with higher-than-actual maf (or ve I suppose, if you're running sd) values to reach a richer target.

[Blu-by-U]

Help. Anyone get an "Oops error writing to the ECU" when re-flashing your twin?

[Tenchi]

Originally Posted by jdv14476

Help. Anyone get an "Oops error writing to the ECU" when re-flashing your twin?

I have. I just restarted the write process over again and it was ok.


Sent from my iPhone using Tapatalk

[Blu-by-U]

Tried that and I keep getting the same error. Did you have to try multiple times?

Originally Posted by Tenchi

I have. I just restarted the write process over again and it was ok.


Sent from my iPhone using Tapatalk

[Tenchi]

Originally Posted by jdv14476

Tried that and I keep getting the same error. Did you have to try multiple times?

No I just tried one time but unplugged the OFT.


Sent from my iPhone using Tapatalk

[steve99]

Originally Posted by jdv14476

Tried that and I keep getting the same error. Did you have to try multiple times?

Hopefully it just the cable connections, check it plugged in at oft end correctly and at obd port end all the way. Also try putting some pressure in forwards or backwards direction on obd port end use a rubber band , try cleaning cable and port with electrical solvent

[Blu-by-U]

Cables has been working great for data logs and I leave it plugged into the OBD port. Did my read file when I received the OFT and finally tried to write to the ECU.

Originally Posted by steve99

Hopefully it just the cable connections, check it plugged in at oft end correctly and at obd port end all the way. Also try putting some pressure in forwards or backwards direction on obd port end use a rubber band , try cleaning cable and port with electrical solvent

[steve99]

Originally Posted by jdv14476

Cables has been working great for data logs and I leave it plugged into the OBD port. Did my read file when I received the OFT and finally tried to write to the ECU.

Alrighty, so you have never written to ecu before ?

if not then it could be a couple of things
1. you car has been tuned with another device such as ecutek and the stock tune rom has their licene info in it so the checksum is different. If you using the preconfigured tunes it wont write as it see a non stock rom

If you delete the mod file database format tunes in the oft and load up the individual rom files from the openflash site you will be ok

or you have a rearly new rom the oft does not know about in mod file database maybe b01C or D, loading up the individual roms should sort that as well.

The oft guys will be able to help you if you give them a ring

[Blu-by-U]

This the first time writing. Had the OFT for a while, but just logging data. Did a comparison between my original ROM and the stage one OTS ROM for my car (700D). Then I transferred the changes as shown in the YouTube vids and everything seemed fine. I swapped out my stock filter for the K&N that picked up and tried to write the stage one tune. Are you saying that I should try the OTS tune straight up?

Originally Posted by steve99

Alrighty, so you have never written to ecu before ?

if not then it could be a couple of things
1. you car has been tuned with another device such as ecutek and the stock tune rom has their licene info in it so the checksum is different. If you using the preconfigured tunes it wont write as it see a non stock rom

If you delete the mod file database format tunes in the oft and load up the individual rom files from the openflash site you will be ok

or you have a rearly new rom the oft does not know about in mod file database maybe b01C or D, loading up the individual roms should sort that as well.

The oft guys will be able to help you if you give them a ring

[steve99]

Originally Posted by jdv14476

This the first time writing. Had the OFT for a while, but just logging data. Did a comparison between my original ROM and the stage one OTS ROM for my car (700D). Then I transferred the changes as shown in the YouTube vids and everything seemed fine. I swapped out my stock filter for the K&N that picked up and tried to write the stage one tune. Are you saying that I should try the OTS tune straight up?

Yes you should not need to modify tunes just load up the corresponding tune file for your rom calid and it should write

[Blu-by-U]

Ready to try that and I'm going out there now. Let you know how it goes.



Well, it won't write that file either. It seems a little different since the first time I tried to write though. As I recall, the first time I tried, it was key on, confirm, key off, key on, confirm. Hasn't been prompting me to turn the key off the last few attempts.

Originally Posted by steve99

Yes you should not need to modify tunes just load up the corresponding tune file for your rom calid and it should write

[steve99]

Originally Posted by jdv14476

Ready to try that and I'm going out there now. Let you know how it goes.



Well, it won't write that file either. It seems a little different since the first time I tried to write though. As I recall, the first time I tried, it was key on, confirm, key off, key on, confirm. Hasn't been prompting me to turn the key off the last few attempts.

hmmm thats weird, you are turning the key fully on not just accessory right ?
and you definitly loading up the correct calid 700D is a rearly early rom thought a 2013 model would have been A00D or A01D

make sure you turn off car and unplug oft between attempts

[Blu-by-U]

Yep, key fully on. And if I try to start it, I don't even get a click. Nothing at all.


Is there a sensor or something that I might have accidently unplugged while changing the air filter? Guess I'll be calling Toyota tomorrow, rather not.

Originally Posted by steve99

hmmm thats weird, you are turning the key fully on not just accessory right ?
and you definitly loading up the correct calid 700D is a rearly early rom thought a 2013 model would have been A00D or A01D