drive it

iTrader: (1)

Hi y'all. I've been absorbing a lot here, finally registered. I've got a question about the 6E ecm constant "DFCO". Function? What the heck does it stand for? I've been working with the 32 and 32B on tunercat and I'm going to the ARAP now. Also with the 32 and 32B there is an adjustment under constants to increase threshold for a code 33, but on the 6E its gone and instead I find a MAF vs. rpm diag. I tried changing the values in the diag. table but it still set a temporary code 33 when the gm/sec went over 45 at under 2200rpm.With my combo it occl. will hit low 50's gm/sec. Thanks in advance for the help.

------------------
86 406

Craig Moates

I had code33 problems galore with my 32B code, but when I went to ARAP all was well. Anyways, if you're going to use the 6E, you might want to do some hex editing (Hex Workshop, etc):

At address hex-0210, the value here (default=45) will specify the gms/sec MAF signal below which the code33 will be disabled. If you set this to a higher value (100 or so decimal), you should be in good shape. I haven't done it, so can't verify, but I am pretty sure this is correct.

At address hex-0213 you'll find the value representing the RPM above which code33 is disabled. The entered value*25 is the RPM value. Default is 128 (3200RPM), giving a lower value here should disable code33 at lower RPMs. Same disclaimer as above.

These numbers came to me in a dream...

drive it

iTrader: (1)

Craig, Thanks, I'll try it! Any ideas on the DFCO?



------------------
86 406

Grumpy

Decleration Fuel Cut Off.
On the turbo car I disable it as an anti-lag devise. On a N/A car probably helps roll down some, ie saves on brakes. For road racing I'd disable it for keeping some combustion chamber heat, especially with AL heads.

87Formula356

Let us know if the code 33 thing works!!! i need a solution too.

rattle

my solution for a code 33 would be to just disable the code flag.

add a ecu item in the flags area of tunerpro
set as follows

start address 01de
columns 1
rows 1
element size 1
check in front of Bit Mask (array of flags)
map name, fail codes 24 to 35

other side of screen now

x axis, leave all blank

y axis,
leave at rows 1-10
fill boxes like this

1 24 6 33
2 25 7 34
3 26 8 35
4 31 9
5 32 10

boxes 9 and 10 are blank.
now save info
you can now decide whether or not you want any of these codes
to set or not. checked=code diagnostic runs,

also codes 43-51 are at 01df
and codes 52-55 are at 01e0

jackballs529

I know this is an old thread but is there a modern day way to shut off Code33 and code34 in Tunerpro. I saw the directions above but they didn't make sense. I'm a novist at best...

Tuned Performance

iTrader: (92)

33 and 34 have a malf and threshold. If your tuning for a cam and keep popping a 33 raise the threshold. if your having 33 & 34 problems diagnose it don't just disable the malf.