Bonjour. Lots of info and parts changed. What was the reason for a clock spring replacement ?

 

50% of the time...
Just out of curiosity, do all brake lights work all of the time?

 

my 2013, 500sport was doing the same esc/hill assist unavailable and could not get the car out of park ,I replaced the brake switch and bingo everything went back to normal i see you also changed the brake switch but no luck, could the rear hatch wire loom be compremised not sure what else could cause this

 

Dealer had said their techs recommended replacing the clock spring. I don't know why they determined that.

It is at a different dealership now. Getting the recall taken care of so I had them diagnose the error since they'll have it for several days. They said just now it is a bad sensor according to their techs and they have an active code. Parts, labor, tax, it's another $1200... and with no guarantees that this will fix it. They've had it a week now, and it looks like they will have it another week or so.

I would have no idea if the brake lights are working or not other than the dash error when one burns out. They were only checked after the switch was replaced.

I haven't checked the wire loom. I was too afraid that I wouldn't get the plug back in. I had that issue with my previous car. So I didn't want to mess with that.

Hopefully this will be the last time I need to take it to a shop, at least for a while. I'll keep you posted. Thank you for the replies.

 

So far it has been 3 days without the errors. The dealership said it was a sensor that had an internal failure (Yaw Rate Sensor - Mopar (68073504AA)). With labor the bill came to $976.57! Why couldn't have been the brake light switch??? Oh well, as long as the error is gone for good, I'm okay with it. I hope this helps someone out there!

 

Never mind! It started up again 2 days ago! So that money was wasted. It didn't come on yet today though, but it was on for a day and a half. Dealership isn't returning my messages.

 

that stinks boy they sure can take the money and not return your messages

 

Update: I took it back again after they FINALLY returned my message. They had it for a week but did not do anything. They say my OBDII port isn't working so they had to go behind the DLC to get their diagnostics. That can't be true since I run a HUD through OBDII port without communication errors. They claim my after-market reverse camera or my HUD are causing the error. So another $262.03 later I have my car back with everything unhooked. I'll drive it, but I have had this error weeks and months before adding those "after-market item" to the vehicle. Side note: the HUD is the very same one I have used on my last two cars without incident. But FIATs are notorious for being finicky, especially with electrical so it is possible I suppose. It could very well be the ORIGINAL cause of these faults were fixed, but on-going because of one or both of these ad-ons. I'll err on the side of caution for now.

IF, and I say IF, on the off-chance the HUD is causing the faults, I surmise it happens during the car's initial start up when the computer is checking everything. The faults only come on during the first 10-15 seconds, when they do. They won't come on during a drive. Whatever is causing the faults may be borderline on the programmed fault threshold. That being said, what do you think? Would a kill switch to the OBDII port prevent faults? I'm thinking when I turn the car off, I also kill the OBDII. Then after I start the car, and after the initial diagnostics checks, I switch the OBDII port back on with the HUD. Now if the faults are logged when driving instead of during start up, then I should see the errors after starting the car back up after running the HUD, regardless of if it was off during start up. If I remain error-free, then the faults are only checked during start up and not during driving.

There is one more point to consider I have failed to menton. I have a Y-splitter on my OBDII port. One port goes to the HUD; the other, a bluetooth OBDII scanner. There might be a chance that either the Y or the scanner, or combination, could be the cause. I might have to try each one independently until I get a fault. Thoughts? I just find it strange that I would get this SPECIFIC error for a non-related component. Unless somehow the OBDII is preventing communication from the sensors on the ESC and Hill Start assist.

As for the reverse camera, I can change the power source to the cigarette lighter vs the fuse panel. That would elimiate that anyway. The only thing is, I run a 3-port lighter / 2 USB port adapter on it. I use at most, one USB for charging my phone and one cigarette lighter port for my dash cam. I don't want to overload the fuse by adding power to a reverse camera. Thoughts?

 

Did you ever end up figuring this out? I’ve had the same issue for years, and I’m getting tired of it. I have replaced the battery ground, and the earth strap (because they both literally broke in two). So my issue shouldn’t be a ground issue. I’m going to swap the brake lamp switch, but looks like you tried that with no success.

 

Looks like it’s a pain in the *** to get to though

 

lol yes it is, have a young person do it upside down and tight spot are not ment for older folks I am 60 and had my daughters boyfriend crawl under the dash and replace it for me even he was struggling lol