turbo_bu
June 10th, 2010, 03:15 AM
I have found a few problems with the BBL portion of the recent V8 release:
EFILive Scan and Tune 8.1.2.97
Flash Scan V2
Boot Block - 2.06.03
Firmware - 2.06.35
1 - On P12A vehicles (Atlas I4/I5/I6), the knock retard PID has changed from KR to KNKRET. When selecting a group with this in it, the V2 shows and error code of $0283 No such PID. This prevents any logging / displaying of data since it does not know what to do with KNKRET. Interestly enough, if you put in KR instead of KNKRET, the V2 will log OK (no $0283 error), but it will not show KR or log it. Using my older version of BBL (~ May 2008), I was able to log knock retard using the KR PID.
2 - On P11M vehicles (97-01 PCM and 02+ 4 Cylinder), there is no RPM PID listed. I know that this worked before, since I have successfully logged RPM data. Funny enough, looking back at the original PID descriptions for the P11M (~ May 2008) that I have used, it appears as though it was not in there. I do know that if I added it to the list, it worked. I went ahead and manually added it this time to the options.txt file, but it does not show RPM or log it.
3 - Trying to log some transmission and engine data on a LS1B (99 6L). For what ever reason, this combination of PID's causes the BBL to start logging, but then not write any data to the SD card. I have been able to log other vehicles (LB7 diesel) successfully without any issues to the same SD card. Wondering if there is something else wrong with the ls1b.pmm file or maybe my selection of PID's.
; (LSX|TrqRd)
*PSL_01
;
;Node PID Custom (Cap:Units:Prec:Fact:Offs:Inv) Alarm (min:max:style:time*10ms:hold*sec)
;---- ---------------- ----------------------------------------- -----------------------------------------
PCM, TP
PCM, VSS
PCM, RPM
PCM, GEAR
PCM, MAP
PCM, SPARKADV
PCM, KR
PCM, EST_TRQ_M
PCM, EST_XMSN_M
PCM, TRQENG
PCM, TRQTRANS
PCM, TFMPRS
PCM, TCCMODE
PCM, TCCDC
PCM, TCCSLIP
PCM, TFT
PCM, SHIFTERR
PCM, SHIFTDELAY
Total PID count = 24 channels
Don't know if anyone else has had any of these problems. Please post up if you are seeing the same issues that I am.
EFILive Scan and Tune 8.1.2.97
Flash Scan V2
Boot Block - 2.06.03
Firmware - 2.06.35
1 - On P12A vehicles (Atlas I4/I5/I6), the knock retard PID has changed from KR to KNKRET. When selecting a group with this in it, the V2 shows and error code of $0283 No such PID. This prevents any logging / displaying of data since it does not know what to do with KNKRET. Interestly enough, if you put in KR instead of KNKRET, the V2 will log OK (no $0283 error), but it will not show KR or log it. Using my older version of BBL (~ May 2008), I was able to log knock retard using the KR PID.
2 - On P11M vehicles (97-01 PCM and 02+ 4 Cylinder), there is no RPM PID listed. I know that this worked before, since I have successfully logged RPM data. Funny enough, looking back at the original PID descriptions for the P11M (~ May 2008) that I have used, it appears as though it was not in there. I do know that if I added it to the list, it worked. I went ahead and manually added it this time to the options.txt file, but it does not show RPM or log it.
3 - Trying to log some transmission and engine data on a LS1B (99 6L). For what ever reason, this combination of PID's causes the BBL to start logging, but then not write any data to the SD card. I have been able to log other vehicles (LB7 diesel) successfully without any issues to the same SD card. Wondering if there is something else wrong with the ls1b.pmm file or maybe my selection of PID's.
; (LSX|TrqRd)
*PSL_01
;
;Node PID Custom (Cap:Units:Prec:Fact:Offs:Inv) Alarm (min:max:style:time*10ms:hold*sec)
;---- ---------------- ----------------------------------------- -----------------------------------------
PCM, TP
PCM, VSS
PCM, RPM
PCM, GEAR
PCM, MAP
PCM, SPARKADV
PCM, KR
PCM, EST_TRQ_M
PCM, EST_XMSN_M
PCM, TRQENG
PCM, TRQTRANS
PCM, TFMPRS
PCM, TCCMODE
PCM, TCCDC
PCM, TCCSLIP
PCM, TFT
PCM, SHIFTERR
PCM, SHIFTDELAY
Total PID count = 24 channels
Don't know if anyone else has had any of these problems. Please post up if you are seeing the same issues that I am.