September 2021, V8.3.8 Public Release

[Blacky]

V8.3.8 Public Release



Attention:
V7.5 no longer supports installation to Windows XP or Windows Vista. This change is due to SHA1 having been deprecated by digital certificate authorities. More info on SHA1 (https://en.wikipedia.org/wiki/SHA-1)
V7.5 and V8 are now only supported on Windows 7, 8, 8.1 and 10.




Full Release Notes:
Whats New (https://download.efilive.com/Software/whatsnew_8_3_8.htm)


Version Numbers:
After installing this release you should have the following software and firmware versions installed:



[*=1]EFILive V7 software: V7.5.37 To view the installed version, select Help->About (in the V7 Scan or Tune software).
[*=1]EFILive V8 software: V8.3.8 To view the installed version, select Help->About (in the V8 Scan and Tune software).
[*=1]FlashScan/AutoCal V3 Firmware: V3.00.070 (Sep 20, 2021), Boot Block: V3.00.005 (Oct 20, 2020)
[*=1]FlashScan/AutoCal V2 Firmware: V2.08.177 (Sep 03, 2021), Boot Block: V2.08.009 (Feb 27, 2021)


Download here:

Download V8.3.8 (https://download.efilive.com/Software/V8/EFILiveV8.3.8_Setup.exe)
Download V7.5.37 (https://download.efilive.com/Software/V7.5/EFILiveV7.5.37_Setup.exe)


Known Issues:


Issue #1: Importing JTAG E86B files may result in a Boot Software segment checksum error.
Workaround: None. Don't flash imported files with checksum errors. Don't use the EFILive software to correct checksum errors for the E86B imported files as that does not fix the underlying cause of the checksum error - it just masks the error(s) and causes additional problems.

Issue #2: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However, the DMA PIDs may no longer return valid data.
Workaround: EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.

Issue #3: The [F2: Scan] -> [F3: Data] display was not converting the PID values to non-metric units when non-metric units are selected.
Workaround: Fixed in Update 1 (https://forum.efilive.com/showthread.php?30422-October-2021-V8-3-9-Public-Release)

Issue #4: When black box logging multiple controllers, DMA PIDs for the ECM are logging as N/A.
Workaround: Fixed in Update 1 (https://forum.efilive.com/showthread.php?30422-October-2021-V8-3-9-Public-Release)



Regards,
The EFILive Team

[Blacky]

The [Check for Updates] option has been activated for both V7 and V8.

The following versions (i.e. the previous public release) can be updated/patched automatically:

V7.5.36
V8.03.7


Any versions installed before the previous public release will detect that an update is available, but the entire installation will need to be downloaded and installed.

If you have installed any of the beta or RC updates (i.e. any installation of V7.5.37 or V8.3.8) then the [Check for Updates] option will not detect that a newer version is available.
In that case, you should download and install the latest public release from this thread.

Regards
Paul

[1FastBrick]

Curious, V8 flashes fine. But with 7.5 I get this error about firmware even though it was updated. Was trying to flash an LS1B if it matters. I just happen to be more familiar with 7.5 and was looking for a specific issue when I came across this.

23907
23905
23906

[Blacky]

Curious, V8 flashes fine. But with 7.5 I get this error about firmware even though it was updated. Was trying to flash an LS1B if it matters. I just happen to be more familiar with 7.5 and was looking for a specific issue when I came across this.

That is strange, it is also strange that no serial/license numbers showed up in the screen shot.
This is what you should see...

23908

Is it possible that there is another device (AutoCal or other FlashScan) connected?
Maybe the V8 software still has the V2 device connected and is preventing the V7 software from reading it.

Regards
Paul

[1FastBrick]

The license showed up, I blacked it out...23910

I believe Only the The V7 tune was open. I only have one V2 no Auto Cal

I was using a Bench top set up.

[1FastBrick]

Its is working correctly now. 23911 I have flashed a few versions of the same tune successfully with out issue in the V7 software.

I think I ran into this before and it had something to do with needing to re-boot. Which I did not earlier after loading the software and updating firmware.

Next Question. Regarding a full flash. If I full flash a PCM with a completely different calibration, Shouldn't it completely over write an existing calibration? Specifically the LS1B. I know E38 and E67 need to make sure they are compatible with the ECU.

[Blacky]

Next Question. Regarding a full flash. If I full flash a PCM with a completely different calibration, Shouldn't it completely over write an existing calibration? Specifically the LS1B. I know E38 and E67 need to make sure they are compatible with the ECU.

Yes you can full-flash any OS into an LS1 - but remember some LS1 controllers are 512KB and some are 1024KB and you can't mix/match the different memory sizes.
And because the LS1 handles the transmission as well, you also need to be careful about flashing an automatic tune into a manual vehicle and vice-versa.

Regards
Paul

[1FastBrick]

Yes you can full-flash any OS into an LS1 - but remember some LS1 controllers are 512KB and some are 1024KB and you can't mix/match the different memory sizes.
And because the LS1 handles the transmission as well, you also need to be careful about flashing an automatic tune into a manual vehicle and vice-versa.

Regards
Paul

The Memory size and auto/manual transmission I know and understand on these controllers.

Lets use the 1024KB as the example. In the Past I was able to Full Flash one of these with Completely different Base tune with out issue. Recently I can not. The Cycle looks to complete normally but if you go back to read the PCM It still has the old File in it. Now if I change the Vin Number to the new Calibration's vin in the scan tool, It will flash Correctly.

In this case both files happen to be of the same year. One was an 8.1L/ 4L80E 4x4 and I was flashing over it with a 5.3L 4L60E 2wd calibration. Full Flash was used. When I read it back out to verify it still had the 8.1L tune in it. But if I use the scan tool to change the Vin to the 5.3L VIN and then go back and do a Full flash it will take with out a problem.

I also tried the reverse to see if it did the same thing. Does not take until I change the Vin.

Try these for the example.

[Blacky]

How are you determining that the tune was not installed during the flash?
I tried it here on a 1MB PCM with those two files and it all worked as expected.

Regards
Paul

[1FastBrick]

How are you determining that the tune was not installed during the flash?
I tried it here on a 1MB PCM with those two files and it all worked as expected.

Regards
Paul
After flashing it, I read it back out to make sure the file took correctly. Maybe I need to remove and reinstall the software. It doesn't give any errors. I even read it out a second time to confirm.

I appreciate you verifying it.

[1FastBrick]

Ok, I completely removed EFI Live software. I then Shut down and restarted my computer. I Re Download EFI V8 and V7.5 from this thread. I then restarted the computer again. The issue continues. Even if I shut down and reopen V8 between flashes.

Pay attention to the Vin number displayed. I attached them to these file names as well. I had the same issue with the other files I posted. It will Only Full Flash a new file If I change the vin number to that file. I forgot if you do a license check in V8 it will read the Vin Of the current file programed. Service number on PCM is 12589463. Bench Harness is from EFI connection. Let me know if I can provide any other information.

23914
23915

23917
23918
23919
23920
23921
23922
23923
23924
23925

[Blacky]

Again, I need to know how you are determining that the tune file was not flashed in?
If you are basing it off of the VIN then that won't work since the VIN is not changed/updated when you flash a tune file - even during a full-flash.

What you need to do is flash the tune in, read it back out and save it with a different name, then use the tune compare option to compare the tune file that was flashed v's the tune file that was just read back out.
They should be the same. Although there may be a checksum or two that are different. That is because EFILive may automatically adjust some backup ETC (electronic throttle control) tables to ensure correct operation of the ETC system.

Regards
Paul

[1FastBrick]

I have also read it back out after doing a full flash. That's how I knew the file was not changing. here is an example
23926
23927

[1FastBrick]

The 2 files are completely different and should not compare if it correctly flashed the other operating system during a full flash.
23928
23929
23930

[joecar]

I have also read it back out after doing a full flash. That's how I knew the file was not changing. here is an example
23926
23927
These 2 files are completely different (different OS's even)... V8 compare sees them as different:



Calibration comparison summary: Sep 28, 2021 06:22:28 PM

Calibration Name: C:\Users\joecar\Downloads\LS1B_0001 After Full Flash.ctz
Controller: LS1B
Operating System: 12619623

Alternate Name: C:\Users\joecar\Downloads\LS1B_0000 Base read.ctz
Controller: LS1B
Operating System: 12612114

Description Calibration Status Difference Calibration Alternate Units
Different Seg 1 Operating System 12619623 ($BCE9) 12612114 ($EB92)
Different Seg 2 Engine Operation 12619625 ($66EF) 12612119 ($0265)
Different Seg 3 Engine Diagnostics 12591440 ($80FE) 12612669 ($A0E0)
Different Seg 4 Transmission Operation 12591457 ($EADE) 12578782 ($6E10)
Different Seg 5 Transmission Diagnostics 12606607 ($49ED) 12578793 ($ED78)
Different Seg 6 Fuel System 12591497 ($6CAB) 12612129 ($9ACB)
Different Seg 7 System 12591524 ($200A) 12578832 ($15BF)
Different Seg 8 Speedometer 12606732 ($7238) 12579002 ($02D9)
Different B0101 Main VE Table Different from [0,0]..[18,19]
Different B0102 VE while Cranking Different from [0,0]..[8,32]
Different B0104 Cylinder Volume 666 1013 cc
Different B0120 RPM Threshold For Airflow Calculation 4000 4150 rpm
Different B4901 Charge Temperature Blending Different from [0,0]..[0,15]
Different B4902 Charge Temperature Filter Different from [0,0]..[0,15]
Different B3201 Initial Fuel Prime Different from [0,0]..[0,4]
Different B3202 Initial Fuel Prime Delay Different from [0,0]..[0,15]
Different B3203 Initial Fuel Prime Timer Different from [0,0]..[0,15]
Different B3204 Non Sequential First Fuel Pulse Different from [0,0]..[0,15]
Different B3205 Non Sequential First Fuel Pulse Delay Different from [0,0]..[0,4]
Different B3206 Non Sequential Second Fuel Pulse Different from [0,0]..[0,6]
Different B3207 Non Sequential Second Fuel Pulse Delay Different from [0,0]..[0,15]
Different B3604 Commanded Fuel When Cranking Different from [0,0]..[16,18]
Different B3642 After-start Coolant Temp Enrichment Different from [0,0]..[4,18]
Different B3662 After-start Enrichment Factor Different from [0,0]..[0,16]
Different B3627 After-start Enrichment Decay Delay Different from [0,0]..[4,18]
Different B3628 After-start Enrichment Decay Rate Different from [0,0]..[4,14]
Different B3650 After-start Enrichment Decay Factor Different from [0,0]..[4,18]
Different B3661 Restart Enrichment Different from [15,10]..[18,20]
Different B3629 Park To Drive Enrichment Different from [0,0]..[0,15]
Different B3630 Park to Drive Enrichment Decay Delay Different from [0,0]..[0,15]
Different B3631 Park to Drive Enrichment Decay Rate Different from [0,0]..[0,15]
. . .
. . .
. . .
Different H0101 Vehicle Speed Sensor Pulses per distance traveled 62958 68989 count/km
Different H0103 Differential ratio 3.730 4.100 factor
Different H0104 Trans Output Shaft Revs/distance traveled 1577.0323 1733.6250 rev/km
Different Axis H0108 ETC Speed Govern Threshold
Different Axis H0109 Maximum Vehicle Speed (Non ETC)
Different Axis H0110 Overspeed Timer (Non ETC)
Different Axis H0111 Maximum Vehicle Speed (With ETC)
Different Axis H0112 Overspeed Timer (With ETC)
Different Axis H0113 Speed Limiter Disable

[1FastBrick]

These 2 files are completely different (different OS's even)... V8 compare sees them as different:



Which is why I don't under stand what's happening. As you saw in my other post after flashing, It was shown they were similar files and even made a comparison.

Today when I try to compare the same 2 files in V7 it shows they are different. Even shows the warning that they are different and no comparison will be made.
23932

I will Admit I am still fumbling with V8 so I though I was doing something wrong But V7 says the same thing so it leaves me scratching my head.

[Blacky]

Do you happen to have "Test Flash" selected? If so, then nothing will get flashed, it will just go through the motions.
23933
Regards
Paul

[1FastBrick]

No, I do not.
23934

[Blacky]

OK, let's get to the bottom of this. Can you please do the following:

Read the PCM, save the file as "First_read.ctz" and once the read is complete, save a *.htx trace file from the EFILive Control Panel, call it "First_read.htx".
Full-flash a different file, at the end switch off the ign. wait the required time and switch on the ignition again. Save another trace file, call it First_flash.htx.
Read the PCM again, save the file as "Second_read.ctz" and once the read is complete, save a *.htx trace file from the EFILive Control Panel, call it "Second_read.htx".

Then zip up the following five files:


First_read.ctz
First_read.htx
The file that you flashed in.
Second_read.ctz
Second_read.htx


Thanks.
Hopefully I can figure out what is going wrong from that data.


To save a *.htx trace file from the EFILive Control Panel, click the [Control Panel] button in the top right corner of the V8 main window.

23936

23935

[1FastBrick]

Thank you! I will try it right now.

[1FastBrick]

23937

Lets see if this goes through.

[1FastBrick]

Strange. That shows up as different files.

Is it possible something was corrupted on the PCM side?

[joecar]

Strange. That shows up as different files.

Is it possible something was corrupted on the PCM side?

I'm not at my PC/laptop right now so I can't look at the files...

are you saying that the file Second_Read.ctz is different than the .ctz that you flashed into the PCM...?

[1FastBrick]

I'm not at my PC/laptop right now so I can't look at the files...

are you saying that the file Second_Read.ctz is different than the .ctz that you flashed into the PCM...?

Correct, The files are different.

When I attempt to compare both files, I get the correct error showing they are different files. On both V8 and V7 software.

The only thing that changed was I manually stopped mid flash and then did a recovery earlier in the day. Perhaps something was corrupted in the PCM and it was corrected when I did the recovery.

Either way I am Grateful for the help I have received.

[Blacky]

Thanks for sending those test files and trace files. The files do show that everything flashed correctly and read back out correctly.
Please let me know if the problem occurs again.

Is the PCM a RoadRunner PCM by any chance?

Regards
Paul

[1FastBrick]

Thanks for sending those test files and trace files. The files do show that everything flashed correctly and read back out correctly.
Please let me know if the problem occurs again.

Is the PCM a RoadRunner PCM by any chance?

Regards
Paul

No it is not. Just a Spare PCM for my personal Vehicle.

I was told the 1MB PCM's do not function correctly with the road runner and they discontinued support. IT only appears to work for the 512Kb 99-02 style pcm's. I have never had the chance to play with a roadrunner PCM.

[Blacky]

Update 1 has been released here: https://forum.efilive.com/showthread.php?30422-October-2021-V8-3-9-Public-Release
See the "What's New" for changes and updates.

Regards
Paul