Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB

Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB (https://www.ft86club.com/forums/index.php)
-   Forced Induction (https://www.ft86club.com/forums/forumdisplay.php?f=78)
-   -   OpenFlash Tablet Datalogging Suggestions (https://www.ft86club.com/forums/showthread.php?t=51421)

Shiv@Openflash 11-15-2013 02:56 PM

OpenFlash Tablet Datalogging Suggestions
 
Hi guys,
Datalogging/datagraphic (beta) has just been released for the twins:

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

Next week we are going to implement some updates/fixes. But I also want to start working on some features for your FI guys.

So the questions are:
-What channels would you like to see added in addition to what is currently logged (see link above).
-What kind of custom display would you find useful. Perhaps one with Boost (PSI) dominating the screen and coolant, oil and air temp in the background displayed in bar graph? Maybe have the OFT audibly beep and have the screen flash RED when knock correction is greater than 1deg?

Just tossing around some ideas. Looking forward to your feedback :)

Cheers,
Shiv

jamesm 11-15-2013 03:19 PM

maf voltage is crucial. i didn't notice it in the other thread you linked to.

other than that, i'd say ltft, stft, flkc, fbkc, iam, knock correction advance, all the relevant temperatures (especially intake air temp for filtering maf scaling data), map, injection mode (direct/either/port), fuel system mode (cl/ol), port ipw, and probably a bunch more that i can't think of off the top of my head.

really in the end it's best to just give us all of them and let us choose which to use at any given time.

nelsmar 11-15-2013 03:28 PM

Quote:

Originally Posted by jamesm (Post 1333757)
maf voltage is crucial. i didn't notice it in the other thread you linked to.

other than that, i'd say ltft, stft, flkc, fbkc, iam, knock correction advance, all the relevant temperatures (especially intake air temp for filtering maf scaling data), map, injection mode (direct/either/port), fuel system mode (cl/ol), port ipw, and probably a bunch more that i can't think of off the top of my head.

really in the end it's best to just give us all of them and let us choose which to use at any given time.

This. Or hell just give the ability to type in memory address and math formulas if it came down to it.

King Tut 11-15-2013 04:47 PM

I just want it to tell me my distance to empty (DTE). :lol:

Shiv@Openflash 11-15-2013 05:20 PM

Quote:

Originally Posted by nelsmar (Post 1333775)
This. Or hell just give the ability to type in memory address and math formulas if it came down to it.

This is an interesting suggestion. I'll pass that along to the programmers and see if that is feasible within the structure of the OFT software.

AZFA20 11-17-2013 01:56 AM

Pretty much everything mentioned thus far I agree with. Love the idea of knock retard warning especially on a custom display that could be used on more of a daily basis or track events. 1 degree may be extreme though since most of us FI guys are going to experience some level of "tip in" knock correction from time to time. Perhaps 3 degrees or even programmable options that are time based or degree based.

Love where this is going......

FrX 11-19-2013 04:33 AM

Quote:

Originally Posted by jamesm (Post 1333757)
injection mode (direct/either/port), fuel system mode (cl/ol), port ipw

I'd probably like to see Port Injection % as well, and maybe Injection Angle. Realistically, I'd like to be able to just punch in an RAM address and have it's value spit back out at me. AFAIK, this will require a patch to the CAN/SSM handler in the ROM. Which, considering that we are modifying it anyways for our maps, should be perfectly doable.

nelsmar 02-03-2014 12:00 PM

@shiv@vishnu is there any chance we will at least get a log parameter for open / closed loop status and FLKC for easier parsing of logs? I remember you saying you were adding more logging parameters soon, has there been any progress on this? I have had some locals asking me to review their logs but I end up having to meet up with them and logging with my ecutek cable half of the time. :(

zc06_kisstherain 02-03-2014 12:36 PM

is it possible to have separate file that saves datalogging?
like i start 1st one then stop, saves first datalogging file
if i start again, it automatically saves 2nd file of datalogging.
i don't know if this works.

jamesm 02-03-2014 02:24 PM

fuel system status and injection mode are crucial for tuning large injectors or turbo kits where the maf and injectors are replaced at once. i would highly recommend adding those as it will overcome a barrier to tuning FI with OFT.

Shiv@Openflash 02-04-2014 05:27 PM

Hi guys,
Thanks for the feedback. We are just wrapping up the datalogging update for the BMW OFT. After that is done, we are doing the same to the FA20 OFT. At launch we will have the ability to choose from a list of 50 datalog channels (increased from a current list of 12). We can always increase it beyond 50 but I think that will probably be enough. We will certainly make sure we include the channels suggested in this thread :)

Thanks!
shiv

King Tut 02-04-2014 05:28 PM

Sending you a PM about BMW OFT.

nelsmar 02-05-2014 03:31 AM

Quote:

Originally Posted by shiv@vishnu (Post 1503809)
Hi guys,
Thanks for the feedback. We are just wrapping up the datalogging update for the BMW OFT. After that is done, we are doing the same to the FA20 OFT. At launch we will have the ability to choose from a list of 50 datalog channels (increased from a current list of 12). We can always increase it beyond 50 but I think that will probably be enough. We will certainly make sure we include the channels suggested in this thread :)

Thanks!
shiv

Any idea when we may see some of this or get a beat of some sort? This thread is nearly 3 months old and I have been having to use an ecutek cable for datalogging at this time. :( It would be easier to have people send me logs with their OFT with some of the requested items.

Thanks for the response!


All times are GMT -4. The time now is 05:15 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.


Garage vBulletin Plugins by Drive Thru Online, Inc.