bbarnhill

I just added where you could view HP and TQ on the graph all screen. Next Ill work on marrying up the records of HP and TQ and the original records since I trim some out.

JasonC SBB

Another really good figure of merit to plot vs. RPM is VE derived from:

AFR * fuel_pulse_width * inj_size / displacement * correction_factor_from_fuel_pressure

I do this with the AEM datalog software.

JasonC SBB

And then BMEP divided by MAP divided by the above VE.
This will give you an idea of how optimal your ignition timing is.

bbarnhill

yeah ............ seeing as how I dont know what is in each column (that section is dumb) thats gonna be hard to detect automatically. Id have to know each of those column names and types for all 30 loggers it supports ... geez

Thats the problem on these types of calculations.

bbarnhill

I have an idea how it could be done but dang yall really dont want me to get any sleep do ya

hornetball

iTrader: (4)

A sleeping SW Engineer is an oxymoron. In any case, everything that Jason mentioned is already available in our data logs with one magic ingredient missing . . . derived torque . . . which is what Virtual Dyno has!

As for marrying up records to re-include trimmed data, you can just use that interpolation function I posted earlier.

bbarnhill

Geeeeez

Im trying to think about this issue a bit because now Ill be in the file export business

hornetball

iTrader: (4)

Thinking hurts. No pain, no gain.

bbarnhill

It hurts some of us (ME) more than others.

JasonC SBB

bbarnhill,

What smoothing algorithm do you use to smoothen the torque calc?

Way back in 1998 I wrote a Mathcad sheet for extracting torque from an MP3 audio recording of the ignition pulses. The best smoothing function it had that I tried was "LOESS".

bbarnhill

Jason: we need to talk ... I'm looking for another smoothing algorithm other than the one I'm using. I'm currently using an averaging algorithm, and I've tried Bezier curves too (currently disabled). Something just bothers me bout the smoothing and I cant put my finger on it. Dont get me wrong it works pretty darn good but I think something a little more tailored for smoothing curves without flattening their arc too much would be nicer.

JasonC SBB

Show me your smoothing algo.
Can you find some code examples implementing loess?

bbarnhill

havent looked at LOESS ... its literally just averaging the adjacent points together as it walks up the graph

hornetball

iTrader: (4)

Keep getting the following error boxes with 1.1.7:

On startup:

"Could not load columnnames.xml. Default values will be used."

During execution and on shutdown:

"Failed saving columnnames.xml: There are multiple root elements. Line 374, position 6."

Suggestions?

I want 1.1.8 anyway.

bbarnhill

That is a bug that is fixed in 1.1.8 ... default values in the dataset definition were not set ... a bug that I dont know how it just now started showing up but thats how most bugs are. Im going to work with my beta testers this weekend and see if I can get 1.1.8 released while I meet my wife in St. Louis since we are living 7.5 hours apart right now :( (school and work). She will understand that you guys need 1.1.8 though

hornetball

iTrader: (4)

OK, you had your conjugal visit. Where's 1.1.8? JK

bbarnhill

damn you hornet!!! Conjugal visits are what I live for man.

I just sent 1.1.8 beta 7 out tonight with some tweaks to fix drag and drop for those of you that still have UAC turned on. If that beta checks out fine then Im on to releasing 1.1.8

bbarnhill

I sent 1.1.8 beta 11 to the beta tester last night. He will get back to me by the weekend and Ill hopefully get good news and release that to you guys this weekend. No promises just making sure you know that Im still pushing to get 1.1.8 out as it fixes a lot of bugs I hope.

bbarnhill

1.1.8 has been released. Come and get it!!!

Here is a list of the changes:

- Fixed a bug allowing the display values popup on graph other columns to draw offscreen
- Fixed UI bug that left selected profiles blue when another profile was selected
- Fixed miscoloring of smoothing options on run specific context menu
- Fixed UI bug where was border showing on both sides between HPTQ graph and AFRBoost graph
- Fixed delay when profile is selected till the time the menu is hidden
- Fixed incorrect loading of smoothing factor from saved settings file
- Fixed a bug when writing columnnames.xml on update that caused the invalid root element error
- Added dropdown to select profile from bottom of screen where active profile is displayed
- Added check for file in use when loading columnnames.xml as it may still be updating
- Added trimming of commonly trimmed char from column names when looking for column
- Added EcuTek log support
- Added LS2Edit log support (.LOG only)
- Added Link G4 log support (after running the llc2csv converter only)
- Added UV Scan log support
- Added more time formats to be compatible varying time formats
- Added setting to allow toggling smoothing time in case of unsmooth time signal
- Revamped the settings window to be a window instead of a panel
- Persist all settings across program in a common settings object instead of reading form settings screen
- Moved all updating to the splash screen so updates are done before loading the application
- Replaced most typeof comparisons with the 'is' keyword
- Removed system serial number and install id as it caused instability with the UAC
- Removed application manifests that elevated security and disabled drag and drop with UAC on
- All update versions come from the webservice instead of direct web xml reads
- Column updates are now through the webservice
- Cancel zoom button is always visible but disabled when graph is not zoomed

hornetball

iTrader: (4)

text file output?