2006 Charger Trinity Monitoring ESP BAS Ligth and lots more

[theblackone]

I installed my trinity last fall (upgraded from a Predator) but I do not remember going into the monitoring screen before yesterday. (the car was in storage for the winter)

As soon as I go into it, the ESP BAS Light come on, the bell "Ding" ring every few seconds, the RPM needle goes down as the same time as the bell.
If I leave it in monitoring for longer, the Engine light and oil Light start to flash.

Where can this come from?

Currently on 1R08

Running custom tune, same as last year.

Forgot to add, I replaced my PCM because the old one did not supply power to the O2 heater anymoore.

[jackson7840]

You are the third one to report these symptoms that I have seen.. Do you have a 5.7 R/T?

[theblackone]

You are the third one to report these symptoms that I have seen.. Do you have a 5.7 R/T?

Yep, 2006 Dodge Charger R/T Daytona

[theblackone]

Just made a couple of test to be certain the problem was not my new PCM.

Restore the original backup to the new PCM, same problem when entering the monitoring screen.
Installed my old PCM, same problem when entering the monitoring screen.

So the problem is definitively my new PCM.

When the problem occures, I get the TCM code U0002 which from what I could find is "U0002 High Speed CAN Communication Bus Performance"

The trinity seem to mess up the CAN BUS communication.

[theblackone]

It look's like i should have keep my Predator and Dashhawk. Both of them we're working perfectly.

I need to get my car tuned so I am guessing that if the tuner try to log during the process, it will create a mess as well?

Right now, it does the same problem in the Monitoring & Log recoding screen.

[jackson7840]

I am not sure, I have the trinity as well (intended to use the gauges) but I am thinking the Predator is the way I am going to go.. Maybe an Intune.. Just no reason to have the nice one if I cannot use the functionality it provides..

[jackson7840]

My post is Charger New Guy if you want to look at anything that has happened in there thus far by the way...

[theblackone]

It would be nice is the Tech from Predator woudl reply from time to time or at least send me a message with what I should do from there!

[mikel]

Seems we have 2 threads on the same subject, i have been replying regularly to the other one....
As mentioned, Im not 100% sure what to suggest.
I have tried replacing cables, hasnt worked.
I have rma'd tools and tried them in our own 06 LX's (we have 2 here) and neither shows any issue when using these tools in them.
Still investigating what the possible cause may be.

[theblackone]

Ok, here is the solution I found:

I had the chance to have access to two 2006 and one 2005 over the week-end. After some investigation, I found that the two 2006 have 4 additional cable in the OBD2 connector compare the 2006 manual shop (pin 1 - 3 - 10 - 13) and 3 to 2005 (pin 1 - 3 - 13).
The two 2006 had the same problem with the trinity but the 2005 was working fine. So I took the additional cable out one by one and found out that the pin #13 (white & blue cable ) is the one that cause the problem.

So unscrew the connector from under the dash, pull it down slightly, remove the blue tab that lock the pin in place on the pin 9 to 16 side (pin are all numbered on the cable.).
Then there is a small plastic tab on the inside of the connector that need to be pushed toward the center of the connector while you pull on the cable from the back.
Once the cable is out, tape it carefully and put everything back in place except this cable. Connect your trinity and enjoy.

This had been tested on a Daytona r/t 2006 and a 300c srt8 2006 and fixes everything.

[mikel]

wow, thats good info, we'll investigate on our end!

[mikel]

any chance it was actually PIN 14???

[theblackone]

any chance it was actually PIN 14???

I wrote everything down in my manual shop so I can double check tonigh but i am 99.9% certain it is 13.

[mikel]

just curious, as the chrysler website lists the blue/white wire as being PIN 14.

[theblackone]

just curious, as the chrysler website lists the blue/white wire as being PIN 14.

If I remember correctly, pin 1, 3 and 13 we're "duplicate" cable. meaning that there is more than one cable of the exact same color on the OBD2 connector. On the 2005, these is no duplicate.

I will write you the exact details tonight of all 3 cables tonight.