Any way to define variables in a custom PID?

[thunder550]

I wanted to see if it was possible to set up a variable that would continually add data values. I want to create an MPG PID that will not get thrown off when DFCO is enabled, but it would require a running total of fuel used and miles traveled. Is this possible?

[kbracing96]

TTT!!! I would like to know how one would go about this all so Something I'm VERY interested in.

[kbracing96]

Nobody knows how to make these pids add up???

[thunder550]

Bueller?

Bueller?


Anyone?

[joecar]

I think it would require the integrate() function (which used to be in V5) and some conditional gating using the iff() function.

The itegrate() function sums up samples over time.

[SSpdDmon]

If you're logging MPG over a period of time, why wouldn't you want to log when in DFCO? The pure purpose of it is to save on gas when off the throttle.

When you drive, logging MPG from the time you start the car to the time you shut it off should give you an accurate representation of what you're looking for. Knowing where to look is key. You're basically asking for the average for a distance traveled. So, make a map (F11) with MPG as the data value and hit the X for the average value.

[kbracing96]

If you're logging MPG over a period of time, why wouldn't you want to log when in DFCO? The pure purpose of it is to save on gas when off the throttle.

When you drive, logging MPG from the time you start the car to the time you shut it off should give you an accurate representation of what you're looking for. Knowing where to look is key. You're basically asking for the average for a distance traveled. So, make a map (F11) with MPG as the data value and hit the X for the average value.

See, that doesn't work. The only PID we have is INSTANT MPG, which the average of is NOT true MPG. It way over compensates when in DFCO and does not subtract when you are stopped, cuz it setting at 0 and your still burning fuel. Only way to get TRUE average MPG is to is to divide miles traveled by fuel used for the entire log. Make since?

[TAQuickness]

Not trying to be a smart ass, but when you are sitting idle with the engine running aren't you getting 0 mpg?

I've used the custom MPG PID, found somewhere in this forum, and compared it to actual tank top off's and have found it to be very accurate. Also, my Dakota has one of those average MPG gizmo's by the rear view mirror and I've found it to be accurate withing .2 MPG between fillups.

It's not the same as what y'all are after, but food for thought.

[kbracing96]

Not trying to be a smart ass, but when you are sitting idle with the engine running aren't you getting 0 mpg?

I've used the custom MPG PID, found somewhere in this forum, and compared it to actual tank top off's and have found it to be very accurate. Also, my Dakota has one of those average MPG gizmo's by the rear view mirror and I've found it to be accurate withing .2 MPG between fillups.

It's not the same as what y'all are after, but food for thought.

Think about this.... Your INSTANT average is running about 18.2 MPG's on the scanner. Then you stop. Its now sitting at 0, BUT your still burning fuel, so your average MPG should be going down, right? But its not, cuz it's at 0 and not a negative number since your stopped but still burning fuel.

I've used the pid several times, it seem pretty accurate right up until I stop or go into DFCO and it shoots up into the 300 MPG range which RAPIDLY brings the average INSTANT WAY up. See what I'm getting at here. As long as you moving and not getting into DFCO it is pretty accurate, but it's still no as true as if you divided miles traveled buy fuel used. That's all I want guys,

[thunder550]

If you're logging MPG over a period of time, why wouldn't you want to log when in DFCO? The pure purpose of it is to save on gas when off the throttle.

The problems is that the MPG PID assigns some arbitrary value when the truck goes into DFCO mode. The calculation is done as follows:

{SAE.VSS.mph}/({GM.INJFLOW.lbpm} * {GM.IBPW1} * {SAE.RPM} * 4 / 6250 )

When DFCO mode is enabled, injector base pulse width goes to zero, which makes this whole equation a divide by zero equation. It's not possible to include DFCO situations in the MPG average because of this, which makes it very inaccurate when factoring in DFCO situations. Because of this, the only way to get a good average that includes DFCO situations is to sum distance traveled and fuel used, and calculate the average with those two variables.