Can No Longer Flash PCM - Error Message

[Stoopalini]

On Tuesday night, I flashed the Diablo 87 Performance tune onto our 2016 Durango, and everything went fine. Then on Wednesday night, I wanted to put it back to stock to compare knock counts, and the Trinity gave me this message when I clicked the "Performance" icon:

IMG_2762.JPG (2.09 MiB) Viewed 4341 times

I tried resetting the Trinity and the vehicle, but still get the same message.

So I checked the options, and the list VIN is correct, and the CALID looks correct.

screen2.jpg (2.37 MiB) Viewed 4341 times

screen3.jpg (2.6 MiB) Viewed 4341 times

I understand I'll probably need to call support, but thought I'd post here 1st to see if there's an easy fix for this.

[mikel]

thats odd, i am not sure exactly what happened here but I am sure that if you give us a call we can reset the tool and then force it to reload a stock file and retune from scratch.

Thanks

[Stoopalini]

Ya, I thought it was strange too. I had the trinity plugged into my computer and was using dataviewer to view and export logs. When I disconnected the trinity to bring it back to the vehicle, I neglected to close down dataviewer first. I wonder if that has something to do with it?

I won't have time to call until tomorrow, unfortunately. Due to my work hours and Diablo support's hours.

[Stoopalini]

Well, it seems the support team has been unavailable today, so I poked around a bit more with the Trinity.

When viewing "Last Tune Written", I am seeing this:

Last_Tune_Written_1.JPG (307.97 KiB) Viewed 4320 times

Last_Tune_Written_2.JPG (323 KiB) Viewed 4320 times

But when clicking "More Information" on the error screen, I see this:

Error_More_Info.JPG (313.22 KiB) Viewed 4320 times

It appears some data field didn't get updated correctly during the last tune.

[bucky440]

At least you got yours to work once, I can't get past the first step of saving the original tune to even load any of the canned performance tunes.

[Stoopalini]

So I finally got in touch with support today. They had me:

Go into the "special menu" with a code, and do a registry reset.
Then reboot, and load the Mega Crom
Then I reloaded the latest Chrysler Crom for the 2016 support

The above process took a long time, so we hung up while it completed. After completing, the Trinity is now not married anymore.

So now, after the reset, the PCM still has the Perf87 tune loaded, but the Trinity isn't married anymore. I want them to help me get the stock tune loaded back into the PCM while having the Trinity be unmarried.

So we went through a Force Calibration update, which took a while, and then gave a "PCM Write Error Failed (-34)" error. So we rebooted the Trinity, and it went through the Calibration Update again. This time it completed successfully. Apparently the Force Calibration update always fails the 1st try and typically completes the second try.

All in all, the process took about 2 hours over the course of 2 phone calls, but it seemed to have been fixed up, so we hung up.


I then attempted to load the Performance 91 tune in, and received the message
"Original Backup NOT SAVED (-30)."

More Info showed:
"PCM: error verifying backup (1)"

and then:
"Trinity will now make a 2nd backup attempt."


The 2nd attempt resulted in the same message of:
"Original Backup NOT SAVED (-30)"

with More Info also showing:
"PCM: error verifying backup (1)"

and then:
"Trinity was unable to save your original tune after 2 attempts. This can happen if the vehicle already has a performance tune.".

Then finally:
"Not tuning vehicle because of backup (4)"

So it appears the Force Calibration Update did not put an OEM tune back into the PCM. There must be some part of the 87 Performance tune still in there somewhere, which the Trinity is recognizing.

Unfortunately I don't have another couple of hours to spend on this right now, but hopefully can call back in later.

If you're reading this Mike, maybe next time I call I can talk directly to a Diablo support person, instead of having to have a superchips guy IM all questions across? Nothing against the guy who helped me, he was great ... but it certainly made things go a lot longer waiting for answers on IM.

[Stoopalini]

New Update:

AS I continue to troubleshoot this, I decided to push the Hemifever tune onto the Trinity, and just choose my original backup file when prompted instead of trying to get a new one backed up. This worked to get the Hemifever tune onto the Trinity.

Then I took the Trinity to the vehicle to try and load the tune up, and my eye caught the SD Card I have plugged into the Trinity (mainly because it's a bright blue SD Card). So I thought maybe this was causing an issue? SO I removed it.

Then I selected the Hemifever Custom Tune to load, and the backup completed successfully this time, and the tune loaded successfully.

So, maybe having an SD Card in the Trinity when trying to do the initial backup will cause it to fail? Not sure if the SD Card was causing the issue, or if loading a custom tune and selecting the old, original backup file, is what allowed it to complete successfully.

[mikel]

Yeah, SD card, especially if too large or formatted improperly, can cause issues with tool functionality.

Honestly, theres no good reason to use the SD card

[Stoopalini]

Interesting. It's just a 16MB SD Card, which I formatted with the Trinity and have been using it to transfer log files from the Trinity to my computer.

But going forward, I think I'll just stick to moving the Trinity back and forth.

[mikel]

max size for the SD card is 2GB