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

Hi guys,
New v1.50 maps are now available for download.

Since these v1.52b maps are in BETA status, they are available only in (.dev) format. As such, they cannot be viewed or downloaded off the OFT. They must be loaded to the OFT through the ModFiles Database section of OpenFlash Manager. All previous tunes (.bin) must be deleted from the OFT before the database (.dev) file is loaded. [B]These beta maps currently support the following ROM types:
ZA1JA00C
ZA1JA01C
ZA1JA00D
ZA1JA01D
ZA1JB00C
ZA1JB01C
ZA1JB00D
ZA1JB01D
ZA1JA00G [added 1/20]
ZA1JA01G [added 1/20]
ZA1JA01I [added 1/20]
ZA1JA00J [added 1/20]
ZA1JA01J [added 1/20]
ZA1JA00K [added 1/20]
ZA1JA01K [added 1/20]

Additional ROM support will be added over the next several days.

Quick tutorial on how to upload database (.dev files):

1) Connect OFT to OpenFlash Manager v1.06 (or newer). Go to Upload Data. Delete all tune files (.bin) that are currently stored on the OFT. To do this, just click on the red "X" next to the .bin file. Please not that you can only erase modified files. The original ROM cannot be deleted. Once all the modified files are removed, click on "Start" at the button of the window. This will erase all the modified files from the OFT. You must click "Start" after deleting the files or else the files will not be erased on the OFT.

2) Next, go to ModFiles Database section. Select the database file (TOYO04400.dev) that is in the OTS v1.50b folder that you downloaded (and uncompressed) from our website.
http://i85.photobucket.com/albums/k4...ectdevfile.jpg

2) Add the .dev to the OFT. This take a few seconds. After it is done, it will say Status is"synchronized"
http://i85.photobucket.com/albums/k4...vfiletooft.jpg

3) Disconnect OFT from laptop and connect to your car. Go to "Tuning". The OFT will analyze your stock ROM and automatically generate compatible tuning files as per the instructions provided in the database file. Go to "Write" and you will see the compatible tuning files listed. Click on the desired map and click on right arrow to flash the map to the ECU. If the "Write" button is not selectable (greyed out), this means that the instructions in the database file do not support your ROM yet. If this is the case, you can go back to loading traditional .bin files through the Upload Data menu in OpenFlash Manager.

Quick vid showing step 3:
[ame]http://youtu.be/h0iiaLOWkdQ[/ame]

That's it. The new v1.50 maps are quite a bit different from the previous releases. One thing we have not done is adjust with the cold start cranking enrichments on the E85 maps. They are the same a they have been on the previous v1.42 release. Hopefully we will be able to get to that this week once we start running our test car E85 testing again. Once these maps are no longer in beta status, we will release them in traditional .bin format that you can upload/download/edit as you see fit :)

Cheers
Shiv

What's the difference in the map tunes it doesn't say anything in the release notes. Are these the new uel gas tune files?

Hi @shiv@vishnu when will the v1.50 with Australian ROM support be available on the pre-loaded OFT's?

Yes these are brand new stage 2 maps. Both EL and UEL. Lots of refinements to learning limits, fuel/ignition/VVT/etc. Pretty much everything.

I'll be gradually adding rom support to the database file over the next several days. Hard to give a definitely answer but if say it's a matter of days, not weeks.

Will this be your new public beta release method from here on out or is this just for testing of the .dev formatted tunes?

YMMV, but I wasn't able to get into the database section of the OpenFlash Manager with just installing the new version over the top of my old one. I had to completely uninstall it, reboot my computer, and then install the new version fresh before it would try to update the tablet. After that happened, I was able to get into the database section and load the .dev file. Everything seems to work so far, gotta go plug it into the car now!

...and now it's not letting me back into the database section. I keep getting an index out of range exception. I just now realized that my rom isn't supported yet (ZA1JA01D, US 6AT) so that probably has something to do with it not working. :(

Your ROM type is supported. So you should be able to load these new maps. There are a small bug with OF Manager that may result in a Timeout error. But it's just an error message. Everything should still be functional. Something you may want to try is quitting the OF Manager application and erase the .dev file your C Drive ->OpenFlash -> ProgramData -> Database folder and try to load the .dev file again as described in the instructions.

Shiv

Beta maps will most likely be released in this format going forward. It's the only way I can gather data without the possibility of the maps being tweaked in any way by the end user. Once out of the beta testing period, they will be released as standard .bin files as explained in my first post.

Shiv

Thanks....will place my order with Robert tonight. By the way, are all Australian market 86's on the G Rom?

No, we have I series as well.

I spent a long time rescaling my maf for my intake.....I'll wait for the bin.

Unless you have a larger diameter MAF housing, I think you should give it a shot :)

shiv,

Will it be possible to generate the different rom files before plugging into the car?
Can we choose what type of maps we need? as it looks like only two maps not including the original rom would be applicable to us?
For example:
1. Completely stock would need Stage 1 and Stage 1 E85
2. EL would need EL and EL+E85
3. UEL would need UEL and UEL +85

So selection of maps prior to generation and/or prior to plugging into car would make it more noob friendly as well as the early adopters who are now quite versed with OFT.

btw, how does the beta process go for people with different roms?
How long do you expect the beta trials period to last?
are betas only applicable to the US roms?
how do you confirm the betas are fine for the international guys?
Do you expect international guys to be running beta roms all the time?
Will international guys have their betas in open format so we can make changes if we need to?
Or do we need to wait until changes eventually make it to us?

Sorry if this is off topic but I wondering if open flash tablet ots maps fixed the transient timing table issue associated with DI issues?

I saw the timeout error happen the one time I was able to get to the database. Every other time I've tried to go to the ModFiles Database it gives me an index out of range exception. I have the error log file if you want it.

I've been set in ordering a different tuning solution for my STX build, but I'm seriously considering OFT now. Looks simple, easy to use and update like the Cobb AP I had for my last car.
How easy is it to set launch control and flat foot shifting?
Decisions.. Decisions..

I'm having some trouble with the new .dev file. I deleted and erased all the old .bin files from the 'Upload Data' window, and added and synchronized the .dev file through 'Modfiles Database'. Upon entering the 'Tuning' menu, it doesn't generate compatible tuning files like in the video, and the 'Read' and 'Write' buttons are grayed out. I have a US 6MT

Yeah, I'm having the same problem with the 6AT. I've gotten around the error I was having, and I've deleted the .dev file from the program folder multiple times, but the OFT won't generate the tune files.

have it working, try unplugging oft from usb, close ofm, re-open ofm, plug in oft, go to modfile database section. if file is there now, click "sync", if not there, try adding again.

first time mine didnt take, but second try after reconnecting oft and restarting ofm worked.
make sure to hit "sync" even if the file already says "syncronized" in the file status

No go for me; I can't get into the database section again after the first attempt. The only way I can get back into it is to delete the .dev file from the DataBase folder, which effectively resets this process it seems. And even that sometimes is not enough to prevent the "index out of range" exception I keep getting.

I'm running this on Windows 7 64-bit. Anyone else having similar problems?

Sounds silly, but have you tried running the win 8 patch, or renaming the .dev file?
I run 7 64, and win 8patch..

Which OFM are you running?
What is your current firmware version?

OFM is version 1.06, just re-downloaded it from the site.
Tablet firmware is on 1.21.

I've tried installing the Windows 8 patch just for kicks and that didn't seem to have any effect either.

I just uninstalled OFM, went through my registry and deleted all references to OpenFlash, deleted the old installation directory, and restarted my computer. Reinstalled OFM, ModFiles DataBase loads up fine the first time. After closing out of the program and reopening it, I can't get back into the ModFiles DataBase portion of the app.

I HAVEN'T tried renaming the .dev file, I'll give that a whirl.

Edit: Renaming did nothing, but I DID figure out how to get into the database more than once; I have to plug the OFT into a different USB port between attempts. What is this I don't even.

Edit edit: Still won't generate the tune files. I give up til next update. :sigh:

PantsDants,
You don't need to rename any files or do anything other than what i described in my original post. If you are still having issues with file generation, give us a call on Monday and we can sort it out. In the meantime, just go ahead and use previously released maps (.bin).

In time we will provide different .dev files for cars with different headers, turbos, SCs, etc. This is just the first release and there are only so many tune types we have available at the moment. It just happens we can fit them in the same .dev file (up to 5 tuned files per ROM type). One the number of available OTS maps exceeds 5, we will have more .dev file to choose from. It should also be noted that you can replace any of the 5 .dev file generated maps with standard .bin files. Just overwrite them as you would normally do.

Beta process lasts as long as it needs to last. In this case, most of the work I have to do is port over the tune file mapping to all the other ROM types. This will take some time. Then we wait for feedback and see if the maps need to be modified in any way before going non-beta. How long this will take is unknown. If anyone does not want to use beta files or wants to edit their tune, they can still use previously released tune files (.bin) as before.

Shiv

Here is the scenario,
On 1.42, the EUDM and AUDM roms became supported but no logging of iam like the usdm roms at the time.
td-d found the addresses as per your request.
You said that we would get logging for iam, fbkc and flkc for 1.50 international roms.
1.50 USDM roms gets released as a dev file.
The EUDM and AUDM roms are still coming but will be only in a dev file?
So the only ones we can access is 1.42 and we still can't log for iam?

Will 1.50 EUDM/AUDM dev file contain UEL and UEL +E85?
What do we do if we have issues and need to access the tune to see what is going on or make alterations? since there were no tune files available before, do we just wait until you get back to us?

Are you able to put some priority on the EUDM/AUDM guys to get it to the same level playing field?
The reason why I asked the previous questions was because it appears we're been skipped over for beta trials as well as sufficient tune file access now we are switching over to dev files.

Tried to give this a shot this morning, but read/write are grayed out. I'll try to redo it again after work. I have a US 6mt. Installed ofm 1.06 over top of the old one. Deleted the old bins and went to add the .Dev file. I did get a time out error, but it added and showed it was synced.

Any changes for stage 1 gas? Thanks!

Sent from my SGH-I317M using Tapatalk

I'm still not exactly clear on the cal families or whatever. I've got the a700c. I'm guessing it's not covered yet? That correct?

You also said there was some changes in learning which is exciting. Does this go for stage 1 and 2 gas tunes or just stage two e85?

Sorry for my density on the subject.

I'm almost positive he said that all S2 maps had changes to learning. Not sure about S1 maps though.

The release notes say the following:

Except the release notes are wrong. Shiv said in the first post that the cold start cranking enrichments were not changed from 1.42.

No go for me either. I went through the steps several times, reinstalled OFM, same problem. I'm on ZA1JA01C.

Yup, but later he said slightly different things.

I'm just not sure anything is available for me right now. I'm also not sure what's available now is better than my current tune. Shiv made a slight adjustment to mine a few months back. He was going to do more but I waved him off so he could focus on more important things since I'm getting the nameless header anyway. I'll just wait till I know for sure a700c is supported then try it and log to see if it's still rich.

I'm blown away by his desire to help everyone and take on so much work all the time.

I was going to ask if it would eventually be updated so that the .dev file would be loaded with .bin files, but this sounds totally fine. I guess I need to get in on this .dev thing and drop a couple of .bins in place of the tunes I don't need just in case.

What are the FFS and LC settings on the 1.50b maps?

Edit: I forgot to ask, will there be issues if the ROM that is on the car is not there when we do the .dev files? I know this was an issue before.

I'm on that Rom and I got it to work. Did you allow the OFT to do it's updates and delete all the maps you had in it already? The first time I tried I didn't hit start after deleting all the maps on the load tab before trying to load the new map, which causes an error.

Yeah, I removed them properly every time. OFT is all up to date, ver 1.21.

What is it saying when you try to load the new file?