Build 82, WTF?

[Blacky]

Is overwriting the 7.5 folder with a previous version an ok way to revert?

You only need to swap out three files:
EFILive_Scan.exe
EFILIve_Tune.exe
ObdiiV7.dll
You MUST keep them all at the same build number.

Regards
Paul

[Blacky]

Please check out this thread as well. The problems are likely to have a similar cause/solution.
http://forum.efilive.com/showthread....ed=1#post88827

Can you also try the firmware in that post, thanks.

Paul

[Blacky]

Possible solution...
http://forum.efilive.com/showthread....ed=1#post88830

Regards
Paul

[mr.prick]

Possible solution...
http://forum.efilive.com/showthread....ed=1#post88830

Regards
Paul

The obdiiV7.zip fixed it.
Is that newfirmware or altered?

[Blacky]

The firmware I posted is very new and very untested. It has a whole lot of new features which are needed to support standalone reading/flashing.

The obdiiv7.dll is the actual fix for the problem, changing the firmware will not fix the problem. I was at a loss to explain why I was seeing it work so I thought maybe it was the firmware I was using - turns out it was not.

Regards
Paul

[JR-CRUZN-C5]

Guys - My car is going back together NOW. I will be racing again in April. Have not really touched my "stuff" lately.

My current setup is:
V7.5.5 (Build 80)
BB 2.06.02
FW 2.06.06

I have not recvd. any auto downloads in a while.

SHOULD I BE CHANGING ANYTHING???

JR

[Blacky]

Select the option:
Start->All Programs->EFILive->V7.5->Tools->Checkfor New Update.

Check here first to see what has been updated:
http://www.efilive.com/index.php?opt...=57&Itemid=134

The auto update is set to 3:00am Sunday morning by default. I think if you are not connected to the 'net at that time then it won't update automatically.

Regards
Paul

Guys - My car is going back together NOW. I will be racing again in April. Have not really touched my "stuff" lately.

My current setup is:
V7.5.5 (Build 80)
BB 2.06.02
FW 2.06.06

I have not recvd. any auto downloads in a while.

SHOULD I BE CHANGING ANYTHING???

JR

[mr.prick]

The firmware I posted is very new and very untested. It has a whole lot of new features which are needed to support standalone reading/flashing.

The obdiiv7.dll is the actual fix for the problem, changing the firmware will not fix the problem. I was at a loss to explain why I was seeing it work so I thought maybe it was the firmware I was using - turns out it was not.

Regards
Paul

Not to nag but,
why not completely change the number sequence of the firmware?
To avoid confusion.
Was this in the 7.5 update and is it to be used with build 82 and V8 (44)?

By any chance will BBF be usable with the RR?
I know you can`t up/download with RR like you can stock PCM,
just curious.

[Blacky]

Not to nag but,
why not completely change the number sequence of the firmware?
To avoid confusion.
Was this in the 7.5 update and is it to be used with build 82 and V8 (44)?

If I increased the version number and you flashed it in and it caused more problems (untested and all), then you would not be able to go back to V2.06.06. I left it at V2.06.06 so you could go back to the real V2.06.06 if required. I did change the date so you could tell it was different to the "real" V2.06.06 once it was flashed into FlashScan.

I did not include the new firmware update with the latest V7.5.5 build 83 update) it has not been tested enough, it is part of the AutoCal beta test suite). Although I mistakenly added some comments to the "waht's new" web page that indicated that the firmware was being updated with that release - my bad.

By any chance will BBF be usable with the RR?
I know you can`t up/download with RR like you can stock PCM,
just curious.

No plans to allow BBF on RR with the first release, but is something that could be supported in future.

Regards
Paul

[mr.prick]

We can`t go backwards with firmware now?
IRC there was a bad firmware that caused connection problems
and I was able to go back.
It was long ago, maybe before the last bootblock update.