September 2016: EFILive Beta Test Release

[Blacky]

Please download and install both the V7.5 and V8 software packages.

Both the V7.5 and V8 software were updated for this beta test release, you must update both software packages.

Download V7.5 Beta (http://download.efilive.com/Software/V7.5/EFILiveV7.5.8.311_Beta.exe) (104 MB)
Download V8 Beta (http://download.efilive.com/Software/V8/EFILiveV8.2.3.305_Beta.exe) (69 MB)


ATTENTION - BETA SOFTWARE RELEASE:

The EFILive beta software is available to all users. We strongly recommend that you do not install the beta software over the top of your production systems. It is possible that the beta test software may fail and your production system may not be recoverable. If you conduct a tuning business, please take the necessary precautions to protect your business. EFILive recommends that beta testers use a separate FlashScan V2 device (when installing the latest beta firmware) and only install the EFILive beta test software on a separate PC, laptop or virtual machine.


Release Notes:
Whats New (http://download.efilive.com/Software/whatsnew_305.htm)


Key Features:


Controller Authorization to manage heightened security protocols for 2017 GM controllers.
The first release of 2017 GM vehicle support including updated E92 Corvette and E82 ECM for LGX 3.6L V6.
Changes to Remote Linking/Unlinking of AutoCal.
Updated documentation to support recently added features.


Please note, with many new OS's released for 2017 models over several different ECM types, unsupported OS's may take some time to be completed and may not be currently supported in this release.


IMPORTANT:

The EFILive software version numbers have been updated from: V7.5.7 to V7.5.8 and from V8.2.2 to V8.2.3. That version number change reflects two major compatibility updates:




[*=1]The *.ctz and *.coz tune files have been updated.
Tune files that are saved with version V7.5.8 and later or with version V8.2.3 and later are not compatible with previous software versions. Tune files created with previous software versions are 100% compatible with this latest software version.


[*=1] The *.obj read/flash script files have been updated.
Script files distributed with this software version will not operate on devices with firmware V2.07.103 and earlier. So if you create a *.bbx quick setup file for your customers' AutoCal devices using this software version, then you must ensure that the target AutoCal devices are using firmware V2.07.104 or later.



Version Numbers:

After installing this beta release you should have the following software, boot block, firmware versions installed:


EFILive V7 software: V7.5.8 Build 311 To view the installed version, select Help->About (in the V7 Scan or Tune software).
EFILive V8 software: V8.2.3 Build 305 To view the installed version, select Help->About (in the V8 Scan and Tune software).
Boot Block: V2.07.007 (Feb 07, 2014) To view/update the Boot Block, click the [Check Firmware] button in the V8 Scan and Tune software.
Firmware: V2.07.104 (Sep 17, 2016)To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.


Known Issues:

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 and fully integrated with the V8 tuning tool software.
Issue 2:
When logging DMA PIDs (i.e. PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However the DMA PIDs may no longer return valid data.
Workaround:
EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.
Issue 3:
The enhanced PID FSST:FCLA (closed loop fuel active) displays the loop status backwards. I.e. it shows open for closed loop and closed for open loop.
Workaround:
Use the generic FUELSYS PID instead.
Issue 4:
DMA PIDs (i.e. PIDs with names ending in _M) do not log correct values when using the V8 pass-thru scanner.
Workaround:
Use the V7 pass-thru scanner or black box logging to log DMA PIDs.
Issue 5:
Reading and flashing in the V7 tune tool fails if the V7 scan tool property setting: [Advanced]->Priority is set to anything other than 3.
Workaround:
Ensure the property setting [Advanced]->Priority is set to 3.
Or preferably use the V8 tune tool read/flash options or the standalone BBx read/flash options.

[rcr1978]

Awesome thanks guys:)!

Now what do I do with this (see below) on a E82 read, car also sais service suspension system after the attempt to read also ?
Admin: Removed your vehicle data that was posted here

Edit: I found the instructions in the V8 documents for the above authorization process and going to purchase on the site.

Thanks
Robert

[GMPX]

Awesome thanks guys:)!

Gee you were quick Robert.
In future just the Auth-Code is needed when placing the order in the store - Eg - 8LPJ-J73N-D9N7-F1Y8-4LPC-8532 , so just use 'Copy Code'when using the store.All the other fields are just for reference within the software.

With regards to the service suspension warning, I'm not sure what vehicle you have there but we did test this on a 3.6L Camaro and it was ok.
No doubt it was because the bus went silent briefly. When the real read or flash happens all DTC's get cleared, in the mean time if you manually clear the DTC's yourself the car should be happy again.

The good news is that OS in your car is already mapped and in this release.

Also something we need to make note of in the documentation is if you change computers and want to read or program that same car all you need to do is copy over the completed Authorization code you were just Emailed.
You can also sync your Auth codes to V2 and AutoCal for standalone reading/flashing of your car.

Regards,
Ross

[rcr1978]

Yeah I saw the update and got all excited :muahaha:. It's a 2017 GMC Acadia Denali, I checked for codes and it didn't have any but I will try and clear anyways in the morning if that doesn't work I will try the battery also. Guess if it's still pissed then I will be back here.

[rcr1978]

Here is a New E82 OS for the list 20239
Good news the service suspension warning was gone when I went back out for the read, bad news it came back again after the read maybe it just needs a little time for the module to settle down. I will check again tomorrow for it also.

Also thanks for mapping the T43 file I put in the trans forum for this vehicle it now opens, great work guys.

Thanks
Robert

[GMPX]

Oh I'm sorry to get your hopes up on that OS comment I made, I looked at the E82 Camaro file here which is supported (with my non computer glasses on) and saw the same thing:

12673933 << Camaro LGX
12679553 << Arcadia LGX

To a guy with bad eyesight that is the same :bawl:

[rcr1978]

No big deal I wasn't expecting it anyways, would you be willing to post that camaro file though? 😁

Sent from my HTC One M9 using Tapatalk

[BlackCPG]

Paul -

I'm still having issues with pass thru logging in V8. Same symptoms as the last update. I attached a trace file. 20246

I also noticed under OBD status the OS number is now 0. In the full flash status window, the first two digits of the OS are swapped. It reads 35xxxxxx, and it should read 53xxxxxx.

[joecar]

V7 tunetool Save As is not incrementing the _nnnn at the end of the filename.

[rcr1978]

Doubled checked the car today the service suspension message goes away after it sits for a little bit, not sure why the module would take a while to settle down though.

[cindy@efilive]

V7 tunetool Save As is not incrementing the _nnnn at the end of the filename.

Save as and Ctrl+T, and Save tuning file for AutoCal and Shift+Ctrl+T all add the 4 digit suffix for me. Do you have any more information on reproducing this?

Cheers
Cindy

[GMPX]

Doubled checked the car today the service suspension message goes away after it sits for a little bit, not sure why the module would take a while to settle down though.
Thanks for letting us know.

[Blacky]

Paul -

I'm still having issues with pass thru logging in V8. Same symptoms as the last update. I attached a trace file. 20246

I also noticed under OBD status the OS number is now 0. In the full flash status window, the first two digits of the OS are swapped. It reads 35xxxxxx, and it should read 53xxxxxx.

The trace file did not show any attempt to connect/scan any controller. Can you please supply me with some error message or description of what is not working?Sorry if you've reported it before, if there is a post that you've already made about it, just link me to that post.

Can you post a screen shot of the OS not showing correctly? And a trace file that you saved from the EFILive Control Panel after displaying the OBD info.

Regards
Paul

[Blacky]

V7 tunetool Save As is not incrementing the _nnnn at the end of the filename.

For V7 only:
The sequence number won't increment unless you are saving a completely new file that was just recorded. If you open a file and then do "Save As" (any number of times) it will use the same name and not increment the sequence number.
That is just an unfortunate consequence of the way the V7 Scan tool was originally designed.

V8 Scan, V8 Tune and V7 Tune will (should) increment the sequence number on all "Save As" operations.

Regards
Paul

[BlackCPG]

The trace file did not show any attempt to connect/scan any controller. Can you please supply me with some error message or description of what is not working?Sorry if you've reported it before, if there is a post that you've already made about it, just link me to that post.

Can you post a screen shot of the OS not showing correctly? And a trace file that you saved from the EFILive Control Panel after displaying the OBD info.

Regards
Paul

https://forum.efilive.com/showthread.php?26884-July-2016-EFILive-Beta-Test-Release/page2

about half way down. I sent you an email with everything else.

[anarchydiesel]

Cannot upgrade any CME OS to CSP4. Option to upgrade is not available under the "upgrade OS" tab. Reverted back to public release software and option is available.

[GMPX]

I just opened up three different CME OS's (one a C&C the other two pickups) and the upgrade option is showing. The only thing I can think of is the USB driver didn't install correctly when you upgraded, I think the upgrade option doesn't show unless V7 can talk to a V2.

[anarchydiesel]

re-installed the beta software and now it is there. Must have been the drivers.

[GMPX]

Phew! Cheers.

[joecar]

V7 tunetool Save As is not incrementing the _nnnn at the end of the filename.Ok, it was me that failed...

my filename was 12212156_0007.tun

and when I did Save As, the new filename was 12212156_0007.ctz

and this is why the _0007 was not incremented to _0008 (because the filename/extension is different);

now after saving as _0007.ctz, when I do Save As again, I now see the next increment _0008 (with the .ctz extension), and now the increments work properly.

See, it was me --> :chair:<-- .ctz

[Tre-Cool]

Is there a limit to how many channels can be polled when working with the e98?

It seems as soon as you add a 4 channel pid, i have to have almost next to nothing else logged or i get random errors or the logger will just not start or it starts and i get this wonderful pointless error.

20258

If i drag a pid from top to bottom a pid that wasnt working will start logging. but other pids get no data.
20259

[Blacky]

Investigating...
Regards
Paul


Is there a limit to how many channels can be polled when working with the e98?
It seems as soon as you add a 4 channel pid, i have to have almost next to nothing else logged or i get random errors or the logger will just not start or it starts and i get this wonderful pointless error.
If i drag a pid from top to bottom a pid that wasnt working will start logging. but other pids get no data.

[Tre-Cool]

Just adding in, it appears you don't need to add any of the 4 channel dma pids for pids not to work.

Attached is a log, where 2 types of Pedal data would not populate along with engine torque.

Good old DPF regen going on for a good part of it so noticed EGT1 got to 716'C!20260

FYI, someone needs to edit the VB backend to allow PLD files now.

[Blacky]

FYI, someone needs to edit the VB backend to allow PLD files now.

In V7, highlight the PIDs and select Edit->Copy for export to V8, then paste them into V8.

Regards
Paul

[bobo]

Tuned a 6.7 cmc today. I did not notice any changes in the tune file for rpm limit increases over the release I am running on my other laptop. Is this something that will be added in beta?

[GMPX]

The Cummins CMC (CM2100) was not worked on during this beta phase. Both the CMD (CM2200) and CME (CM2350B) were.

[Tre-Cool]

In V7, highlight the PIDs and select Edit->Copy for export to V8, then paste them into V8.

Regards
Paul

Any particular reason you want me to do this? I just started V8 scan and added in the supported pids from a fresh. I'll do as requested in an hr when i drive home from work though.

Would you like for me to get a sample log from 7.5 at the same time? I can happily use 7.5 for now i was using v8 purely to see the additional vane % & desired boost pids.

[Blacky]

Any particular reason you want me to do this? I just started V8 scan and added in the supported pids from a fresh. I'll do as requested in an hr when i drive home from work though.

Would you like for me to get a sample log from 7.5 at the same time? I can happily use 7.5 for now i was using v8 purely to see the additional vane % & desired boost pids.

Ahh no, sorry. When you posted this:

FYI, someone needs to edit the VB backend to allow PLD files now.
I misread that to be "PID files". I was just trying to explain how to copy V7 PID selections into V8 because you can't open *.PID files inV8.

Now I'm not sure what you meant by PLD files. (Plus what do you mean by "the VB backend"?)

Regards
Paul

[Tre-Cool]

It was in reference to the VBB forum software. It doesn't allow you to upload v8 log files. due to the new file extension. :-)

202642026520266

If you look at the v8 log files attached, the torque figures are ridiculous/garbage.

Slightly off topic, Can i also ask if we can get the additional injection modes added? I think when the car goes into dpf regen mode it's switching to a different injection mode as on my drive home again it went real doughy and i noticed it was no longer running the injection timing i had set. (tested by setting both my mode 1/2 identical)

[bobo]

The Cummins CMC (CM2100) was not worked on during this beta phase. Both the CMD (CM2200) and CME (CM2350B) were.
Are you going to add the rpm limit fix to the CMC (CM2100)?

[GMPX]

Are you going to add the rpm limit fix to the CMC (CM2100)?
I've struggled with that for a long time Bobo.
But at least recently we've seen good feedback for the 2010+ RPM's and Fueling with some additions we've added.

[Tre-Cool]

Did some playing today/tonight and i can confirm the 17 model Aus Colorado does not use the Pattern 1 & 2 Injection timings maps.

I suspect it uses at least 2 other ones. 1 for normal running & another for when its doing a DPF regen (could be 2 here 1 for idle, 1 for non-idle)

To test my theory I added 4 degrees to the entire maps, all 3 for injection 1. logged, even did some wot. then i repeated for injection 2 maps and put injection 1 maps back to stock. both logs were identical.

As for the DPF Maps, i noticed the car got more doughy/smell while i was driving which is an easy tell, & while the car was idling at a mates place (I still had logger going) the car made a distinct Idle Rpm/Vac & Ignition timing change. Which again does not match Inj 1 or 2 maps.

I've uploaded that log here.

Bare in mind that my maps are probably not stock in those other maps thanks to *cough* .20272

[GMPX]

Well the whole operating mode thing is a mess to be honest, I was going to add in a DMA PID to make life easier to track what it was doing but the way the code is done it is not the same between OS's.
Eg if you logged it was in Mode 4 on an Aussie model that might not be the same map sets the US model was using, it's a bit ugly. I do know that pre 2017 they only ever seemed to use 'normal' mode which is why we never looked too much more in to it.
I'll just add to that when I had my Diesel Cruze I only ever tuned the normal running mode maps, when it was doing a regen I just figured I'd let it do its thing the way the factory intended, but that's just my thought process.

[Tre-Cool]

Well the whole operating mode thing is a mess to be honest, I was going to add in a DMA PID to make life easier to track what it was doing but the way the code is done it is not the same between OS's.
Eg if you logged it was in Mode 4 on an Aussie model that might not be the same map sets the US model was using, it's a bit ugly. I do know that pre 2017 they only ever seemed to use 'normal' mode which is why we never looked too much more in to it.
I'll just add to that when I had my Diesel Cruze I only ever tuned the normal running mode maps, when it was doing a regen I just figured I'd let it do its thing the way the factory intended, but that's just my thought process.

I was wondering if there was a Mode Pid, it would definitely be handy for development or laying out what the car is doing. But i guess doing a couple of changes & then flashing to find out where things are is not that hard either. Biggest issue would be is you sometimes don't know if it's doing a full regen or a partial in the my17. I was going to start a thread with all my findings once I had it sussed out, just to make it easier/less guess work for others in the future.

Do you require a copy of my tune to decompile?

[GMPX]

The problem with a Mode PID as such is in the code GM use jump tables to select the maps to be used, so for example something like this (these aren't real values).
Mode PID
1 = Use Normal Mode Maps
2 = Use Alt Mode 2
3 = Use Alt Mode 2
4 = Use Normal Mode Maps
5 = Use Alt Mode 1
6 = Use Normal Mode Maps

And so on, I think from memory there was at least 12 or 13 'Modes' that then point to 5 or 6 map groups, on the US cals there is more.
But here is there problem, take a different OS and it might work like this:

Mode PID
1 = Use Normal Mode Maps
2 = Use Alt Mode 4
3 = Use Normal Mode Maps
4 = Use Alt Mode 1
5 = Use Alt Mode 1
6 = Use Alt Mode 2

Sure we could log the value that defines what Map to jump to, but we can't always know what that Map is because from one OS to another 2 does not mean the 2nd map and so on.

[Tre-Cool]

Yeah i understood what you meant the first go around. Would be bit coding involved on your end to work it all out & then i guess you would need to setup configs based on each OS or Cal once it's defined.

I'm guessing it's in the Calibration side of the OS since it's still the same OS between 16 & 17 Aus colorado's?

I'm happy to work things out myself if you can provide me a cal with the additional modes and I'll report back my findings.

[GMPX]

Would be bit coding involved on your end to work it all out & then i guess you would need to setup configs based on each OS or Cal once it's defined.
Yes, which the scantool cannot currently do.


I'm guessing it's in the Calibration side of the OS since it's still the same OS between 16 & 17 Aus colorado's?
Yes, this stuff is hardcoded in the OS.


I'm happy to work things out myself if you can provide me a cal with the additional modes and I'll report back my findings.
That would take me days to add all the additional modes in, so maybe not right now. And part of the reason we never did it for the local OS was because they only ever ran in normal mode until the 2017 model came along.

[Tre-Cool]

Looks like i might need to flash to the 16 model os even earlier. haha.

No big deal as i can wait. I'm only up to 1300km's on it now.

[GMPX]

Didn't you try the 2016 cals already?

[Tre-Cool]

Yeah i did. the stock 16 file worked fine. when i tried a file that had been blended with some mods from hpt is where it did weird things with stationary to moving power. (like nothing nothing, let's go! power!!!)

I'm just a bit concerned about running the 16 cal long term while i still have the dpf crap still on it. Since the longest i've gotten so far is about 300km's before regen distance resets.

I did go from about 110rwkw to 137 with the 17 cal, but no matter what i tried I couldn't get it to increase boost.

After finding the hpt stuff is all kinds of messed up, I'm trying to stay away from using it. I can happily wait for the additional tables to appear as im not looking to tune these in a commercial sense, this is my own personal vehicle.

I'm also curious to know how the Custom OS will handle the DPF regen's now too, especially if they are using different modes. Or are you guys simplifying the code some how? Maybe that's an option for me?

[GMPX]

I'm also curious to know how the Custom OS will handle the DPF regen's now too, especially if they are using different modes. Or are you guys simplifying the code some how? Maybe that's an option for me?
The custom OS only switches the normal mode tables, all the other modes remain factory.

[Mitco39]

I am having an issue with the permissions of the file.

If I link a ctz to a serial number, but leave the premissions as able to modify and view I would suspect that I could still open it in V7.5. However with these premissions set it still does not allow reading of the ctz of the file in v7.5. Is there something I am missing.

Thanks so much,

Mitch

20341

[Blacky]

I am having an issue with the permissions of the file.

If I link a ctz to a serial number, but leave the premissions as able to modify and view I would suspect that I could still open it in V7.5. However with these premissions set it still does not allow reading of the ctz of the file in v7.5. Is there something I am missing.

Thanks so much,

Mitch

20341

No you're not missing anything.

The V7 software does not "understand" and cannot manage all the individual V8 security options in the *.ctz file. If any security option (other than Auto-Lock) is set in a *.ctz file then it can't be opened in V7.

Regards
Paul