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

[Shiv@Openflash]

Originally Posted by FrsDuke

Is it possible to do this from j700c to ja01c with OFT?
If so I'd LOVE it.

At this time, you cannot update your ROM without actually installing the OFT. And part of the installation process is reading your original ROM. If it is an old 700c ROM, you will only be able to load tune files that are compatible with 700c ROMs. With the .bin approach, that's not a problem since all our tune files are a01c roms that have had has their ID changed to 700c so that the OFT doesn't see any software mismatch while still giving you what is essentially an updated ROM.

One thing that I've been thinking about is adding a function to the OFT that will allow you to update your ROM (with an updated stock ROM) prior to actually "installing" it. It would certainly be less work on my part than to right an .dev instruction set that converts an old 700c/900c ROM to a new A01c ROM. I'll talk with the programmers tomorrow and see if that can be implemented quickly.

Shiv

[Shiv@Openflash]

Originally Posted by AdrianG

How long will I be waiting for a 1.50 bin release?

- AdrianG

I don't know at this time. If you email me your stock (but not actually stock) ROM, I can add it to the .dev file and release a new version of it that will support your ROM.

Cross- I looked at the stock ROM you sent me and it is indeed stock. So I don't why you are still have a problem. If you give us a call on Monday I can walk through things with you to make sure everything is done correctly. One thing that bothers me is that your fw number still shows 113 in your OpenFlash Manager. It should say 121 which suggest that your OF Manager software may not have been updated correctly somewhere along the way. My suggestion is to go to control panel and remove OpenFlash Manager application. Then to go C drive and delete the entire OpenFlash folder. Then download the Setup application from our website again and install it. Then give it another try.

Shiv

[Cross]

Alright I am going to put my car back to stock, complete erase my OFT then load the 1.42 E85 UEL Map and see if I can get past my issue.

This will also tell me if it drops my FW Version as 1.14 and goes up to the new version. More of just a side thought.

I will give the delete and reinstall a shot now too.

[FrsDuke]

Kinda what I was getting at . Would save you a ton of time to only have to publish a C family D family etc .dev and bins. Looking forward to that.

Originally Posted by shiv@vishnu

At this time, you cannot update your ROM without actually installing the OFT. And part of the installation process is reading your original ROM. If it is an old 700c ROM, you will only be able to load tune files that are compatible with 700c ROMs. With the .bin approach, that's not a problem since all our tune files are a01c roms that have had has their ID changed to 700c so that the OFT doesn't see any software mismatch while still giving you what is essentially an updated ROM.

One thing that I've been thinking about is adding a function to the OFT that will allow you to update your ROM (with an updated stock ROM) prior to actually "installing" it. It would certainly be less work on my part than to right an .dev instruction set that converts an old 700c/900c ROM to a new A01c ROM. I'll talk with the programmers tomorrow and see if that can be implemented quickly.

Shiv

[Cross]

Alright the return to stock, full delete off my laptop went well. It registers the OFT as never having been connected.

I am going to connect it and then give it a try again with 1.5, I have uploaded a screen shot that says everything went smoothly... Just like last time.

[Lytheum]

My original was the stock ROM and car currently has ots 1.42 loaded. Still haven't given the whole process a second try yet.

[Cross]

This time it seems to have worked.

Shiv does this seem like having a modified version of one of your roms already loaded that is also renamed could be the issue or was this just some random glitch?

I am waiting for it to finish loading when it does I will check that all area's say the FW version is 1.21. Before the top FW Version did but when you selected Upload or Download that section still said 1.14 as I had mentioned before and a few others had mentioned and posted screen shots of a while ago.

Both Firmware in the Top Right and the Update/Download sections say 1.21 now.

[Terrapin77]

Originally Posted by shiv@vishnu

At this time, you cannot update your ROM without actually installing the OFT. And part of the installation process is reading your original ROM. If it is an old 700c ROM, you will only be able to load tune files that are compatible with 700c ROMs. With the .bin approach, that's not a problem since all our tune files are a01c roms that have had has their ID changed to 700c so that the OFT doesn't see any software mismatch while still giving you what is essentially an updated ROM.

One thing that I've been thinking about is adding a function to the OFT that will allow you to update your ROM (with an updated stock ROM) prior to actually "installing" it. It would certainly be less work on my part than to right an .dev instruction set that converts an old 700c/900c ROM to a new A01c ROM. I'll talk with the programmers tomorrow and see if that can be implemented quickly.

Shiv

@shiv@vishnu, just an FYI that A01C is not the newest ROM for US cars, For the A/T, it is ZA1JB01D. For the M/T, it is ZA1JB01C.

[Shiv@Openflash]

Originally Posted by Terrapin77

@shiv@vishnu, just an FYI that A01C is not the newest ROM for US cars, For the A/T, it is ZA1JB01D. For the M/T, it is ZA1JB01C.

Correct. A01c/A01d is the newest in the a A series roms (usdm 2012)
And B01c/B01d is the newest in B series (usdm 2013)

When updating roms, you want to update to the newest rom in the same letter series. You don't want to update an a01c to b01c.

Both A and B series roms are supported in the v1.50 dev file.

[tonystewart]

Will the new unit I purchased today come with the new 1.5 dev file?

[Terrapin77]

Originally Posted by shiv@vishnu

Correct. A01c/A01d is the newest in the a A series roms (usdm 2012)
And B01c/B01d is the newest in B series (usdm 2013)

When updating roms, you want to update to the newest rom in the same letter series. You don't want to update an a01c to b01c.

Both A and B series roms are supported in the v1.50 dev file.

Are you sure about that? Take a look at the attached screenshot. It is from a TSB in December. Sorry, if this is a dumb question. I'm new to tuning and I'm trying to learn all that I can. The way I understand how the OFT works is that you use the lastest ROM from Toyota/Subaru as your base, then make your changes and then convert the CAL ID's so it works for all the various ID's. For instance, my CAL ID is ZA1J700D, but in reality, when I flash your OTS map, the base of that map should be ZA1JB01D. Am I correct in my thinking?

[zc06_kisstherain]

great to have new updates

[Shiv@Openflash]

Originally Posted by Terrapin77

Are you sure about that? Take a look at the attached screenshot. It is from a TSB in December. Sorry, if this is a dumb question. I'm new to tuning and I'm trying to learn all that I can. The way I understand how the OFT works is that you use the lastest ROM from Toyota/Subaru as your base, then make your changes and then convert the CAL ID's so it works for all the various ID's. For instance, my CAL ID is ZA1J700D, but in reality, when I flash your OTS map, the base of that map should be ZA1JB01D. Am I correct in my thinking?

I have run into an issue with a customer trying to backdate a B01C rom to a A01C rom. I have not had an issue updating my A01C rom to a B01C rom (other than some logging channels not working after the update). So I'm a bit hesitant to routinely update A01Cs to B01Cs until I know more about the update. It's certainly possible (and likely from it seems) that it's a valid update. But in the spirit of KISS (keep it simple stupid), we are going to differentiate between them until we have reason not to

shiv

[Burn]

Hi Shiv,

Do we need to wait for our ROMS to be supported in the database first or we can download the dev file and load into the OFT for the case of non USDM roms ?