tunerpro shows timing of 23038.6

[pima.1971]

Under wide open thottle, TPRT shows timing to be 23038.6 degrees:whatever: @3000rpm and up. But I'm also getting knock counts but no retarding showing up.
AFR is rich at 11.7

Can running too rich cause knock? Don't think so, but I thought I'd ask.

Is this the computer retarding timing below zero and this is how TPRT interprets it.

All input is appreciated.

94 5.7 ecsb z71
7427 ecm

[1.721afr]

Under wide open thottle, TPRT shows timing to be 23038.6 degrees:whatever: @3000rpm and up. But I'm also getting knock counts but no retarding showing up.
AFR is rich at 11.7

Can running too rich cause knock? Don't think so, but I thought I'd ask.

Is this the computer retarding timing below zero and this is how TPRT interprets it.

All input is appreciated.

94 5.7 ecsb z71
7427 ecm

It's starting to sound like you have the wrong .bin or adx loaded, too much stuff ain't right.

[pima.1971]

Afr is a standalone unit. Doesn't give me that timing reading at part throttle at those rpms. The bin and adx appear to work fine datalogging through out the rpm range. I was out doing a log during wot. AFR progressively got rich. Timing started showing funny readings around 3k rpms. Back off the throttle a little and timing comes back in to about 10 degrees. Bin and adx is originally from tunerpro website. No changes to the adx. VE tables are being changed in the bin. Keepem coming. I bet somebody else has seen this before.

[1.721afr]

Pop a spare module in there to eliminate that as a problem.

While you are there give the pickup an ohm test and good eyeball for problems, as well the module/pickup (twisted pair) wires and connector.

Those parts would have the greatest likelyhood of failure caused problems. Ground failure can cause symptoms like this but usually affect all readings.

Finally RF (radio frequency interference) can cause data scatter, make sure no sensor or computer wires are close to high voltage secondary.

[pima.1971]

It was negative timing. In my attempt to start looking at timing, I had zero'd out "CTS Spark Advance Compensation vs. Vacuum vs. Temperature" table but did not zero out the"Coolant Spark Bias" scalar. So my timing was going into the negative at certain areas if my SA table was not above 20degrees. Now I know. It does the same with the EGR Bias and other Bias stuff I imagine.