OK, a lot here so buckle up:
1.
First, you can tune without a knock sensor attached (with Err 43). Just won't get any knock retard if it's warranted.
That's what I thought, and that's why I had set the enable temp for knock retard to 151° to keep it from happening. When I first put the knock sensor in the truck leaving the knock retard on made it undriveable. That's why I tuned it out and intended to tune without it. Just fwiw.
2.
Your Err 42 must be corrected. Either you have voltage on the distributor bypass line at less than the cranking threshold RPM (generally 300), or there is no voltage on the line when RPM is > the cranking threshold RPM. Check all coil and distributor connections and those to the ECM. Something's not right.
Not sure what was causing this, think it may have been related to KS somehow. Changed the sensor over the weekend and this code is now gone as well. Verified on a drive tonight.
3. Your log indicates there is no spark retard when a knock is recognized. Need to correct #1 and #2 above before this can be reported.
Understood. Again, had purposely disabled the spark retard for sake of drivability until I could get that sensor changed.
4.
Spark reported in a log will never, repeat NEVER, agree with your Spark table. The code makes many adjustments. The main culprit in most masks is Low Octane retard. In $8d this can be disabled. I'm sure it can also be disabled in $0D, but I don;t know how. Search on how to do it if want to eliminate it. The low octane routine will always reduce SA by 1-2 degrees in most masks unless disabled. But really not a big deal if you know this is happening.
Have come to understand that (and your #5) through more in depth research. Agreed, so long as you know it is happening you should be able to compensate for it in the spark table. I guess to me though is the representation of the data just is kinda screwy? Seems like it should function as an HEI would where the curve is more or less fixed. Minus the ~10degrees of variable vacuum advance at the top of a traditional HEI distributor the mechanical advance stays the same as it is based on centrifugal force. Seems to me these modifiers overcomplicate things. I digress, now I understand that the stock vortec table showing 36° in some spots is truly only about 26°. It still surprises me that I have enough advance to be knocking. But after my drive tonight it appears this only occurs from ~2000-3000 RPM at WOT (90-100kPa) so I think I am going to pull a degree or two from those columns and see what happens. I suppose the vehicle that stock table is for could be a lot lighter than my pig Suburban and I have heard heavier vehicles sometimes need less timing due to the load?
5.
The spark in the Open and Closed Throttle Tables is not the real spark advance (TDC). For reasons unknown, in $0D the spark bias at 0x413c (9.8 degrees) is being subtracted from the value entered in these tables. Look at the conversion equation in the XDF and you can see the bias (correction "Y"=Main SA Bias") is subtracted. But the code also subtracts it when determining the final SA. This is why reported SA is low. You can prove the table entry by entering 40 degrees in the table and you'll see 30.1 degrees returned. I contend this is incorrect. Rather than the conversion formula being [(X * 0.351) - Y], I believe it should be (X * 0.351). Maybe someone who truly understands $0D will chime in as what is going on here. But this is the reason your history table (actual spark provided) is approx 10 degrees lower than the your spark table. But if 40 degrees in in the table and 10 degrees is subtracted by the code, you will be seeing 30 actual degrees in a TPro history table, which is what the ECM is seeing and what it should be. I'd change the conversion equation and increase all values in the open and close throttle SA tables by 9.8 degrees. See what happens. If not desirable, can change back.
There are a multitude of spark corrections in $0D. A spark correction is accomplished in the code by adding spark from a table to the total SA, and then subtracting a correction factor. Any difference adjusts SA +/-. This is done in virtually all GM masks. So if the table value equals the correction factor, there is no spark correction. The $0D corrections I see are below. Hex address in the bin are provided as opposed to XDF descriptions because the descriptions can be different among XDF files. The hex address in the bin calibration never changes. The XDF item can be accessed by opening the hex editor in TPro and clicking on the hex address. If the item is in the XDF, it will be highlighted in the item list. Clsoe the hex editor and click on the item in the list to access it:
$0D SA Corrections
a.
If EGR Active - Can reduce SA 3-4 degrees from table at 0x4855. Is not in the XDF so can't see it but can be added if needed. The default is to access the table with vacuum (0x4855, bit = 1) to get a value. There is no correction factor for this. Here's the table:
Code:
;~~~~~~~~~~~~~~~~~~~
;-EGR SA correction
;~~~~~~~~~~~~~~~~~~~
;
L4855 FCB 1 ;EGR load opt. byte, 1=vacuum, 0=%EGR flow
;
L4856 FCB 16 ;800 RPM, row offset
FCB 0 ;0 kPa, column offset
FCB 13 ;# cols per row
;
; SA = value x .351
;
; kPa: 0.0 2.5 5.0 7.5 10.0 12.5 15.0 17.5 20.0 30.0 40.0 50.0 60.0 ; RPM
;
FCB 0, 0, 0, 3, 3, 6, 9, 9, 9, 9, 9, 9, 9 ; 800
FCB 0, 0, 0, 0, 0, 0, 0, 9, 9, 9, 9, 9, 9 ;1600
FCB 0, 0, 0, 0, 0, 0, 0, 9, 9, 9, 9, 9, 9 ;2400
FCB 0, 0, 0, 3, 3, 6, 9, 11, 11, 11, 11, 11, 11 ;3200
FCB 0, 0, 0, 3, 3, 6, 9, 11, 11, 11, 11, 11, 11 ;4000
b.
Called "Alternate SA Correction" (this is actually a SA correction based on the difference between actual kPa and Barometric kPa) - The table is at 0x44CB and the correction factor is at 0x413E. In your bin, both are at 10 degrees, so no correction. By default, the table is accessed based on SD vacuum (option at 0x43AD) where bit =0.
c.
Main SA Correction - The Table is at 0x43B1 and the correction factor is at 0x413D (20 degrees). So at any given temperature, the table value is added to total SA and the correction factor is subtracted. Generally, unless there are extreme temps to be dealt with, the entire table should equal the correction factor to ensure there is no correction. Looking at your bin, there are a lot of corrections (mostly reductions) that may not be warranted.
6. Where did you get the ADX file you posted? Unless I'm missing something, neither Air Flow nor sensor frequency is reported. It's critical these be known in order to tune to adjust BLMs. Try using the attached ADX and you can add things in your ADX the attached ADX does not include [Accel Enrich, Power Enrich, etc.] (recommended for completeness).
That adx is straight from the TunerPro website under the $0D options. I am not sure that Air flow or sensor frequency would be a part of this bin? $0D can be run with a hack to use a MAF sensor, but in stock format is speed density only.
7.
Your bin does not have any air flow values in the frequency signal table at 0x6B89. This cannot be correct unless you are disregarding the MAF sensor input and running only in Speed Density Mode. Must correct. Look at another $0D bin for a starting point.
As above, I am not running the MAF hack and I am tuning in speed density only.
8.
Current BLMs in your log are reasonable. Some low, some high. Look at that below from my Analyzer program and you can see where corrections are needed.
Attachment 15930
Attachment 15931
There may be more, but that's enough for now.
HTH, Elky
