they're the names of the actual parameters in the ADX. they're also in the 'export log' function.
they're the names of the actual parameters in the ADX. they're also in the 'export log' function.
very very early alpha version, please help test the various features and see how it behaves with actual data in it. it doesn't do anything but chart the data yet.
http://fbodytech.com/files/trimalyzer-alpha1.zip
a few notes:
- logs must be CSV (comma seperated) files. in tunerpro, you have to 'export log' to get a csv format log.
- they all have to have identical fields and ordering right now (so exported from the same program)
- for single o2 sensor (single bank) cars, just set BLM bank A.
this version uses an experimental type of analysis. instead of putting data into a 'cell' with 'borders', which would have no interpolation ability whatsoever, we use some geometry.
each data point kinda forms a circle of effect (actually an oval, we scale map and RPM different), and the center of each table cell is an observer. if the observer is located within the range of the data point, it counts towards its average. this should better reflect the reality of trims being an imprecisely located data point, and the usual logic that if one cell is affected, the surrounding cells also require modification or smoothing.
of course these are not literally circles, since checking distance between the two points is cheap mathematically, we can just check the range of radius between points, so the analysis happens very quickly.
i may add a bit of magnitude adjustment vs. distance later which might result in better data, early attempts failed because my math skills are a bit shitty.
let me know how it works so far and i'll keep going
Hi
Got annual MOT due shortly. Car has been running really well in OL SD but I've put it back to CL SD for the ticket.
Been out today for half an hour and ran the log through the analyzer.
VE tables came out 97 to 101. I presume this is %age.
Worst blm was 16 at 121/ 127
I was expecting a much richer result just swapping back to narrowband after tuning on the wideband as the wideband appears much more lean whilst cruising.
Nice one Steveo, excellent as ever.
Keep it coming.
Mitch
Terminal_Crazy
'95 Z28 M6 -Just the odd mod.
'80 350 A3 C3 Corvette - recent addition.
yes it's percentage
in default configuration it rejects tps < 1 so it isn't going to help you with idle (aka cell 16) (assuming it found that field, otherwise it wont add the filter for you)
stand by for next version with hugely improved analysis interpolation!
tricky part is, there's so much math now that we have to tune the tuner. there are all these scalars and multipliers to make the analysis behave correctly without adding data to the wrong cells. i think in the end it'll be awesome.
this one is more better:
http://fbodytech.com/files/trimalyzer-0.2a.zip
uses data point distance scaling to feed a weighted average system, with high pass filtering to remove noise and clipping at the top to ensure maximum strength of data points near the target.
also added a UI for the advanced tuning settings, so users can experiment with different parameters to try to figure out how to optimize this thing for me.
it has a checkbox so you can disable the interpolation and try a traditional cell-bounded analysis.
feedback please
edit: fixed that link .....
analyzed a bunch of logs and tuned it a bit more
http://fbodytech.com/files/trimalyzer-0.3a.zip
if you had used that last alpha version, once you install this, use advanced settings -> reset all
also has knock event map
the math in the above version has a flaw. it works alright... but...
will fix it later tonight.
oh and just to be clear, i am not tuning chevs anymore, so i wont be testing this software in real world conditions, i rely on you guys to do that, i'm just doing this as a fun project.
Getting ready to do some datalogging so I will try it in an hour or so. Thank you!!!!!!!!!!!!!!
Brian
Bookmarks