HP Tuners for 2005-2015

Sounds an awful lot like my "USB cable" incident..

 

Can you elaborate more on this bench harness? It sounds like something I'd be into.

 

Chop off some ECU connectors at a wrecking yard along with the OBDII plug and a bit of wiring.

Consult the EWD to determine the 12v constant, ignition, and ground. Extend the wiring for 12v+ and add a switch for the Ign+/Gnd to a bit so you can connect to a power source.

Then you'll do the same to wire in the OBDII directly to the ECM harness. Allowing you to flash the ECU outside the vehicle.

 

There absolutely has been a shift in how things were written and verified since the initial release and current.

Initial release it would write in ~ 1.5-2min total, then another 1.5-2 min to verify. Now its 3-4min of writing with no verify.

 

What is a bench harness? Does HPT recommend hooking up the truck to a charger when flashing the truck?

 

↑
Can you elaborate more on this bench harness? It sounds like something I'd be into.
Chop off some ECU connectors at a wrecking yard along with the OBDII plug and a bit of wiring.

Consult the EWD to determine the 12v constant, ignition, and ground. Extend the wiring for 12v+ and add a switch for the Ign+/Gnd to a bit so you can connect to a power source.

Then you'll do the same to wire in the OBDII directly to the ECM harness. Allowing you to flash the ECU outside the vehicle.

 

yeah we just got rid of the verifying message becuase some people thought the could disconnect, the underlying process is the same.

 

Ah ok. That makes sense.

Could a disruption in usb connectivity (ie failing cable) cause this? or is this more likely an undervolting / extra draw from accessories (like a fuel pump turning on as previously mentioned) causing disruption to the ecu?

Does the MPVI2 store (buffer) the whole tune file while writing, or is it pushed bit by bit to the MPVI2 as needed?

Just asking questions to be more educated and mitigate losses better. As always thank you for your support @HPTuners

 

thanks for this info.

 

Yes, anything that disrupts comunication on the CAN bus or the USB link could cause the problem. We just see a packet timeout becuase usually a USB noise issue or intermittent problem isn't enough to drop the USB link and make the USB driver report anything unusual happened. The communications is buffered to a degree but not the whole tune. In future we will have this option on the MPVI2 as Standalone Flashing, it will help guard against PC or USB issues but these aren't a major source of problems thesedays (not since the debarcle of Windows Vista and USB driver compatibility anyway). The real problem is the robustness of the Toyota system which cannot be changed.

 

@HPTuners is removal of fuses an acceptable way of solving voltage hiccups? like fuel pump? s/c coolant pump? make sure radio and climate controls are off? don't touch window switches?

 

It's hard to say, we flashed our Tundra hundreds of times without a problem, we also have a few testers for diesel and other vehicles that haven't reported problems that weren't explained by faulty things. eg. JustDSM's USB cable

 

if you have a cable length, type, and quality we should invest in I'd like to know. this truck is my dad, and I'm not as tuner savvy as some guys here. I'd really be poked if I had computer failure.

 

@HPTuners, I finally submitted my ticket. #182488

 

My stock fuel pump wiring is disconnected. I have my aftermarket fuel pump wired to come on anytime the ignition is on.

I’ve been flashing with the MPVI2 while the fuel pump is running the whole time. No issues yet, but I do use a maintainer.

 

I also use a maintainer as well, while loading tunes on my truck. Despite being a completely different standalone ECU.

 

So, is the battery main lead about the only stock part of your powertrain left?

 

I think his battery cables have also been modified!

 

I figure the ground wire has, just wasn't sure about the positive ??

 

And the cab.