Sy#26 said:
Delay time for boost reduction on my ECM seems to correlate more w/ 0x03A2, KWGMAPTM - High Load Fuel Shutoff Time Threshold - being @ zero seconds.
Anybody running a benchtop ECM? Seems my MAP data values (like @ what MAP something happens) differs from benchtop to truck by almost 2psi. Huh?? ADC variations? Sure like to get them to read the same.
Barry - Sy#26
Bangor, MI
This from the code:
d90c b6c3a3 Rd90c LDAA BST_FCUT_H
d90f 13b62003 BRCLR #$20,BST_MODE_FL,Rd916 ;*+$07
d913 b6c3a4 LDAA BST_FCUT_L
d916 913f Rd916 CMPA MAP_KPA
d918 2418 BCC Rd932 ;*+$1a
d91a 96ad LDAA LZad
d91c b1c3a2 CMPA KWG_MAP_TM
d91f 2405 BCC Rd926 ;*+$07
d921 4c INCA
d922 97ad STAA LZad
d924 200f BRA Rd935 ;*+$11
d926 14b620 Rd926 BSET #$20,BST_MODE_FL
d929 142b01 BSET #$01,Z2b
d92c 4f Rd92c CLRA
d92d 5f CLRB
d92e dde2 STD ZNe2
Basically, what happens above is that if the high threshold ($c3a3) is
exceeded, a flag is set to indicate that it has been exceeded since the
last time we were in this loop. It then compares the current value in the
timer at $ad, to the timer value at $c3a2. If it's less, it increments the
timer, and waits for the next loop.
Once the next loop comes around, if MAP has dropped below the low
threshold ($c3a4), the timer gets cleared, and the whole process
starts over again.
If the MAP is still above the low threshold, it once again checks the
timer against $c3a2. If the timer exceeds this value, it clears out the
injector BPW, and cuts the fuel. This *will* make the MAP go below the
low threshold, and fuel resumes. This is what causes the "buc-buc-buc"
when the cutoff is hit... the continual cutoff/resume/cutoff of fuel.
I've noticed similar things regarding MAP scaling being off... I'm wondering
if it's a function of the scan tool, rather than the ECM, though.
Later,
Dig