2007 Escalade + BBL

[Tony @ MPH]

Connected it up without fanfare, for the most part. V2 did complain that a PID was invalid and asked me to deselect it. I used the E40 Auto PMM -- could not immediately find a way to deselect that PID.

It was real cold outside so I only tinkered for about 5 minutes. Will get more data tomorrow.

[Tony @ MPH]

Note, the same thing happens on the E38 Auto config, which is the proper controller for this vehicle. It does not happen on E40 Manual or E38 Manual.

The missing PID is TFMDC.

The tranny on this vehicle is a 6 speed auto. I think most other E38's may be 4 speed autos but admittedly, being a MT guy I usually do not pay attention to what AT is in what vehicle these days :D

[Tony @ MPH]

Oh and BTW, going through the process of upgrading the bootblock, firmware, and getting this connected to my vehicle really makes me appreciate the amount of design and forethought that went into not only the code but also the hardware design and integration.

There is no doubt, what EFILive is doing is no easy job -- you guys are freakin' geniuses and always a pleasure to work with. Thanks guys (and ladies!)

[Blacky]

The missing PID is TFMDC.

The strange thing is (and I'm still trying to figure out why), is that the TCM reports that PID as supported (when validating PIDs in the PC based Scan Tool) but when any attempt is made to log it via BBL, the PCM reports that PID as not supported. It may turn out to be "only" supported for freeze frame data or something like that.

Any chance of attempting to log that PID using the PC based Scan Tool and see what happens? Do a validate PIDs on the TCM first, and check the valid PIDs to make sure that PID is not flagged as invalid.

Regards
Paul

[Blacky]

Oh and BTW, going through the process of upgrading the bootblock, firmware, and getting this connected to my vehicle really makes me appreciate the amount of design and forethought that went into not only the code but also the hardware design and integration.

There is no doubt, what EFILive is doing is no easy job -- you guys are freakin' geniuses and always a pleasure to work with. Thanks guys (and ladies!)

Glad you appreciate it, The FlashScan development work is a bit like an iceberg, only the top 10% is visible.

Regards
Paul

[Tony @ MPH]

The strange thing is (and I'm still trying to figure out why), is that the TCM reports that PID as supported (when validating PIDs in the PC based Scan Tool) but when any attempt is made to log it via BBL, the PCM reports that PID as not supported. It may turn out to be "only" supported for freeze frame data or something like that.

Any chance of attempting to log that PID using the PC based Scan Tool and see what happens? Do a validate PIDs on the TCM first, and check the valid PIDs to make sure that PID is not flagged as invalid.

Regards
Paul

Sure Paul, I'd be happy to. We're having a bit of a hectic day here so it will be later this evening, Eastern time. But I'll definitely get to it this evening.

BTW, are there any known bugs pulling the knock retard PID from the PCM? As far as I could tell there are not. But I noticed this vehicle, which is 100% stock, gets a LOT of knock. Anywhere from 3 to 8 degrees and mostly at light/part throttle. But I can see the PCM is commanding an awful lot of timing, usually over 40 degrees. It seemed almost unbelievable how much it was knocking, or thought it was knocking.

[Blacky]

Sure Paul, I'd be happy to. We're having a bit of a hectic day here so it will be later this evening, Eastern time. But I'll definitely get to it this evening.

BTW, are there any known bugs pulling the knock retard PID from the PCM? As far as I could tell there are not. But I noticed this vehicle, which is 100% stock, gets a LOT of knock. Anywhere from 3 to 8 degrees and mostly at light/part throttle. But I can see the PCM is commanding an awful lot of timing, usually over 40 degrees. It seemed almost unbelievable how much it was knocking, or thought it was knocking.

I have heard this from others as well, so there may well be an issue. We are still looking at it. If you could send a *.efi file showing the knock, that would help a lot.

Regards
Paul

[Tony @ MPH]

I have heard this from others as well, so there may well be an issue. We are still looking at it. If you could send a *.efi file showing the knock, that would help a lot.

Regards
Paul

Consider it done, I'll do both this evening. Thanks Paul.

:cheers:

[Tony @ MPH]

OK, TFMDC shows up as invalid when connected to the T43 TCM on this vehicle (both before and after doing a validate PID).

Also, I have a BBL .efi file with what appears to be extraneous KR. I am just not entirely sure how to get it off the flash memory on the V2. I tried dragging and dropping in E-explorer but with no success. :help2:

For what it's worth... the reason I didn't even think that there was a bug was because I could visually see actual spark dropping when KR was introduced. Since both values moved together or at least appeared to on the LCD I figured it may not be a bug. But on the other hand, it really seems to knock an awful lot. Hmmm...

[XLR8NSS]

Tony - I really haven't done a lot of logging on my truck yet but, I see some part throttle KR also on mine. It's a 2007 GMC Sierra 2500HD 6.0L/6L90E E38. Seems to knock a lot at low speeds with around 30-40% throttle. I'm gonna have to take the laptop out and do some real logging though.

[Blacky]

OK, TFMDC shows up as invalid when connected to the T43 TCM on this vehicle (both before and after doing a validate PID).
Can you locate the *.vpl that was created wehn you validated the PIDs. It will be in the \My Documents\EFILive\V7.5\PIDs folder and will be named XXXXXXXXX_X.vpl where the X's are the digits from your TCM's VIN. (The underscore is the position of the VIN's checkdigit and is not included in the filename). Please send it to me at paul@efilive.com


Also, I have a BBL .efi file with what appears to be extraneous KR. I am just not entirely sure how to get it off the flash memory on the V2. I tried dragging and dropping in E-explorer but with no success. :help2: Are you getting $0185 errors? If so please read this:
http://forum.efilive.com/showthread.php?t=7017


For what it's worth... the reason I didn't even think that there was a bug was because I could visually see actual spark dropping when KR was introduced. Since both values moved together or at least appeared to on the LCD I figured it may not be a bug. But on the other hand, it really seems to knock an awful lot. Hmmm...
Well that does sort of indicate that the ECM "thinks" there is knock. It wouldn't be pulling spark if it was just EFILive recording the knock value incorrectly.

Regards
Paul

[Tony @ MPH]

Those VPLs are coming your way Paul.

Regarding the PCM thinking there is knock, I am 100% on board with you. That is precisely why I felt it may not be a bug and that it may be real.

In other related news (and confirming this theory) I received a call today from a shop that built a custom turbo kit for the E38 Escalade. They said they were *also* seeing crazy knock on the stock tune. The motor needed new pistons and rods to drop the CR before it would make good, reliable power with the turbo.

So I guess this is a bit of good news for you (e.g., no bug to fix) and bad news for me (e.g., that blower kit I just bought... you know, the one I was going to slip past my significant other, because there's so much room on the trucks that it couldn't possibly take longer than 6 hours to install.. yeah... that one... well, it's going to be a much more involved install than just strapping the blower on if the PCM knocks this much from the factory :frown: ).

I'm dumbfounded. How can GM ship a motor that knocks this much from the factory without wrecking itself inside of 30K miles? We're not just talking 1-2*, we're talking 8* or more... frequently... :nixweiss: