Ending up erasing everything and starting from scratch. Still no IAM or KC learned (unless I'm having huge knock issues). I guess the old 700C is a bit different.


From what I understand, flashing the ECU will overwrite the entire software load. So when I flash, these parameters (IAM and KC) will function properly? Will I have any problems since this is an old ROM?

If you have a 700c why can't you flash to stock, take it to Toyota or Subaru and get them to flash to 701c. It's a tsb and shouldn't be an issue?

http://www.ft86club.com/forums/attac...1&d=1386706237

Tsb to get flashed off the 700c calibration

Unfortunately I don't believe Subaru ever released a TSB for this?

No idea but you are not the only one. It doesn't work on the ZA1JA01I either.

I believe Subaru's solution was to actually replace the ecu. It's been over a year though.

Can anyone answer these questions?

This is strange. I'm not getting any other reports of 700C ROMs not logging IAM and KC. I have even seen datalogs from 700C customers showing both channels logging properly. The only time IAM and KC won't log properly is with the stock (original) ROM. But once you upload one of our OTS maps, you will effectively have a A01C ROM and both channels should log properly. Unless something else is going on, I have not had any other reports of 700C not logging IAM or KC. But I'm open to the feedback of others just in case there is something else going on that I'm not aware of.

http://www.ft86club.com/forums/showthread.php?t=53696

Shiv

I am still on the stock ROM. If this is the way it is supposed to work (incorrect IAM and KC on the STOCK ROM), then there may not be a problem at all!

Correct. Looks like there is no problem after all. Just load one of our OTS maps :)

I have done some modification to the my Stock Rom , and pulled some data logging
Feedback are welcome

http://datazap.me/u/larbikinaa/super...-calibration?1

What have you changed?
It doesn't appear to be running lean anymore.

basically a local tuner helped me
i don't know exactly which tables he modified ,I just want to post and share the results with you guys and get some feedback on how my car is running

Is tranny temp something that will be available to monitor at some point @shiv@vishnu

I don't see why not. If it can be logged in Techstream, we can log it with the OFT too. I guess that's another reason to get my Techstream working :)

Got curious of my own after seeing these logs and decided to make one on the drive home tonight

http://datazap.me/u/mok/1222-all-stock-91-octane

Any feedback appreciated!

IAT - can we log this?
 

When OFT data logging first came out, we had IAT. With the update, this was replaced. Can this be logged again or somehow chosen over something else in the OFT? Thanks.

logging IAT
 

If the OFT won't monitor/log IAT (assume this is intake air temp) then you can do it with one of these

http://www.ebay.com.au/sch/i.html?_s...rt=nc&LH_BIN=1

using android torque app and most likely the included windows software, however i have only used torque app in android

With the next update to datalogging, the number of available datalog channels will increase significantly. IAT removal was just a quick fix so that we had room to add Adv Mult within the available framework. Next update will allow you to pick (from a much bigger list) what channels you want to log/monitor/graph.

thanks - i actually have the torque app - gotta be one of the all time bests - i use it in hud to watch afr
with the oft, though, it logs faster and more accurately than it does with the torque app
can't wait for the next update

I really don't want to take the time to read through he previous ten pages. I have looked in a number of threads and your website and maybe I am just not finding it... But can you give me a list of what is currently supported for data logging and what is to be expected within the next 60 days?

I have had a number of people locally ask me about OFT and I have not been following all of the threads on the recent updates. There doesn't seem to be a central place that actually specifies what is all currently supported at this time.

I can't be the only person that has interest in data logging capabilities... Right?

http://www.ft86club.com/forums/showthread.php?t=53554

Keep in mind they are adding more channels soon as well.

Thanks. I wonder where @shiv@vishnu is on this topic...

So there is no logging for engine load, commanded AFR, FLKC, throttle, accelerator, coolant, oil, MAP, VVT Exhaust, or other bits I would use when actually tuning? These aren't "required" for tuning but make my life a hell of a lot easier than guessing. Having to calculate engine load by hand would be irritating.

I originally contacted offering to help with data logging a while back but was not getting much of a reply other than "talk to so and so" which just went in circles.

Can anybody confirm for me that the only log results are:

Currently you can log the following on oft.
Time[s]:
Engine Speed:
Throttle:
MAF Voltage:
Engine Load:
VVT Intake:
VVT Exhaust:
Ignition Advance:
KC Learned Value:
AFR:
ST Fuel Trim:
LT Fuel Trim:
Adv Multiplier:

there are some very important ones missing, but i'm sure they'll be added in time. what's there now isn't really sufficient for the purpose of tuning.

Yeah... Personally there are more things I want. And have heard "Soon". I have been falling behind on this and the open source stuff. Not to throw this off topic but have the open source guys gotten something usable working now? Or still heavy in testing phases?

not what i'd call 'useable' at this point. last i heard they were still figuring out parameter locations and there was still no support in romraider's logger, only direct to sd card in the cable. i could have out of date info though.

The channels the OFT currently logs is just the bare minimum required for tuning (as per the list that FRSDuke provided). The framework of the data logging interface is in the process of being updated to allow for the user to log/monitor/graph on-screen up to 12 channels out of a selection of 30-40 channels (at ~15 samples per second). We hope to have that up and running within the next few weeks. I don't like giving ETAs because that is only one of the updates we are working on now.

Cheers,
shiv

Out of curiosity, what other values are missing that should be noted when properly tuning? Every opportunity I get I'm trying to pick on how to read data logs to see how the engine is handling the given tune. Once I have a good grasp on where values should be and am able to point out abnormalities I may venture into editing maps, but I'm not quite there yet. @jamesm thanks for posting the screen casts. I'm sure many of us find them informative and appreciate you taking the time to put them up.

On screen is cool and all, and useful but all I personally care about is having them on my computer, where i am actually editing the tune. When I am tuning I don't have to look at a second little screen for data i already have one in the laptop. Are there any plans for your device to support J2534 to go along with the other "open" stuff? Or is it going to stick mainly as a handheld device for basic flashing with no direct ecu communication with a laptop? Sounds like extra work on my end for logging personally.

a few crucial ones i can think off-hand are:

injection time port/direct final
fbkc
flkc (maybe that's knock correction learned value?)
fuel system status
map sensor
intake air temp
throttle delta (useful for tip-in enrichment tuning, not crucual though)

intake air temp and map are most important as they are necessary for calculating things like ve and fueling error. knock parameters are of course very important as well.

You can export the datalog file from the OFT to your laptop in OpenFlash Manager. It less than 3 seconds to download a 100k datalog file (.csv) and can store a hours worth of data (12 channels logging at ~15hz). At that point you can view it in our datalog viewing software, on datazap, in Excel, etc,. Do you have an OFT?

We don't have any immediate plans for direct ECU-to-laptop communication (i.e., OFT connecting to both the ECU and the Laptop at the same time). It's not been a popular request but I suppose anything is possible with enough time.

Shiv

with oft you'd log everything to csv then open the files on your computer. i'm pretty sure it can store a sufficient amount of data. given the transferring back and forth would be a bit of a pain, it's workable, very similar to using a tactrix cable to log.

FLKC for one is something i highly desire. MAP input is something I would need for anything higher horsepower, this is considering if the open source community does get SD up and going somewhat soon. But there are still benefits to this.

I use Commanded AFR quite a bit, just makes life easy to see how far maf scaling is off. Also is there any support for a wideband? The stock wideband is great and all but having to combine the log files my self is annoying. I would rather the hardware log it for me, or software or however the "package" works. Sure I can just log wideband & RPM and then look over it while on the dyno, that works fine but it is handy to actually have this in one log file together. Especially when street tuning vs opening two files and viewing them independently.

I could go down a long list of additional things I would want like throttle delta, PI duty, total ML injection, port time, and DI time. Its nice to be able to do the math and ballpark where you are on injector duty. There are tons of things that can be used in a number of scenarios. Hell getting CPS Voltage would even work as a rugged hack for wideband logging if it was available.

Oil temp can help to diagnose issues, as well as coolant temp, the list goes on.

I do not but a number of locals have contacted me about tuning on OFT and I said I would research what tools were available with its package. Looks like at this point it isn't up to par to what I am wanting for actual tuning. For being a flasher like cobb it seems like a great device for OTS maps etc and some basic tweaking but really is lacking in the datalogging & extra work required for datalogging if i am going to have to transfer logs back and forth like that. Not having live editing alone is already a massive hassle. We calculated the time I have spent flashing a local car during extensive testing and we are almost to 7hrs just waiting for the ecu to flash at this point.

This is exactly my view as well. Sounds like a great device for minor work but for heavier work it might not be what I am looking for.

In the next OFT datalogging update, all of those (among others) will be added to the list of available channels. As well as a screen dedicated to the Fine Learning knock correction matrix.

Cheers
shiv

good call on the matrix view... very useful thing i miss from brzedit

Hi all,

just had my first attempt at data logging and I uploaded the file here

http://www.datazap.me/u/boofneenee/b...l-1?1-7-8-9-11

I believe you should be able to copy paste link into browser and view yourself. Actually, thats sort of what I was hoping you would do! I dont really know how to interpret these figures and I would appreciate it if someone with knowledge in the area can have a look. I did not have the opportunity to get the rpm's past 6800 as cars on the highway prohibited me! I had two decent pulls in 3rd gear as you can see from engine speed tab.

In any event, I have a K&N filter, nameless 2.5 inch OP/downpipe 1 piece combo with 5" mufflers.

I will be running another log later today and pulling to redline.

thanks!

Always include a couple good third gear pulls going 1500-7500 rpm at WOT if you can. I usually do this on a flat rural highway that is free of traffic and speeds of 70+ mph are permitted.