SO... I already have a case opened with Superchips, but I was hoping to get some advice from you guys.

I got my Flashpaq tuner (3840) recently and it connected and runs fine (identifies vehicle), but when I try to tune it, it prompts me to reconnect my transmission. The truck is my daily driver and hasn't given me a check engine light or anything. The last time I was on the phone with Superchips, the service rep kind of seemed like he thought it was something on my end. Is it possible that the truck would run fine (it actually runs great and I love it) without any CEL or other apparent issues if the transmission isn't connected to the PCM? Best I can tell, the wiring is in good condition. If it ever stops raining here, I'll take a closer/longer look.

Thanks in advance for any advice.

Truck: '05 Dakota 4.7L v8 4x4 545RFE(automatic transmission).

 

Did you update it on your computer first?

Make sure the programmer is firmly connected when tuning the truck.
Also, I think all of us have the SC 3865, not sure if anyone has used the SC 3840.

 

Apparently the 3840 supersedes the 3865. Like Dakotaff says, you gotta update it right out of the box. Get used to tech support blaming you for any issues. Updates have to be made on a PC hardwired to the net. Wireless internet does not work very well for the superchips updates. Is it really telling you to "reconnect the transmission"? At what point are you supposed to disconnect the transmission??

 

Yes, I updated it right out of the box, haven't had any of the issues I've read about their "Spark" updater not working... yet.

The tuner connects just fine (I have identified the vehicle and even changed my tire size), but I can't tune because apparently, on my daily driver and primary means of transportation, I've disconnected the transmission.

The exact message is: "Transmission not detected. Please reconnect."

I couldn't get a hold of a 3865, but I'm hoping that Superchips will come through and figure something out.

 

When I mean that the connection has to be firmly in place, sometimes it's connected and you can go through menus and access information. But when loading the tune, sometimes you'll get strange error messages. I have this problem with my SCT X3 programmer with my car. I have to hold the rear of the OBDII port on my car with one hand, and really press the SCT plug in tight with the other hand, for it to work correctly. Once it's plugged in, it's ok, and I don't have to hold anything in place while using the programmer.

 

sounds strange..I would check the forum on Superchips.com for the error under the experience of others

 

3840 supports diesels too I think... hence why they went with it instead of the previous 3865 like most of us have (gas-only unit).

Superchips will blame you until at least one other person reports the exact same problem. Before I bought a SCT for my Ram 1500, I tried a Superchips. It worked fine out of the box, but after I updated it on my computer, the truck would choke, stutter, almost die repeatedly until the closed loop kicked it. No CEL (flashing or otherwise), so i was stumped. Ran great without the tuner.

Superchips told me repeatedly it was something with my truck. The reps claimed they asked the engineers to look at it, and they wouldn't because I was the only one experiencing the issue. I spent $$$ replacing almost all the sensors on the engine, new spark plugs, new spark plug wires, new ignition coil, etc. thinking this was an issue with my truck that would eventually rear its ugly head, and that the Superchips pushing it to the edge of performance just brought it up sooner.

Finally, another 2001 Ram 1500 came onto the forums and said he had the exact same issue. Finally the engineers looked at it, and low and behold, the compiler that put the code together for distribution to the tuner software had an error that screwed up the fuel map ONLY for 2001 Ram 1500s with the 5.9L V8. After this, one of the reps told me not to update my tuner, stating that if it works don't fix it. This runs in contradiction to them telling us to update our tuners for fixes...

Despite the fact they finally fixed it, I sold the sucker a week later and got a SCT. Would get a SCT for my 2010 if they still made them, and if they allowed Sean (hemifever) to program the 2008+ models.

That all being said, I haven't had a problem with my 3865 and current truck.

 

Hey Jedi I'm having the same problem.

I found your thread on Superchips but I can't respond there since I need to have an admin confirm my account and they're closed till after the first of the year. So I stumbled across this one and figured I'd post.

So here's the deal, I'm getting the exact same error as you but it's on my 05 Jeep Grand Cherokee Hemi. It's the same software for both vehicles from what I've seen in the info section on the Flashpaq. I was able to download the stock program fine and then just like you I get to a point where I get the error. I've tried to tune it a few times now and no luck. I tried the quick tune and the advanced tune and get the same response. I was able to change the tire size and tweak my tire pressure monitor alarm too with out issue.

Flashpaq was updated prior to trying to tune too.

So I'm guessing that this is a problem with the Flashpaq and not that our transmissions are not hooked up. No trouble codes on mine either.

 

Medic - I am glad you found this thread and posted. I actually had to email "Ron" on the Superchips Forum to get access to it (I had waited about a week and a half before sending that email). But getting back to me, he is pretty timely.

Glad to know that it isn't an issue with my truck. I've changed my tire size too, but every time I try to quick tune or advanced tune, I get the error. I'll keep you posted in the event I get any new information from Superchips.

Thanks again.

 

Once I can log in over there I'll start hitting them with the problem too. I'm hoping we can get them to take it more seriously with the two of us having problems. Haven't seen anyone else with the Jeep having this problem yet so we'll see what happens.

Have tried seeing if its a connection issue with the OBD port like DakotaFF said? That could be the issue but it didn't seem like it could be pressed on any tighter.

During your update did you have to start over at all? It failed at one point for me but then went all the way through the second time. Thats' the only thing I can think of.