Just got my Crossfire back from the dealer and guess what, it wasn't fixed. As I mentioned before, they stated that the check engine light never came on for them, but I can assure you it was on when I pulled into the service bay. They worked with the Chrysler Service Center and admitted that they didn't have any idea what was wrong. They reset my O2 sensors and told me not to worry if the check engine light came back on because it wouldn't negatively affect the car's performance. When I picked up the car, the check engine light was not on, however, about 3 miles down the expressway, there it was again. Unfortunately, it was just after 5pm, so with rush hour traffic, there's no way I could have made it back to the dealer before they closed at 6:00 pm. As soon as I got in the door, I called them just to let them know the check engine light was back on, and I was told again not to worry. I'm not sure what to do next. To the dealer's credit, I was not charged for the time they were looking into the issue, but I did have to pay just under $90 for the 3 days I had their rental car. I'm contemplating going to another 5-star dealer that's close by and get a second opinion, but I don't want to drop any more money on a rental. Anybody have any ideas?

 

My Crossfire came with free rentals any time the car is in for warranty service.

 

Shocker, they cant find a thing wrong and cant get it to 'act up' as they say, no codes have been stored in the ECU. They will check for TSB's and let me know tomorrow. I guess i'll be getting the car back...

 

Just another update - Mine died again, this time at a stop light on my way to work. Once again, it started right up. I called the dealer (not the dealer 300 miles away that I purchased the car from), but my local dealer and they said they were working with a Chrysler Service Rep, but could not do anything to help me at this time. I once again asked if driving my car would make things worse, and the answer was no. I'm really afraid that this is going to come back and bite me in the as*. So, now what, do I head to another dealer, contact Chrysler directly, wait for a resolution? I think I will call the dealer I bought the car from and see what they have to say.

Hey Britt1 - Just curious, how many miles/km do you have on your car? I'm just under 50,000 miles.

Also, I'm not sure who is running this site now, but what do you think of creating a section for the Chrysler reps that pop up from time to time, so they can easily find our current concerns/problems? Just an idea.

 

I have 40K miles on the car now...I bet you this turns into a common Xfire problem. Still think its CPS...you can check out this...I just posted as a 04' slk (pretty much is).

http://www.benzworld.org/forums/foru...223342&posts=8

There are lots of issues similar to the ones we are having and all roads lead to the CPS, however he CPS doesn't seem to always turn he check engine light on...I may tell them to go ahead and change it tomorrow (if they can get the part). What's a couple hundred bucks to get it out of my head.

There are two common SLK problems that are very similar symptoms to the ones we are getting. One was the CPS (or CKP as MB call it) and the second was the K40 relay (which they apparently re-designed a couple of years back, having a hard time confirming that).

I think the owner of the site Mighty, went away awhile back, but maybe he is still around. I know Andrew is a moderator but i'm not sure he can set up a new forum subject.

I'll keep you updated so please do the same.

 

i do have the ability to add another forum subject...but i would like to speak to mighty prior to doing so.

i'll keep you up-to-date.

cheers!

 

after reading this thread, was there a final resolution?

 

No resolution, I will pick the car up from the dealer tonight and continue to use it as normal. They cannot reproduce the problem. The dealer was kind enough to not charge for the tests they have done. So far and i just have to keep them posted as to any troubles i get, if or when they happen again.

 

I had a similar problem with a SAAB 9-5 that would die going 60. After a couple of tries to fix it, the dealer had to buy it back under the Texas Lemon Law. Kind of a safety issue.

 

FYI, Try to pay attention to the cars voltage, when it is feeling like it is maybe sluggish. I had they same things going with my car. What started out light, it then built into me being able to reproduce the drop points when ever I had the radio on, my cell plugged in & hit my brakes, The harder I pushed on the brakes, the lower the power drop would go. Somewhere in the ECU's protocol, it's just not shaking hands with the other modules. So here's what my guess is on what's happening. I think that all the different makes of ECU/MAF/Transmission Control module. Example : The ECU' has a mix and match set of chipsets, There is Texas Instruments, & Bosch's in house, & AMD, Now I can't remember off the top pf my head what Chip sets Siemens uses, but What I am getting at is. Not all of those are all compatible with each other. They may be compatible depending upon on the sequencing that is caused by the conditions that the sensors are reading. Now the other thing is Backwards compatibility, Sometimes protocols will not be able to come together and work as one under normal traditional binary coding. Sometimes you can get lucky, and have one of the two different chipsets be backwards compatible. Its kind of like the saying "opposites attract". So I think if maybe all the components were running under the same Protocols, because they are all from the same manufacturers (Siemens, Bosch, Texas, etc...) Then there wouldn't have to be any piggy backing, or daisy chaining. So the likely hood of something missing a mark, and causing flags to go up, which will only make the computer that much more sensitive causing a virtual domino effect. And it is all very easily done by just one part of the linked system, to miss just one assignment. And causing catastrophic problems.
Don't hold me to it though, It's just what I have encountered in building computers. I understand a motherboard in a PC, I haven't had to much experience with the Mini-Module Boards.

 

What!!!!!!

 

Just wanted to give you an update, I removed the crankshaft position sensor on Saturday (6 mm Socket and it slides right out). Cranked the engine without it and it cranked but didn't start (check engine light came on). Put the new CPS in the motor connected it back up. Cranked the engine (still has check engine light) motor started & took it for a spin. I then left it for 24 hours. Got in it this morning no check engine light and no problems on the way to work, seems to idle steadier. Noticed one thing while changing the CPS, there was a louder ticking noise coming from the cylinder closest to the drivers side back of engine..thinking i may change the plugs or at least get them out to have a look at them. I'll prob listen again once i get home after work to see if its still there after this extended run since replacing CPS. I'll keep you updated as im sure i haven't heard the last of this... The part was $52 from a Non official merc online dealer, its like $115 from DC.