2004 LLY U-7185 dissatisfaction

[JoeLee]

I purchased a U-7185 for my 2004 LLY diesel truck. There are several problems that I have with the programmer. First, when using the 100 hp setting the throttle becomes unresponsive, that is, until I stop the vehicle and reprogram with another setting I cannot move the vehicle. any suggestions? I have checked with the dealer and the PCM is programmed with the latest software. Second, there is an enormous amount of smoke from the exhaust on acceleration. Third, the transmission shifts excessively during acceleration. Fourth, the vehicle surges under light load (such as when cruising in a parking lot). Fifth, when using the programmer in any setting besides the stock setting, the Average fuel economy display becomes wildly inaccurate.

[mikel]

1. I have never seen that before, what is the revision on the top line of the main menu of the tool?

2. sounds like the trans is still relearning.

3. same as 2.

4. That would more likely point to a clogged/dirty fuel filter or injector issue...

5. That is not uncommon when tuning any diesel.

Try loading the tune then drive around for a day or so easy on the throttle and let the trans relearn to see if it clears up the issues.

Thanks

[JoeLee]

Tool info
serial: 7f00bbc2
Part: u7185u7185
version: v.9r07
Hardware: UNIV_REV2
The transmission shifting problem has been constant since installing the reprogram. I have logged over 4000 miles since installing the program and I do not usually change the program from the 80hp setting. I know that there is a transmission relearn process so, it usually stays in the same setting and program for an extended time.
Each time I try to use the 100hp setting it loses throttle after as many as 100 miles or as little as 15 miles.

[mikel]

any codes when it loses throttle?

my guess is it is limping the trans...

[JoeLee]

That's what's weird. There are no codes and no "Check Engine" light. No trans codes either. My scanner shows no bad trans data.

[mikel]

that is really weird. Even if the pedal signal was dropping out for some reason, it really should throw a code.

Maybe see if you can reproduce it and let it run for a bit after it does it to see if it will throw a code?