November 22nd 2010 pre-release

[Blacky]

The pre-release software is no longer available. Instead you can download the latest public release here:
http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

Please remember to update the firmware in your FlashScan and your Customers' AutoCal devices to V2.07.03
Important: If your FlashScan/AutoCal device has previously been updated with a previous pre-release firmware V2.07.03, you will need to use EFILive_Explorer to program the updated firmware. The automated firmware update detection will not recognize the new firmware (as an update) because it has the same version number.

The firmware update also requires that you update all script files (*.obj files) that exist on your FlashScan (or your customers' AutoCal) devices. Failure to update the script files will result in error $050B Script file not supported by current firmware version.

The most convenient way to update the script files on your devices is to:


Connect your FlashSCan or AutoCal device to the PC.
Run the EFILive V8 Scan and Tune software.
Select the F5: BBX option.
Click on the [Read] button to read the current setup of the attached device.
Click on the [Program] button which will cause all outdated files to be updated.
It is not necessary to save the BBX Options file after performing the above procedure.


If you receive error $0194, please use the "Format" option on the [Program] button between steps 4 and 5. Error $0194 usually means that the file system is full. Formatting the file system removes all unnecessary data.

This update contains fixes for most of the problems that have been reported in the previous pre-release software and firmware. If you have reported a problem and discover that it has not been fixed in this pre-release, please create a support ticket explaining the problem in detail here: http://support.efilive.com/

Known issues for the current release (these will be addressed in a future update).


P11 (4 Cyl 02-05) controllers are incorrectly auto-identified as P08 (4 Cyl 98-02) controllers.
AL5 pass-thru flashing shows up a small number of retries, AL5 BBF does not.
DMA PID's for the E39/E78 cannot be logged from V7 Scan direct, BBL is the only way to capture DMA PID's.
Full Flash and locking is not yet available for the E39 or E78.

Regards
Paul

[odd boy]

today i have some ls1 cars for tuning, will test it and post u result......

[odd boy]

the old firmware had the same number of the new one. I cheated the system by changing the name to 04 to make the new update.

However, I flashed, reflashed, logged LS1 successfully with no problems. I will get comments if I face any.....

Good luck

[Tordne]

Just an FYI; when we release a updated firmware but don;t increment the firmware version number you just use EFILive Explorer (Firmware tab) to install the newer firmware.

[odd boy]

may be I didn't explain it well....

The release that u made few days ago has the same firmware version number of the new release that u made today.

[Tordne]

Yeah, that's what I'm saying ;). You just use EFILive Explorer to load in the updated (but same version) of the firmware.

[odd boy]

so, it is better if it was included in the mentioned instructions above. Sure for simple people like me :) thanks

[Blacky]

There is a good reason that we don't update the firmware version number in pre-release software. If the newer firmware fails then you can go back to the older firmware because it has the same version number. If we increased the version number and it failed, then you would not be able to go back to the previous working firmware. The only way to tell the difference between all the pre-release firmware versions is by looking at the date. The most current V2.07.03 pre-release firmware should be dated Nov 22, 2010.

But you've got a good point, as part of the pre-release we should explain that you need to use EFILive_Explorer to update the firmware when the version number has not increased.

Regards
Paul

[Chuck CoW]

http://www.stoploubarletta.com/wp-content/uploads/2010/09/Is-Mayor-Lou-Barletta-on-Drugs.jpg

Paul...

So, what you are saying is......YOU'RE ON DRUGS???:fluffy:

Hopefully they inspire some AMAZING new features for EFI LIVE V8!

Get well soon!
Chuck CoW

[L31Sleeper]

There is a good reason that we don't update the firmware version number in pre-release software. If the newer firmware fails then you can go back to the older firmware because it has the same version number. If we increased the version number and it failed, then you would not be able to go back to the previous working firmware. The only way to tell the difference between all the pre-release firmware versions is by looking at the date. The most current V2.07.03 pre-release firmware should be dated Nov 22, 2010.

But you've got a good point, as part of the pre-release we should explain that you need to use EFILive_Explorer to update the firmware when the version number has not increased.

Regards
Paul

So basically you are saying that Odd Boy shot himself in the foot !! by increasing the number?

[odd boy]

So basically you are saying that Odd Boy shot himself in the foot !! by increasing the number?

no brother, even if I request new number it uses the number that is originally assigned by efilive team after completing the update!!!! Beautiful, isn't it???

[Blacky]

So basically you are saying that Odd Boy shot himself in the foot !! by increasing the number?

No not really, what he did will work and obviously did work, quite clever really.
It is just a bit quicker/simpler to use EFLive_Explorer in this particular case.

Regards
Paul

[Suhail]

2006 Commodore

08:29:39.716: Scanning for EFILive FlashScan V2 HAPI
08:29:39.747: Autodetect interface ...
08:29:40.028: Interface firmware version: 2.7.3
08:29:40.043: Connection to [FSV2] interface is OK
08:29:40.293: Interface firmware model: FSV2
08:29:40.324: Interface firmware version: 2.7.3
08:29:40.355: Interface firmware date: Nov 18, 2010
08:29:40.386: FlashScan serial number: 003782291113
08:29:40.418: FlashScan license number: 003782291113
08:29:40.464: Disconnecting ...
08:29:41.088: CAN-VPW Bridge Deactivated
08:29:41.104: Disconnected
08:29:41.806: Scanning for EFILive FlashScan V2 HAPI
08:29:41.837: Autodetect interface ...
08:29:42.134: Interface firmware version: 2.7.3
08:29:42.165: Connection to [FSV2] interface is OK
08:29:42.212: CAN-VPW Bridge Activated
08:29:42.290: Current protocol set to: "SAE J1850 VPW"
08:29:42.321: Autodetect PCM...
08:29:42.586: Connection to PCM is OK
08:29:42.617: Autodetect TCM...

[ScarabEpic22]

Um, Suhail what are you trying to show here? You need to manually update your firmware still, you have the November 18th version loaded now not the November 22nd.

[Tordne]

No not really, what he did will work and obviously did work, quite clever really.
It is just a bit quicker/simpler to use EFLive_Explorer in this particular case.


He saw me do that when I was trying to downgrade his firmware originally to 2.07.01 :). I didn't think it worked in Hapi though as the internal version is still the same. Might try that later myself...

[Blacky]

He saw me do that when I was trying to downgrade his firmware originally to 2.07.01 :). I didn't think it worked in Hapi though as the internal version is still the same. Might try that later myself...
It won't work for downgrading...
Regards
Paul

[odd boy]

He saw me do that when I was trying to downgrade his firmware originally to 2.07.01 :). I didn't think it worked in Hapi though as the internal version is still the same. Might try that later myself...

Touch the wood, u still remember.....

You offered me a good help on that day, I am a good student "never forget" from the first seen.........

Thanks again




2006 Commodore

08:29:39.716: Scanning for EFILive FlashScan V2 HAPI
08:29:39.747: Autodetect interface ...
08:29:40.028: Interface firmware version: 2.7.3
08:29:40.043: Connection to [FSV2] interface is OK
08:29:40.293: Interface firmware model: FSV2
08:29:40.324: Interface firmware version: 2.7.3
08:29:40.355: Interface firmware date: Nov 18, 2010
08:29:40.386: FlashScan serial number: 003782291113
08:29:40.418: FlashScan license number: 003782291113
08:29:40.464: Disconnecting ...
08:29:41.088: CAN-VPW Bridge Deactivated
08:29:41.104: Disconnected
08:29:41.806: Scanning for EFILive FlashScan V2 HAPI
08:29:41.837: Autodetect interface ...
08:29:42.134: Interface firmware version: 2.7.3
08:29:42.165: Connection to [FSV2] interface is OK
08:29:42.212: CAN-VPW Bridge Activated
08:29:42.290: Current protocol set to: "SAE J1850 VPW"
08:29:42.321: Autodetect PCM...
08:29:42.586: Connection to PCM is OK
08:29:42.617: Autodetect TCM...

Suhail,

Call me this afternoon to upgrade the firmware if you still have the issue

[Wasted Income]

Pass-thru reading would NOT work on an LBZ that I attempted to read this afternoon. However, it worked fine on my LS1.

[Wasted Income]

Is it because I was trying to use 7.5 to read the ECM? Do I need to use V8 or scan and tune or what? Need to make a few tweaks to a buddys LBZ that I previously tuned and I am not currently able to. Thanks.

[odd boy]

did apply the latest firmware update?

[Wasted Income]

Yes sir.

[odd boy]

Try to read with V8....

[ScarabEpic22]

Having severe issues flashing P10s, with V7.5, V8, and BBF. Updated everything to the latest and greatest (2.07.03 Nov. 22, 2010 fw and 2.07.01 BB), formatted config and SD card. Getting "error $0502 Script not found" when trying to BBF, Ive checked and rechecked and I have all 5 P10 related files (P10.pmm, both read files and both write files). V8 S&T Pass-thru doesnt work, it properly recognizes the controller when I load a file as the P10 but just sits at 0:00 when trying to flash and doesnt give any error messages until I manually abort. Nothing about the PCM missing a calibration (which it is currently).

Flashing aborts at 19kb data transfer every time, it went through properly the first time (V7.5) then on subsequent flashes with V8 and BBF it failed. To try and recover the PCM I used V7.5 which failed every time. I saved a few trace files on my V2, Ill upload them in the morning, and I can upload the error files from V7.5 then as well.

Am I missing anything? This could or could not be the first issue with this release/firmware, I havent flashed my P10 since June or July so there have definitely been a few updates since then.

[Blacky]

I just tested reading and flashing a P10 on the bench here and it worked fine on V7.5 pass-thru and V8 BBR/BBF.
I also tried killing the flash and recovering from the failed flash, which also worked fine.

Have you tried flashing the controller using a bench harness?

Regards
Paul

[ScarabEpic22]

I havent, unfortunately I dont have access to a bench harness. What's so weird is it worked just fine the first time with the new fw and freshly formatted V2, but when I tried to flash with V8 it failed. Ive always been able to recover P10s, not worried about that, problem is I was trying to load an 87 octane tune so my parents could sell the truck right before I drove 300 miles back to school and had to leave them with a dead truck in the garage. Ill be able to try again either thursday night or friday when I head back there.

Ive attached the .blx files from a successful flash (20101128_145513_download.blx) and then the subsequent failures. Also attached is the BBF .exf error from my V2. If you need the tune as well let me know (I tried the stock tune, the previous tune, and the tune I was trying to flash) or any other .blx files, there are about 30 of them from yesterday! :shock:

P.S. If we could upload *.blx and *.efx files that would be great, right now you have to zip them!

[Blacky]

The software has been officially/publicly released on EFILive's web site here:
http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

If you want to log any issues with the latest software, please create a ticket here:
http://support.efilive.com/

Regards
Paul