question on autove and decelorating

[dbaxter_ss]

When logging coming home today I am seeing during decel or coasting the aft going to 19+ and BE map for 3200x30map is at 1.6.

I changed the filter to remove the decels, anyone think of reasons that would be a problem?

[joecar]

It seems to me that in your filter you need to change the AND to OR.

Do you have DFCO enabled...?

[dbaxter_ss]

step 5 in the autove tutorial says to have it enabled and set to 122c

5. Open calibration {B3313} "DFCO Temp Enable" Set it to 122 °C

my settings in the tune:
LABELS Selection
Parameters Value
{B3307} DFCO Re-Enable Timer 5.000000 Seconds
{B3308} DFCO M6 Enable Temp 50.000000 °C
{B3309} DFCO M6 RPM 900.000000 RPM
{B3310} DFCO M6 MAP 104.980469 kPa
{B3311} DFCO M6 TPS 8.007813 %
{B3312} DFCO M6 Speed 28.000000 MPH
{B3313} DFCO Temp Enable 121.992188 °C
{B3315} DFCO Vehicle Speed Hysteresis 2.000000 MPH
{B3317} DFCO Throttle Hysteresis 0.996094 %
{B3319} DFCO RPM Hysteresis 5.078125 RPM
{B3321} DFCO MAP Hysteresis 0.996094 kPa

[Tordne]

Change B3308 to max temp as well, that is the DFCO M6 enable temp which looks like it is currently at 50.

[Tordne]

Also if you want to filter out Decel try logging the Fuel Trim Cell # PID and then you can filter out FTC # 21 frames. FTC 21 = Decel

[SSpdDmon]

Also if you want to filter out Decel try logging the Fuel Trim Cell # PID and then you can filter out FTC # 21 frames. FTC 21 = Decel

That's kinda what I do. I log FTC and tell it to exclude data cells where FTC > 19. That plus excluding data where TP% is changing more than 2% in 500ms usually gets me some nice numbers. One thing I want to try is to see what the IAT temp is the majority of the log and filter all data where IAT doesn't equal that number. I have a feeling this will also help keep numbers consistent.

[caver]

The easiest is to disable dfco completely. As the values in the ve table are in part derived from temperature the iat makes a huge difference.
I make sure I keep it at a reasonable level the whole time I am logging and try and complete the tune in 1 go.
Otherwise you have to have to exclude ce3lls that show a huge difference from the last adjustment.

[SSpdDmon]

The easiest is to disable dfco completely. As the values in the ve table are in part derived from temperature the iat makes a huge difference.
I make sure I keep it at a reasonable level the whole time I am logging and try and complete the tune in 1 go.
Otherwise you have to have to exclude ce3lls that show a huge difference from the last adjustment.

Even with DFCO disabled, you still will hit the decel FTCs. It will affect your numbers...

[TAQuickness]

That's kinda what I do. I log FTC and tell it to exclude data cells where FTC > 19. That plus excluding data where TP% is changing more than 2% in 500ms usually gets me some nice numbers. One thing I want to try is to see what the IAT temp is the majority of the log and filter all data where IAT doesn't equal that number. I have a feeling this will also help keep numbers consistent.

That doesn't sound like it would work very well. In OLSD, you have FTC 20, 21, & 22. FTC>19 would exclude all data.

[dbaxter_ss]

That doesn't sound like it would work very well. In OLSD, you have FTC 20, 21, & 22. FTC>19 would exclude all data.

Yup and thats what it does.