OpenFlash Tablet v1.52b Maps now available in Database Format

[Shiv@Openflash]

Originally Posted by YMAA

Shiv,

I took my car in for service at the dealer yesterday because my car had been randomly having trouble starting and throwing a code (P0193). Was using the 1.42 beta map but flashed back to stock before taking it in. The code seemed to indicate a fuel pump problem from searching online, but the service manager said they couldn't find anything mechanically wrong and flashed an update to the ECM citing an "out of range error".

I got home, wiped the tablet with the OFM software, and read the stock ROM on the car. Previously I had an ZA1JA01C ROM, and after the update it's showing ZA1JB01C.

Is it possible that the trouble I was having was related to the 1.42 ROM? My plan for now is to leave the car with the stock ROM for the next two weeks or so and see if the problem went away, if so I'll flash the latest release out by then.

The only diagnostic code we disable with tune files is for cat inefficiency (P0420). Other than that, we don't do anything to change diagnostic functions. So it's highly unlikely that the v1.42 tune had anything to do with the fuel rail pressure code (P0193) that you saw. If that is the code you saw, I'd drive around stock for a few days and see if it comes back. If it does, it's definitely a hardware issue (bad fuel rail pressure sensor likely). I don't think any of the software updates issued have anything to do with fuel rail pressure.

My experience brings up an interesting question...if someone has a very old ROM type, could they simply go to the dealer and get their ECM updated to a more recent type and potentially have an easier time flashing with OFT?

Sure. But this only really applies to those running much old 700 or 900 series ROMs. If you have A00, A01, B00 or B01, it doesn't matter.

But everyone should remember to flash their stock ROM back to the ECU before going to the dealership. This will allow you to erase your OFT and re-install it if the dealership ends up updating your ECU.

Cheers,
Shiv

[FrsDuke]

Originally Posted by YMAA

My experience brings up an interesting question...if someone has a very old ROM type, could they simply go to the dealer and get their ECM updated to a more recent type and potentially have an easier time flashing with OFT?

They won't do it simply because it's old there has to be a justification. Even saying "I want the updated cal to protect against DI seal failure" doesn't fly. However you can try claiming intermittent idle instability. "Hey sometimes for no apparent reason my idle gets low then comes back up when my AC is off." If they are cool and take you at your word you can execute a TSB reflash for the issue. If they are not cool they will want to witness it themselves.

S-SB-0040-13 : Intermittent RPM Drop TSB info.

[Burn]

Hi Shiv,

When is the next beta version coming ? Still waiting for the support of my ROM ZA1J700G ? Thank you

[Terrapin77]

Originally Posted by shiv@vishnu

The only diagnostic code we disable with tune files is for cat inefficiency (P0420). Other than that, we don't do anything to change diagnostic functions. So it's highly unlikely that the v1.42 tune had anything to do with the fuel rail pressure code (P0193) that you saw. If that is the code you saw, I'd drive around stock for a few days and see if it comes back. If it does, it's definitely a hardware issue (bad fuel rail pressure sensor likely). I don't think any of the software updates issued have anything to do with fuel rail pressure.



Sure. But this only really applies to those running much old 700 or 900 series ROMs. If you have A00, A01, B00 or B01, it doesn't matter.

But everyone should remember to flash their stock ROM back to the ECU before going to the dealership. This will allow you to erase your OFT and re-install it if the dealership ends up updating your ECU.

Cheers,
Shiv

Since your having issues updating the old 700 & 900 series ROMs, is there a chance you will have to stop supporting them? I'm stuck on my 700 series ROM. I've been to 4 Scion dealerships in Atlanta trying to get the latest ROM but they all refuse. I was told by one of the dealers that there are so many problems with the FR-S, that Corp refuses to pay for warranty work unless the dealership documents the issue first.

[R2]

Originally Posted by shiv@vishnu

The only diagnostic code we disable with tune files is for cat inefficiency (P0420). Other than that, we don't do anything to change diagnostic functions. So it's highly unlikely that the v1.42 tune had anything to do with the fuel rail pressure code (P0193) that you saw. If that is the code you saw, I'd drive around stock for a few days and see if it comes back. If it does, it's definitely a hardware issue (bad fuel rail pressure sensor likely). I don't think any of the software updates issued have anything to do with fuel rail pressure.

Cheers,
Shiv

I had this same code (P0193) twice within a couple of weeks of each other. Both times I had v1.34 flashed. The scenario for both was a cold start when ambient temperatures were in the 0C range and the block heater had been plugged in for more than 3 hours. The code popped up almost immediately after starting and I had zero throttle control until clearing the code/restarting the car. The car idled perfectly fine, and after clearing the code the engine ran completely normally. My theory is that the localized heating from the block heater affected the fuel rail pressure sensor or caused some anomaly in the fuel rails that persisted very briefly.

I flashed back to stock and ran it for a couple of weeks and had no further issues, even after having the car plugged in for a few hours on a warm 0C day. I had no issues at all last winter. That being said, I went to v1.42 since that and haven't seen the code again.

Normally I don't plug the car for more than an hour unless it is colder than -10C, but an interior heater, a programmed block heater timer and ultimately laziness occasionally sets the stage for longer times.

[Shiv@Openflash]

Originally Posted by Terrapin77

Since your having issues updating the old 700 & 900 series ROMs, is there a chance you will have to stop supporting them? I'm stuck on my 700 series ROM. I've been to 4 Scion dealerships in Atlanta trying to get the latest ROM but they all refuse. I was told by one of the dealers that there are so many problems with the FR-S, that Corp refuses to pay for warranty work unless the dealership documents the issue first.

Of course we will still support older ROM (700 and 900) types. We just need to work out a method to allow for the new .dev file to make ALL the changes necessary to update it to newer ROM type. Currently, too many patches are required which means that your only current option is to load the last .bin file update (v1.42). That essentially updates you to A01.

But we are working on a solution to update to v1.5 for the old ROM types as well. Just may like a little time.

Shiv

[86-tundra]

lol at all of those .ds_store files

shiv, use a mac much

[jflogerzi]

@shiv@vishnu, Does your tune help with the stumbling idle issues? I am thinking about ditching my ecutek and going wit OTF seeing how active and easy it is to get updates. FI is not in my future anytime soon.

[Shiv@Openflash]

Originally Posted by jflogerzi

@shiv@vishnu, Does your tune help with the stumbling idle issues? I am thinking about ditching my ecutek and going wit OTF seeing how active and easy it is to get updates. FI is not in my future anytime soon.

In all our tuned maps, we bump up idle speed targets by 50-100rpm which helps a lot with the idle dip/stumble that a few people have reported with the stock tune. So yes, it should help. We will also be testing the new BA01C/BA01D ROM which supposedly have some idle-related improvements as well. If this turns out to be true and effective, we will use them as the base for the next generation of tuned maps.

[jflogerzi]

one more quick question. I have an aFe intake(don't ask, it was my first mod before I knew better) Anyways, Do you have a tune that has the correct MAF settings for this plus a UEL header?

[Shiv@Openflash]

Originally Posted by jflogerzi

one more quick question. I have an aFe intake(don't ask, it was my first mod before I knew better) Anyways, Do you have a tune that has the correct MAF settings for this plus a UEL header?

I haven't tested the aFe intake so I can't tell you definitively. You can certainly give it a try and post up a datalog after day or two of learning and see how things look. If they are skewed (which is less than likely with the new v1.5 maps), you can always get custom tuned or throw your stock intake box back on. Would be a good opportunity to modify the inlet duct since it's out of the car right now

[jflogerzi]

Originally Posted by shiv@vishnu

I haven't tested the aFe intake so I can't tell you definitively. You can certainly give it a try and post up a datalog after day or two of learning and see how things look. If they are skewed (which is less than likely with the new v1.5 maps), you can always get custom tuned or throw your stock intake box back on. Would be a good opportunity to modify the inlet duct since it's out of the car right now

I know I should. I even have the Perrin inlet tube and TRD air filter. I really am trying to avoid taking the bumper off. I don't want the gap like everyone else gets after they take off there bumper

[Shiv@Openflash]

Originally Posted by jflogerzi

I know I should. I even have the Perrin inlet tube and TRD air filter. I really am trying to avoid taking the bumper off. I don't want the gap like everyone else gets after they take off there bumper

[jflogerzi]

Originally Posted by shiv@vishnu

Order processed for competitive discount on a OFT. Looking forward to the OTF. The service you provide is top notch. Also the regular updates are great! Can't wait. What kind of shipping do you guys use? Hoping I can get it by Friday since I live in CA