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

[FrsDuke]

Originally Posted by shiv@vishnu

These beta maps currently only support ZA1JA00C, ZA1JA01C, ZA1JA00D, ZA1JA01D, ZA1JB00C, ZA1JB01C, ZA1JB00D and ZA1JB01D ROM types. Additional ROM support will be added over the next several days.

Given that all J___C share the same XDF and all J___D roms share the same XDF, are the j700c/d and j900c/d roms supported by the .dev?

Thanks,

[Cross]

Is there going to be the possibility of adding editing of Launch Control and Flat Foot Shifting using the OFT itself? As you have now put the Beta's in .dev its hard to make the changes some of us have needed to. Launch Control and Flat Foot Shifting is minor but thats why I ask about editing it in the OFT.
However this is what concerns me, in one place you say these maps have been changed to address cold start issues. Then as pointed out someone else quoted where you said they were not. I'm not sure what to believe here but I do know I had to make changes to get my cold starts dialed in.

[FrsDuke]

Originally Posted by Cross

Is there going to be the possibility of adding editing of Launch Control and Flat Foot Shifting using the OFT itself? As you have now put the Beta's in .dev its hard to make the changes some of us have needed to. Launch Control and Flat Foot Shifting is minor but thats why I ask about editing it in the OFT.
However this is what concerns me, in one place you say these maps have been changed to address cold start issues. Then as pointed out someone else quoted where you said they were not. I'm not sure what to believe here but I do know I had to make changes to get my cold starts dialed in.

If I were on e85 and needed to fine tune my cold start stuff I would wait till 1.5 leaves beta and is available in bin format. (I would hate having to wait, but it is what it is)

I know the plan is to allow FFS and LC adjustment via OFT without having to monkey with a computer... I do NOT know if it's implemented yet, and I'd have to assume it is NOT yet available.

[steve99]

Originally Posted by FrsDuke

I'm still not exactly clear on the cal families or whatever. I've got the a700c. .

Found this, I believe FD is final drive (assume diff ratio)

• ZA1J700A - 2012 JDM Manual High FD
• ZA1JA00A - 2012 JDM Manual High FD
• ZA1J700B - 2012 JDM Auto
• ZA1JA00B - 2012 JDM Auto
• ZA1J700C - 2012 US Manual
• ZA1J900C - 2012 US Manual
• ZA1JA00C - 2012 US Manual
• ZA1J700D - 2012 US Auto
• ZA1J900D - 2012 US Auto
• ZA1J700E - 2012 C6 Manual
• ZA1J700F - 2012 C6 Auto
• ZA1J700G - 2012 EU Manual High FD
• ZA1JA00G - 2012 EU Manual High FD
• ZA1J700H - 2012 EU Manual Low FD
• ZA1JA00H - 2012 EU Manual Low FD
• ZA1J700I - 2012 EU Auto
• ZA1JA00I - 2012 EU Auto
• ZA1J700J - 2012 KS Manual
• ZA1JA00J - 2012 KS Manual
• ZA1J700K - 2012 KS Auto
• ZA1JA00K - 2012 KS Auto
• ZA1J700N - 2012 EH Manual
• ZA1J700O - 2012 EH Auto
• ZA1J400P - 2012 JDM Manual Low FD
• ZA1J700P - 2012 JDM Manual Low FD
• ZA1JA00P - 2012 JDM Manual Low FD

If your ROM has 01 instead of 00 then I believe this is the "updated version for transient retard table fix for DI seal problem.

[Cross]

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.

Your not the only one I am having issues with it as well. I have deleted all my tunes, deleted the .dev in the OpenFlash Folder and reloaded it 3 times now with no luck both Read and Write are Gray and it still reads my custom E85 rom on it.

I am not sure about PantsDants but I have my own edited version of 1.42b loaded. Could that be the issues, we need to go to a non-modified version of 1.42 before it will allow us to go to 1.50b?

Perhaps the .Dev releases needed further testing before release?

[FrsDuke]

wonder if you need to flash to stock rom on the car before you let the OFT build it's new tune list.

[s2d4]

Originally Posted by FrsDuke

If I were on e85 and needed to fine tune my cold start stuff I would wait till 1.5 leaves beta and is available in bin format. (I would hate having to wait, but it is what it is)

Sounds great in theory, but a possible consequences of this is the people who are able to make some sense of the tunes/logs won't be thoroughly beta testing the new tunes.

[Cross]

Originally Posted by AdrianG

I load the Dev file successfully, it says it's sync'd, I sync anyways and all is well. I connect it to the car and read & write are both greyed out. From within openflash all looks fine

- AdrianG

This is what I'm seeing too, it all appears fine but it will no let me load a tune.
That's why I find myself wondering of it's looking for a specific flash to already be on the ecu and if it's not it will not allow you to load the new beta.

If this is the case as pointed out by another member, this will prevent those who should be looking at the betas from looking as well as normal users to think the OFT has issues which they will the begin mentioning.


Sent from Spaceball 1

[jvincent]

I just loaded the 1.50 beta .dev onto my OFT. I made sure I had erased the two existing .bins first.

Plugged it into the car, it did it's thing, and the 5 pre-canned tunes were there. The car was flashed with 1.34 when I did this. I reflashed with the 1.50 stage 1. We'll see how it runs this week.

[jvincent]

For the guys with the greyed out write button, did you see the OFT go through the steps of creating the files shown in the video at the top of the thread?

[Cross]

No it didn't.


Sent from Spaceball 1

[AdrianG]

I just tried flashing back to stock and repeating the whole process again, no luck. I was running 1.42b with a small change to LC delta.

- AdrianG

[jvincent]

Originally Posted by Cross

No it didn't.

That probably explains why the write button is grey.

As I understand the process, the OFT reads the .dev file and then based on the ECU image it detects it then generates the 5 programming images.

Not sure what could mess up the procedure, but it sounds like something has gone wrong somewhere. I didn't go back and check, but you are running the latest F/W I assume.

[Cross]

Yes I am and everything is deleted. So far it seems confirmed we have three users with issues and two have modified the base roms.
One for launch control.
One for llc, ffs, and cold starts on E85.

This is the only similarity I can find. However it was just stated that one tried going back to stock I was not clear though if they still had modified llc.


Sent from Spaceball 1