Release Candidate 1, Aug 04, 2011

[Blacky]

Release Candidate 2 of the EFILive V7.5 and V8 software is available for download.
http://forum.efilive.com/showthread.php?17096-Release-Candidate-2-Aug-19-2011&p=153132#post153132

[Duramax 6.6L]

Down loaded and installed, Trying to scan a vehicle right now

[Ninety8C5]

Included in V8 was FW V2.07.19. There is no mention of it in post 1. Should we update firmware ?

Thanks.

[Duramax 6.6L]

I updated to the latest firmware

[Blacky]

Included in V8 was FW V2.07.19. There is no mention of it in post 1. Should we update firmware ?

Thanks.

Yes, you'll need to update the firmware so that it remains compatible with the V7.5 software.
When the build number of the V7 software increments, the firmware gets updated so that it "knows" it is compatible with that latest V7 build.
That in turn triggers an update to the firmware build number.

Regards
Paul

[540diesel]

I have updated to this latest software. Over the weekend I tried to perform a full flash on a LMM ecm with V8 and ended up with the $0322 error about 3/4 through the program. I was then able to perform the full flash using V7 with no problem. I just thought I would let you know. I did take a screen print of the error on the screen if you need it.

If you need more info let me know and I will try to get it for you,

[Blacky]

I have updated to this latest software. Over the weekend I tried to perform a full flash on a LMM ecm with V8 and ended up with the $0322 error about 3/4 through the program. I was then able to perform the full flash using V7 with no problem. I just thought I would let you know. I did take a screen print of the error on the screen if you need it.

If you need more info let me know and I will try to get it for you,
The V8 software saves a trace file of the reflash and stores it in the folder: \My Documents\EFILive\V8\Trace
The file will be called E35B_F_YYYYMMDD_HHMMSS.htx
where YYYYMMDD is the date and HHMMSS is the time that the full-flash failed.

Can you please locate that trace file and email it to me at paul@efilive.com

Regards
Paul

[AFTERMATH DIESEL]

On two lmm trucks today I have had to relicense atleast three or four times. When I go back and check my licenses it doesn't use another one. Not sure why but I had this problem on an Lly about a month ago and since then it's never happened. I always end up un plugging the v2 from the computer, and I've had to restart the computer a few times to get v7 and or scan tool also to close after the screen freezes.Sorry for the vague report it's been a long day and I'm on my phone.
If there's anything I can do let me know.
Thank you
Chris

[540diesel]

Paul,

I did not get time to email you that trace file last yesterday. I will try to get it to you today.

Bryon

[minytrker]

Issue #1
Sometimes at the start of a read or flash operation the V7.5 software will complain that it cannot communicate with the FlashScan device. Sometimes after clicking [Ok] the software is able to reconnect. Sometimes you need to restart the read or flash procedure and other times you need to exit and restart the Tuning Tool application.
We are trying to find a set of actions that can reliably reproduce that situation.

I tuned a 2000 F-body today and had to restart the flash procedure a couple times. I then tuned a 2008 5.3 silverado and it took me 10mins of restarting and re-booting the V2 just to get the scan tool to connect. I also couldnt flash it with 7.5 and had to flash it with V8.
I have several LS1 and E38 vehicles I can try it on if there is anything I can do to help.

[MikeyC]

I just tried to Copy and Paste Calc.VET PIDs from V7 to V8 and nothing happened... Am I doing something wrong?

[Blacky]

I just tried to Copy and Paste Calc.VET PIDs from V7 to V8 and nothing happened... Am I doing something wrong?

Calc PIDs are not supported directly in V8 therefor they are not supported during copy/paste operations.

To specify calc PIDs in V8 click on the [V7] button in the BBX setup window and enter the calculated PIDs that you want active when you view the data in the V7 Scan Tool software.

Regards
Paul

[MikeyC]

Thanks Blacky, I'll give that a try.

[jennett_c]

Hey guys i apologize if this has been discussed recently in another thread but has there been any progress to support flashing a a50 tcm? thanks

[GMPX]

Jennett_c, I was hoping to get that in this release but once again that wretched TCM is causing me grief, I had to put it aside so we could try to finalise these releases.

[jennett_c]

ok no problem. just checking haha

[Blacky]

A series of flash failures with the latest release candidate software has been identified. The following issue has been added to post #1.


Issue #3
Flashing some VPW based controllers may fail.
Full Flashing an E35 (LBZ/LMM) will fail with $0322 at about 80% completion.
Flashing an E60 (LLY) will fail.
Please use the V7 software to flash the above vehicles.


Regards
Paul

[minytrker]

Just did update and now I CAN'T connect to E38 with scan tool. I tried two different vehicles one of which I own and mess with all the time so I know its not the vehicle. I can BBL but no matter what I do the scan tool will not connect. I tried different cables with no luck. I can connect and data log with auto cal or a V2 but can not connect through the scan tool. I can read and flash the ECM with my laptop through V8.

EDIT: I went back to the last build for V7 and V8 and it works...I tried the latest updates twice and both times I couldnt connect the scan tool to E38 vehicles.

[Chalky]

It might just be me but the latest release has crashed my system twice now. System in 64 bit WIN 7 Toshiba. Both crashes occurred when reviewing scantool data.. Once with TuneTool open as well. My screen slows and I lose mouse function. I had to do restore to regain system function and reinstalled mouse drivers to get system back. Also had to install a usb mouse to get system working.

By chance, it is possible to download the July 18th releases of 7.5 and V8?

[mr.prick]

Just did update and now I CAN'T connect to E38 with scan tool. I tried two different vehicles one of which I own and mess with all the time so I know its not the vehicle. I can BBL but no matter what I do the scan tool will not connect. I tried different cables with no luck. I can connect and data log with auto cal or a V2 but can not connect through the scan tool. I can read and flash the ECM with my laptop through V8.

EDIT: I went back to the last build for V7 and V8 and it works...I tried the latest updates twice and both times I couldnt connect the scan tool to E38 vehicles.

I too have found passthru fails to log E38 but BBL works.
Build 176

[Blacky]

It might just be me but the latest release has crashed my system twice now. System in 64 bit WIN 7 Toshiba. Both crashes occurred when reviewing scantool data.. Once with TuneTool open as well. My screen slows and I lose mouse function. I had to do restore to regain system function and reinstalled mouse drivers to get system back. Also had to install a usb mouse to get system working.

By chance, it is possible to download the July 18th releases of 7.5 and V8?

The previous releases are still available here:
http://forum.efilive.com/showthread.php?16919-Pre-Release-Update-July-29-2011

Regards
Paul

[Chalky]

Forgot, have latest firmware. No going back I guess.

[Duramax 6.6L]

My system is is also crashing, Had to reintall a disk image to fix. Will wait for next release to try again as I also updated the firmware.

I know there is a way to go backward, but not sure how to do it.

[Duramax 6.6L]

Blacky could you post how to revert to an older firmware version?

[minytrker]

Going back to the previous release I now had PID's that don't work. I still have problems with connecting, it took me 45 mins just to download a tune and to get the scan tool working.

How do I go back to the last firmware and bootloader? It won't you do it by the normal update methods.

I lost almost a $1,000 dollars today and had to customers drive over 2 hours each and I couldn't tune there vehicles. I need to go back to the last version really bad.

[Blacky]

The attached firmware should work with build V8.2.1.166-167 and V7.5.7.176-177.

Regards
Paul

[Chalky]

The attached firmware should work with build V8.2.1.166-167 and V7.5.7.176-177.

Regards
Paul

Thank you! :)

[Duramax 6.6L]

The attached firmware should work with build V8.2.1.166-167 and V7.5.7.176-177.

Regards
Paul

Thank you for the quick reply

[minytrker]

The attached firmware should work with build V8.2.1.166-167 and V7.5.7.176-177.

Regards
Paul

How do I go back to the firmware before 166 and 176.......ALL my problems started when I went to the new firmware and to build 166 and 176. I can't afford for it not to work, so I know my V2 works with the previous build and firmware. Insn't there a manual way to override and flash the firmware back to an older version?

[Duramax 6.6L]

I lost almost a $1,000 dollars today and had to customers drive over 2 hours each and I couldn't tune there vehicles. I need to go back to the last version really bad.

I have the same problem as you, at least you only lost money, I lost two LBZ computers I had to replace and program back to stock tunes with Tech II, I can not communicate with the ecm any more.

[Duramax 6.6L]

How do I go back to the firmware before 166 and 176.......ALL my problems started when I went to the new firmware and to build 166 and 176. I can't afford for it not to work, so I know my V2 works with the previous build and firmware. Insn't there a manual way to override and flash the firmware back to an older version?

I also would like to know how to go back to V7.5.7.170 and V8.2.1.160 from July 3, 2011. Could you let us know how to go back to these versions.

[Chalky]

Added revised firmware last night. Did logging and updated tune in E38 today and no issues to report.

[joecar]

I went with my wife to Palm Springs for a week or two and I missed all the fun :doh2:

[Chalky]

Post count seemed kind of stable. :)

[Ninety8C5]

The attached firmware should work with build V8.2.1.166-167 and V7.5.7.176-177.

Regards
Paul

Will this firmware fix the problems with Release 166 & 176 or should we use it with the July 29th release 165 & 175?

Thanks.

[swingtan]

Just a quick note on one small issue.

It seems that for some time now, if you name a tune file with multiple "_" characters, the auto numbering feature breaks. I'm guessing that the code looks for a numeric string after the first "_" and if it's a non numeric, the code gives up.

That's about it for me. Everything else has been working fine. Keep up the good work guys.

Simon

[etmotorsports]

Swing


It seems that for some time now, if you name a tune file with multiple "_" characters, the auto numbering feature breaks. I'm guessing that the code looks for a numeric string after the first "_" and if it's a non numeric, the code gives up.


with that said should you always let the auto number string at the end stay?

[swingtan]

If you want auto numbering to work, you must have the _NNNN syntax at the end of the file name ( but before the file extension ), so it needs to be...

My-tune_0000.tun or My-tune_0000.ctd

What I found was that if I called the file "My_tune_0000.tun" then the auto incrementing numbering stopped working. Changing the first "_" to "-" restored the function.

Simon

[nevinsb]

I just use spaces, guess I never noticed.

[swingtan]

I never use spaces! I hate spaces in file names...... ( pick the Unix admin...... )

[etmotorsports]

I must be blind or just not thinking clearly this morning where do you find the build 166 and 176 versions i cannot i found the firmware file but that is all?

[joecar]

Post #1 sends you back to 165/175 since there was a problem with 166/176.

see 3rd paragraph of post #1 of this thread.

[etmotorsports]

Ok so use the firmware for 166/176 but the builds 165 and 175 that is how i read that paragraph is that correct.

[joecar]

David,

If you installed builds 167/176, the see post #26 for the firmware to use: Release-Candidate-1-Aug-04-2011 post #26 (http://forum.efilive.com/showthread.php?16989-Release-Candidate-1-Aug-04-2011&p=152591&viewfull=1#post152591)

[etmotorsports]

No i loaded the firmware for 166 and 176 but couldn't find the software for 166 and 176 i am using the firmware posted on 26 but the software is gone. No my 7.5 will not work at all reading the car scan or tune but the 8.2 will load a tune but i still have the same issues.

[joecar]

Ok, with the firmware from post #26 use software 165/175 from here:

Post #1 sends you back to 165/175 since there was a problem with 166/176.

see 3rd paragraph of post #1 of this thread.

[etmotorsports]

Ok that is what i am doing 7.5 will not read or flash no will the 7.5 scan tool work. Or is it just mine?

[cme265]

no, not just you, reverted to build 175, did firmware from post 26, now efi live not campatible with flashscan firmware

[Blacky]

no, not just you, reverted to build 175, did firmware from post 26, now efi live not campatible with flashscan firmware
When you installed build 175, make sure that build 175 is actually installed. i.e. check the Help->About window.
Sometimes the Windows installer will not overwrite a newer version of the software with an older version.
You may need to uninstall 176, then re-install 175.

Note: Release Candidate 2 is scheduled for release in about 3-4 hours. It fixes all of the outstanding problems in RC1.
I recommend waiting for RC2 and upgrading to that.

Regards
Paul

[Tre-Cool]

and you were expecting to knock off early for a few beers....

[Blacky]

and you were expecting to knock off early for a few beers....
Time for that now... :cheers:

[Blacky]

Release Candidate 2 is now available.
See first post.
http://forum.efilive.com/showthread.php?16989-Release-Candidate-2-Aug-19-2011&p=151932#post151932

Regards
Paul

[swingtan]

Thanks Blacky! You had me very confused for a bit there. I was trying to work out how "RC 2, Aug 19 2011" got to 6 pages long so fast......

[Blacky]

Thanks Blacky! You had me very confused for a bit there. I was trying to work out how "RC 2, Aug 19 2011" got to 6 pages long so fast......

Hmm, yes its a bit confusing with all the RC1 comments.
I've created a new thread for RC2 here:
http://forum.efilive.com/showthread.php?17096-Release-Candidate-2-Aug-19-2011&p=153132#post153132

Regards
Paul

[cmkelly01]

Sorry if this is a repeat - I put it in another thread that was probably not the right one.

FYI – I just updated my V8.2.1 to Build 170. When I downloaded Build 170 and installed it, and then opened S&T, it indicated that it was indeed Build 170. However, when I went to V8>Tools>Check for Updates, and had it download and install the updates, re-opening S&T indicated that it was now Build 160. Maybe a minor issue, maybe not.

[Ninety8C5]

Sorry if this is a repeat - I put it in another thread that was probably not the right one.

FYI – I just updated my V8.2.1 to Build 170. When I downloaded Build 170 and installed it, and then opened S&T, it indicated that it was indeed Build 170. However, when I went to V8>Tools>Check for Updates, and had it download and install the updates, re-opening S&T indicated that it was now Build 160. Maybe a minor issue, maybe not.

Don't use Check for Updates. Use the downloaded Build 170 (V8) & 180 (V7.5). Also update the bootblock, if needed, and firmware on the V2.

[joecar]

+1 what Ninety9C5 said... do not use Check for Updates.

After you get back to builds 180 (V7) and 170 (V8) you need to install the newer bootblock and firmware that comes with V8.

[cmkelly01]

I'm using bootblock 2.07.03, and firmware 2.07.22. I'm just concerned that since I can't use the Update feature, that I'll be missing some newer files. Thanks.

[Duramax 6.6L]

I'm using bootblock 2.07.03, and firmware 2.07.22. I'm just concerned that since I can't use the Update feature, that I'll be missing some newer files. Thanks.

You are using the latest updated version, But since this is a standard release and not a beta, I wonder why the check for updates is not for the new version of 180 and 170.