OpenFlash Tablet Firmware 1.23 Preview

[R2]

So, I learned tonight that in this firmware version you need to stop logging before turning the ignition off. What happened was I logged for probably 40minutes, shut the car off then went to hit stop logging. Within about 3 seconds, but before I could hit the STOP button I got an "Operation Failed" error or something to that effect. I figured the data would still be saved but it wasn't. The data was from my previous logging session. I'm pretty annoyed by that.

[Shiv@Openflash]

Originally Posted by R2

So, I learned tonight that in this firmware version you need to stop logging before turning the ignition off. What happened was I logged for probably 40minutes, shut the car off then went to hit stop logging. Within about 3 seconds, but before I could hit the STOP button I got an "Operation Failed" error or something to that effect. I figured the data would still be saved but it wasn't. The data was from my previous logging session. I'm pretty annoyed by that.

Of course you need to stop logging It's only then that it saves data to csv file as stated in the on-sceen message.

[Shiv@Openflash]

Originally Posted by wparsons

Tried to pull some a new log off the tablet today, still no luck.

Updated OFM to a freshly downloaded 1.07 again, re-updated the template from a freshly downloaded copy again, took a log with the default 12 channels and it still crashes OFM when trying to download the log.

I'm also getting the IAM dropping quite a lot in daily driving (~0.5-0.7) running 1.56b stage 1, so I'd love to pull the logs to see why.

I highly question the fuel quality in Canada. Most often than not, I've seen their "94oct" perform worse than our 91oct. So I think it's just going to be a matter of being more conservative given octane constraints.

Also with regards to datalogging, can you try to de-select all the channels (in configuration menu) and then enable only engine speed. And then confirm that that works. If it does, then is going to be an issue of one of the datalog channels not be compatible with your ROM ID. It would be good to know which one that is and de-select it.

[steve99]

Originally Posted by shiv@vishnu

I highly question the fuel quality in Canada. Most often than not, I've seen their "94oct" perform worse than our 91oct. So I think it's just going to be a matter of being more conservative given octane constraints.

.

That looks like its also true for Australian Fuel our 98 RON is supposed to be equlivent to US 93 AKI but it does not seem to be as I get the same problem here with IAM dropping does so even on 100 RON (98 + 10% Ethanol).

Cheaper too I reckon we pay about US $2 a litre for premuim fuel ($7 a US gallon ?)

[Nardi330]

Originally Posted by Drofnum

I just got my OFT, loaded a new flash up and all went well. Love the tune. But i am having a problem logging, any time i try to start it up i get an error. I've attached a picture showing the error.

Originally Posted by steve99

Might be worth connecting OFT to PC/computer with latest 1.07 Open flash manager software and let it update over internet then apply the template 1.23 files as well

http://openflashtablet.com/products/...s-2/index.html

i have the exact same thing.

i updated to 1.07 last week and used the latest template 1.23 (freshly downloaded today). maybe i need to re download + install 1.07 tomorrow.

[troek]

yeah im having issues pulling the datalog off my OFT as well.

[Luckrider]

I tried to pull a log last night. I removed IAM and KC Learned I believe. I added in Intake temp and vehicle speed and OFM would freeze when trying to pull the log.

[wparsons]

Originally Posted by shiv@vishnu

I highly question the fuel quality in Canada. Most often than not, I've seen their "94oct" perform worse than our 91oct. So I think it's just going to be a matter of being more conservative given octane constraints.

Also with regards to datalogging, can you try to de-select all the channels (in configuration menu) and then enable only engine speed. And then confirm that that works. If it does, then is going to be an issue of one of the datalog channels not be compatible with your ROM ID. It would be good to know which one that is and de-select it.

It's not fuel quality, guaranteed. If I'm stuck in traffic or in the city the IAM constantly falls, but if I'm out in the country at WOT it climbs back up. If it were fuel quality then it would be dropping even worse at WOT. I can get it up to 1 consistently by beating on the car, but driving nicely in the city or in traffic has it falling fast. This is exactly what other people find on most tunes, even running e85. It's from tip in knock at low load low rpm. The "fix" seems to be to zero out the ignition advance in that range and keep all the timing in the base timing, which keeps it from affecting using coarse correction if it picks up any knock. @jamesm has been playing with this a lot, and has some good info in the thread he started about tip in knock.

I actually got a log to pull off mine last night, not sure what exactly fixed it but here's what I did.

Reflash car back to original bin
Redownload and install OFM 1.07
Update OFT
Upgrade template
Reupload the dev file to the OFT
Reupload each bin file (1.42 stage 1 and 1.56b stage 1)
Flash car with 1.56b
Configure data channels, leave original 12 selected
Log a few minutes
Read from OFM.

Since then I changed back to the channels that first gave me issues, will try to pull if off once I find a USB cable at work (forgot mine at home). If this fails I'll try a channel at a time tonight to see what the culprit is.

[Shiv@Openflash]

Originally Posted by Nardi330

i have the exact same thing.

i updated to 1.07 last week and used the latest template 1.23 (freshly downloaded today). maybe i need to re download + install 1.07 tomorrow.

Did you go to the Configure Channel sceen first? This needs to be done one time (after firmware update) to initialize the channels you want to view/log in the realtime data screen. If you don't do this, you will see that communication error.

[wparsons]

Tried pulling the log from this morning off just now, same symptoms as before. Looks like it's back to square one

I'll go through channel by channel to see which one(s) causes the issue.

[Nardi330]

Originally Posted by shiv@vishnu

Did you go to the Configure Channel sceen first? This needs to be done one time (after firmware update) to initialize the channels you want to view/log in the realtime data screen. If you don't do this, you will see that communication error.

yes i did. i checked pretty much all of the channels.

i just re-installed OFM and will try again later today.

Thanks.

[Burn]

Just connected to my OFT and now firmware is updated to 1.24

[Shiv@Openflash]

Originally Posted by Burn

Just connected to my OFT and now firmware is updated to 1.24

Yep... just some update unrelated to the FA20 protocol. Nothing worth mentioning

No need to reload the latest Template file if you did so already.

Shiv

[steve99]

Originally Posted by wparsons

It's from tip in knock at low load low rpm. The "fix" seems to be to zero out the ignition advance in that range and keep all the timing in the base timing, which keeps it from affecting using coarse correction if it picks up any knock.

Note I did not zero out all the "Knock advance table max A" to stop my IAM dropping.

The first screen shot shows the changes I applied ie -0.35 to about 12 cells.
The "zero's" are no change. This was at screen shot of table comparison between modified table and standard table from 1.56 stage 1 tune

The Second screen shot shows the resulting values in the Knock advance table.

see here

http://www.ft86club.com/forums/showp...0&postcount=64

This has been working quite well for me.