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

[zeppy]

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?

[PantsDants]

Originally Posted by shiv@vishnu

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

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.

[xDanger_208x]

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..

[moK]

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

[PantsDants]

Originally Posted by moK

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.

[Danklvr]

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

[PantsDants]

Originally Posted by Danklvr

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?

[Danklvr]

Originally Posted by PantsDants

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..

[s2d4]

Originally Posted by PantsDants

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?

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

[PantsDants]

Originally Posted by s2d4

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.

[PantsDants]

Originally Posted by Danklvr

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

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.

[Shiv@Openflash]

Originally Posted by PantsDants

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.

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).

[Shiv@Openflash]

Originally Posted by s2d4

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?

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

[s2d4]

Originally Posted by shiv@vishnu

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.