Knock Error | P0330 & P0325

[l.thomas]

Recently purchased Trinity T2 EX and PCM for my 2015 Jeep SRT. Before purchase/install only mods are catch can and CAI. With exception of the PCM and the T2 and tunes nothing else has been done to the vehicle.

Initial install went smooth and had a check engine light that I figured would go when I pushed a tune. I flashed the 93 tune and Trans tune, didn't turn vehicle on, then flashed the 91 tune. Tune was AWESOME for the few weeks I had it however the check engine light was still on. My main issue outside of the CEL itself was that remote start didn't work because of it. I was getting a P0600 error code for serial connection. Long story shot PCM went back to Diablo, was reflashed and sent back.

In sending the PCM back, I restored tune to stock, and put factory PCM back in. From this point on I now get knock sensor error and CEL within a mile of very tame driving (have cleared the code a few times) and something with the vehicle is clearly wrong. The error codes I'm getting are P0325 from the Jeep and P0330 from the Trinity - Knock Sensor 2 Circuit. I get the same error codes with the stock PCM as well as the Diablo PCM (after being sent/reflashed).

It seems to me with the timing of the knock code and the PCM swap there is something related and it's a tune issue- but many of you have more knowledge in your pinky toe on this subject than I do. If anyone has any direction to take I would appreciate it. Not sure if it's a tune thing or something mechanical that will require a trip to the shop. Below is screenshot from today when the vehicle threw the code after it was cleared if it's of any help.

Thanks in advance...

[mikel]

do you happen to have MDS disabled?
If so, can you go back and re-enable it then reinstall the tune and let me know if the code comes back?


Thanks

[l.thomas]

Thanks Mike. Yes, MDS was disabled. Just re-flashed the 91 tune with MDS re-enabled.

Felt 'good' for about a min (tame driving) then didn't feel right and felt like it should have thrown the code. I turned engine off, started again, and didn't feel good and threw code in short order.

Now that I think about it- throwing the code seems to be consistent with the 2nd engine start after CEL is cleared. I took a video of the gauges when I drove if that's of any help.

[l.thomas]

Link to Video | First Start After Re-Flash (91 tune, MDS Re-Enabled)
https://drive.google.com/file/d/1a_RDkP ... sp=sharing

Link to Video | Second Start and Knock Sensor Error/CEL
https://drive.google.com/file/d/1ba-2sa ... sp=sharing

[mikel]

OK, well I thought I had the answer
Please post the file called last tune written from the tunes folder and I will get it sorted out.

[l.thomas]

Thank you. Attached.

[l.thomas]

One thing I wanted to add...may be of some help to my situation.

I have the T2 connected to computer to pull the tune requested and just now decided to open the Update Agent. It said I have an update so I updated it and looked successful. (see 'screenshot before updating - #1').

I then closed the program and opened again, and it said I have an update so I did it and again as some of the info presented was a little different, and again the update looked successful. (see 'screenshot before updating - #2')

Then closed and reopened and said I need to update, however this time info presented was same as previous update (showed same screenshot - see 'screenshot before updating - #2). This time there was some sort of hiccup in green text, and, again looked like it was successful. I have tried closing and opening program and updating and get the same hiccup every time. I did this one more time while recording the screen so you can see the error. Link to video is here:

https://drive.google.com/file/d/1YyMZRV ... sp=sharing

[l.thomas]

For anybody reading/interested this is apparently unrelated to anything Diablo and just coincidence with the timing of the PCM swap and knock sensor code.