[mrsaturn7085]

Since the upper range cut tables haven't been found in the current definition, the hysteresis tables are a little wonky to use. The OFF table should be the higher RPM value, and the ON table should be a few hundred RPM lower. From what I can tell, there is no way to disable the high RPM cut.

There are four reasons to disable the DFCO:

1. You want the vehicle to roll on decel - this is why Cadillac fuels on decel.
2. You want a smooth decel - this is why (non-endurance) racing vehicles rarely run a fuel cut.
3. You are tuning the vehicle - this just removes a variable for the tuner to consider while reading logs.
4. You want to make noise - disabling decel fuel cut and running rich on overrun is a surefire way to get burbles, pops, and bangs.

 

[obijuanito]

I had DFCO turned off... I did the wrong question... Is there any advantage in turning the component protect off besides the backfires? Did you see any improvement by turning it off?

Enviat des del meu LG-H870 usant Tapatalk

 

[mrsaturn7085]

See my post above. There are multiple valid reasons to disable DFCO.

 

[theogmantonio]

Time to revive this thread! I'm struggling with the python script. I continue to get 'No valid AFR data available' in my logs when attempting to run the correction. I have a WBCX installed on the bike and logs within WinPep8 of with a graph of 'Air Fuel Ration 1 (AFR)' synced to C3 still throw this issue. My logs are failry short, so I was curious as to if there isn't enough data, or if I'm missing something else. I've downloaded the few guides, and been through this 'juicy' thread many times. I'm not certain what I'm missing yet, but I feel like im close.

I'm currently attempting to use correction to dial the bike in at idle, where it really stumbles and farts, and runs LEAN (15-20) at idle as it struggles. Low throttle is pretty rough too. Once the RPMs come up and I whack the throttle, fueling get's nice and fat and the thing rips along, but I don't like running it at idle much. Happy to provide logs and such if anyone might have time to help a fellow grom nerd out. Thank you!

 

[theogmantonio]

Lies! My heart is filled with sadness. I will admit, the screen priror to 'perform correction' I leave at 13 across the board.

 

[theogmantonio]

It may also help to know, it's a Koso 170 4v with all the koso intake goodies and a hindle exhaust with the rev.2 silencer to quiet this thing up a little. It has all the supporting mods and I believe to be healthy otherwise. The only item I was concerned about is the PCX150 injector that sat for sometime (I've drained and refilled tank with fresh 93!) but I do have a new injector coming just in case!

 

[theogmantonio]

Juicy detail right here!!!

 

[theogmantonio]

Well, I ironed out the idle, but I can't seem to dial in the low throttle at all. I saved a new map with the changes at idle and 0% TPS, then logged tiny throttle input and the PV3 seems to no longer be logging TPS input so I can't correlate data within C3.

You can see it does TPS voltage, but not the input that C3 needs.

 

[MiniMotoMan50]

A little back tracking here. When I put in my pv_info and get the stk file from dyno jet it only has a few tables. Where are all the other tables like setting AFR target, tip-in etc. I thought there were like 50 tables that could be modified not 9. All I get are the basic fuel and spark maps. I have a 2014-16 grom. Do I have to tell the software to add the table to the explorer tree that I want? If so how? Apologies for the backtracking...

 

[jeff@ddtperformance]

have you updated your software lately? i opened a 2018 tune for the first time and had like 200+ options.

 

[MiniMotoMan50]

have you updated your software lately? i opened a 2018 tune for the first time and had like 200+ options.

I just downloaded the software & it says its up to date. I go to dj website & give it my pv info file and i get the stk file. When i open thay stk file there are like 9 tables. All the other premade maps are locked so i cant modify one of those.