Results 1 to 8 of 8

Thread: 2020 Dodge Durango 3.6l procharger setup. Hard bucking

  1. #1
    Tuner in Training
    Join Date
    Sep 2024
    Posts
    14

    2020 Dodge Durango 3.6l procharger setup. Hard bucking

    Hey everyone. just to give you a quick background, I took a 2018+ WRANGLER 3.6l procharger kit and adapted it to fit my 2020 Durango GT. Mechanically just had to make my own charger mount pulleys and IC tubing. Pretty easy really. However I am struggling with the tune. I had HPT unlock the PCM and have been tuning with a tuner for the last 2 weeks back and forth remotely and we cannot get rid of this hard bucking between like 18-25% throttle. Its bad and there is no way this 8spd zf trans will hold up to it. I am coming up on losing interest to save the life of my drivetrain and wondering if anyone else has found a solution to this. I have heard this of Ripp Magnussen, Procharger and basically all of them. LTFT 1 and 2 are banging up and down as it bucks exactly on pace so I would have to imagine its related. I can load a log if it helps. Thx in advance

  2. #2
    Advanced Tuner
    Join Date
    Nov 2019
    Posts
    243
    Upload your current tune and datalog of the issue. Without these you will get all sorts of assumptions and guesses.
    FYI, there should not be no "hard bucking" once tuned correctly unless you have some mechanical/electrical issues.
    Ripp, Sprintex, Maggy even turbo 3.6's can have factory like smoothness once tuned correctly.

  3. #3
    Tuner in Training
    Join Date
    Sep 2024
    Posts
    14
    HaasExp thx for your reply. I assumed the same. Here it is. I feel like something is mechanically off and thats why the tuner maybe cant get around it.
    Attached Files Attached Files

  4. #4
    Advanced Tuner
    Join Date
    Nov 2019
    Posts
    243
    Just had a quick look at the log mate and those fuel trims are all over the place.
    There's a 10% bank to bank variation at idle which comes as no surprise because the tune is requesting it (I have no idea why you would do this).
    The tune also has a lot of other bizarre things going on which seem odd to do on a boosted Pentastar setup. Eg the MAP sensor settings.
    How many revisions are you in? Are you running the stock coils?

  5. #5
    Tuner in Training
    Join Date
    Sep 2024
    Posts
    14
    Quote Originally Posted by HaasExp View Post
    Just had a quick look at the log mate and those fuel trims are all over the place.
    There's a 10% bank to bank variation at idle which comes as no surprise because the tune is requesting it (I have no idea why you would do this).
    The tune also has a lot of other bizarre things going on which seem odd to do on a boosted Pentastar setup. Eg the MAP sensor settings.
    How many revisions are you in? Are you running the stock coils?

    Yeah so im a hardware guy, I know nothing about tuning and i dont want to point the finger at the tuner I dont think they have exp with these vehicles. i supplied much needed info from this and other sites to help get where we need to go. anyhow i can clearly see every bog/buck fuel trims spike. Also, this is a 7lb setup(or should be anyhow) and the srt4 map sensor reads waaay higher than it should be so i dont know how anyone really can even read actual boost levels. Has to be multiplier added i would think to get correct boost reading

  6. #6
    Tuner in Training
    Join Date
    Sep 2024
    Posts
    14

    flutter

    here is a log with the "flutter" only
    Attached Files Attached Files

  7. #7
    Advanced Tuner
    Join Date
    Nov 2019
    Posts
    243
    Check your inbox on here. I sent you a message.

  8. #8
    Tuner in Training
    Join Date
    Sep 2024
    Posts
    14
    So for those with this problem most especially with a procharger kit I have a fix for you. I brought my car back to stock and it still did the stutter though not as bad. What did fix it though was I removed the pcv valve procharger has you install in the line from by the throttle body back to the rear of the manifold. And no it wasn't backwards. Wether it was an issue with the tune not set for it or simply mechanical it's now fixed.