Quote Originally Posted by 1project2many View Post
Did I miss the reason why you aren't using a knock sensor?

You can deselct the code 43 flag to prevent the code completely but I'm not sure what side effects this creates. The older C3's would inhibit other functions if code could not determine the ks was present and working.
I'm not running one because I had read somewhere that a bad KS signal is worse than no KS signal. I will not be offended if you tell me I am wrong or that is a ridiculous idea.

Since AMC never had a KS in their V8s, I didn't think there would be a good KS to install. You're thinking the same thing I am about just disabling the flag (not sure what side effects this creates).
Quote Originally Posted by dave w View Post
There is the option to actually connect a knock sensor to the 19197427 computer. Instead of screwing the knock sensor into the block (where it is supposed to be). drill and tap a hole in the Jeep frame for the knock sensor to screw into. Once the knock sensor is securely mounted in the frame, connect the knock sensor wiring to the knock sensor. With the knock sensor mounted in the frame, code 43 will be PERMANENTLY disabled. Not all knock sensors are same, you will need a knock sensor for $OE. Having a knock sensor mounted in the frame, only disables Code 43. A knock sensor mounted in the frame will not protect an engine that is KNOCKING. No chip programming modifications required with a frame mounted knock sensor.


dave w
That's a good idea! Maybe I will grab one and mount it in my cab just because my KS wire was clipped about a foot from my computer and I do not want to have to run another wire through my firewall grommet (it's super tight already). Copy that (will not protect an engine that is KNOCKING). I am still running the stock timing tables and will be keenly aware to listen for knock.

Are $OE and $OD KSs the same? I am thinking of transitioning over to $OD...