OpenFlash Tablet

[keen as]

Originally Posted by shiv@vishnu

Yep! That will come later. The colorful bar graph on the bottom would actually display AFR while the numberical value would show boost.

Excellent, I look forward to the update.


Can oil temp be added as a third display?


Also can an option be added for Metric measurements including degrees Celcius for temps?

[steve99]

Originally Posted by nelsmar

Yes on ecutek we can use it as an input. However in factory form there is a fuel trim compensation for rear o2. I have a local who has a problem and is getting DTC's that I have resolved by setting these values to 0 from -0.5 / 0.5 (factory values). The oem ecu uses these values to apply minor fuel trims. I never tested to what extent it will trim through, its a bit of a PITA to test something like that!

Where did you find those tables ?

[nelsmar]

Originally Posted by steve99

Where did you find those tables ?

In ecutek:
Fueling -> Air/Fuel Correction -> AF Correction #3 Limit - Rear O2 Sensor

[mid_life_crisis]

Finding E85 is a bit of a PITA around here, but I just have to try it once to see what all the fuss is about. I'm sure this was covered somewhere, but again, too many threads/posts to read them all.
So my questions are: "how low do you have to run the tank of 93 before refilling with E85 and reflashing?" and "is it the same level when going back to 93?"
That last seems like an obvious "yes" but I've learned to take nothing for granted.

[Luckrider]

I have switched just a few times, but I always run it down as low as possible. I usually get 11.5 gallons in when I switch and I drive for several miles before flashing. If the trims are fluctuating too much after flashing (like 51 miles), I will usually flash again to the new map under the assumption that the first flash was too early and the trims were compensating for the 93.

[mid_life_crisis]

Originally Posted by Luckrider

I have switched just a few times, but I always run it down as low as possible. I usually get 11.5 gallons in when I switch and I drive for several miles before flashing. If the trims are fluctuating too much after flashing (like 51 miles), I will usually flash again to the new map under the assumption that the first flash was too early and the trims were compensating for the 93.

I had to think about this for a second until I realized I had overlooked the fuel already in the line. I hadn't even considered logging, which I now realize was short sighted. It sounds like a whole can of worms I should avoid for a one time thing. Especially since if I like it that much, I'll be screwed because corn juice is not readily available in these parts.

[Luckrider]

Originally Posted by mid_life_crisis

I had to think about this for a second until I realized I had overlooked the fuel already in the line. I hadn't even considered logging, which I now realize was short sighted. It sounds like a whole can of worms I should avoid for a one time thing. Especially since if I like it that much, I'll be screwed because corn juice is not readily available in these parts.

Hell No... I did it for just one tank of e85 and it wasn't bad at all. It might not have been optimal, but that is how you make sure everything is good.

[keen as]

Originally Posted by mid_life_crisis

Finding E85 is a bit of a PITA around here, but I just have to try it once to see what all the fuss is about. I'm sure this was covered somewhere, but again, too many threads/posts to read them all.
So my questions are: "how low do you have to run the tank of 93 before refilling with E85 and reflashing?" and "is it the same level when going back to 93?"
That last seems like an obvious "yes" but I've learned to take nothing for granted.

I was looking for this info myself. See http://www.ft86club.com/forums/showp...32&postcount=1


After changing to E85, I idled the car for a couple mins, then drove low revs and slowly for about 5 mins.


The second tank E85 feels slightly better.

[steve99]

@shiv@vishnu

Just connected OFT to laptop it did upgrade. also upgraded OFM to 1.07.1 version connected again and let it update. Firmware in OFT 1.26.

also update template again no joy.

Tried to read new datalog and get unhandled exeption error

Bug ?? or am I doing something wrong

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Source array was not long enough. Check srcIndex and length, and the array's lower bounds.
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length)
at PWGDATALOGGING.PWGDataLogging.readSignals(Byte[] Src, List`1& Signals)
at PWGDATALOGGING.PWGDataLogging.getFileFromDevices(B yte[] DataFile, DataSet& Values)
at PWGPro.DataLoggingForm.readRtime(String NomeFile)
at PWGPro.DataLoggingForm.buttonReadDevice_Click(Obje ct sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3655 (GDR.050727-3600)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PWGPro
Assembly Version: 1.7.1.0
Win32 Version: 1.7.1.0
CodeBase: file:///C:/OpenFlash/OpenFlash%20Manager.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3645 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3644 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3644 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CommonResources
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/CommonResources.DLL
----------------------------------------
PWGResources
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/PWGResources.DLL
----------------------------------------
PWGCommand
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/PWGCommand.DLL
----------------------------------------
PWGService
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/PWGService.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3654 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3654 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
r7bmnqxt
Assembly Version: 1.0.0.0
Win32 Version: 2.0.50727.3644 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
HidLibrary
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/HidLibrary.DLL
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.1 built by: SP
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms.Ribbon35
Assembly Version: 3.5.7.0
Win32 Version: 3.5.7.0
CodeBase: file:///C:/OpenFlash/System.Windows.Forms.Ribbon35.DLL
----------------------------------------
PWGPro.resources
Assembly Version: 1.7.1.0
Win32 Version: 1.7.1.0
CodeBase: file:///C:/OpenFlash/en-US/PWGPro.resources.DLL
----------------------------------------
System.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3645 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
----------------------------------------
PWGResources.resources
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/en-US/PWGResources.resources.DLL
----------------------------------------
PWGCommand.resources
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/en-US/PWGCommand.resources.DLL
----------------------------------------
PWGService.resources
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenFlash/en-US/PWGService.resources.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Td-d]

Originally Posted by nelsmar

In ecutek:
Fueling -> Air/Fuel Correction -> AF Correction #3 Limit - Rear O2 Sensor

I've added AF 3 correction, learning and rear o2 comps to the ZA1JA01C definition up on Github. I'll add to the other definitions shortly.

EDIT - added to all roms on Github

[R2]

Originally Posted by steve99

@shiv@vishnu

Just connected OFT to laptop it did upgrade. also upgraded OFM to 1.07.1 version connected again and let it update. Firmware in OFT 1.26.

also update template again no joy.

Tried to read new datalog and get unhandled exeption error

Bug ?? or am I doing something wrong

I'm having the exact same issues on two different PC's. I contacted them and am hoping for a quick solution as well.

[DC2R]

Originally Posted by R2

I'm having the exact same issues on two different PC's. I contacted them and am hoping for a quick solution as well.

Name sure you manually stop the logging. Had same issue when I just unplugged tablet and forgot to stop logging first.

Sent from my SM-N900T using Tapatalk

[phrosty]

Originally Posted by steve99

@shiv@vishnu

Just connected OFT to laptop it did upgrade. also upgraded OFM to 1.07.1 version connected again and let it update. Firmware in OFT 1.26.

also update template again no joy.

Tried to read new datalog and get unhandled exeption error

Was the log recorded prior to the update? Looks like the data log record size has changed. Wonder if this brings any new goodies.

[R2]

Originally Posted by DC2R

Name sure you manually stop the logging. Had same issue when I just unplugged tablet and forgot to stop logging first.

Sent from my SM-N900T using Tapatalk

Yeah, I thought this might be it, but this morning I made sure I stopped the log before turning the car off or disconnecting the OFT. Same result.