Filtering Graph Data with a User Math Parameter?

[Stoopalini]

Is it possible to leverage a User Math Parameter as a Functional Parameter in a Graph's Filter setup?

I've set up two Math Parameters to track WOT and DFCO on my GPEC2A Hemi, and would love to use these in various Graphs to filter the data; but it seems you're not able to select Math Parameters as a parameter for the filter function.

Am I missing something here, or is this not an option? Seems like it should be for boolean math parameters ... I do see you can select Scalers, States and Flags ... it would be great if we could define a boolean resulting user math parameter as a Flag, and then be able to use it to filter graph data.

[tonn0297]

Nope, not possible. ive asked for a while and no response. best is looking at injector flow, if under xxlbs/s then its dfco

[Keith@HPTuners]

Interesting. This was created quite a while ago but I'm surprised it was never added.

I'll add it to the list.

[Stoopalini]

That's what I figured. If HP Tuners could give us the ability to classify User Math Parameters as a Flag, for those which output a boolean value, and then use that flag as a graph filter .... it would be really nice for things like this.

In terms of DFCO, I'm sure inj flow/PW works well. I'm currently using WB EQ to do it though, and it also works well. It identifies DFCO exactly when the EQ curve deviates from lambda until it returns.

([50127.238] > 1.0 & [50127.238.avg(-1200)] > 1.4) or ([50127.238] > 1.0 & [50127.238.avg(1000)] > 1.4)


So instead of adding this string to every graph I want to exclude the data from, it would be much nicer and easier to manage if I could reference the user math parameter instead.

[Stoopalini]

Interesting. This was created quite a while ago but I'm surprised it was never added.

I'll add it to the list.

Hey Keith ... any word if this will be coming in a future Beta release yet?

[Keith@HPTuners]

The ETA will be a bit. We're working on a few very big things internally at the moment. Stay tuned!

[Stoopalini]

The ETA will be a bit. We're working on a few very big things internally at the moment. Stay tuned!

No worries, sounds good ... Thanks for the support!

[LilSick]

In terms of DFCO, I'm sure inj flow/PW works well.

I'm currently using WB EQ to do it though, and it also works well. It identifies DFCO exactly when the EQ curve deviates from lambda until it returns.

it works great - im rolling. relative pedal and the inj pw are both zero. criteria met : )

wb eq "exactly when it deviates from lambda" could be attributed to other factors; other than just dfco

[Stoopalini]

wb eq "exactly when it deviates from lambda" could be attributed to other factors; other than just dfco

Of course it can ... but I'm not using that as the criteria to know when DFCO is activated. Check out the filtering criteria I posted above to get an understanding of what I am using. It's based on actual EQ, but is future and past looking, with a base criteria of being over 1.0 and a time based ramp threshold of 1.4.

What I'm saying is that criteria aligns the "DFCO active" and "DFCO inactive" triggers to fall right at the moment EQ deviates from lambda, but only when DFCO is active (ie: not when other things cause actual EQ to deviate from commanded).

Here's what the trigger looks like with my criteria charted on top of CMD EQ and Actual EQ:

DFCO_Active.JPG


Here is what it looks like charted against injector PW, with the VCM time marker in the same place as the image above. Notice if I based this off of INJ PW, it would lag and include EQ data for the ramp time (which I definitely don't want):


DFCO_Active_INJ-PW.JPG


So when I'm using DFCO to filter data out to get a clean EQ graph, I don't want the ramp up or ramp down of the actual EQ included. Meaning, I want the data during the time it's heading in or out of DFCO to be excluded. This is why I'm using the calculation I am .... to filter this data out cleanly.

I'm not just looking at the chart, but want to filter it out of graph data. Hence the request to use user math parameters as filtering function criteria.

[LilSick]

maybe you are trying to log too many channels at once?

if i am working on fueling i only log what i need for fueling

*pedal - 0.00
*pw - 0.00
*the engine is still rotating

vehicle must be decelerating and the fuel musta got cut

lol

what do i know tho... i am just a stupid drag racer : )

[Stoopalini]

It has nothing to do with being a drag racer. I am using the criteria to filter out graph data, and if I used the criteria you are suggesting, it will include EQ data I don't want included.

If you are only looking at charts and not using graphs, then either way works. But I think you have DFCO disabled anyway, right? So it's probably a moot point for you.

[LilSick]

It has nothing to do with being a drag racer.

I think you have DFCO disabled anyway, right?

ouch. so just the 'stupid' part... not the drag racer part? rofl

yes, but it wasnt always : )