January 24th 2011 pre-release

[Blacky]

Thanks for the response Paul. The folder is empty. I'm using the BB Flashing and not the PC with pass thru with 7.5. The PC with pass thru works fine. It's just when I try to use the V2 by itself. The first thing I noticed after choosing the tune file which displays E60 then below that is the tune file "LLY_0007.ctd" which is on the SD card. After I choose that then I get "Trying MFG Key". Then it checks the tune file and then gives me the message "License this controller now?" I choose no.

I've managed to confirm it is a bug with the E60 flash routine in FlashScan. I have fixed it and the fix will be in the next update.
Meanwhile, don't license it using BBF, just use the pass-through mode where it detects the license correctly for now.

Regards
Paul

[Blacky]

I had the same problem with my LBZ. I had to define the PID and tune controller under BBx in the V8 software (right click and select controller). The PID was showing unknown & A40 and the tune was blank for LBZ. All the diesels were blank in the tune section and unknown in the PID section. Pass thru was never a problem for me.

That may be because we have changed the codes used to identify the LB7, LLY, LBZ, LMM and LML controllers.

The changes are:
LB7 is now E54
LLY is now E60
LBZ is now E35A
LMM is now E35B
LML is now E86

You may need to double click on each of the entries that reference any of those controllers and re-select the correct controllers based on the new codes.

Regards
Paul

[Blacky]

That may be because we have changed the codes used to identify the LB7, LLY, LBZ, LMM and LML controllers.

The changes are:
LB7 is now E54
LLY is now E60
LBZ is now E35A
LMM is now E35B
LML is now E86

You may need to double click on each of the entries that reference any of those controllers and re-select the correct controllers based on the new codes.

Regards
Paul

I have now changed the code that reads the Options.txt file and it now automatically makes those changes.
That will be available in the next update.

Regards
Paul

[lakingslayer]

You guys are awesome. Thanks for the support.

[ScarabEpic22]

Although, if the original file can be BBFF then that indicates all necessary files are available.
One thing that does come to mind is the filename length. I think it needs to 16 or less characters long.
Regards
Paul

OK Ill try that today, it is a different OS if that makes a difference. Ill try renaming the files a few different ways to see if it works.

[oztracktuning]

Since this new version when i open E38 files the red options to enable patches is not appearing even when Flashscan is plugged in. Is this happening with everyone?

[GAMEOVER]

Since this new version when i open E38 files the red options to enable patches is not appearing even when Flashscan is plugged in. Is this happening with everyone?

I don't see them either....

[Blacky]

Since this new version when i open E38 files the red options to enable patches is not appearing even when Flashscan is plugged in. Is this happening with everyone?

It is a known issue, it is fixed and an update is almost ready (in about 30 minutes)...
Regards
Paul

[Blacky]

New update available here:
http://forum.efilive.com/showthread....11-pre-release

Regards
Paul

[swingtan]

I'm a bit confused on this one......

I've swapped back to the STD OS of my car 12607218 and can no longer BBF the E38 controller. I continually get the following...

"ERROR: $0502
Script file not found."

But if I try and BBF the old COS "02607218" I do not get the error.

V7.5.6.149
V8.1.2.142

V2 Firmware 2.07.05 29/01/2011

Config Files:

E38.pmm 19/01/2011
E38_F.obj 23/12/2010
E38_F.bix 03/02/2011
E38_L.bix 23/11/2010
E38_R.bix 18/01/2011
E38_R.obj 03/02/2011
E38_W.bix 23/12/2010
E38_W.bix 03/02/2011

Any ideas on this? It seems it has been doing it for the last few updates as I've gone from build 139 through to 149 trying to get it working.

Simon