Noticed that during BBL, if I use a group which has a total of 24 bytes, the V2 will log without any issues. Now, if I select a group which has say, 22 bytes, it will log for a while (like ~30 minutes), then lock up. The screen will show that it is still logging, but if you look at the variables, some are changing some are not. And when you hit the cancel button to stop logging, it says writing file like there is nothing wrong. When you look at the data, it also looks fine up to the point when it locked up (a sort of soft failure mode I guess).

Has anyone else noticed this? I am using this on an '04 LB7 Diesel with an Automatic. The logging is done to the internal memory as well, so this is not an SD card issue.

Maybe this has to do with some kind of memory buffer that is left when recording the data that eventually fills up with "extra" data that then causes it to lock up????

Good Log file group: No problems
LB7A - Total = 24
VSS [1] Vehicle KMH Sensor (kmh)
RPM [2] Engine RPM (rpm)
TP_A [1] Throttle Position (%)
FUELQ_MAIN_M [2] Main Injection Fuel Flow Rate 2 (mm3)
MNINJTIM [2] Main Injection Timing (°)
FRPDES [2] Desired Fuel Rail Pressure (MPa)
FRPACT [2] Actual Fuel Rail Pressure (MPa)
MAINBPW [2] Main Injection On Time (us)
DMAX_TRQ_M [2] Maximum Engine Torque (Nm)
BOOST_M [2] Turbo Boost Pressure (kPa)
MAF [2] Mass Air Flow (g/s)
PIINJTIM [2] Pilot Injection Timing (°)
TCCDC [1] Torque Converter Clutch Duty Cycle (%)
GEAR [1] Current Gear


Bad Log File Group: Locks up after ~ 30 minutes of logging.
Trq - Total = 22
VSS [1] Vehicle KMH Sensor (kmh)
RPM [2] Engine RPM (rpm)
TP_A [1] Throttle Position (%)
FUELQ_MAIN_M [2] Main Injection Fuel Flow Rate 2 (mm3)
MNINJTIM [2] Main Injection Timing (°)
FRPDES [2] Desired Fuel Rail Pressure (MPa)
FRPACT [2] Actual Fuel Rail Pressure (MPa)
MAINBPW [2] Main Injection On Time (us)
DMAX_TRQ_M [2] Maximum Engine Torque (Nm)
BOOST_M [2] Turbo Boost Pressure (kPa)
TCCDC [1] Torque Converter Clutch Duty Cycle (%)
GEAR [1] Current Gear