Here I am

Rail Pressure Brief Intermittent Signal

Attention: TDR Forum Junkies
To the point: Click this link and check out the Front Page News story(ies) where we are tracking the introduction of the 2025 Ram HD trucks.

Thanks, TDR Staff

Aftermarket cruise control

First start after rebuild.

The root of this issue is that I get a very sporadic 10 Chimes and WTS light.
The truck has no codes set using my code scanner, or 3 on / 2-off ignition method.

By sporadic I am talking once or twice a year. This has happened after long hill decents but also while pulling ~ 6 - 10% grades under full load, towing ~10,000#’s with RPM’s at 2300 or so. It does seem to happen more when towing but the truck logs the most miles on towing trips so this may be coincidence.
It has happened when truck was empty as well but always during highway travel and at a steady rpm, not under hard acceleration.

I have never noticed any performance issues what-so-ever. Never a miss, no loss of power (except when it derates after the 10 Chimes), no excess smoke, no loss of mileage etc. The truck runs perfect as best I can tell.

I have read-up on the excess return flow issue and was planning to pay a shop to do the return flow test.
Before I did that I was thinking through what could cause the 10 chime “code”. It is my understanding that the ECM looks at rail pressure and uses the pressure transmitter to calculate flow rate.
Soo, I hooked up my code scanner as this also will display live PID data including rail pressure in KPA.

I have observed the following: The pressure reading is typically steady, it steadily increases as RPM increases and falls as RPM falls with some lag.

Here is what I am calling odd and am seeking feedback – At highway rpms for an extended amount of time ( 10 minutes or more) the Fuel Pressure will be steady in the 55000 KPA range, then at random times the fuel pressure reading displayed on the scanner will drop to something in the hundreds, say 700’s, it may bounce around that range for 3 -5 seconds then return to the 55000 range and stay there steady, a random time later this repeats.
This occurs randomly at different steady RPM’s ( cruise control set) and may happen every minute, or maybe every 10 minutes, its seems completely random. (Again no performance issues are ever noticed, even when towing in mountainous terrain)

The reading never seems to hang in the deviation low range for more than a few seconds

My current thought is that whatever is causing this low pressure reading may be triggering the 10 chime code if it happens to hang at the low range for too long.

I have removed, inspected, cleaned, added dielectric grease and reinstalled the Rail Pressure Sensor electrical connector. ( It looked very clean and rubber “boot” on connector appeared to already have dielectric grease on it – so nothing suspicious)
I closely inspected the connectors to the ECM for signs of rubbing, damage, oil intrusion etc. Nothing found. Disconnected batteries and removed ECM connectors, inside was immaculate clean, female sockets bright shiny brass. Cleaned with contact cleaner, dieltric grease around outside of plug and reinstalled.
Same observations remain.

I am suspicious of the Rail Pressure Sensor as I find it hard to believe that the actual pressure could be dropping this low without any sign of performance issues especially when pulling a grade. However, this would seem to me to be a very odd mode of failure for the sensor.

Has anyone seen these symptoms or have any comments ( if you were kind enough to read my whole post).

I have no problem replacing the Rail Pressure sensor but would like to try and verify beyond my knowledge or be able to test it before throwing a couple hundred bucks at it. Being it is so random it may be impossible to reproduce on any type of bench test???

Thanks - Jeff
 
When I got the intermittent 10 chime issue, changing the FCA fixed the issue. I didn't log rail pressure to see what it was doing but I would be suspicious of FCA over the sensor.
 
A lot will depend on year of truck you have and where you are reading rail pressure. Guessing it is off the data bus as you are referencing Kpa instead of PSI. Intermittent conditions of the data bus is usually a connection issue some where if you see no other indications. The reported pressure of 55000 Kpa at cruise also way off, that is barely above idle pressure and way low for cruise at 2300 rpms. Odds are you have some invalid info on RP being displayed.

There are codes stored, your code reader just doesn't have the capability to see or translate them. The calculation for leak detection is using RP and duration to calculate a fuel usage over time then comparing that to the duty cycle of the FCA and what it is providing for fuel volume. A divergence trips the DTC and chimes, if it happens more than 10 times in a set period it derates the engine.

An injector that is compromised internally by a worn seat, a scored pintle, or weak solenoid may never show signs on any available test before it melts a piston and fills the crank case with diesel. A random DTC for leaks is more concerning than a constant one that lets you KNOW there is an immediate problem. On the other hand, an LP that is starting to fail, an FCA that is not working as effectively as it should, a leaking rail PRV, and probably some more specific situations will cause a false positive for leak detection.

In addition to the above, pedigree and age of the injectors, existing filtration, lifetime fuel quality, consistency of additive package application all play a role in what the problem could be. There are some limited tests and basic replacement parts you can do as a stop gap, but, in the end the injectors are the likely source of the problem and there is no sure way to tell how critical it is.
 
Thanks for the reply and for reading my whole post. I suspected that there would not be a simple or straight forward answer. What fun would that be?? Right? I was hoping to see a reply saying "yes this is exactly what my pressure sensor did"

I add the following information to maybe provide a few more clues:

A lot will depend on year of truck you have and where you are reading rail pressure. Guessing it is off the data bus as you are referencing Kpa instead of PSI

Year 2006 - 130K miles
Have always used commercial diesel fuel ( no Bio, homemade, mixed, blended, or any other variants of fuel, nor fuel from construction / portable fuel tanks etc. n)
Run Stanadyne Jr every 2 - 5 tanks or so
Truck is bone stock, except for 2 mircon filter kit added between stock fuel filter and CP3. (Glacier Diesel Power Kit)
Rail Fuel Pressure Reading referenced is on my ODBII scanner connected to ODBII port

The reported pressure of 55000 Kpa at cruise also way off, that is barely above idle pressure and way low for cruise at 2300 rpms. Odds are you have some invalid info on RP being displayed

Agree overall that something is a-miss with these pressure readings.
I am not sure if it was truly 55K at 2300RPM. I have seen the Rail Pressure hover in the 70,000 and 80,000 range - I used the 55,000 as an example of steady higher pressure reading.
I could record actual pressure and RPM but I have a fuel pressure chart that was posted on TDR and again I agree the pressure data is whack all way around.

There are codes stored, your code reader just doesn't have the capability to see or translate them

I also can not see any codes using the ignition key sequence and trying to display the codes at the Odometer. Do they not show up there either? - So how can I see any stored codes? Can only the dealer get these codes?
Of note: I have seen DTC's such as crank position sensor performance that led me to change that sensor. Are the fuel related codes hidden or masked for some reason?

The calculation for leak detection is using RP and duration to calculate a fuel usage over time then comparing that to the duty cycle of the FCA and what it is providing for fuel volume. A divergence trips the DTC and chimes, if it happens more than 10 times in a set period it derates the engine

I have read your and as many other posts that I could find on the 10 Chime causes ( Thanks for all the info!!) - And your note here seems to confirm that the Rail Pressure Sensor data IS a variable in the triggering of the 10 Chime alert, and so,

I am stuck at first solving why I am seeing this pressure variation data. I am thinking that everything could be related to that. My reasoning is that by reading the Rail Pressure out of the ODBII port I would assume that this value is what the ECM ( or whatever is controlling FCA, calculations for return flow etc. ) is using to process fuel control and /or DTC related algorithms.

Perhaps as a next step it would be most beneficial to verify actual rail pressure using an external, independent gauge / gauge set-up.

Do you find it odd that even under full load towing up a significant grades that there is never a performance issue realized? I do this over and over without Chime issue or any performance issues. Then at a total random time - the old 10 chimer occurs. But only once or twice a year or 10-15K miles or so. ( I recently pulled a 2000mi. towing trip (~10K#) with no issues)

That is also why I am stuck thinking that the Rail Fuel pressure is perhaps normal but something in the pressure sensor, connectors, wiring, or ECM interpreting the signal is experiencing as issue.

Thanks again for any comments.

Jeff

Thanks for your comments on injectors. I have read many of these related posts too. All good information - Thanks.
 
Last edited:
What you see on the bus is not what the ECU sees, there is another step in there to put it on the CAN bus which in itself is questionable in an 06. Anything coming of the data bus in the first couple years of these trucks switching to CAN has been proven to be slightly less than accurate at times. For actual troubleshooting a good analog gauge is still the most accurate.

Starting with the 06's you need a scanner, one with current Dodge references, to see codes accurately. The odo window is totally unreliable as are a lot of generic code readers.

Rail pressure itself won't trigger the DTC's especially if the ECU sees it to far out of range. It will discard anomalous readings to a degree and if the readings are too far out of range you will get codes for rail pressure inconsistencies. If none of them are showing the ECU is likely seeing it correctly but it is getting scrambled on the bus or on the way there.

The ECU can compensate for wear to a degree to maintain power under a full load, not so much on coast operation though. It seems there are more indications on coast operation than high throttle for these DTC's. No real reason but that is the way it is. You have to check the things I suggested then decide form there, not always straight forward what the real solution is.
 
Thanks again for your input. That info changes my approach. I may do the independent rail pressure gauge set-up. This could never hurt to have for now or future issues.

I think I am going to drive it until I get the 10 Chimer again then get it to the dealer to see if there are any DTC's set. Sounds like this may get me closer if there really are codes that I cant see. With those codes perhaps all the other posts related to 10 Chimes will apply and I'll arrive at the excess return flow scenario. Which having that test performed is where I was headed in the first place.

Thanks Again for replies - This helps!!
 
The dealers in my area charge an hour of shop time just to hook up the scanner. That made just throwing a FCA from Geno's a wash on cost. So between the intermittent dings and occasional rail pressure code I took the chance and it fixed it. Just food for thought.
 
If there are actual codes and the calculation is suggesting a leak you will have P1222 and\or P1223 stored. They should still be there unless those will clear after a period of time automatically.
 
Thanks to all for continued feedback

Ipennock - I hate throwing parts at something in general but must admit this has served me well on a few occasions as it did you in this case.

SAG2 - Thanks. I am not sure I have this exact TSB. I have taken these to the dealer on other occasions and "enlightened" then with them. That's always discouraging but we always have to be our own advocate.

Thanks again.
 
FYI- Update on my instance of P1222

Cerb – Thanks for all the info. You def have written the most comprehensive explanation of this issue.

Noting that this issue is most prominent during motoring I was able to reproduce the DTC by engine braking over and over again down a big set of hills close by. Also, noting a generic ODB scanner may not capture all these codes once tripped I used the 3 on 3 off key method to try and retrieve DTC’s. I eventually got the P1222.

Sooo, back to square 1 on the P1222.

Noting that this code is still very sporadic under normal use I took Ipen advice as this info and I also talked with some local guys that had the same type issue and they indicated that they had spent extensive time / money troubleshooting this issue and on multiple occasions arrived at the FCA. Also, local ex-Chrysler tech told me he found these FCA’s a common culprit on lower mileage vehicles with known history of proper service and clean fuel use, and would change this first as for cost and effort its’s an relatively inexpensive cheap first step.

Against my principle of throwing parts at a problem I changed the FCA out as for < $100 and 15 minutes labor, this seemed logical.

It could be my imagination but it seemed to me that with new FCA the truck just ran better overall. Runs smoother, pulls harder etc. Tows better – seemingly more power. Again maybe my hopeful imagination.

After about 4 weeks I have been unable to reproduce the P1222 or 10 chime fault. I hooked my camper up last weekend and took an 80 mile ride finding every long grade I could find and engine braking all the way down over-and-over in an attempt to trip this code. So far I have been unable to reproduce the fault.
I am cautiously optimistic that this may have been the culprit but won’t be surprised if it’s not. Experience says usually nothing is this simple. But not being able to reproduce seems like a good sign especially since I was able to reproduce multiple times just before changing out the FCA.

I’ll update with any new info but it may be spring before any long heavy mountain towing.

Thanks again for the replies!!
 
Just a quick FYI. Approx 10K miles. A few short ( less than 500 mi ) towing trips.

No further instances of P1222 after FCA replacement.

Keeping my fingers crossed.
 
If you want to seriously repair your truck yourself then buy the Autoenginuity Software with the Chrysler Enhancement.

With that you are as close as possible to the WiTech.
 
Just for food for thought JCHrest. took me some time to figure out the same prob , fix was retorque fuel injector tubes is a must especially if you did a injector replacement, prob fixed :)
 
Back
Top