DIY PROM Do It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.

ESC code 43 switch question

Thread Tools
 
Search this Thread
 
Old Aug 10, 2005 | 04:11 PM
  #1  
rons85's Avatar
Thread Starter
Junior Member
 
Joined: Aug 2005
Posts: 3
Likes: 0
From: Huntington.\, Ma.
Car: 1985 vette, 1978 K-1500
Engine: L-98
Transmission: 700R4
ESC code 43 switch question

Maybe someone here can offer some advice on this issue. This is not specifically an F-body problem, the car is actually an '85 vette... I dove into editing the eprom file a bit ago trying to eliminate the code 33 MAF error that I started getting after going to a larger throttle body (this is an '85 with a mild cam, OEM TPI, mildly ported heads, no cat, larger MAF, etc..).

The original mask or definition file I had ($1F - using TunerCat ) did not include the switch settings for any of the diagnostic codes. After mentiong to TC what I was trying to do he sent me an Updated file that now Does include switch settings (on / off) for the code 33 MAF, and also the code 43 ESC, code 32 EGR and code 24 VSS.

It appears that the MAF code 33 switch does, indeed, prevent that code from happening - at least I have not been able to make it appear since setting that switch to off, in Several versions of files I have tried so far.

I have doubts about the ESC code 43 switch, however. While experimenting with spark advance I have had the car drop out of normal (closed loop) operation and into Limp-in mode - under fairly heavy load, repeatedly - without turning on the SES or saving a code (nothing on the scan tool after the event). It Acts as if it would be a knock issue - as if it had seen a code 43, but not stored it. I cannot make the thing repeat the fault while monitoring the knock counts with the scan tool....nor does the scan tool (Snap-on MT-2500) display any knock counts under conditions that would cause the event if the scan tool was not connected (in diagnostic mode).

Is it possible that the switched bit is not actually preventing the code from triggering, but is only preventing the "display" of the code event? I'll be playing with identical versions of a program where only the code 43 switch is on or off to try and prove to myself that the triggering event causing the thing to drop into Limp-in is, in fact, the ESC detonation signal. If it is Not that signal (not a code 43) then I'll have to try and figure out what else is going on....
Reply
Old Aug 11, 2005 | 08:14 AM
  #2  
dimented24x7's Avatar
Supreme Member
iTrader: (2)
 
Joined: Jan 2002
Posts: 9,962
Likes: 5
From: Moorestown, NJ
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
The diag. masks prevent the code/error from being set and will also prevent some things associated with the code from being run. For example, no PE SA when code 43 is disabled.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
MustangBeater20
TBI
11
Oct 29, 2022 09:20 PM
89GTAOz
Tech / General Engine
13
May 16, 2020 09:31 AM
redmaroz
LTX and LSX
7
Aug 16, 2015 11:40 PM
Fronzizzle
Electronics
2
Aug 9, 2015 01:15 PM




All times are GMT -5. The time now is 11:44 AM.