Copperhead Calibration Only Reflashing now in VCM Suite 3.7 Beta

[Eric@HPTuners]

Several customers have contacted us about adding the ability to do calibration only reflashes on the Copperhead to save time.

As of VCM Suite 3.7.110, this is now the default method for flashing. You must first disable the P0605 DTC from the DTC list before using this method of reflashing.

Total time required for a full reflash is 3 minutes, 15 seconds.

Total time required for a calibration only reflash is 53 seconds.

If you are changing strategies, or applying an OS Patch (such as the Copperhead limiter patch), you must do a full reflash. Once the strategy has been changed or the patch applied, you can use calibration only.

[tbrtuning]

Thank you. The time saved definitely adds up.

[15PSI]

Same here. Thank you Eric. That makes things so much easier.

[Jn2]

You the real MVP Eric, so we should make sure the first write is a write entire and then after that we can always use write calibration only(unless we are applying a patch of changing strategy)? or can we read the stock file and immediately do just a write calibration only the first time we go to flash the car?

[bbrooks98]

Noticed the rest of the torque ratio tables were labeled too.

[Jn2]

Noticed the rest of the torque ratio tables were labeled too.

Wot you are right....wonder what else has been added

[bbrooks98]

Noticed fuel rail temp compensation too. Yea that labeling fixed my target N hunting issue. It was disabled lol

[96gt4.6]

Awesome! This will certainly save a lot of time.

Any chance this will be coming to the TC-1797 Eco?

You da man Eric!

[Engineer@HPT]

Awesome! This will certainly save a lot of time.

Any chance this will be coming to the TC-1797 Eco?

You da man Eric!

As of the latest 3.7, TC-1797 takes ~50 seconds using the same method.
TC-1767 and Oak1472 have also been updated with 30 and 40 second flash times.

[tbrtuning]

Is there a changelog somewhere for the Beta so I can keep an eye on it to see if anything gets added that I would be interested in? I don't want to miss any little changes that don't get mentioned and could help me write better tunes.

[Ranger Coyote]

I can't seem to locate a download for the beta? where can I get 3.7?

[tbrtuning]

Email [email protected] and ask them to add it to your downloads page. Include your interface id

[tbrtuning]

Wot you are right....wonder what else has been added

2011 Coyote Mustang

TorqueMulitplierVsLambda.PNG

[murfie]

The clip/add torque makes more sense with off, look up, intervention prevention, adaptive rather than what it was. I saw a few other switch labels.

[tbrtuning]

Yes. They added some Ecoboost truck stuff too. Started messing with one this morning and saw it. They say the HSPI and LSPI tables are based on octane modifier like I have always thought would make sense rather than what one of the major teaching sources said they are in relation to. I've been keeping my high where I want it and dropping 0.05 or so to nominal then more to low so it works out.

[Jn2]

I have a questiona bout the "disable P0605" part of the instructions.

I tried to use "write calibration" last night on a Saleen I was tuning and it gave me a window to make sure the code was disabled, I double checked and the code was set to "no error reported", but to be safe I made sure the drop down list didn't also have a "disabled" option. Since it did not does this mean we only need to make sure the code is set to "no error reported" not "disabled"?

[bbrooks98]

Pretty sure it's No error reported. That's what I've been using and it's flashed fine with a calibration write only.

[Jn2]

Pretty sure it's No error reported. That's what I've been using and it's flashed fine with a calibration write only.

Awesome, thats what I figured but wanted to be sure.

[Jn2]

Wrapped up a tuning session over the weekend and got to say the "write calibration" functions saves so much time

[GHuggins]

It didn't save me a whole lot of time on the whipple tune OS - honestly seconds If that, but saved LOTS of time on the Roush OS I tuned today... May have just been the Roush OS as they cause issues randomly on their own, but has anyone had problems with traction and stabilitrac lights randomly coming on with engine fire up after doing it this way? Honestly was probably just where I forgot to do a full vehicle DTC clear after dynoing and completely my fault, but wanted to make sure - all lights went out after driving a second time like they did the first time - thought they would have stayed off after passing everything the first drive?