V2 won't data log

[Quinton]

Ok here are the screen shots. Config file system.
Open option.txt
Program ALL
Right?

[Blacky]

You don't have any controllers or PIDs selected, so you won't see any data being logged.
You should have something like this (for example to log data on an E38 controller):



Regards
Paul

[Quinton]

You don't have any controllers or PIDs selected, so you won't see any data being logged.
You should have something like this (for example to log data on an E38 controller):



Regards
Paul

Yes I've done this but didn't program all. Wasn't sure if it was right. But this is what I was wondering. Will I have to hook up to the vehicle with the laptop first to select the pids for it then save it?

[Blacky]

Yes I've done this but didn't program all. Wasn't sure if it was right. But this is what I was wondering. Will I have to hook up to the vehicle with the laptop first to select the pids for it then save it?

No, you can configure it all without the vehicle connected. That's the whole point of Black Box Logging.

Step 1: Select the controller(s) and PIDs you want to log (on the [F2: Scan] tab page).
Step 2: Select the controller(s) that you want to read/flash if you want to read and flash any controllers (on the [F3: Tune] tab page).
Step 3: If you are using EFILive's switchable tunes, enter the tune names for your switchable tunes (on the [F4: Switch] tab page).
Step 4: Select which DTC description files you want to be copied to your device (on the [F5: DTCs] tab page). If you do not select any DTC description files then you save will a lot of space on you device, space that you can use for more data logging or more tune files. However, without any description files, when you display trouble codes you won't be able to see the codes' descriptions.

Step 5. Select Program->Format CONFIG file system to clear out any existing settings.
Step 6. Select [Program] to copy all the configuration files required for the selections that you have made **.
Step 7. Wait for the programming to complete.
Step 8. Disconnect the device and take it to your vehicle.
Step 9. Connect to your vehicle.
Step 10. Select the controller/PIDs you want to data log
Step 11. Start logging.

Step 12. Stop logging.
Step 13. Disconnect from vehicle (after the blue LED has turned off - which indicates the data has finished saving)
Step 14. Connect your device back to your PC.
Step 15. Use EFILive Explorer to copy the Scan (and/or tune) files from the device to your PC.
Step 16. Display the log files in the Scan Tool (both V7.5 and V8 Scan Tools will display the logged data).


**
Clicking the [Program] option will only copy files that are newer than the files on your device. This can save time by not re-copying the same files each time you make a small change to your PID selections.
Clicking the [Program All] option will copy all files regardless whether the files are newer or not.
Clicking the [Program Selections Only] option will only copy the Options.txt file -don't use that option unless you've only made changes to the PID selections and have not added any new controllers.
Clicking the [Format CONFIG file system] option will delete all files that exist on the device. It is usually a good idea to format the config file system at least once after updating the software. It ensures that old (and probably out of date) files are removed and ar enot hanging around potentially causing compatibility problems with the updated software/firmware.

Regards
Paul

[Quinton]

Okay I got it now. I guess I need a SD card now! I thought they could hold more than only a few pids. Don't want to lose the DTC's. thanks for all the help!!

[Blacky]

Okay I got it now. I guess I need a SD card now! I thought they could hold more than only a few pids. Don't want to lose the DTC's. thanks for all the help!!

The SD Card won't increase the CONFIG file system size. That's fixed at around 2MB in the internal memory inside FlashScan. Within that memory, you can configure many controllers and up to 32 sets of PIDs selections each with as many PIDs as each controller supports. The blue bar at the bottom of the windows shows how much of the internal CONFIG file system is required to store your configuration selections.

Adding an SD card will allow you to log more data and store more tune files.

Regards
Paul

[Quinton]

The SD Card won't increase the CONFIG file system size. That's fixed at around 2MB in the internal memory inside FlashScan. Within that memory, you can configure many controllers and up to 32 sets of PIDs selections each with as many PIDs as each controller supports. The blue bar at the bottom of the windows shows how much of the internal CONFIG file system is required to store your configuration selections.

Adding an SD card will allow you to log more data and store more tune files.

Regards
Paul

Ohhhh okay. Thank you so much for your help. One more question I just tried to tune a 2002 lb7 duramax (E54 controller I believe) and after pulling the stock tune it showed me this and wouldn't let me tune it because of it. Any ideas? When I try my truck it works fine just not his, and I tuned another lb7 and Lbz few days ago just fine.

[Blacky]

The LB7 NVRAM (non-volatile ram) memory area has been corrupted by a previous programming procedure. Most likely because a non-compatible OS was flashed into the controller. GM's SPS system can ( and does ) cause that. Unfortunately, there is nothing that can be done to fix that via the OBDII port. The flash chip needs to be removed and reprogrammed in a chip programmer. Socal Diesel can perform that work. Their contact details are listed here: https://www.efilive.com/index.php?op...=60&Itemid=153

Regards
Paul