PDA

View Full Version : Update: May 15, 2013



Blacky
May 14th, 2013, 02:48 PM
EFILive encourages customers to use this public update in their production environments.

Important:

This latest software update requires updated USB drivers (V2.08.28). You cannot use this version of the software with older versions of the USB drivers.
If you are having difficulty connecting to FlashScan/AutoCal after installing this update, DO NOT DOWNGRADE THE USB DRIVERS. The problem is possibly a USB 2.0/3.0 incompatibility.
Try using FlashScan/AutoCal in a USB 2.0 port instead of a USB 3.0 port.


Download here:

http://download.efilive.com/Software/V7.5/EFILiveV7.5.7.231_Setup.exe
http://download.efilive.com/Software/V8/EFILiveV8.2.2.225_Setup.exe


Updates:

V7



[*=1]Automatically generate \My Documents\EFILive\V7.5 folder hierarchy if it does not exist at application start-up.
[*=1]*.cax files may not contain any user defined calibrations that overlap existing EFILive calibration definitions or that reference data outside of the calibration memory area. If they do, the user will be notified that the *.cax calibration will be ignored.
[*=1]*.ctz files with V8 security restrictions (cal-only, flash-only) can no longer be loaded into the V7 software.



V8



[*=1]LML cal-flash and full-flash is now available.
[*=1]Automatically generate \My Documents\EFILive\V8 folder hierarchy if it does not exist at application start-up.
[*=1]Stopped PID selection lists from auto-expanding/collapsing when selecting PIDs in Scan Tool and BBX tab pages.
[*=1]Auto-Locked E38 controllers can now be auto-unlocked successfully.
[*=1]Explorer was asking for overwrite permission twice when copying files, now it only asks once.
[*=1]Explorer now refreshes top pane correctly when dragging/dropping files from device to PC.
[*=1]When reporting OS mismatch, error message now shows "Unknown" (instead of -1 or $FFFFFFFF) for operating system number



Firmware



[*=1]Fixed AutoCal LCD screen display corruption.
[*=1]Fixed "Record All Diags" option to include freeze frames and System Readiness Tests.
[*=1]Increased pre-defined calculated PIDs per BBL PID selection from 8 to 32.
[*=1]Updated USB drivers to V2.08.28.



Drivers


[*=1]List of updates since V2.08.14 available here: http://www.ftdichip.com/Drivers/CDM/CDM%202%2008%2028%20Release%20Info.rtf


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.




[*=1]FlashScan and AutoCal Version numbers and version dates do not display in the EFILive Control Panel (aka EFILive_HAPI) application on the [F6: Firmware] tab page (fixed in next update).
[*=1]PID custom units are not being loaded correctly when opening a BBX configuration file (fixed in next update).
[*=1]Copy/Paste of BBX PIDs does not copy the custom units or alarm settings (fixed in next update).
[*=1]BBX PID display order is not being maintained (fixed in next update).
[*=1]Connecting FlashScan or AutoCal to USB3.0 ports may cause very slow connections or no connection at all - try using a USB 2.0 port instead (under investigation).
[*=1]Clicking [Display Image] in EFILive Explorer on the [F11: Splash] tab page causes a "$0101: No data received" error after 5 seconds (fixed in next update).
[*=1]LS1A and LS1B controllers report as "Locked with a custom key" when attempting to read or flash using V7.5. Use V8 to read/flash LS1A and LS1B controllers (fixed in next update).
[*=1]BBx option "Record All Diags" does not save freeze frame data (fixed in next update).
[*=1]BBx option "Record All Diags" does not show monitor supported status (fixed in next update).


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 231
To view the installed version, select Help->About (in the V7 Scan or Tune software).

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

Boot Block: V2.07.04 (Dec 12, 2011)
To view the installed version, Select F7: Licenses (in the V8 Scan and Tune software).

Firmware: V2.07.40 (May 10, 2013)
To view the installed version, Select F7: Licenses (in the V8 Scan and Tune software)

T2000
May 14th, 2013, 04:21 PM
[*=1]Increased pre-defined calculated PIDs per BBL PID selection from 8 to 32.

[INDENT]


NICE!
Thanks so much for checking this out and better still adding even more :cucumber:

Cheers, Chris

IJ.
May 14th, 2013, 04:23 PM
Thanks Paul!

IJ.
May 14th, 2013, 06:00 PM
Ok thought I'd jumped the gun a bit after reading the description that the added slots were in Firmware.. Have updated my V2 and am still not seeing the new PID slots..

Is there a step I've missed? (newbie to this software/hardware so have made lots of mistakes)

T2000
May 14th, 2013, 06:15 PM
Same scenario as Ian. All upgraded and still only 8 slots in S&T bbl V7 settings

IJ.
May 14th, 2013, 06:17 PM
Calc Pids file edit to use these maybe?

Blacky
May 14th, 2013, 08:45 PM
Ok thought I'd jumped the gun a bit after reading the description that the added slots were in Firmware.. Have updated my V2 and am still not seeing the new PID slots..

Is there a step I've missed? (newbie to this software/hardware so have made lots of mistakes)

It just means you can still only define up to 8 calc PIDs in the V7 compatibility window but another 24 calc PIDs in the normal V8 PID selection (which can also have the same name as existing V7 calc PIDs).

Regards
Paul

T2000
May 14th, 2013, 11:10 PM
It just means you can still only define up to 8 calc PIDs in the V7 compatibility window but another 24 calc PIDs in the normal V8 PID selection (which can also have the same name as existing V7 calc PIDs).

Regards
Paul

okay IJ, maybe not such a big problem,
we'll have a look at your sae_generic.txt file and make some edits there to make use of the new capacity.
we will just need to be very careful when you change versions ;)

joecar
May 15th, 2013, 04:09 AM
Thanks.

ScarabEpic22
May 15th, 2013, 05:57 AM
I updated V7.5 and V8 then plugged my V2 in, (new) drivers installed just fine. Opened V8, and get a cannot connect error. Used the USB Manager and uninstalled, rebooted, then reinstalled the latest drivers. No luck. Plugged my V2 into another USB port on my laptop, and all is fine. I have never had this issue with any previous drivers, I will try going back to the old ones later on today after I get some tuning done.

The problem ports/controller are my USB3 ports and the older USB2 ports work fine. If you need any USB controller specs, please let me know. I will report back later tonight if using the old drivers makes the USB3 ports work again (they're the ones Ive always used for tuning in the past).

Also, after updating my firmware to the latest .40, I clicked the Refresh button and fields stayed blank. I have a pin on my V2 so the first time after a firmware update I have to enter my pin and click Refresh to get the status update, but Ive never seen this happen before. I shut V8 down completely and re-opened it, still nothing appeared in the fields (but the FlashScan V2 line item updated correctly).

If it helps, I simply installed these versions over the top of my existing Public Release 4/23 versions.

15060

GMPX
May 15th, 2013, 09:08 AM
The problem ports/controller are my USB3 ports and the older USB2 ports work fine.
I've noticed that USB3 ports are a pain, I have a few on my PC and I find it can take 20 seconds before it recognises a device has been plugged in, yet other true USB3 devices connect instantly. I just avoid using them if I have a USB2 device.


Also, after updating my firmware to the latest .40, I clicked the Refresh button and fields stayed blank.
I found that yesterday as well and let Paul know.

joecar
May 15th, 2013, 10:35 AM
Comments:


EE: Splash: Display Image

when it finished displaying the image, this box pops up:



---------------------------
EFILive Explorer
---------------------------
Error: $0101: No data received.
---------------------------
OK
---------------------------



S&T: BBx: Read

Custom Units field goes blank for undefined units text (e.g. LAM).

joecar
May 15th, 2013, 10:55 AM
Also, in BBx, the pids do not stay in the order that I placed them, after you save to file newly added pids seem to fall to the bottom of each list.

joecar
May 15th, 2013, 10:57 AM
Also (this was ongoing) when you copy/paste pids in V8, the custom units/alarms don't get copied.

Blacky
May 15th, 2013, 11:16 AM
Thanks for the testing Joe, I can reproduce all of those issues. I'll list them in the known issues and get them fixed for the next update.

Regards
Paul

DURAtotheMAX
May 15th, 2013, 11:22 AM
Paul does this release have the EGR/DPF restrictions for the US diesel customers?

Blacky
May 15th, 2013, 11:31 AM
Paul does this release have the EGR/DPF restrictions for the US diesel customers?

No. When we release the version with that functionality removed it will be clearly announced so that there is no confusion.
Right now we're still cleaning up the last few bugs from the last major pubic release, there will probably be 1 or 2 more minor updates before we get stuck into the next major release (i.e. the one with the DPF/EGR removed)

Regards
Paul

Blacky
May 15th, 2013, 05:53 PM
Also, in BBx, the pids do not stay in the order that I placed them, after you save to file newly added pids seem to fall to the bottom of each list.

The PIDs of the first controller listed in the list of "BBL Enabled Controllers" will be sorted correctly. You can re-order them and add/remove PIDs and the order is retained.
The PIDs of all other controllers will lose their sorted status.

Guess which one I tested :(

Regards
Paul

vortecfcar
May 16th, 2013, 04:23 AM
Just had two of my staff update their computers to the newest version. They also updated their drivers to 2.08.28 and verified via the control panel. Neither computer will recognize EFILive hardware in any USB port. Both computers are new and equipped with USB 3.0.

I strongly recommend not upgrading if you're in a production environment and have USB 3.0.

We're uninstalling now and reinstalling the previous builds.

Nick

ScarabEpic22
May 16th, 2013, 06:50 AM
Please delete...

joecar
May 16th, 2013, 07:49 AM
From post #1:



Important:

This latest software update requires updated USB drivers (V2.08.28). You cannot use this version of the software with older versions of the USB drivers.
If you are having difficulty connecting to FlashScan/AutoCal after installing this update, DO NOT DOWNGRADE THE USB DRIVERS. The problem is possibly a USB 2.0/3.0 incompatibility.
Try using FlashScan/AutoCal in a USB 2.0 port instead of a USB 3.0 port.

GMPX
May 16th, 2013, 08:46 AM
I strongly recommend not upgrading if you're in a production environment and have USB 3.0.
Nick, what I have found with the USB3.0 ports on my PC (and this was before the update so I don't think it is the latest FTDI drivers) is the V2 wouldn't be recognised for at least 20 to 30 seconds when plugged in, it was the oddest thing, after it finally woke up everything was fine. This also happened on a number of USB memory sticks too, it wasn't just the V2.

ScarabEpic22
May 16th, 2013, 08:47 AM
From post #1:




:shock::doh2:

Going to edit my previous post, I was going to try downgrading my drivers today but guess I wont do that just yet.

vortecfcar
May 16th, 2013, 09:17 AM
From post #1:




Joe, if you read my post you'll see that we did update the drivers and still are unable to connect on any of the USB ports.


Nick, what I have found with the USB3.0 ports on my PC (and this was before the update so I don't think it is the latest FTDI drivers) is the V2 wouldn't be recognised for at least 20 to 30 seconds when plugged in, it was the oddest thing, after it finally woke up everything was fine. This also happened on a number of USB memory sticks too, it wasn't just the V2.

Maybe it's just our computers, or we're idiots, but we sat there and waited until it said drivers loaded successfully and still received error messages indicating inability to connect.

Nick

joecar
May 16th, 2013, 10:34 AM
Joe, if you read my post you'll see that we did update the drivers and still are unable to connect on any of the USB ports.
...Oh, I was just alerting that the old driver cannot be used.

joecar
May 16th, 2013, 10:37 AM
Paul,

Here are some minor things I saw:


in the BBx Search bar, the Channels box is truncated:

15062


in HAPI the firmware/bootblock fields are blank (not sure if they're supposed to be):

15063

GMPX
May 16th, 2013, 10:44 AM
Maybe it's just our computers, or we're idiots, but we sat there and waited until it said drivers loaded successfully and still received error messages indicating inability to connect.
Don't be so hard on yourself Nick :)
The point I was trying to make was I don't think that USB3.0 ports behave exactly like USB2.0 ports. I avoid using USB2.0 devices on my USB3.0 ports, it's almost like a USB3.0 port tries to behave like a 3.0 port by default (which makes sense) and when it finally figures out it's got a 2.0 device connected it drops down to 2.0 spec, but that doesn't happen instantly.

Unfortunately for us we are a little bit at the mercy of FTDI's USB drivers, we assume they have thoroughly tested them on USB3.0 ports.

I know earlier this week I had some major issues with USB communications when I was testing some of Paul's updates until I was able to install the latest release with matching drivers, I wonder if there is some installer issues with some computers.

Blacky
May 16th, 2013, 11:31 AM
in the BBx Search bar, the Channels box is truncated:
What settings do you have for font DPI?
15064


in HAPI the firmware/bootblock fields are blank (not sure if they're supposed to be):

Its a bug, fixed in the next update.

Regards
Paul

Blacky
May 16th, 2013, 11:32 AM
Unfortunately for us we are a little bit at the mercy of FTDI's USB drivers, we assume they have thoroughly tested them on USB3.0 ports.

I have logged a support call with FTDI, but still no response yet...

Regards
Paul

joecar
May 16th, 2013, 02:07 PM
What settings do you have for font DPI?

1440 x 900 @ 96 DPI

15065

My screen is odd sized due to my laptop being a MacBook.

joecar
May 16th, 2013, 02:24 PM
Also: V2 BBx mode, when you read all diagnostics to file, the freeze frames are not included...

see attached.


Question: do readiness monitors have the ability of indicating "not supported"...?

joecar
May 17th, 2013, 08:15 AM
Also: V2 BBx mode, when you read all diagnostics to file, the freeze frames are not included...

see attached.


Question: do readiness monitors have the ability of indicating "not supported"...?

For example, here's a read all diagnostics from a year ago:



[PCM INFO]
. . .

[System Readiness Tests]
MIL=OFF
DTC_CNT=0
MIS=Ready
FUEL=Ready
CCM=Ready
CAT=Ready
HCAT= N/A
EVAP=Ready
AIR=Pending
ACRF= N/A
O2S=Ready
HTR=Ready
EGR= N/A

. . .


i.e. the readiness monitors should have 3 states: ready, pending, n/a.

Blacky
May 17th, 2013, 01:29 PM
Also: V2 BBx mode, when you read all diagnostics to file, the freeze frames are not included...

see attached.

Question: do readiness monitors have the ability of indicating "not supported"...?
Yes, it should display Supported/not supported.
And FF are being re-activated in the next update.

Regards
Paul

SkinnyPedal
May 18th, 2013, 04:03 PM
Were B2307 and B2308 removed from this version? They are on the LS1B pcms.

catman3126
May 19th, 2013, 06:10 AM
15079

This is all I get when i try to connect with my scanner or V7 tune tool. i used V8 to DL a LBZ tune this morning and that worked fine. But I have done the latest update and made sure the firmware is updated and nothing is working right. I guess from now on I will not be updating my V2 anymore once I get this working again. i have spent the last 3 hours reading and updating and trying different USP drivers to try to get this to work. and it seems to be that everytime I update my V2 this happens. very frustrated with all of this and I have a couple duramaxs to tune this week and would really like to be able to use the scan tool. Any ideas?????

catman3126
May 19th, 2013, 06:30 AM
Ok so once again i had to use the "OLD" drivers to get this to work even though in the USB drivers post we were told to NOT go back to the old ones. so just to see if it would work i ran as admin the usb drivers manager and did the old ones and it works fine now......

draftee
May 20th, 2013, 06:14 AM
Problem 1: Cannot connect - shows error $0001: Device not connected.
Problem 2: I do not have the password for administrator, so I cannot run the USB Manager as admin...
Suggestions PLEASE!

Blacky
May 20th, 2013, 07:27 AM
Problem 1: Cannot connect - shows error $0001: Device not connected.
Problem 2: I do not have the password for administrator, so I cannot run the USB Manager as admin...
Suggestions PLEASE!

Check that your FlashScan/AutoCal is connected to a USB 2.0 connector. Currently USB 3.0 connectors do not recognize FlashScan/AutoCal devices.
USB 3.0 connectors can usually be identified by their blue color.

If you don't have the admin password how did you install the latest software? You must have the admin password to perform the install correctly.

Regards
Paul

draftee
May 20th, 2013, 09:56 AM
We definitely have USB 2 connectors.

As far as an admin password, do you mean an EFI Live admin password, or do you mean the computer's administrator account?

I guess I was able to install the software because my account on this computer has admin rights. The administrator account on this computer has no password set and I am concerned about the warnings of data loss if I set a password.

I would really appreciate your advice.

Blacky
May 20th, 2013, 10:19 AM
Does the FlashScan screen show a menu or is it blank when it is connected via USB to the PC?
If it is blank then the drivers are not installed correctly.

Check that the drivers have been installed correctly by right clicking on Start->Computer and selecting "Properties".
Select "Device Manager" and expand the "Universal Serial Bus Controllers" item.
Locate the FlashScan item and right click it and select "Properties", then select the [Driver] tab page and check that the version is V2.08.28

15089

If the drivers are not correct, use the EFILive USB Manager program to install the latest drivers. You can run the latest version without using the "Run as Administrator" option. The latest version automatically checks to see if you have admin privileges and uses them if you have.

Once the drivers are correct, check connectivity by running the program: Start->All Programs->EFILive->V8->EFILive Control Panel.
A small FlashScan icon will appear in the System Tray at the end of the Windows Task Bar near the clock.
Click on that icon to open the EFILive Control Panel.

Click the [Status] button to see if the control panel can communicate with FlashScan. It should look something like this. You should have at least 2 green ticks.

15090

Regards
Paul

Blacky
May 20th, 2013, 11:57 AM
New update is available here:
http://forum.efilive.com/showthread.php?22635-Update-May-20-2013&p=191606#post191606

draftee
May 21st, 2013, 06:54 AM
-FlashScan screen shows a menu.
-Device Manager shows Driver date of 1/18/2013, Driver version of 2.8.28.0
-Status is not showing green ticks, and when I look at Firmware under the EFILive Control Panel, it is still showing "Not connected"
Once again, I really appreciate your help.

draftee
May 22nd, 2013, 12:54 AM
OK, here's the latest on my end: I set an administrator password, rebooted, and attempted to load the driver again. I am still getting the same errors: Status is not showing green ticks, and when I look at Firmware under the EFILive Control Panel, it is still showing "Not connected". Please advise.

joecar
May 22nd, 2013, 06:01 AM
OK, here's the latest on my end: I set an administrator password, rebooted, and attempted to load the driver again. I am still getting the same errors: Status is not showing green ticks, and when I look at Firmware under the EFILive Control Panel, it is still showing "Not connected". Please advise.Run the EFILive software as Admin...

i.e. rightclick on the executable and do Run As or Run As User and tell it Admin.