Black box logging and throwing VCM codes

[John_F]

Weird problem here. If I scan just using the black box I get some serious weirdness and VCM codes. If I scan with the laptop there are no problems.
Somehow there seems to be some type of feedback loop or something. If I blackbox log the VCM will throw a code, its either MAF Rich or Lean, I dont remember offhand.
Scanning with the laptop is normal and no codes or weirdness.
Take a look at 2 logs from this morning using only black box.

I'll try to get a couple more logs today with the laptop hooked up to show how normal it is or I'll find a log from a few weeks ago when I noticed all this happening.

I know its a pretty vague post, I'll try to get more info and provide anything needed to get this resolved.
The car is the 04 GTO in my sig.

EDIT: I've attached the Black Box config file also, maybe something is screwed there. I'm 95% sure thats the right config file.

[Bill@HPTuners]

Try logging less than the max 48 bytes to see if it goes away, it appears standalone logging is dropping frames, I'll have our hardware engineer look into why its doing that.

[John_F]

OK, will give that a try.
I just took a drive and scanned using the laptop this time. No changes other than using the laptop, same config file.
Other than my tune being off a bit, its all normal.
The 2 codes are:
[PCM] P0172 - Fuel Trim System Rich Bank 1 (History) (Immature)
[PCM] P0175 - Fuel Trim System Rich Bank 2 (History) (Immature)
They only show when blackbox logging.

I don't understand how it can throw codes just from scanning.
It appears that it screws the tune when logging via blackbox.

[John_F]

Did anyone get a chance to look at this Bill ?

[Bill@HPTuners]

Its on our to do list, did you try logging less then the max bytes to see if you still have the issue?

[John_F]

I loaded the config file below and it wouldn't do anything except give me errors. It's supposed to be 24 bits if it worked.

[Bill@HPTuners]

What type of errors? Did you follow the standalone datalogging demo in the help file.

-Bill

[John_F]

I've done the blackbox logging many times in the past Bill, it always worked fine until I tried it with the GTO.
I dont have any idea on the errors, it wouldn't connect. The red flashing error light just kept coming up.

The Odd part is that it seems to somehow change the tune in my car when logging that way.
Otherwise how would it throw codes only when logging?

[Bill@HPTuners]

The ERR light will flash after a record request if the interface could not establish communications with the vehicle. The configuration setup is vehicle specific and may require you to program a new configuration for the vehicle you are logging.

[John_F]

Did you check the config files?

[Bill@HPTuners]

Just to be sure you DID connect your laptop to the vehicle, click the connect button, then and ONLY then add/delete your pid's and then configure your standalong datalogging config?

If you don't connect to the vehicle the hardware has no way to validate the PID's you've selected.

[Bill@HPTuners]

The config file can look fine, that doesn't mean it will work if you don't connect as shown in the demo.

[John_F]

eh, I dont remember. I tried a 100 different things all at once.
I'll give it a go again tomorrow or whenever.

[John_F]

The Odd part is that it seems to somehow change the tune in my car when logging that way.
Otherwise how would it throw codes only when logging?

Is this part even possible? ^^^

[Bill@HPTuners]

Not that I'm aware of.

[John_F]

OK, I did what Bill suggested and started a new config file with only 24 PIDs or bits or whatever they are. Black Box logging worked fine, no problems.
Using the same config file I added more (PIDs, bits, whatever), up to 43. The same crap happened again. Scan was screwed like in the above logs and it threw the codes again
What gives?
How many (PIDs, bits, whatever) can everyone else scan using blackbox without errors?

[John_F]

Hello ??

[Chris@HPTuners]

it's not possible for the tune to be modified when scanning. The rich/lean codes you are seeing occur when the LTFT's need to move too much to correct the rich condition. ie. too far negative

if logging more than 24 bits in the scanner causes a problem then it should cause it on the regular scanner as well, blackbox logging sends the same commands as VCM Scanner does. If it in fact is a problem my guess would be a GM issue where the obd2 code is not throttled correctly. The workaround being don't log more than 24 bits.

Hope that helps,

Chris...

[John_F]

it's not possible for the tune to be modified when scanning. The rich/lean codes you are seeing occur when the LTFT's need to move too much to correct the rich condition. ie. too far negative

Chris...

What moves the LTFT so much when blackbox logging, it only occurs while using the blackbox, not using a laptop.

if logging more than 24 bits in the scanner causes a problem then it should cause it on the regular scanner as well, blackbox logging sends the same commands as VCM Scanner does. If it in fact is a problem my guess would be a GM issue where the obd2 code is not throttled correctly. The workaround being don't log more than 24 bits.

Chris...

Well it doesn't.
Again, it only happens when using blackbox, the same config can be used on a laptop and there are NO problems.

Does it sound like a hardware problem?

[Chris@HPTuners]

are you blackbox logging large negative LTFT's?

i doubt it is a hardware problem because you would see the issue when regular logging. very weird.