BB Logging - Missing Data ?

thanks for the reply swingtan, good to know i'm not the only one to experience the log of notes. i think the problem is BBL/V2 related and nothing to do with ScanTool and other applications running on the laptop as every time it happens the file viewed in EFILive Explorer is only 2KB (when it should be between 2,400KB and 8,800KB for the distance traveled) and no VIN is stored.

i can close every application down one at a time, use a different computer and re-boot as many times as i like, the file will still look the same.:confused:

A 2KB file is about the right size for the file header ( 1024 bytes ) and the metadata only. 2KB would probably have little or no real data in there at all. I've had this once or twice and the usual reasons were....

• I'd filled the SD card and there was only enough room to write the file header.
• The ODBII cable connection was interrupted mid log, causing the V2 to abort writing data.
• The SD card was removed from the V2 before canceling the logging operation.
• The SD card suffered a connection loss during the logging process.

There have been one or 2 rare occasions where I have corrupted a file like this by turning off the ignition before stopping a log. But that was a couple of firmware revisions back and I haven't been able to replicate that. So I think it may have been an SD card issue. I've since swapped from using a 2GB card to a 32MB card and found it to be more stable. Perhaps the use of bigger cards may take up more resources and cause an issue?

Simon.

Quote:

---

Originally Posted by swingtan

*The ODBII cable connection was interrupted mid log, causing the V2 to abort writing data.
*The SD card suffered a connection loss during the logging process.

I've since swapped from using a 2GB card to a 32MB card and found it to be more stable. Perhaps the use of bigger cards may take up more resources and cause an issue?

---

I think you might be onto something there Simon. Always a wealth of information. :book:....:good:

Quote:

---

Originally Posted by Blacky

Thanks, I received the file.

I've gone over the log file and the data looks normal and correct to me.
Has it happened again, since then?

Regards
Paul

---

Paul,

these are similar type of logs I have seen. I don't think that is normal. If you look at ECT and IAT under F9 for data. I don't think 419 F is normal for the max of that value. There's a spot in the log that shows 419F. why? Look at the log below. Why near the end of the log. Data goes from 800RPM to 16K RPM and there's other data that's not correct in that area :confused:

This kind of goes along with the thread in the Beta section.

Quote:

---

Originally Posted by CV8IIM6

thanks for the reply swingtan, good to know i'm not the only one to experience the log of notes. i think the problem is BBL/V2 related and nothing to do with ScanTool and other applications running on the laptop as every time it happens the file viewed in EFILive Explorer is only 2KB (when it should be between 2,400KB and 8,800KB for the distance traveled) and no VIN is stored.

i can close every application down one at a time, use a different computer and re-boot as many times as i like, the file will still look the same.:confused:

---

Can you please send me some samples of the 2K log files?
Regards
Paul

Quote:

---

Originally Posted by Biodiesel66

Paul,

these are similar type of logs I have seen. I don't think that is normal. If you look at ECT and IAT under F9 for data. I don't think 419 F is normal for the max of that value. There's a spot in the log that shows 419F. why? Look at the log below. Why near the end of the log. Data goes from 800RPM to 16K RPM and there's other data that's not correct in that area :confused:

This kind of goes along with the thread in the Beta section.

---

I can't explain what happened in that log file. The data is corrupt. I don't think it is an SD card issue or any other hardware issue because the corruption is not random and the frame integrity has been maintained. That indicates that there is a software/firmware problem somewhere - I just don't know where or why.

The is being investigated...

Regards
Paul

Would having 48 channels selected, cause a problem?

Code:

---


swingtan > logtool.pl -s BBL00303%20RPM.efi

Source file: BBL00303%20RPM.efi
Source size: 820531
Source Meta size: 2019

ChannelCount: 48
Frame size: 56

Data length: 817488

---

Quote:

---

Originally Posted by Blacky

Can you please send me some samples of the 2K log files?
Regards
Paul

---

Hi Paul,

I attached one of the files in post #19 of this thread.
I never saved any other log files but I could get more within a week or 2 if required.

Cheers.

Quote:

---

Originally Posted by swingtan

Would having 48 channels selected, cause a problem?

Code:

---


swingtan > logtool.pl -s BBL00303%20RPM.efi

Source file: BBL00303%20RPM.efi
Source size: 820531
Source Meta size: 2019

ChannelCount: 48
Frame size: 56

Data length: 817488

---

---

That shouldn't be??

I don't recall any problems prior to the newer A/C and F/S firmware releases.

I think it's something in the Firmware as Paul stated. The more you use BBL with A/C and F/S the more you'll start to see the problem. Some might over look the log as a fluke? But when you see a 2k log with no data and you can view F/S PID data, using internal or the SD card memory. I see it about 3% of the logs. Could be 1 in 3 or up to 1 in 16 or more.

I have 1 log that is 35.3 MB (BBL 311) no problems using the same PID as Log BBL 303.

I'm not sure what the max channel count is for the diesels, but for the LS1 controller it's 26 and anything over that can cause random issues, from missed frames to a total lock up. I'm wondering if the random issues you are having is due to the number if channels.

I managed to get a 2K file yesterday, but that was because the car I was logging had a slightly flat battery and I tried logging the start. The cranking drew too much current and the V2 shutdown.