Well, I hesitated for the longest time to actually use HP Tuners on my truck, finally did, wrote a few times to the ECM and now it?s bricked my ECM. Does not recognize the key is on to turn the bus on.
Printable View
Well, I hesitated for the longest time to actually use HP Tuners on my truck, finally did, wrote a few times to the ECM and now it?s bricked my ECM. Does not recognize the key is on to turn the bus on.
Wow, really? What year is your truck? I'm assuming you have a recovery file you can use via the other platform's tuning hardware to revive it?Quote:
Originally Posted by Jim P
That's crazy!
I've heard of issues like these occurring due to checksum errors when flashtbacj to stock from other tuning platforms before. But I'm sure you're just as aware of these issues as anyone.
I just had a failure today as well. Mine states "controller init: failed". It will try to write and after like 5 seconds I get the error. When I try to read it says "detect protocol failed" It is like the bus in not there. Could I be experiencing the same issue? I opened a ticket with support, but haven't heard back yet. Right now my rig is a giant paper weight.
-dieseldude
On my 2010, I had a something similar happen. One time, HP Tuners erased the ECM, but then failed to connect, and nothing worked. I walked away after messing with it for a bit to write an email to HP Tuners, and when I went back out, everything worked just fine. I hope that happens for you...
I hope so too. I have tried charging my batteries, cleaning the battery connections, checking the connectors on the TIPM. I have tried to write like 10 times with the same error.Quote:
Originally Posted by jfreemanak
It?s a 2012. Nothing works to try to flash anything to it. I?ve had the dash say no bus at one point. HP Tuners says Init: Fail. MM3 won?t read make connection the ECM, EFI Live returns a $0549: Ignition is turned off error, even though the fob is in the run position.Quote:
Originally Posted by B00STJUNKY
Needless to say, I?m pretty pissed. I?ve tried every avenue I have available to try to get it to work on something for hours and have gotten nowhere and I don?t have my Cummins hardware with me to hook directly up to the ECM to try that method.
I?ve had failed writes before to the moon and back on other platforms and have always been able to recover, for this to say it completed and validated them shit the bed killing it completely is infuriating.
Sorry to hear it, brother. I wish I had some advice to offer in a situation like this, but in most cases, I suspect most folks would be turning to you for advice.Quote:
Originally Posted by Jim P
Good luck with it, I hate hearing stories like this. It doesn't exactly inspire confidence. :(
What are the odds that this would happen to two people. I have seen other posts where this happened on other vehicles. I wonder if it has something to do with the latest version of the Editor? I think I will try the beta tomorrow. I suppose it can't get any worse. If I end up having to get a new PCM, I am going to not have confidence that HP Tuners won't do this again. I just don't want to dump a bunch of money and time into a different platform. Maybe support will come back with something.
Yes, what are the odds indeed??
I work in the IT realm, and the first question I had was, did HPt do a recent update? And did both users update their laptop computer/interface/etc ??
This could also be a windows issue. I?ve seen Microsoft screw up a LOT of programs with their OS As of recent, and I would NOT doubt if this could even be intentional...
Tinfoil hat aside, I?ve learned to keep my old junky Surface 2 and Lenovo laptop that I use for tuning/logging OFF of the interwebs unless something is not working with them. The control that ?they? have over your stuff is all encompassing, but it ends when the connection gets cut...
HPT did do an update recently to beta, which I use and the interface module, I did one flash after that update, next one it killed my truck.
I am running version 4.8.7 and I thought the same thing about maybe a corrupt file. I downloaded the 4.8.7 package again and ran a repair on my install. I got the same error when trying to flash. I haven't tried the beta yet.
Yea I?m having to order a new ecm.
I don't have an EFI Live, but I found this thread where they were able to flash with EFI Live and fix it. Might be worth a try if you have one.
https://forum.hptuners.com/showthrea...ontroller+init
My FlashScan won?t connect to the truck. Everything I have won?t connect to the truck. The ecm needs to be bench flashed most likely and I don?t have my Cummins hardware with me to plug in directly to the ecm.
Might want to check with "RoninDusette" here on this forum. He has equipment to repair ECM/PCM that have been bricked using Ktag. Don't know if he can fix yours specifically but it may be worth a shot. At a minimum if you do get another you would have this as a spare.
Support has gotten back to me and asked for my tune files (stock and current), debug.dat, and VCM Suite Info log. I sent the files over promptly and they asked if I had anything else connected to the OBD2. I did have a CTS3, but disconnected that yesterday after my first failure. I am connected directly to the OBD2 port. Waiting on their next response.
Same boat here pretty much
One thing I?ve noticed at times after a flash with hp tuners is the service 4 wheel drive will come up aim first start after flash and 4 wheel drive won?t work or it won?t come up but 4 wheel drive won?t work. Need to shutdown then restart the truck again and then 4wheel drive will work.
Mine has been pretty trouble free for the most part. I have flashed it about 20-30 times over the last 11 months making minor tune changes here and there. They way I am viewing this is HP Tuner support needs to figure this out. My truck was running fine until I tried to flash it with their software. I am not going to be satisfied with me having to start replacing parts. I just completed a 5 hour haul pulling 10000lbs. My rig was running fine. I just made a few minor pressure changes to help with mid RPM response. I have done everything in my power to check everything on my end to eliminate points of failure.
This evening I?ll send files to support and see what they can do. I?ve ordered an ecm, if can?t get the one on the truck talking to write a file to I?ll have to swap out the ecm and when I can get my Cummins hardware I?ll try bench flashing to recover the original and keep as a backup in case this ever happens again. I?ve had plenty of failed writes on the mm3 due to battery voltage running to low but have always been able to recover it with the mm3 without a hitch.
I thought it might be my batteries too based what I have seen with previous posts about it. I put mine on a charger overnight before trying again (I have two new batteries on order due to arrive this week). Support just got back to me and said that I have to return to stock with my Edge CTS3 monitor if I flashed it with the Edge. I explained that the CTS3 is a monitor only and there is no other flash besides what I have done with HP Tuners.
I am theorizing here, but I asked support if the VCM Editor will write if it does not detect a tune on the PCM. The erase completed before the write failed. If that is the case, then it won't write my tune since it has been previously erased. They need to fix that if it is the case.
Just as a side note on programming I have done over the last 3 decades or so.
1. Battery fully charged.
2. Optima battery on HEAVY DUTY (I use welding cables) jumper cables.
3. Turn off every service, email, any internet using app, or anything that may start during programming.
4. Turn off screen saver and power saver on laptop.
5. Have laptop hopefully plugged into a power source or at a minimum 50% battery.
6. Turn on vehicles ignition and leave it on for a good 3 minutes. 5 to 10 is better. That lets all modules on com/CAN lines to "go to sleep". Make sure ALL accessories are off. Lights, radio, HVAC, seat heaters, interior lights etc.
7. During programming I touch NOTHING on the computer. Not a key, not the mouse, nothing
8. During programming keep doors shut or open with latch clicked and touch NOTHING inside. Not even a radio button.
9. After ANY programming I power cycle the whole car. That means turn ignition off, Key out, open and shut the door. If it has a fob I take it far enough away to know that it is powering down. This should be a minimum of 30 seconds. The longer the better.
10. Power KOEO for a solid 10 seconds and without input by any pedal or button of any kind start the vehicle.
11. Go back and clear all codes. Not just PCM/ECM/TCM but all from every module.
12. Collect the money $$$$$
🤨 some of that makes no sense
Let me know what you think makes no sense and I will explain the reasoning and how it was discovered.
Support wanted me to try the Beta. When I connected to my truck it updated the firmware on the MVPI2. Same problem. It will start the tune process, it performs the erase, the after 1-3% of the write it fails. Truck is still a paper weight. I sent them back what happened. Waiting again on their response.
Well you make it further than I do, mine won?t even start the write process, I get a no bus message on the truck and a initialize failed message on hp tuners when I try writing.
Where are you seeing the "no bus message"? Is that from the VCM Editor? I want to check mine later.
Attachment 106690
Attachment 106691
It shows right on my truck, in the EVIC. Only comes up after clicking the write button on the editor though
All HP Tuners can see is the my write successfully completed and then the next try the truck was completely dead.
Mine seems to erase successfully, but won't write. I have two new batteries I am installing later. Don't know if it will make a difference, but I figured it was worth a try. I was running Optima red tops and I have seen recent posts and videos from people having problems with them. I had a charger on them before I tried to flash. Support wanted me to try to flash my stock tune from my initial read. That didn't work either and I sent them back the debug. When I run the VCM Suite Info it shows at the bottom "Unable to detect the vehicles diagnostics protocol". I am hoping support will have an answer.
I?ll have a pre-programmed ecm by mid next week to put in my truck.
I am dreading having to do the same thing. I am holding out hopes that support will come up with something. You don't happen to sell pre-programmed ECMs do you? :D
If I had my Cummins hardware I could maybe do recoveries.
I found a couple of places I can get a pre-programmed ECM from, but it would set me back around $1000. I am not very happy with HP Tuners right now. It would be good to know what caused this.
The debug file from my laptop shows that the write to the ECM was successfully completed then nothing after that. The dash lights up like it does when writing a tune with the mm3 so I believe it?s stuck in boot mode for writing to. I?ll post up results of putting in another ECM once I get it.
I am shipping my ECM to support. They are going to try to bench flash it. The debug shows ECM active, so it doesn't appear to be toast. We'll see I guess. I am debating whether to.get a spare also. I told support we need a root cause so I can have confidence it won't happen again.
Any update on this? I'm very curious to see if they know what the issue might be.
Nothing on my end, fighting with the outfit I ordered an ecm from. Basically took my money, created a shipping label with UPS and have given me nothing but lies on where they are at with programming the ECM and getting it shipped. Gonna try to find a different outfit that will do a rapid turnaround on reprogramming the ECM that?s bricked on my truck.
My ordered ECM is getting delivered today.
Good to hear