Installing the V8 Software

[picnic_george]

I've been hearing about how awesome V8 is supposed to be for scanning/tuning and reducing flash times by a lot. This transition has been years now, is it going to be ready or am I doing it wrong and everyone is using it already?

Thanks
Kris

[Blacky]

I've been hearing about how awesome V8 is supposed to be for scanning/tuning and reducing flash times by a lot. This transition has been years now, is it going to be ready or am I doing it wrong and everyone is using it already?

Thanks
Kris

You're not doing anything wrong, it is still in transition.

As of now, the V8 Software can (and should) be used for the following tasks:

• Display/playback log files in the V8 scan tool software.
• Display controller info (for most controllers).
• Read and flash all supported controllers in pass-thru or stand-alone modes.
• Setup FlashScan/AutoCal for black box logging, reading and flashing.
• Managing VIN and stream licenses.
• Various tools such as searching through tune files on your computer for specific data (e.g. VIN, serial numbers, controller type etc).

The main things that V8 does not support yet are:

• Pass-thru data logging.
• Retrieve OBDII DTCs and related data.
• Edit tune files.

Those last three items are being worked on and will become available as they are completed.

Regards
Paul

[cindy@efilive]

For the last few years now, New vehicle support has only been added to V8 for reading and flashing, so V8 is very much an essential and currently used part of our framework. You cannot tune a late model GM vehicle (E78, E39, E92 etc) or a Cummins vehicle without using V8 for reading and flashing.

We made the decision to deliver a quality product V8, and it's fair to say every component released to date is far superior to V7, and in many cases far superior to comparable products available in the market.

Will V8 ever be finished? Well that depends how you define finished. The plan is you will be able to do everything currently available in V7 within V8 and then some, but I doubt it would ever be finished. Technology is moving at a faster pace than ever before, customer requests, comments and needs are constantly changing, so we continue to make adjustments to our products. For ever item ticked off our development list we add about 5 more 'new' items to the list.

Development continues on the tune tool component of V8 to give customers a single piece of software to navigate, but I'd take the compromise of time (and 2 pieces of software) over a substandard product any day.

Cheers
Cindy

[picnic_george]

I mean specifically from what v7 can do now. I read about scanning and tuning without having to disconnect to flash, just using it in general.
What I really want to know is when v7 will be obsolete, that's what I'm looking forward to. I have to use v8 for certain things, and v7 for others and I'd perfer to just use 1. Not too concerned with features will be added in the future as we all know there will more than likely be a bunch. Thanks

[cindy@efilive]

I mean specifically from what v7 can do now. I read about scanning and tuning without having to disconnect to flash, just using it in general.
What I really want to know is when v7 will be obsolete, that's what I'm looking forward to. I have to use v8 for certain things, and v7 for others and I'd perfer to just use 1. Not too concerned with features will be added in the future as we all know there will more than likely be a bunch. Thanks

It's a high priority for us, however we will not put a time frame around V7 replacement.

Cheers
Cindy

[GoneNomad]

Looks like I'm having a similar problem as the OP.

My current Flashscan firmware version is 2.4.70.

I downloaded the "Upgrading FlashScan.pdf" and noted the following instructions...

...about needing to do a multi-step firmware update from a version as old as mine.

But my searches for those older version firmware updates either come up empty, or I find pages like this one (which appears to be too new anyway) that have download links that do not work.

If anybody knows where I can find the older firmware updaters I need, I would appreciate it.

[Blacky]

You need to first update to V2.4.72 using the V7 firmware program:
Start->All Programs EFILive->V7->EFILive Firmware Programmer

Regards
Paul

[GoneNomad]

^ I assume that is accomplished by using the file "FSProg_V2_4_72.ffw" that is included with the V7.5x installer?

What had me confused is these instructions: don't seem to apply (at least I couldn't find the "F6: Device Settings" option in the left-hand pane).

Anyway, from what I see here:


The boot block has to be updated first. The Flashscan must be in the "normal" mode to do this.
Then the firmware has to be updated, and Flashscan has to be in the dead poll mode to do that. But the Boot Block update automatically puts Flashscan in that mode.

One thing though, this says:

FlashScan and AutoCal are designed to be field upgradeable and have been configured with two distinct software modules:
1. The boot block.
2. The firmware.

I only see the one file "FSProg_V2_4_72.ffw" in the V 7.5 folder. (evidently the filename extension changed to ".efw" in the current format)

While this page says "Note: Always update the Bootblock version first"
apparently in the case of the older (legacy) firmware, the upgrade to firmware version V2.04.72 must happen FIRST, as per these instructions.

Sorry if I'm seeming a bit slow on this, but the problem is seeing instructions that conflict, apparently because the legacy stuff is a little different.

[Blacky]

Most instructions (that have been written in the past few years) about the firmware and boot block only applies to devices that are running boot block and firmware versions V2.05.xx or later.
Get your device to firmware V2.04.72, then perform the build in boot block upgrade to V2.05.xx, then you can start using the various instructions that you have listed above.

Regards
Paul

[Blacky]

While this page says "Note: Always update the Bootblock version first"
apparently in the case of the older (legacy) firmware, the upgrade to firmware version V2.04.72 must happen FIRST, as per these instructions.

That should really be more clear and it should say:

If/when you are prompted to update both the firmware and the boot block, update the boot block first.

Regards
Paul