Openflash Tablet v1.31 beta maps (including Stage 2!) now available for download

[cnk]

Originally Posted by Boofneenee

How does pressing and releasing the gas pedal when the car is off help the ecu to learn? I was under the impression the car uses an analysis of exhaust fumes to determine calibration. What am i overlooking?

The car is Drive-by-wire so the ECU just needs to relearn what the range of motion is on the gas pedal after an ECU reset/flash. No idea where you got exhaust gas analysis from.

Originally Posted by Norkoastal

What is the time sequence of all these steps? I know some cars have time requirements with throttle relearn procedures.. The steps above didnt work for me this go around when I flashed (my throttle already corrected so this would be good to test for the next flash)..

No time sequence.

[brn12345]

What is the impact of Sportmode/Traction off on engine mapping? Are the tuned maps adjusted for both sportmode and normal mode?

[jeebus]

I'm not trying to be a squeaky wheel, but I had some issues with 1.33b as well. I flashed the same way I normally do. Turned car "on" and did the gas pedal trick 15 times, then started the car and let it idle for a minute before driving.

The first thing I noticed was VVT was definitely disabled. It never happened to me before with any of the flashes. It came back on after 10 miles or so. But after another 10 miles and two drive cycles, I can say that I was getting a lot of knock in the 2500-3000 range on tip-in and a ridiculous amount of knock after each shift. My wife was in the car and she was like what is that?

So I flashed 1.31 back on, did the same song and dance, and everything seems just fine now.

Any ideas?

[Norkoastal]

Originally Posted by jeebus

I'm not trying to be a squeaky wheel, but I had some issues with 1.33b as well. I flashed the same way I normally do. Turned car "on" and did the gas pedal trick 15 times, then started the car and let it idle for a minute before driving.

The first thing I noticed was VVT was definitely disabled. It never happened to me before with any of the flashes. It came back on after 10 miles or so. But after another 10 miles and two drive cycles, I can say that I was getting a lot of knock in the 2500-3000 range on tip-in and a ridiculous amount of knock after each shift. My wife was in the car and she was like what is that?

So I flashed 1.31 back on, did the same song and dance, and everything seems just fine now.

Any ideas?

How many days/miles are you making these observations after the flash? For every flash i've made, the car wakes up around day 3 which is usually when I would have driven 50ish miles with 6+ start/stop cycles. I wish OFT included additional steps to help the ecu learn the throttle faster before driving around.. Nothing more than a nag but it could always be a feature down the road if possible to code in.

[jeebus]

Originally Posted by Norkoastal

How many days/miles are you making these observations after the flash? For every flash i've made, the car wakes up around day 3 which is usually when I would have driven 50ish miles with 6+ start/stop cycles. I wish OFT included additional steps to help the ecu learn the throttle faster before driving around.. Nothing more than a nag but it could always be a feature down the road if possible to code in.

I drive 80+ miles per day. That said, the map has IAM set to 1 already, so other than fuel trims I don't think there's a lot of learning to do. My issues with 1.33 had to do with knock though, not performance (except during the initial VVT disabling)

[BRZ Fanboi]

Originally Posted by jeebus

What map does your car take? A00, A01, etc?

ZA1JA01C

[sierra]

Subscribe.

[Shiv@Openflash]

VVT disabling after start up has nothing do with the map. It is caused by the flashing process. Specifially not by not letting the car idle for a short period of time after the flash process (as instructed). And this applies to any flashing system (ecutek, brzedit, ecuflash, oft, etc).

[jeebus]

Originally Posted by shiv@vishnu

VVT disabling after start up has nothing do with the map. It is caused by the flashing process. Specifially not by not letting the car idle for a short period of time after the flash process (as instructed). And this applies to any flashing system (ecutek, brzedit, ecuflash, oft, etc).

any idea why the latest 1.33b on my A00C car would have me knocking all over the place at tip-in, in the 2500-3k range, and post shift but going back to 1.31 fixes it?

[Shiv@Openflash]

Originally Posted by jeebus

any idea why the latest 1.33b on my A00C car would have me knocking all over the place at tip-in, in the 2500-3k range, and post shift but going back to 1.31 fixes it?

What map are you running? What modifications?

[jeebus]

Originally Posted by shiv@vishnu

What map are you running? What modifications?

stage 1 AOOC map. Only mods are a drop-in and a catless front pipe. Didn't have any issues with 1.2. 1.31 felt a tad less punchy in the low revs, but felt smoother overall than 1.2. No issues there. With 1.33 the knock was really noticeable going up hills and after shifting during mid throttle application. Went back to 1.31 and drove the same circuit without issues.

Running Chevron 91 (cali piss).

[jeebus]

BTW, I'd really like to give @shiv@vishnu props for following these threads and answering questions.

[Shiv@Openflash]

Originally Posted by jeebus

stage 1 AOOC map. Only mods are a drop-in and a catless front pipe. Didn't have any issues with 1.2. 1.31 felt a tad less punchy in the low revs, but felt smoother overall than 1.2. No issues there. With 1.33 the knock was really noticeable going up hills and after shifting during mid throttle application. Went back to 1.31 and drove the same circuit without issues.

Running Chevron 91 (cali piss).

The only mapping change between the latest Stg1 map and the earlier Stg1 map is the transient ignition retard table. The latest Stg 1 map uses stock TIR table data. The earlier Stg1 version was retarded an extra 20 degrees. So yes the earlier map was more conservative during throttle transients. But that's it. Under sustained load it will perform identically. If for some reason your car is the only car I've ever seen, tested or has been reported to knock with any of these maps, perhaps something else is going on. I'm just reporting what I know to be the difference. If you want to go back to the earlier map version, you can do it. Nothing wrong with that more conservative approach.

Lastly, let's not forget that the all the maps are actually A01C maps. They are just given 700C, 900C, A00C and A01C designation for the sake of the OFT software since it is only allows you to upload ROMs with the same cal ID as your original ROM. It is not aware that the FA20 ECU allows you to use ROMs with different cal IDs (just as long as they are in the same family).

Shiv

[jeebus]

Originally Posted by shiv@vishnu

The only mapping change between the latest Stg1 map and the earlier Stg1 map is the transient ignition retard table. The latest Stg 1 map uses stock TIR table data. The earlier Stg1 version was retarded an extra 20 degrees. So yes the earlier map was more conservative during throttle transients. But that's it. Under sustained load it will perform identically. If for some reason your car is the only car I've ever seen, tested or has been reported to knock with any of these maps, perhaps something else is going on. I'm just reporting what I know to be the difference. If you want to go back to the earlier map version, you can do it. Nothing wrong with that more conservative approach.

Lastly, let's not forget that the all the maps are actually A01C maps. They are just given 700C, 900C, A00C and A01C designation for the sake of the OFT software since it is only allows you to upload ROMs with the same cal ID as your original ROM. It is not aware that the FA20 ECU allows you to use ROMs with different cal IDs (just as long as they are in the same family).

Shiv

That's why I thought it was weird. Even doing diffs all I can see are TIR changes, which I realize are just to get the scaling correct. The only other changes appear as "table not defined"...I assume you added some new tables to the definition.

Just reporting what I saw. Maybe I'll give the 1.33 another shot after this weekend's autoX. I don't want to chance anything before then.