Monkeywithawrench
Senior Member
We have a 930M loader, PN KTG00960
Been having issues with it going into 'Safe harbor mode' (This is derate/ limp mode) since this past fall.
I keep getting codes:
E1389(2) Aft 1 SCR OPERATOR INDUCEMENT
First 9781.5 Last 9835.3 Count 3
E1389(3) Aft 1 EMISSIONS FAULT
First 9781.6 Last 9835.4 Count 4
E1389(1) Aft 1 SCR OPERATOR INDUCEMENT
First 9766.5 Last 9835.2 Count 6
E1410(2) AFT 1 CONVERSION EFFICIENCY INVALID
FIIRST 9766.5 LAST 9835.2 COUNT 6
This is when it first started:
(These are my service notes)
10/10/23 9782 Codes for SCR operator. E1389(2) and E1410(2) active events. Machine in SAFE HARBOR mode. Run After Treatment Functionality test. Codes clear…………..unknown why or what caused it.
WHAT THE f**k??!!!
Create warranty report and create product status report for review later. It's 7pm!!!
Latest incident was last night:
2/20/24 9894H Codes for SCR operator…again. E1389 (1), E1389 (2), and E1410 (2)Invalid Aftertreatment #1 SCR Conversion Efficiency. active events. Run after treatment functionality test.
60H since last reset………..need to figure this out.
DPF SOOT LOADING @ START 79.85%
FINISH 26.19% SOOT LOADING
Functionality test success………..codes cleared!!
So I'm getting between 40-60 hrs running time on the machine between it going into limp mode. Every time it goes into limp mode I just run a After Treatment Functionality test and the codes clear. There is no direct indication as to what is causing this......sensor, SCR pump/module, etc.
I've talked to the CAT Tech help line a few times. This guy is knoweledgeable ........and sadly, he is going to retire in a few weeks. He is at a loss........other than to start shotgunning parts at it. One thing that did strike me as odd..........he was VERY SUPRISED I was able to get it out of Limp Mode by running the After Treatment Functionality test. He said it usually locks the ECM out and you need to enter the SUPER SECRET CAT FACTORY PASSWORD to get it out of limp mode.
So I'm just wondering if anyone else has run into this issue and what they found the problem to be??
Nige........any guesses on this one??
Been having issues with it going into 'Safe harbor mode' (This is derate/ limp mode) since this past fall.
I keep getting codes:
E1389(2) Aft 1 SCR OPERATOR INDUCEMENT
First 9781.5 Last 9835.3 Count 3
E1389(3) Aft 1 EMISSIONS FAULT
First 9781.6 Last 9835.4 Count 4
E1389(1) Aft 1 SCR OPERATOR INDUCEMENT
First 9766.5 Last 9835.2 Count 6
E1410(2) AFT 1 CONVERSION EFFICIENCY INVALID
FIIRST 9766.5 LAST 9835.2 COUNT 6
This is when it first started:
(These are my service notes)
10/10/23 9782 Codes for SCR operator. E1389(2) and E1410(2) active events. Machine in SAFE HARBOR mode. Run After Treatment Functionality test. Codes clear…………..unknown why or what caused it.
WHAT THE f**k??!!!
Create warranty report and create product status report for review later. It's 7pm!!!
Latest incident was last night:
2/20/24 9894H Codes for SCR operator…again. E1389 (1), E1389 (2), and E1410 (2)Invalid Aftertreatment #1 SCR Conversion Efficiency. active events. Run after treatment functionality test.
60H since last reset………..need to figure this out.
DPF SOOT LOADING @ START 79.85%
FINISH 26.19% SOOT LOADING
Functionality test success………..codes cleared!!
So I'm getting between 40-60 hrs running time on the machine between it going into limp mode. Every time it goes into limp mode I just run a After Treatment Functionality test and the codes clear. There is no direct indication as to what is causing this......sensor, SCR pump/module, etc.
I've talked to the CAT Tech help line a few times. This guy is knoweledgeable ........and sadly, he is going to retire in a few weeks. He is at a loss........other than to start shotgunning parts at it. One thing that did strike me as odd..........he was VERY SUPRISED I was able to get it out of Limp Mode by running the After Treatment Functionality test. He said it usually locks the ECM out and you need to enter the SUPER SECRET CAT FACTORY PASSWORD to get it out of limp mode.
So I'm just wondering if anyone else has run into this issue and what they found the problem to be??
Nige........any guesses on this one??