Is a code 43 (ESC Monitor Error) common with aftermarket ignition systems? I am seeing a code 43 after a couple minutes of running the engine. My ignition is an Accel 300+ CDI box and coil. Could a faulty knock sensor throw this code? No knock counts show up in WinALDL.
EDIT: Just ran the engine and got knock counts. Idle speed at 1025rpm (cold idle) and idle MAP 53.1kPa. Initial timing in BIN is about 6 (OEM ANLU BIN). WinALDL is flashing green with 20 in the little square. Is that saying that WinALDL is logging and noted 20 knock counts? Also, when I first turn the switch to ON (not START) the SEs flashes once and then stays on.

 

you can try tapping your engine block with a hammer while the engine is running to see if you register a knock count, this would test the knock sensor. Also it is normal for your SES light to stay on when the engine is off and the key in the ON posistion

 

That's kinda what I thought about the SES light. I am still a little worried about the ESC and the knock counts. I think I'll try the hammer test. It seems to work for everything else...like finding rusted floorboards.

 

I've had, and a few others have had code 43s that were just random, try burning the chip again. Yes, this doesn't make sense.

 

The '7747 and '8746 ECMs attempt to force knock during PE mode, if knock does not occur a code 43 is set. Is your code 43 happening during wot/pe mode? Do you hear the engine knock at this point in time?

RBob.

 

No knock/ping is audible. The engine seems to be running well. This is happening at idle with TPS of 3.6%...no WOT/PE mode AFAICT. Just normal cold idle. Idle speed fluctuates arounf 975-1050rpm...livable for me unless I can make it better. Is the engine forcing itself into PE mode for some reason?
I haven't reburned the chip yet. I am still welding my cage up. I noticed this all when I was testing out the AutoProm using WinALDL. It worked well AFAICT. I got seamless data transfer. I'll log a few runs and post/send the files as required.

 

Then the ECM is setting an error code due too run-away knock. Have scan tool? Do the knock counts just run up and cycle back through (0-255-0)? Look for an open wire between the ESC module and the ECM. Can also be a knock sensor/wire that is picking up a lot of noise.

RBob.

 

I have WinALDL. I'll check the knock counts in a few minutes and let you know what I find. I have a log file from last night if you want to have a look at it. When I was running it last night, the SES stayed on. This probably isn't good.

 

Oh yeah...this is fixed now. Thanks guys!