What's new
Ram Heavy Duty Forum

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Anybody Have Any Issues with the new HD's yet?

I checked it tonight after fueling up for the first time. Same result as BnO there.

Nothing but the EVIC image lighting up at one stop light - through I was also scrolling through it at the time. I have my chime disabled so only the little red belt indicator in the cluster and that big EVIC image once. I turned on the cruise and then the ACC as well (but did not set a speed duh) and nothing. I do have FCW set to only warn with lights and chime and lane assist set to low.

Maybe it's the Hemi or because it's a 2500? I know there's some things like TPMS that are different on the HD's but not sure if that one in particular was just for the 3500.

FYI, ACC can't seem to distinguish lanes very well. I had it on recently on a 4-lane divided state highway and it backed off aggressively (E brake was on) when a vehicle in the lane next to me slowed. I had it set to "close" in or whatever it's called too so I don't really trust it yet. I've heard reports of active FCW stopping vehicles going under bridges and for shadows and such so I don't trust that either. It all came with the 2020 Limited packages so it's not like I really extra for it or needed it. The lane assist seems to work pretty well although I haven't yet tested its ability to correct me. ;-)
 
Dialed her up to 30 MPH and... nuthin.

Thanks Burn'n Oil. I appreciate you checking that out. I think I have some sort of problem I went to Walmart this AM to pick up a precription. Started the truck, put the seat belt on....just like a normal person. Got up the road a couple of hundred yards and up come the FCW, Traction Control, and Anti-Lock brake messages. Went in at Walmart for about 30 minutes and everything was clear on the way home. I stopped on the side of the road about halfway home and put it in Park and disconnected my seat belt but did not turn the engine off. I put it in Drive and ran it up to 60 on the way home with no messages, no errors, all the way home. So since it went off this morning with the seat belt on and normal driving I think I must have a problem....an intermittent problem that will get me the old "we could not duplicate" routine from the dealership. I've already told the wife that the next time it does it, no matter where I am going, I'm headed to the dealership about 40 miles up the road and will sit there with the engine running until I get a service writer to see the messages and give me a work order saying they saw the messages.

Anyone know if a warning message like that in the EVIC sets a retained code in the computer that they can see even if the message has cleared?
 
I checked it tonight after fueling up for the first time. Same result as BnO there.

Nothing but the EVIC image lighting up at one stop light - through I was also scrolling through it at the time. I have my chime disabled so only the little red belt indicator in the cluster and that big EVIC image once. I turned on the cruise and then the ACC as well (but did not set a speed duh) and nothing. I do have FCW set to only warn with lights and chime and lane assist set to low.

Thanks brutal. Yep, I'm pretty sure I have a problem since all the messages came up again this AM with the seat belt buckled and normal driving. I hope those EVIC messages set a code they can see with their reader. If not I will be in for multiple "we could not duplicate the problem" visits to the dealership.

I have my Lane Assist on the lowest setting and it goes on and off like a neon sign on a liquor store on a state 2 lane highway with fresh lane markings. It's about as useless as teats on a boar hog.
 
Thanks brutal. Yep, I'm pretty sure I have a problem since all the messages came up again this AM with the seat belt buckled and normal driving. I hope those EVIC messages set a code they can see with their reader. If not I will be in for multiple "we could not duplicate the problem" visits to the dealership.

I have my Lane Assist on the lowest setting and it goes on and off like a neon sign on a liquor store on a state 2 lane highway with fresh lane markings. It's about as useless as teats on a boar hog.

Pictures or video or it didn't happen.

LOL, pretending to be the dealer...
 
Check all of your fuses and make sure they're all fully seated. If they are, you may have a grounding issue that needs the dealer to track down.
Thanks Burn'n Oil. I appreciate you checking that out. I think I have some sort of problem I went to Walmart this AM to pick up a precription. Started the truck, put the seat belt on....just like a normal person. Got up the road a couple of hundred yards and up come the FCW, Traction Control, and Anti-Lock brake messages. Went in at Walmart for about 30 minutes and everything was clear on the way home. I stopped on the side of the road about halfway home and put it in Park and disconnected my seat belt but did not turn the engine off. I put it in Drive and ran it up to 60 on the way home with no messages, no errors, all the way home. So since it went off this morning with the seat belt on and normal driving I think I must have a problem....an intermittent problem that will get me the old "we could not duplicate" routine from the dealership. I've already told the wife that the next time it does it, no matter where I am going, I'm headed to the dealership about 40 miles up the road and will sit there with the engine running until I get a service writer to see the messages and give me a work order saying they saw the messages.

Anyone know if a warning message like that in the EVIC sets a retained code in the computer that they can see even if the message has cleared?
 
Check all of your fuses and make sure they're all fully seated. If they are, you may have a grounding issue that needs the dealer to track down.

I checked the fuses the second day I had it. None of them were fully seated but they are all fully seated now. I think the first trick will be to find out if it is setting a permanent code when this happens or if the codes are clearing when I turn it off and let it reset. If they are clearing my only hope will be to drive it straight to the deal when the messages are displaying........leave the truck running.....and grab a service writer by the short hairs and force them to acknowledge the messages in writing on a service order. :)
 
I've got one more theory to check out before I take it to the dealer. As I stepped up in my truck today I had one of my many flashes of brilliance and decided to unplug my radar detector.....which sits mid-dash just left of center over the radio and plugged into the 12V lighter plug. I swapped the fuse position for that plug so that it turns on with the start button. Anyway, I unplugged the radar detector before I started the truck.....did NOT hook my seat belt...and drove about 5 miles to the gas station to fill up. I did not get any FCW, Traction, or Anti-Lock messages going or coming home. So I'm going drive it a week of so to see if there is any possibility my old Escort Passport might be interfering with the FCW. It's a long shot but easier than driving 40 miles to the dealer.

I wonder if anyone has had problems with a radar detector setting off the FCW.
 
I've got one more theory to check out before I take it to the dealer. As I stepped up in my truck today I had one of my many flashes of brilliance and decided to unplug my radar detector.....which sits mid-dash just left of center over the radio and plugged into the 12V lighter plug. I swapped the fuse position for that plug so that it turns on with the start button. Anyway, I unplugged the radar detector before I started the truck.....did NOT hook my seat belt...and drove about 5 miles to the gas station to fill up. I did not get any FCW, Traction, or Anti-Lock messages going or coming home. So I'm going drive it a week of so to see if there is any possibility my old Escort Passport might be interfering with the FCW. It's a long shot but easier than driving 40 miles to the dealer.

I wonder if anyone has had problems with a radar detector setting off the FCW.

Please be sure to keep us updated, @jerryw1000. We are more than happy to provide you with an additional layer of support if you do need to work with your dealer.

Mark
RamCares
 
I guess I can't say it's absolute yet but it appears my radar detector was causing the FCW, et. al. messages. I unplugged it for a couple of days and no messages. Then I moved it from the center dash over the radio to on the dash beside the driver's side A pillar 6 days ago. Maybe the radar detector, being directly over the radio, booting up and going through it's self test when the ignition switch came on it somehow interfered with the FCW/Traction Control/Anti-Lock Brake during uConnect boot up. The radar detector is still turning on with the ignition with the only difference being it is by the A pillar instead of being on top of the radio. Anyway...8 days now and no "unavailable" messages so I'll keep my fingers crossed. I hope that is all it was. I really wasn't looking forward to the techs pulling on wires and popping module on my new truck.
 
I had abs, traction, cruise control and something about “trailer” lights on. I wasn’t towing anything- tried a few re- starts but light still on- finally went off after 45 minutes of driving and haven’t come on since. Other than that it’s been great I love the truck.
 
I guess I can't say it's absolute yet but it appears my radar detector was causing the FCW, et. al. messages. I unplugged it for a couple of days and no messages. Then I moved it from the center dash over the radio to on the dash beside the driver's side A pillar 6 days ago. Maybe the radar detector, being directly over the radio, booting up and going through it's self test when the ignition switch came on it somehow interfered with the FCW/Traction Control/Anti-Lock Brake during uConnect boot up. The radar detector is still turning on with the ignition with the only difference being it is by the A pillar instead of being on top of the radio. Anyway...8 days now and no "unavailable" messages so I'll keep my fingers crossed. I hope that is all it was. I really wasn't looking forward to the techs pulling on wires and popping module on my new truck.
Radar detectors of old (80s, 90s) were notorious for their ability to generate electrical interference. Many were FCC compliant but still played havoc with vehicle electrical systems. Just something else to make ya go hmmm...
 
Found a leaky front shock yesterday at <14K miles.
That sucks but at least they can see the problem unless they tell you they need to see CEL first :rolleyes: I bought a new Dakota in 2000 and it didn’t even have a bottom shock bolt!:mad: That one had a clunk on the way home. Crawled under for a look see and had to just shake my head.
View attachment 3453
 
Radar detectors of old (80s, 90s) were notorious for their ability to generate electrical interference. Many were FCC compliant but still played havoc with vehicle electrical systems. Just something else to make ya go hmmm...


This one was newer than that...probably 2010 or so......but still a relatively cheap Escort in a plastic case and bound to emit some amount of signal. I run a Valentine 1 in my Jeep Grand Cherokee but just didn't want to spend another $500 on a new detector right now. I'll put that on my birthday wish list for next month.
 
Bilstiens or Fox 2.0 or Kings?

I am thinking about changing mine out closer I get to 20k


Sent from my iPhone using Tapatalk
 
Back
Top