OpenFlash Tablet Update (Template and Tuning Alerts)

[hmong337]

Honestly, the biggest drawback for me would be load time of the tune file with the OFT. Dyno time is at a premium and it would be hard facing precious tuning time being lost to file writing- even for the smallest changes. That's sorta the debate I'm having with the OFT. I am okay to drop ~$1000 for the Ecutek stuff but their business model stinks and would rather just avoid them entirely. I can't do a standalone EMS because of emissions laws in my region so I'm left with not much else. I guess I will continue to lurk around OFT and see what happens? But for real, OFT and it's monitoring and logging capabilities are worth the $500 alone.

Is there anyway to speed up file write times?

[Shiv@Openflash]

Originally Posted by hmong337

Honestly, the biggest drawback for me would be load time of the tune file with the OFT. Dyno time is at a premium and it would be hard facing precious tuning time being lost to file writing- even for the smallest changes. That's sorta the debate I'm having with the OFT. I am okay to drop ~$1000 for the Ecutek stuff but their business model stinks and would rather just avoid them entirely. I can't do a standalone EMS because of emissions laws in my region so I'm left with not much else. I guess I will continue to lurk around OFT and see what happens? But for real, OFT and it's monitoring and logging capabilities are worth the $500 alone.

Is there anyway to speed up file write times?

Speeding up writes times is easy. It just involves writing a small portion of the ROM (where the mapping data is located) instead of the whole ROM. This would reduce write times to 30 sec versus 5 minutes.

The problem with this is that it can be risky if the user doesn't know what he is doing. It's would be possible to write a portion of a ROM into a ROM file that isn't compatible. Which would result in a corrupt file and a possibly nonrecoverable ECU. This is not to say that we will never offer partial writing. But it is something that takes a good amount of time to implement correctly with sufficient safeguards for the end user.

[Robert@Openflash]

you should get one and I can set one up for you.

Originally Posted by hmong337

Why don't I have one of these yet!?!?

[steve99]

Originally Posted by Shiv@Openflash

Speeding up writes times is easy. It just involves writing a small portion of the ROM (where the mapping data is located) instead of the whole ROM. This would reduce write times to 30 sec versus 5 minutes.

The problem with this is that it can be risky if the user doesn't know what he is doing. It's would be possible to write a portion of a ROM into a ROM file that isn't compatible. Which would result in a corrupt file and a possibly nonrecoverable ECU. This is not to say that we will never offer partial writing. But it is something that takes a good amount of time to implement correctly with sufficient safeguards for the end user.

Dont like contradicting anyone but taxtrix\ecuflash does complete rom write of 1280k bytes

tactrix\ecuflash does full erase first then writes complete rom its always 80 sec does not matter if your writing a couple of changes to an existing rom or a complely new rom ie different calid like updating from A01G to D00G. that has completly different structure so partial write would not work.in that case.

So its certianly possible to write a full rom in that timeframe.

Agree partial write would be a dangereous practice with all the different rom types structures, patches ect.

[Shiv@Openflash]

Originally Posted by steve99

Dont like contradicting anyone but taxtrix\ecuflash does complete rom write of 1280k bytes

tactrix\ecuflash does full erase first then writes complete rom its always 80 sec does not matter if your writing a couple of changes to an existing rom or a complely new rom ie different calid like updating from A01G to D00G. that has completly different structure so partial write would not work.in that case.

So its certianly possible to write a full rom in that timeframe.

Agree partial write would be a dangereous practice with all the different rom types structures, patches ect.

If they are writing the entire file in 80 seconds, that's great news. We should be able to do that as well as it would just be a matter of reducing the wait time between each CAN command. I'll CAN sniff a write through Taxtrix cable to confirm. Thanks for the info!

Cheers,
shiv

[Jyn]

Seems like this would make using E85 without a flex fuel kit much less stressful. Very nice!

[Thorpedo]

Originally Posted by Shiv@Openflash

You can configure up to 3 different Tuning Alerts. And each Tuning Alert can have up to 4 conditionals that can be set as an OR or AND condition. For available channels, it will be a subset of the up-to-14 channels you configured for data logging/viewing. So if you wanted to create a lean run alert, you would do something like this in one of the 4 Tuning Alert menus:

Throttle > 70%
Engine Speed > 2000rpm
Engine Load > 1.0
AFR > 13.0
AND

With these settings, the alert would trigger if all of those conditions were met. The throttle and engine load conditions would keep the alert from triggering during lean spikes caused by lift throttle or traction control intervention. And the RPM condition would keep it from triggering at very low RPM where AFR can be a bit unstable. The AND setting makes sure that ALL of these conditions must be true for the alert to sound. If you used an OR setting, only one of these conditions would have to be true for the alert to sound.

You must be in the Realtime Data screen for the Tuning Alerts to work. You can be in any one of the 3 viewing options (14 channel, 3 channel or graphic). One the alert triggers, the OFT will beep and the flash the screen. After that the triggered channels will flash. To reset the channel flashing, simply press the RESET button.

To create a good Tuning Alert for low Advance Mult, you can simply set up a second Tuning Alert using just one single conditional.:

Advance Multiplier < 0.5

For a good Tuning Alert for overboost, overheat and knock, you can set up a 3rd conditional like this using an OR setting (so only one single condition needs to be true for the alert to trigger):

Boost > 10psi
Coolant Temp > 240
Knock Correction < -3.0
OR

Pretty awesome, huh?

Cheers,
shiv

My god man, I got a chubber from reading that.

[Tromatic]

I'd like to see the OFT tablet become a "dongle" that could connect via BT or WiFi to a tablet or laptop. That would be cool.

n7777;2102108]So many vendors have come and gone. So many tuners have come and gone. You keep rocking.[/QUOTE]

And each tune only gets better as well.

[Malt]

Originally Posted by Tromatic

I'd like to see the OFT tablet become a "dongle" that could connect via BT or WiFi to a tablet or laptop. That would be cool.

So many vendors have come and gone. So many tuners have come and gone. You keep rocking.

And each tune only gets better as well.

That sounds like a dangerous proposition considering if you ever lost wifi or bluetooth connectivity with the device you'd be left with a partially written ECU. If you are looking for just something with a real time display of stats then torque with a bluetooth dongle will work somewhat but I cant imagine we'll ever see any tuning device offer full wireless writing to the ECU. The risks are just to high.

[Shiv@Openflash]

Originally Posted by Thorpedo

My god man, I got a chubber from reading that.

Just the kind of feedback I like hearing

[phrosty]

Originally Posted by Malt

That sounds like a dangerous proposition considering if you ever lost wifi or bluetooth connectivity with the device you'd be left with a partially written ECU. If you are looking for just something with a real time display of stats then torque with a bluetooth dongle will work somewhat but I cant imagine we'll ever see any tuning device offer full wireless writing to the ECU. The risks are just to high.

I agree, wireless flashing sounds like a disaster waiting to happen.

If one doesn't already exist, it likely wouldn't be too challenging or expensive to create an OBDII -> serial -> usb cable, and then a tablet app that could interface with it. Would enable some cool possibilities that aren't really possible on the OFT hardware.

*hint*hint* Openflash

[Malt]

Originally Posted by phrosty

I agree, wireless flashing sounds like a disaster waiting to happen.

If one doesn't already exist, it likely wouldn't be too challenging or expensive to create an OBDII -> serial -> usb cable, and then a tablet app that could interface with it. Would enable some cool possibilities that aren't really possible on the OFT hardware.

*hint*hint* Openflash

They have USB dongles that can interface with a laptop (Tactrix) and yes I realize that you are looking for a tablet app but I'm curious what cool possibilities do you envision that would be possible with such a setup that isn't possible with the current OFT?

[hmong337]

If you can get the write times down a lot more, I'll be all over this. 80secs is good. But not the painful 5+ minutes it takes as seen in your OFT video.

[phrosty]

Originally Posted by hmong337

If you can get the write times down a lot more, I'll be all over this. 80secs is good. But not the painful 5+ minutes it takes as seen in your OFT video.

Do you change hardware often enough for it to matter?

Don't get me wrong, I'd love an 80sec flash time as well but a few minutes is so far from a deciding factor for me.