Cummins Injection Status Codes

biggy238

biggy238

Active member
When logging my truck over the last year or two, I noticed that I was never crossing 130mm^3 cmd on the WOT pulls. I didn't give it much thought since i was trying to iron out some other things, but then I found a thread on EFI Live last night that was requesting information of fueling status codes.

As it turns out, my OS doesn't like how quickly I am telling the engine to accelerate, so it switches from code 7 (normal operation) Screenshot 2022-11-21 135545.png
to code 45
Screenshot 2022-11-20 212509.png

I was being old and fell asleep while i was searching for entry conditions that make the system switch status codes.
Something I am curious about is, I know that the file I'm currently using is not the one that I created originally as James that was helping me tune already had a tune that worked with the injectors that I purchased.
I will eventually hunt down what the OS is looking for and try to minimize it. The first thing that caught my eye was that it set when boost passed 70kPa but thats a very low number that would happen routinely during stock operation.
My next thought is RPM rate of increase.
Maybe someone has sorted this or just jumped OS and ignored the issue?

Image showing the status change, Also, something caused it to drop out of inhibit and go right back.
Screenshot 2022-11-20 215706 Markup.png

Here is the cummins status code document that was found on EFI Live
View attachment Fueling States 2013.zip
 
Well...... this looks grim. Looking at an older log with some decent power pulls, the ecm is going into code 45 "derate" any time the uS crosses the 1600 threshold. Here is a zoomed in view of a log that has 5 instances where it jumped from normal to derate.
Screenshot 2022-11-21 204245.png
Here you can see that the injection duration plateaus after having a consistent rate of increase which correlates to the status change.
Screenshot 2022-11-21 204547.png


This isn't going to be fun to tune if it can't get past 1600uS
 
Last edited:
95cummins5.9 said:
Break down the 1600uS. Please?
Click to expand...
So your injection events are made up of 3 components: Rail Pressure, Start of injection event (timing) and on-time, known as pulse width. Those 3 things electronically control the volume and atomization of the fuel delivered, injector physical characteristics determine this as well. This is important because if you run larger nozzles or entire injectors, the ecm doesn't know this, so you have to compensate by changing those 3 components.

I'm just noticing that when my fuel map calls for over 1600uS or 0.0016 seconds of on time, the operating system on this ecm is derating in an attempt to keep the engine from spinning up too quickly. I'm not the only one, several guys on EFI Lives forum have caught it too, but I didn't see a resolution there.

Sent from my motorola one 5G using Tapatalk
 
Last edited:
Screenshot 2022-11-26 184303.png
Log from today. I'm going to have to go after this CSP5 switch because I switch this to tune 5 with the V2 and it actually scared me a little.
On-ramp onto interstate, 30ish mph roll to 110ish, 3-4 shift.

You can see the rate of climb on all of the fuel related positions and then it switched to status 45 and everything lays over. It still pulled through but nowhere near what it is capable of with no derate.

I guess if anyone has info on this hit me up somehow since this part of the forum is tumble weeds.
 
0 00=not_set:
2 01=jcomtorq:
2 02=jcomsped:
3 03=psspeed:
4 04=pto:
5 05=usercomd:
6 06=limphome:
7 07=asgthrot
8 08=four_d:
9 09=cruise:
10 0a=rsg:
11 0b=lsg:12
12 0c=hsg:
13 0d=trqdrovr:
14 0e=lowgear:
15 0f=altderat
16 10=afcderat:
17 11=ancderat:
18 12=epf:
19 13=maxthrot:
20 14=jctrqder:
21 15=outogear:
22 16=crank:
23 17=override
24 18=engbrake:
25 19=oversped:
26 1a=stop:
27 1b=shutdown:
28 1c=fssderat:
29 1d=epfderat:
30 1e=asg_appl:
31 1f=alt_torq
32 20=msovride:
33 21=esuoillm:
34 22=ptoderat:
35 23=torqctrl:
36 24=ptpderat:
37 25=t2spd:
38 26=t2torq:
39 27=t2derat
40 28=noderat:
41 29=atderat:
42 2a=ptthlm:
43 2b=ssambtdr:
44 2c=tscooldr:
45 2d=torqmgmt:
46 2e=ctderat:
47 2f=freeaccl
48 30=vgtdrate:
49 31=ofcstate:
50 32=afrstate:
51 33=rmg:
52 34=airdenlm:
53 35=chifullm:
54 36=tfcderat:
55 37=grossovr
56 38=chmderat:
57 39=jcptpder:
58 3a=ofcderat:
59 3b=nettorq:
60 3c=tvalimp:
61 3d=lofprder
 
I am duking it out with mode 45 as well (2006 CM849a).

As I am at the starting line and start to build boost, the ECM enters mode 45 and limits the command to 115 mm3. Mode 45 exists until I breach 25 mph.

I discovered this issue at UCC/ ODR this year. Went to a local track, took data and saw what the issue is. I think it's due to my bumping in to the lights. I did some staging in my driveway and the issue does not exist. Went to SDX and the issue came right back. I race on DR2's and completed the driveway stage on set of street tires.

Spoke to Larson at SDX, he thinks it's OS related, like what you're stating. I am using OS 55352409.

My truck is put away for the winter. My plan is to track down a few more OS's and then build a few files to see if it is indeed OS related.
 
That's where I stopped, I don't have anything older than 602 and 409.
One of my last logs indicated 115mm^3 as well.
On a side note, I thought I was formatting a Nintendo switch SD card and formatted my EFI card with my latest tune and recent log files.
I rebuilt the tune from an older revision but no more log files.

Sent from my motorola one 5G using Tapatalk
 
RD TRCTR said:
I am duking it out with mode 45 as well (2006 CM849a).

As I am at the starting line and start to build boost, the ECM enters mode 45 and limits the command to 115 mm3. Mode 45 exists until I breach 25 mph.

I discovered this issue at UCC/ ODR this year. Went to a local track, took data and saw what the issue is. I think it's due to my bumping in to the lights. I did some staging in my driveway and the issue does not exist. Went to SDX and the issue came right back. I race on DR2's and completed the driveway stage on set of street tires.

Spoke to Larson at SDX, he thinks it's OS related, like what you're stating. I am using OS 55352409.

My truck is put away for the winter. My plan is to track down a few more OS's and then build a few files to see if it is indeed OS related.
Click to expand...
So ... I had a random thought today on my way home.

We aren't able to change the threshold for when the sensor rationality code sets, P0191.

I need to test it, but I bet the ECM is limping as soon as it thinks the rail pressure is out of control.
The only fix for that is to go back to the stock pressures for the 849.
I scaled and utilize up to 180 on my maps, but I think it limps at 130

Sent from my motorola one 5G using Tapatalk
 
Can anyone confirm the set condition and reaction for P0191?

Sent from my motorola one 5G using Tapatalk
 
OK, hode on...

Are you thinking that rail pressure is causing the Mode 45?

According to ProDemand, P0191 sets when the fuel pressure sensor reading at key on does not match the expected fuel pressure reading at key on.

My experience with P0191 is to replace the rail pressure sensor and the issue is addressed
 
RD TRCTR said:
OK, hode on...

Are you thinking that rail pressure is causing the Mode 45?

According to ProDemand, P0191 sets when the fuel pressure sensor reading at key on does not match the expected fuel pressure reading at key on.

My experience with P0191 is to replace the rail pressure sensor and the issue is addressed
Click to expand...
I was grumbling about the status 45 after a hard pull and decided to check codes and found that. More wanting to rule it out as a cause. After I cleared codes, it did not reappear even with it pulling fuel at wot immediately the code clearing

I think Mode 45 is torque management and reacting to rate of change of the engine rpm.

Sent from my motorola one 5G using Tapatalk
 
i know wnothing of this but cant ya fool where the reading is coming from maybe with a resistor or something? just so it cant make the limp limit?
 
biggy238 said:
I was grumbling about the status 45 after a hard pull and decided to check codes and found that. More wanting to rule it out as a cause. After I cleared codes, it did not reappear even with it pulling fuel at wot immediately the code clearing

I think Mode 45 is torque management and reacting to rate of change of the engine rpm.

Sent from my motorola one 5G using Tapatalk
Click to expand...

Gotcha.

As we have already discussed, apparently some OS's struggle with it and some don't.

With race season quickly approaching, this has been on my mind. I have not dug through CalTerm yet, am planning on trying all of the OS's that I have and see if I can get consistently lucky. If not, I will be going digging.
 
RD TRCTR said:
Gotcha.



As we have already discussed, apparently some OS's struggle with it and some don't.



With race season quickly approaching, this has been on my mind. I have not dug through CalTerm yet, am planning on trying all of the OS's that I have and see if I can get consistently lucky. If not, I will be going digging.
Click to expand...
What exactly can calterm do?

Sent from my motorola one 5G using Tapatalk
 
You must log in or register to reply here.
Back
Top