Known issues with March 2015, Release Candidate 1

[Blacky]

Currently known issues and possible workarounds for the March 2015, Release Candidate 1 of the EFILive Software and Firmware

• Software: V7.5.7.280
• Software: V8.2.2.274
• FlashScan/AutoCal firmware: V2.07.81

---

Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None. It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available.

---

[catman3126]

tuning an lly tonight and everytime I save the LLY tune after converting it to DSp5 it locks it and I have to open with V8 and clear restrictions, and it would not let me save it without my V2 connected when I was done. never had this happen before.

[Blacky]

In the release notes we have this:

IMPORTANT
Your security restriction options on the [Permissions] tab page in the V7.5 Tune Tool software may change during the upgrade to this version of the V7.5 software. Please review those security restriction options and reconfigure them according to your preference.

It is possibe, (probable even) that your security restrictions in the V7 tuning tool software have been changed during the update. Please make sure they are set like this, which is the default value:



What happened in a previous version was the settings got saved incorrectly into the V7 registry. That meant when we corrected the bug in this version, there was no way for the softwar to automatically "fix" the settings. So we advise you to check them and set them to what you want them to be.

You can use the V8 software to remove any security settings that got set when you saved the files using V7.

Regards
Paul

[Mitco39]

Paul,

I dont think the BBX quick setup is saving the security restrictions properly. The CTZ to COZ worked great however with the ctz if I save it as private and then export it to a folder I can still open it as none of the security flags are set. I would assume its the same for the .coz's.

Thanks

Mitch

[Blacky]

Hi Mitch,

Security restriction changes are not "baked into" the tune files in the BBX list until the BBX file is saved. So if you change the restrictions, then export the file it will have the original restrictions that the file had when it was added to the BBX list.
If you save the BBX file first, then re-open it (as would be the case if you sent it to a customer), then export the files you will see that the security restrictions are retained.

Regards
Paul

Paul,

I dont think the BBX quick setup is saving the security restrictions properly. The CTZ to COZ worked great however with the ctz if I save it as private and then export it to a folder I can still open it as none of the security flags are set. I would assume its the same for the .coz's.

Thanks

Mitch

[Mitco39]

I tried that as well. I get the .coz cannot be opened error when trying to open that file. Thats if I double clicked the .bbx file in my windows explorer. If I open up the bbx file inside of V8 it opens up like you said it would in the post above. Is there a way to send this to the customer and just have them double click the bbx file and have it pop up the window for them to click program?

Or maybe I am missing something.

Everything else seems to work perfectly. I was also wondering is it possible to add in a feature that would update the autocal/v2 firmware to the current version of their software they have downloaded automatically? It would really make this a one or 2 click process for the customer if we were able to do that.

Thanks a bunch Paul,


Mitch

[Blacky]

Hi Mitch,

You can't (yet) double click on a *.bbx file and have it open automatically. But we're working on it, so soon you will be able to do that.

We have decided against automatically updating the firmware since it is impossible to downgrade the firmware once it has been updated. We have been asked about an auto firmware update option and we are still considering it. Meanwhile, the [Check Firmware] button on the main V8 Scan and Tune window is the quickest/simplest option for now.

Regards
Paul

[Chuck CoW]

Hi Mitch,

You can't (yet) double click on a *.bbx file and have it open automatically. But we're working on it, so soon you will be able to do that.

We have decided against automatically updating the firmware since it is impossible to downgrade the firmware once it has been updated. We have been asked about an auto firmware update option and we are still considering it. Meanwhile, the [Check Firmware] button on the main V8 Scan and Tune window is the quickest/simplest option for now.

Regards
Paul

That's good. Automatically (or forcing) firmware upgrades will cause problems for some of us. Given the volume of autocal customers and the range

of years past since some of their use can make headaches... It's even troublesome at times just keeping things straight between Release Candidates and

public release stuff. Sometimes I force the customer to have to update and other times they download new stuff and force me to update and as simple

as it sounds, it's either 10 mins of customer service support, 1 hour of phone support, and remote log in sessions at times depending on the customer

computer skill level and intelligence.

The Software has evolved where it's much easier than in the beginning, but It's still quite a lot of unnecessary phone support to keep everyone on the same page.

I had some ideas to make it easier and I'll reach out to you when I get everything on paper.

Chuck CoW

[GMPX]

That's good. Automatically (or forcing) firmware upgrades will cause problems for some of us.

But when people don't update the firmware to match the software releases it causes us support problems, the firmware works hand in hand with the PC side software, they have to match.

[Chuck CoW]

Agreed... BUT YES, it causes problems for you with support.

YES, it causes problems for ME having many autocals out there and everyone has different software.

YES, it causes problems for the END USER cause he's not the designer of the software, not a tuner,

and usually can barely turn on a computer no less wrap their head around drivers, firmware, release candidates,

public releases, etc. They just want their shit to work and don't care how.

If EFILIVE is wasting lots of time with support for issues such as this, just remember that they are usually calling the tuner first.

I think there can be a better way to handle the software updates and compatibility issues, but we all need to toss around some ideas

while each of us considers the possible consequences for the developers, the tuners, and the users.

I'm thinking about this good cause it's always been a problem. All of us are always excited to get the latest STUFF, but all too often

it comes with a price.

I'll keep thinking about this and get back to you soon.

Chuck CoW