Calibration Missing

Requesting assistance. I was flashing the ecm to dial in the speedometer and the new tank capacity and ran into some problems. I get the error message that the "calibration is missing" and "flash can is not able to determine the license status of this ecm". Attached is the calibration details and a screenshot during a recent flash.

Calibration Details

VIN 1GCHK23D57F1944XX
Serial BKN07015PRHR
Hardware N/A
Operating System 25803708
Calibration 25818885
BCC 5321
Operating System 25803708
Engine Operation N/A
Engine Diagnostics N/A
Engine N/A
Fuel System N/A
System N/A
Speedometer N/A

Calibration Screen Shot

15:33:42.093: Scanning for EFILive FlashScan V2 USB
15:33:42.109: Autodetect interface ...
15:33:43.937: Interface not detected
15:33:44.609: Scanning for EFILive FlashScan V2 HAPI
15:33:44.625: Autodetect interface ...
15:33:44.828: Interface firmware version: 2.6.35
15:33:44.828: Connection to [FSV2] interface is OK
15:33:44.890: Interface firmware model: FSV2
15:33:44.906: Interface firmware version: 2.6.35
15:33:44.937: Interface firmware date: May 03, 2010
15:33:44.968: FlashScan serial number: 003742023957
15:33:44.984: FlashScan license number: 003742023957
15:33:45.031: Disconnecting ...
15:33:45.890: CAN-VPW Bridge Deactivated
15:33:45.906: Disconnected
15:33:46.578: Scanning for EFILive FlashScan V2 USB
15:33:46.593: Autodetect interface ...
15:33:48.406: Interface not detected
15:33:49.078: Scanning for EFILive FlashScan V2 HAPI
15:33:49.093: Autodetect interface ...
15:33:49.296: Interface firmware version: 2.6.35
15:33:49.296: Connection to [FSV2] interface is OK
15:33:49.328: CAN-VPW Bridge Activated
15:33:49.421: Current protocol set to: "ISO 15765 CAN"
15:33:49.421: Autodetect PCM...
15:33:51.453: PCM not detected.
15:33:51.453: Autodetect ECM...
15:33:52.609: ECM not detected.
15:33:52.609: Autodetect TCM...
15:33:52.640: Connection to TCM is OK
15:33:52.671: Current protocol: No Protocol
15:33:52.734: Interface firmware model: FSV2
15:33:52.765: Interface firmware version: 2.6.35
15:33:52.781: Interface firmware date: May 03, 2010
15:33:52.812: FlashScan serial number: 003742023957
15:33:52.843: FlashScan license number: 003742023957
15:33:53.984: Current protocol: "ISO 15765 CAN"
15:33:54.000: Getting status...
15:33:54.296: Status: Calibration missing.
15:34:04.262: Preparing ECM for reflash...
15:34:05.465: ECM seed is: $AE2D
15:34:05.465: Unlock attempt 1 of 1
15:34:05.637: Initializing ECM...
15:34:06.450: Request GM operating system...
15:34:06.512: GM operating system: 52606128
15:34:07.653: Request serial number...
15:34:09.356: Serial number: 86J701401310
15:34:14.589: ECM is in an unknown state.
15:34:16.714: Clear emisison related DTCs...
15:34:16.777: Clear DTCs for all modules...
15:34:17.933: Autodetect interface ...
15:34:18.027: Interface firmware version: 2.6.35
15:34:18.027: Connection to [FSV2] interface is OK
15:34:18.027: Autodetect ECM...
15:34:18.667: ECM not detected.
15:34:19.511: Disconnecting ...
15:34:20.339: CAN-VPW Bridge Deactivated
15:34:20.339: Disconnected
15:34:20.355: Data transfer was interrupted.
15:34:23.222: Done!

How could the OS and calibration change during a flash. I have no idea what vehicle supports OS 25803708 or Calibration 25818885.

No disconnects were noticed, perhaps a surge in vehicle battery? Anyways, I am skeptical in operating the truck under these conditions. Even a full flash has not resolved the issue. Look forward to your evaluation of the situation.

I have used the following trouble shooting to this point:

Disconnected the batteries for 15 minutes and tried flash again.
EFLive unit lights up when plugged into the OBD-2 connector only (no laptop)
No Blown Fuses

Currently using EFILive V7.5.6 Build 117
Flashscan V2 Firmware 2.06.35
Flashscan V2 Boot Block 2.06.03

Thanks

Interesting, first try the latest release (it is currently under the red text in the following link) and upgrade your firmware (even though it is the same version number, the date is June 30 and it is different, beta testing is happening behind-the-scenes) using EFILive Explorer.

Download Link

Are you trying to flash the ECM or TCM? Its not detecting your ECM at all, just the TCM (for a speedo flash Id imagine this make sense). Are you trying to flash an LBZ or LMM? Have you been able to successfully flash this same truck previously?

Quote:

---

Originally Posted by ScarabEpic22

Interesting, first try the latest release (it is currently under the red text in the following link) and upgrade your firmware (even though it is the same version number, the date is June 30 and it is different, beta testing is happening behind-the-scenes) using EFILive Explorer.

All releases, including beta are installed after pulling these codes.

Download Link

Are you trying to flash the ECM or TCM? Its not detecting your ECM at all, just the TCM (for a speedo flash Id imagine this make sense). Are you trying to flash an LBZ or LMM? Have you been able to successfully flash this same truck previously?

---

Flashing the ECM. Detects ECM with a red X, after upgrade a green checkmark on a LBZ system. I have been able to flash successfully in the past with no issues, at least with no complications of this magnitude. I will update my signature to avoid vehicle stats questions in the future.

Definitely do try the latest pre-release software/firmware version. With this installed the versions will be:
- 7.5.6 Build 125
- 8.1.2 Build 105
- V2 firmware 2.067.35 (30 June 2010)

Quote:

---

Originally Posted by Tordne

Definitely do try the latest pre-release software/firmware version. With this installed the versions will be:
- 7.5.6 Build 125
- 8.1.2 Build 105
- V2 firmware 2.067.35 (30 June 2010)

---

That is the same versions currently installed on the laptop and handheld as we speak. Currently performing a full flash now.

Log keeps retrying previous block, erasing ECM flash menmory, ecm flash memory erased OK, then retrying. This cycle has been going for over an hour. Does this seem strange to any one?

On another note, what does the last 3 digits on a time stamp represent?

It's found the ECM at one point as it shows the OS 52606128 (DSP5), but initially it is finding the TCM (the 2xxxxxx type OS numbers are the TCM).
Does the truck start and run?

Quote:

---

Originally Posted by GMPX

It's found the ECM at one point as it shows the OS 52606128 (DSP5), but initially it is finding the TCM (the 2xxxxxx type OS numbers are the TCM).
Does the truck start and run?

---

Yes

So if we're certain that everything is up to date (including the 30 June 2010 firmware) this is interesting; we've not seen any similar behavior to draw upon. Out of interest are you able to read the ECM? Can you also perhaps send the debug files to me (support@efilive.com) as described here (http://support.efilive.com/kb_articl...8254-QOGC-9586). Please do only send the specific files for the read/flash attempt.

In a previous question; the extra 3 digits on the times recorded in the logs are thousandths of seconds.

Quote:

---

Originally Posted by Tordne

So if we're certain that everything is up to date (including the 30 June 2010 firmware) this is interesting; we've not seen any similar behavior to draw upon. Out of interest are you able to read the ECM? Can you also perhaps send the debug files to me (support@efilive.com) as described here (http://support.efilive.com/kb_articl...8254-QOGC-9586). Please do only send the specific files for the read/flash attempt.

[COLOR="rgb(0, 0, 0)"]Yes I am able to read the ECM, Funny thing though every tune uploaded is void of a operating system and not recommended for flashing. Missing checksums. Unfortunately I am unable to send the requested data since the EFI program will not allow me to program the ECM with the operating system and calibrations any longer. [/COLOR]

In a previous question; the extra 3 digits on the times recorded in the logs are thousandths of seconds.

---

That was my 1st impression. I was hoping that it might refer to the sectors of the ECM drive. Files requested in e-mail.

Is your file in .tun or .ctd format? You're not getting an error like in this thread (http://forum.efilive.com/showthread....-t-Load-a-File) are you? You should be able to email me the calibration (even if it is corrupt)?

http://www.efilive.com/index.php?opt...111&Itemid=121
Send the relevant *.blx files to me at paul@efilive.com

Regards
Paul

Paul, I've just recently sent across the ones I requested (a couple of posts back) that are from today.

Quote:

---

Originally Posted by Tordne

Is your file in .tun or .ctd format? You're not getting an error like in this thread (http://forum.efilive.com/showthread....-t-Load-a-File) are you? You should be able to email me the calibration (even if it is corrupt)?

---

The files I tried flash scan, to include the stock, are all *.tun. No, I have not seen this type of message to this point.

After looking at the blx files they all show the same problem. The ECM refuses to go into programming mode. At this stage, I don't know why.
I am in the process of uploading a new software version that contains new LBZ/LMM BBF flashing options. Those options can be used to reflash an LBZ or LMM engine controller using the FlashScan device in standalone mode.
It would be worth trying the new standalone BBF options to reflash your truck. That will help rule in/out a problem with the V7.5 re-flashing software.

Once the new release is available I can help you set up the BBF options. It should be ready in the next 24 hours.

Regards
Paul

Thanks Paul. Thought I fried the ECM. Look forward to the updated version.

I think we are talking the same problem truck here.
This was the one with a standard (non DSP) calibration flashed in to a DSP5 OS?
If yes, I looked over the DSP5 code this morning and I think if you just move your switch back to the position that uses the factory (non DSP) maps then the ECM might actually work correctly again. If that works then flash back in a DSP5 calibration and everything should be happy again.

Quote:

---

Originally Posted by Blacky

...The ECM refuses to go into programming mode. At this stage, I don't know why.

---

can bus voltage do this?

Quote:

---

Originally Posted by killerbee

can bus voltage do this?

---

Over/under voltage on the CAN bus will cause problems but I don't think it would cause this particular problem.
Other CAN messages are being transmitted ok so the CAN bus is working correctly, only the programming messages are failing.

Regards
Paul

I have been having this same issue. Twice in the last week. It will allow me to access and clear codes with my V2 but I can't read, log, or flash. I did find the last time I had it happen that I could flash a previous tune after I cleared the codes.

I haven't updated in 6 months but it seems the above problem occurs with the latest release as well.

A very similar thing happened to me today. I upgraded to the latest version of EFIlive, and when i went to connect to a truck, it stated PCM not detected. I know for sure i was able to connect to the truck before. I will try tomorrow with the old version of EFILive and see what happends.

I am having this same problem on a truck that has never been tuned. Its an lmm and we took off the dpf and he just wanted the codes turned off, so i read the stock data and it said ecm had missing calibration but it completed the read. I still tried to turn codes off and fully reflash it but would not let me. It does not give me the green check mark that says ecm is ok.

Can you please ensure that the software and firmware you have installed is the latest versions? We made an update just a couple of days ago.

Here are a couple of knowledgebase articles that discuss software and firmware updates:
- Software
- Firmware

Please let us know if you still have issues after installing these releases.

Well my software is up to date but when i went to update my firmware it popped up that the device has previously been upgraded to boot block v2.05.xx or greater. Then it says i have to use efi live explorer what does that mean?

See the Firmware knowledgebase link in my previous post for guidance on updating your FlashScan V2 bootblock and firmware. If you are still running the very old 2.04.x firmware please see the noted document at the bottom of the article.

it does not let me click on efi live control panel icon. I have v7.5.6 build (139)

Try the following so we can work out your firmware version:
- Connect V2 to your PC
- Go into the V7.5 Tune Tool
- Select the 'Help->FlashScan V2 / AutoCal V2 VIN Licensing' menu option

The firmware version will be shown in one of the text boxes.

Ok i got it to update i will try it on the truck tomorrow and let you know. thanks a lot for your help

No worries, let us know how it goes :)

well it gives me the green check mark now but now when im reading or flashing either one it gives me an error code 12:56:20.734 failed controller has returned to normal operation. then a 12:56:16.171 unregistered interface some features have been disabled

So your software versions are now 7.5.6 Build 139 and 8.1.2 Build 127, and your bootblock and firmware are 2.07.01 and 2.07.04 respectively?

Have you tried reading the ECM using the pass-thru functionality of the V8 software?

Incidentally, this isn't a DSP5 you're trying to read is it (because that is not actually possible)?

Cheers,

You would be correct. No I have not how do i do that? and no it is not a dsp5

To try the pass-thru function in V8 do the following:
- Connect V2 to your laptop and vehicle.
- Open the V8 'EFILive Scan and Tune' application; there should be a shortcut on your desktop.
- Go to the 'F3: Tune' section.
- Click the 'Auto Detect' button and it should show the LMM ECM. If it does not you can right-click and select manually.
- Click the 'Go' button to start the read.

ok thanks a lot i will give it a try and let you know

Ok so it still did not work but after i updated my firmware it said it was successful but i just went to double check it and it still says my firmware is 2.6.33. Sorry if im being a pita

If you downloaded the latest software you should be on firmware 2.07.04. See these knowledgebase articles regarding software and firmware updates:
- Software
- Firmware