LogWorks 2.0: General Discussion

[mazur50]

When will we be seeing a new and better version of logworks for the LM-1

[LegoZ81]

Originally Posted by mazur50

When will we be seeing a new and better version of logworks for the LM-1

LMAO I was SO about to post this.
I am definitely wanting 2.0 to come out so that I can edit the values (Map/RPM in my case) in the Chart view to make it match my tuning software.
Come on Klaus work some miracles here.

[klatinn]

Believe me, everybody here asks me that a couple of times every day. It will be done when I am satisfied with it (and I'm not easy to please). Sorry, can't get it closer. I need to sleep sometimes too.

Regards,
Klaus

[mazur50]

you got a a demo that we can play with

[LegoZ81]

Originally Posted by klatinn

Believe me, everybody here asks me that a couple of times every day. It will be done when I am satisfied with it (and I'm not easy to please). Sorry, can't get it closer. I need to sleep sometimes too.

Regards,
Klaus

Someone buy Klaus a case of beer so we can cloud his judgement
Sorry for pushing we are just eager...
After all this is your fault for making us all LogWorks addicts :P

[mazur50]

any new news on version 2.0 of the software.

[klatinn]

Hi,

Here some screenshots:

The TraceWnd shows the new main trace window. Just moving the cursor over a trace shows the name and hilites the trace. With the magnifying tool or smoothing tool you can magnify/smooth the trace. The current values under the cursor of all channels are shown on the (resizable) right section.
The little note icon at the bottom shows that there is a comment added at that point. Moving the cursor over the icon will show the comment in the right side of the window.

The XY-Plot shows overlays of AFR, Torque and Power of 2 3rd gear runs. Trq and PWR calculated with the trace calculator from RPM slope.

The Playback window shows some of the different conf. options for the dials.

The chart shows the familiar 3D chart, colorized by average AFR with an inverted rainbow pattern.

The Chart3D window shows the same chart rendered as a 3D surface. Graphic can be rotated, panned and zoomed.

Regards,
Klaus

[candymanjl]

wow, I wasn't all that eager for a new version, the current one works great for me. but now that I've seen the screen shots, he he, now I'm getting eager

so would the HP and TRQ work like the way a gtech calculates it? logworks would have to know the weight of the car then figure everything out based on how hard it's accelerating? or would this only work with the auxbox's accelerometers? (please say no because I don't have an auxbox )

[klatinn]

so would the HP and TRQ work like the way a gtech calculates it? logworks would have to know the weight of the car then figure everything out based on how hard it's accelerating? or would this only work with the auxbox's accelerometers? (please say no because I don't have an auxbox )

Calculated from weight, gear ratios and tire diameter. Works with Auxbox ACCEL channel (better and more precise) and ONLY RPM (exmpl. RPM converter). With only RPM from RPM converter (as shown in the screenshot) you need to do some smoothing. The numbers will have large tolerances, but, for the same car, it's very useful for comparative runs. You can easily see where you gained/lost power and how much (%wise). Just don't expect a dyno for free .

Regards,
Klaus

[candymanjl]

Originally Posted by klatinn

Just don't expect a dyno for free

dang it, that's what I want

so the software would need to know the weight, gear ratios and tire diameter. then the log would just have to have rpm and then we can see the power?

[VPapaefthymiou]

Dear Klaus,

Based on the promised features of LogWorks 2.0 and the screenshots provided earlier, I can say that I don't mind at all your need for sleeping, as long as you produce such work !!!

BTW, I would like to make a suggestion (don't know if it's already been made before) regarding the Chart window. I think it would be very helpful to be able to "filter" the "content" values included in the chart based on user defined values of the a) number of datapoints present, and/or b) the standard deviation of recorder datapoints. In that way, we would able to exclude "low accuracy" data from our analysis.

Keep up the good work

Vangelis

[clint78z]

Looks real good Klaus, must have taken a little head scratching to make multiple run info start at the same rpm point to calculate HP. The avaliable info from this little box just keeps expanding, never seen many products with this much direct support.

Another idea popped into my while viewing your charts. You know how hard it is to tune delta TPS, and delta Map settings on an ECU. This problem requires some thought on how to solve. My first thought is to have a table with map vs rpm, the z axis will be (delta AFR/delta map). Does this make sense to you Klaus ?? The z axis is an arbitratry number but is shows how far your AFR is getting out of wack compared to the change in Map. Obviously soem smoothing needs to be on this as well.

If anyone has a better way of doing this chime in, going to put my thinking cap on.

Is Logworks 2.0 VBA compatible, I thought I heard something about that a while ago ??

[klatinn]

Hi,

First of all the VBA (Visual Basic?) question. Unfortunately it won't be in the first release for time reasons. Definitely in the next.

With regards to calculations with the 3D chart:

The Math Parser (Trace calculator) is also available in the chart. The chart can hold up to 16 overlays. You can cut and paste charts between Excel (or other programs for that matter) and LogWorks back and forth. The chart is on the clipboard just as tab-delimited text as lowest common denominator.
For example you can create a target AFR chart and paste it in.
Then you paste in also your current fuel map.
You then automatically calculate a new map based on how the fueling relates to AFR changes and cut-paste this into whatever will accept it.

The math parser also handles Boolean functions like and/or > < and NOT. For example you can calculate a new chart that contains only those points where the std. dev is below a certain value. Example as you would put it into the calculator:

chart_numpts = (chart_numpts) * (chart_stddev <= 1.5)

The term (chart_stddev <= 1.5) evaluates to 1 if the std. deviation is less or equal to 1.5 and evaluates to 0 if not. Basically this throws out (sets number of points to 0) every entry where the std. deviation is more than 1.5.

For example to calculate a new overlay chart holding the difference between AFR values of the main chart and an overlayed chart:

NC = ovlc1 - chart_avrg

NC is a new chart. ovlc1 is the first overlayed chart.

The 3D graph can overlay ONE of the overlays (you select which one) on top of the main graph. The overlay surface is shown half transparent.

Just remembered this:
I ran autoselect on a large log with many 3rd gear runs. Select only WOT area. Then calculate TRQ on all runs. Then create a chart with TRQ as z-axis and AFR and RPM as x and y. When looked at in the 3D graph you can see a ridge whose ridge-line corresponds to the optimum AFR for each RPM point at WOT.


Regards,
Klaus

[LegoZ81]

Originally Posted by klatinn

Calculated from weight, gear ratios and tire diameter. Works with Auxbox ACCEL channel (better and more precise) and ONLY RPM (exmpl. RPM converter). With only RPM from RPM converter (as shown in the screenshot) you need to do some smoothing. The numbers will have large tolerances, but, for the same car, it's very useful for comparative runs. You can easily see where you gained/lost power and how much (%wise). Just don't expect a dyno for free .

Regards,
Klaus

oh no, now I want it even more
you guys rock.
and always if you need a beta tester LMK

[Mellon]

sounds great.. I haven't seen an area for feature requests so I'll put it here.

I do the same smoothing on my logs every time for each paremeter and it sure would be nice if logworks would save that as a preference so I wouldn't have to zoom in 3 times and apply smoothing to each individual item over and over. I sometimes do 10 back to back 1/4 mile runs and save them each as a separate session with notes on what was changed to keep it straight.

example:

rpm = 1.06 seconds of smoothing..the rpm signal is pretty noisy
boost = .41 seconds
a/f = .41
tps = 0 I don't require it to be a smooth line, just to know where I went WOT

example of my log this morning which shows what it looks like when I shift into 3rd gear (pump gas tune)