PDA

View Full Version : Twenty Thousand Degrees Advanced



ericburgundy
07-18-2014, 09:40 PM
Hi, I'm new to the forum.
I have a problem I haven't been able to find a solution for.
94 GM TBI 7.4 Truck. 395 ECU BHDF Moates G1 adapter, Tunerpro RT.
I can rev up moderately just fine, but if I WOT from idle, it instantly reads 6375 RPM and 23000 degrees spark advance.
(about 1200 RPM by the external tach) It then backfires through the throttle body.
It does this with the stock $OE bin, I also tried a stock $OD bin with the same results.
This is in Open loop, map reading of 80, TPS 2.1 volts.
I replaced cap/rotor/wires to rule out secondary ignition misfire, but this seems more of a computer issue.
Could I have a bad ECU?
Could I have a bad Memcal?

other unrelated issues:
ECU reads the O2 constant 446mv, but I measure varying .90-.93v at the pin.
On hot restart, it struggles against the timing. Even though it's reading 0 degrees advanced.
If I reset the ECU by disconnecting the battery, it starts up with ease.
Has anyone seen this before?

Fast355
07-18-2014, 10:03 PM
Hi, I'm new to the forum.
I have a problem I haven't been able to find a solution for.
94 GM TBI 7.4 Truck. 395 ECU BHDF Moates G1 adapter, Tunerpro RT.
I can rev up moderately just fine, but if I WOT from idle, it instantly reads 6375 RPM and 23000 degrees spark advance.
(about 1200 RPM by the external tach) It then backfires through the throttle body.
It does this with the stock $OE bin, I also tried a stock $OD bin with the same results.
This is in Open loop, map reading of 80, TPS 2.1 volts.
I replaced cap/rotor/wires to rule out secondary ignition misfire, but this seems more of a computer issue.
Could I have a bad ECU?
Could I have a bad Memcal?

other unrelated issues:
ECU reads the O2 constant 446mv, but I measure varying .90-.93v at the pin.
On hot restart, it struggles against the timing. Even though it's reading 0 degrees advanced.
If I reset the ECU by disconnecting the battery, it starts up with ease.
Has anyone seen this before?

I wouldn't rule out a bad Memcal or ECM, but I would start by locating the ECM grounds and cleaning them as well as where they attach to the block. I am not as familiar on the 454 with their location, but on the same truck with a V6 or smallblock V8 the grounds are on the thermostat housing and on the rear of passenger side head.

ericburgundy
07-19-2014, 09:41 AM
Good call on the ground, and thank you for your response!
o2 is working and now i've discovered i was extremely rich.
I leaned out the VE tables and also rerouted the #7 plug wire away from the wiring harness in case it was causing interference. This has nearly cured the misfire.
I still have the hot start issue which feels like i'm overly advanced although I'm reading 0 degrees.
I'll have to get the wife to crank while I check with a timing light to be sure.
My gut says the memcal is faulty, even though I don't know exactly how it works.

1project2many
07-19-2014, 02:08 PM
You might have a mismatch between the ADX and the calibration. There's really no way the ecm should be sending a message for 23k degrees timing.

JeepsAndGuns
07-19-2014, 02:27 PM
I remember something like this happening to me once. If I remember correctly, I changed a spark advance setting, maybe a bias setting, and did not reset the ecm before I installed the chip and run it.
I just remember the spark advance number on my ADX jumping to some crazy stupid number and it running like doo-doo.
I have no idea if this has anything to do with your issue, but just figured I would share.

RobertISaar
07-19-2014, 05:46 PM
i get the feeling that the spark is being reported as a 16-bit value but someone never set the box for signing.

23,000/.35 = 65,714, which is right around the 16-bit limit, indicating spark is happening negative to reference(or TDC, i don't know the late TBI code too well).

ericburgundy
07-19-2014, 07:32 PM
I think Robertlsaar is on to something.
It makes sense that the ecu would try to retard the timing, but then mis-interperet the negative data.
It also makes sense that super-retarded timing wound backfire the intake.
Would a ADX make difference here?
Could you guys suggest/link one for my $OE bin?

steveo
07-19-2014, 07:53 PM
lets see the adx you're using it can probably just be fixed

also i really dont see why the calibration shouldn't be set up to clamp timing to 0 degrees minimum anyway. since when has a car engine actually wanted spark after top dead center?

RobertISaar
07-19-2014, 07:59 PM
lowish RPM, WOT with a quick throttle transition to get there(triggering burst knock protection or torque management in the process)?

i could see it going ATDC from that.

ericburgundy
07-20-2014, 05:37 AM
how do i upload my ADX to this thread?

1project2many
07-20-2014, 06:26 AM
If you click "go advanced" you'll be able to attach it as a file. Or send it to me and I can attach it.

ericburgundy
07-20-2014, 08:50 AM
My 3 files

RobertISaar
07-20-2014, 04:39 PM
well, i was right: 16 bit, but no sign.

try this out. it will likely fix the advance being reported incorrectly, but it won't help with how the engine is running.

EagleMark
07-20-2014, 05:28 PM
Do all 16 bit data have to be signed? Because the BPW is 16 bit and not signed too...

RobertISaar
07-20-2014, 05:43 PM
not required of all 16-bit, some 8-bit values are even signed at times.

if there is a value that can go negative and it doesn't have a negative offset in its equation, that is a good indication that it is a signed value. otherwise, you get the whole wraparound issue that happened here. if spark happened 4.9* BTDC, the raw value is 14 (14X.35=4.9). if it happened 4.9*ATDC, the same 14 comes into play, but it is subtracted from 65,535(or 65,536, i can never remember), so 65,535-14 = 65,521.

it's kind of like a compliment situation, except the MSB of the value determines the sign. 0-32,767 is positive and 32,768-65,535 is negative. with 8-bit values, 0-127 is positive and 128-255 is negative.

while the MSB is set(so, things are negative), the scales are reversed(large raw values are actually small real-world values).


it's still kind of confusing to me at times.

ericburgundy
07-20-2014, 07:32 PM
You're genius!!!!!
replayed the log with the new ADX, and what was 23000 SA is now -3.867
I have factory spec 4 degrees advance at the distributor. Does the computer factor that in, so in this instance we have 4 ATDC?
With timing that late, I could see the spark jumping to #8 cylinder.... = fireball.

What advance range should we be in with low RPM/WOT/low load?

ericburgundy
07-20-2014, 09:41 PM
At warm idle, the data says 10 degrees advanced.
But at the damper checked with a timing light its 4.
I have verified the marks are correct on the damper.
I have set base timing to 4 degrees with ETS disconnected.
Now I should either read 10 degrees with a light if the computer accounts for the base time,
Or 14 degrees if it does not.
Why the discrepancy?