Apr 16, 2023, V8.3.38 Public Release (Update 1 for V8.2.37)

V8.3.38 Public Release (Update 1 for V8.2.37)

Full Release Notes:

Whats New

Version Numbers:

After installing this release you should have the following software and firmware versions installed:

• EFILive V8 software: V8.3.38
  
• FlashScan/AutoCal V3 Firmware: V3.00.106

Download here:

Download V8.3.38_Setup

Known Limitations:

Limitation #1: 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.

Limitation #2: When opening CMF (CM2450B) Cummins 2022 tune files, the EFILive software will complain with the following message:
Attachment 24399
That is expected and the message may be ignored. We have only added the option to open CMF 2022 stock files so that EFILive can flash stock files. EFILive cannot be used to update the check sums of modified files. Modified files cannot be flashed.
Ignore the message if you are opening and flashing a 100% stock tune file. Do not attempt to flash a modified file, it will fail at the end of the flash and the vehicle will be left in a no-start condition until a stock file is flashed in.
Workaround: None.

Limitation #3: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), that are specific to a custom operating system such as DSP2 or DSP5 PIDs when running a stock operating system, the values returned by those DMA PIDs will not contain valid information and should be ignored.

Known Issues:

Issue #1: When flashing CME/CMF (CM2350B/CM2450B) Cummins controllers with AutoCal/FlashScan V3 devices the flash can sometimes fail with error $0322.
Workaround: Download and install firmware update V3.00.107 attached to this thread.

Issue #2: *.cax8 files containing blank lines that contain one or more space characters will fail to load with the error "Index out of range".
Workaround: Remove the spaces from blank lines, or remove the blank lines.

Regards,
The EFILive Team

Can i ask that to get the seed value to show up when checking if an ecu is locked in the v8 editor? as apposed to saying it's locked/using a non standard seed?

The old V7 would show it in the on screen log, so it was easy to check a list of previous ecu's i had unlocked for a similar seed.

Cheers

I'll add that in, I didn't realize it was not already there.

Meanwhile, you can view the seed using a V3 device (if you have one) using the option Diagnostics -> F1: Display Info -> F1: Display VIN Info, which displays this type of info:
Attachment 24412

Or using the [F4: OBD] window, which displays this:
Attachment 24413

Regards
Paul

This change will be in the next EFILive release:

When a controller is not locked with a custom key - i.e. it is using the standard GM seed/key pair which are both shown:

Attachment 24418

When a controller is locked with a custom key - i.e. it is not using the standard GM seed/key pair which are both shown.
The standard GM seed/key pair is still shown but the GM key is shown in red to indicate that it is not valid and that a custom (i.e. user defined) key must be used instead.

Attachment 24417

Regards
Paul

Beautiful.

I have a bench setup with a a 4 port obdi plug. so i leave it running with another tool to find the key. then once found i unlock with the v3 device.

Did this for when im away and remote in.

Thanks.

I like it...

Working very well.

A request for future development is the ability to undo a change made by a script. Let's say you run a script and one table was modified that you didn't want to change. In V7.5 you can just undo it. In V8 it doesn't let you, so you need to open another file to copy and paste the table back to the original.