PDA

View Full Version : Update: Jun 21, 2014



Blacky
June 20th, 2014, 01:50 PM
The June 2014 public pre-release software is now available.

Please download and install both the V7.5 and V8 software packages.

Download V7.5 Software (http://download.efilive.com/Software/V7.5/EFILiveV7.5.7.260_Setup.exe) (92 MB)
Download V8 Software (http://download.efilive.com/Software/V8/EFILiveV8.2.2.253_Setup.exe) (45 MB)

Release Notes:
Release Notes. (http://download.efilive.com/Documentation/June%202014%20EFILive%20Release%20Notes.pdf)

The FlashScan/AutoCal V2 firmware has been updated, the version number has been increased to V2.07.62, and the firmware date has been updated to June 21, 2014. There has been no actual change to the firmware since the previous (V2.07.61) version. The updated version number is for internal tracking/compatibility/consistency only.

IMPORTANT: The *.ctz and *.coz tune file formats were updated in the previous update. All existing *.ctz and *.coz files will continue to operate with the V7.5 and V8 software and with the FlashScan and AutoCal firmware. All new *.ctz and *.coz tune files that are saved using the following software or firmware versions: V7.5.7.259, V8.2.2.252, V2.07.61 (or later versions) will no longer be compatible with older software or firmware versions.
That means if you are using this latest software version, then any tune files that you save may only be shared with other EFILive users who are using this latest (or a later) version of the software and/or firmware. For tuners that means making sure your customers' software matches the software and firmware version that you are using.


Fixed Issues:

[*=1]The PID display sequence in the V8 Scan Tool was not being saved/loaded correctly.
[*=1]Some E86 calibrations that displayed incorrectly have been fixed.
[*=1]Some E39, E78, E83 and E92 calibrations that displayed incorrectly have been fixed.
[*=1]Configuring LMM PID linking between the V7 Scan Tool and Tuning Tool software requires that you copy the existing LBZ_Link.ini file to a new file called LMM_Link.ini. The section name in the new LMM_Link.ini file must also be changed to [LMM].


Known Issues:
Please post issues, questions, clarifications (large or small) in this thread.


As issues are reported and confirmed they will be re-posted as "Known Issues" below.



Version Numbers:

After installing the latest release you should have the following software, boot block, firmware versions installed:



EFILive V7 software: V7.5.7 Build 260
To view the installed version, select Help->About (in the V7 Scan or Tune software).

EFILive V8 software: V8.2.2 Build 253
To view the installed version, select Help->About (in the V8 Scan and Tune software).

Boot Block: V2.07.07 (Feb 07, 2014)
To view/update the Boot Block, Click the [Check Firmware] button in the V8 Scan and Tune software.

Firmware: V2.07.62 (Jun 21, 2014)
To view/update the Boot Block, Click the [Check Firmware] button in the V8 Scan and Tune software.



Regards
The EFILive Development Team

GMC-2002-Dmax
June 21st, 2014, 10:33 AM
Thanks !

garrettg.bpd
June 22nd, 2014, 01:54 PM
I loaded the latest build today and flashed my 5.9L with no problems. Later in the day I plugged in my flashscan to do some bbloging. the problem im having is that the .efi file will only play in v8 and not v7.5. all my old build logs will play in both programs with no problems. 17051 please try this file

Biodiesel66
June 23rd, 2014, 12:08 AM
I loaded the latest build today and flashed my 5.9L with no problems. Later in the day I plugged in my flashscan to do some bbloging. the problem im having is that the .efi file will only play in v8 and not v7.5. all my old build logs will play in both programs with no problems. 17051 please try this file

I just BBL the LML and everything works fine.

I know I needed to redo my BBL PIDs for the LML because of the A/B controller being added and reload all the new Config files.

I think the problem could your Config files did not get updated to the 6/20/14 for your controller?

Just a thought.

joecar
June 23rd, 2014, 07:45 AM
Thanks.

WyoFreeride
June 23rd, 2014, 08:08 AM
Thanks

Blacky
June 23rd, 2014, 10:17 AM
I loaded the latest build today and flashed my 5.9L with no problems. Later in the day I plugged in my flashscan to do some bbloging. the problem im having is that the .efi file will only play in v8 and not v7.5. all my old build logs will play in both programs with no problems. 17051 please try this file

It is a "known/fixed" issue with Cummins BBL data logs. To allow for future expansion, the PID prefix "CH" (which EFILive was using to indicate PIDs from Cummins Diesel controllers) has been recently changed to CM. CH is now reserved for future implementations of Chrysler PIDs. Old Cummins BBL data logs that contain PIDs with the "CH" prefix will not load correctly in V7. If you have old data logs that you really want/need to use in V7, they can be converted by changing all the PID names from CH.xxx to CM.xxx using a program like Hex Workshop.

I've attached your file with the PIDs renamed from CH.xxx to CM.xxx so that it will now load in V7.

Regards
Paul

garrettg.bpd
June 23rd, 2014, 11:11 AM
Paul thanks for the file fix. but all my old bbl files work fine. The one I made yesterday is the only one that wont load after the latest update. All my old logs are cm pids.

Blacky
June 23rd, 2014, 11:17 AM
Check that you have the latest update of the CMB.pmm file on your FlashScan device. The "CM" code is encoded in that file (same goes for CMC.pmm).
The date/time stamp on the CMB.pmm file should be June 26, 2014 1:57pm sorry it should be June 21, 2014 1:57pm

Also make sure you are using firmware V2.07.62

Regards
Paul

garrettg.bpd
June 23rd, 2014, 11:27 AM
Im using firmware v2.07.62. The date stamp on CMB.pmm is 6/20/2014 8.57 p.m.

garrettg.bpd
June 23rd, 2014, 11:28 AM
firmware date 6/21/2014

Blacky
June 23rd, 2014, 11:32 AM
Im using firmware v2.07.62. The date stamp on CMB.pmm is 6/20/2014 8.57 p.m.

Not sure how the date/time stamp works when moving files from here (GMT+10 hours) to the US (probably about GMT-10 hours). It could cause the date/time stamp on your file to be 15..20 hours behind the time/stamp on the file I have here. The tell-tale is the minutes are the same at 57 minutes.

Can you please read the CMB.pmm file from your FlashScan using EFILive Explorer and send me that exact file? Send to paul@efilive.com

Regards
Paul

garrettg.bpd
June 23rd, 2014, 11:36 AM
sent

Blacky
June 24th, 2014, 11:20 AM
sent

The CMB.pmm file that you sent me is the correct file. The data logs should be created with PIDs with prefix "CM". I am not sure why that is not the case on your device.
Can you try BB logging again and see what prefix is on the PIDs in the *.efi log file?

Regards
Paul

garrettg.bpd
June 24th, 2014, 12:15 PM
I just tried logging. Tried passthru and bblogging and both went fine. Not sure what the problem was with that first log. I still cant view the log I posted on the forum. But you fixed that file for me. It was the first log I did after the update. maybe the software was a little unstable. I don't thank I restarted my pc after the update. I'll keep an eye on it and see if it happens again.
thanks
17067 17068

Chavez91
June 25th, 2014, 12:04 AM
A good restart after installs always seems to work wonders. :throw:

cindy@efilive
June 25th, 2014, 10:18 AM
Release switched from a pre-release to public release overnight.

http://www.efilive.com/latest/software-release-jun-21-2014/

Cheers
Cindy

Rhino79
June 25th, 2014, 01:15 PM
I received some .ctz files from a customer we sold an autocal to and EFILive wont open them, any idea whats going on there?

Blacky
June 25th, 2014, 01:27 PM
I received some .ctz files from a customer we sold an autocal to and EFILive wont open them, any idea whats going on there?

Its possible that the customer is using updated software and you have not updated your software to match the version your customer is using.

See the message on this page for more info: http://www.efilive.com/latest/software-release-jun-21-2014/

Regards
Paul

Rhino79
June 25th, 2014, 11:20 PM
Thanks Paul, that did the trick!

nate
June 30th, 2014, 10:49 PM
http://i138.photobucket.com/albums/q242/nate698/Mobile%20Uploads/20140701_210901_zpscfuupnph.jpg (http://s138.photobucket.com/user/nate698/media/Mobile%20Uploads/20140701_210901_zpscfuupnph.jpg.html)ey guys bought a new laptop running windows 8.1 and getting this error coming up when installing the new v8 software
any help ?