That was quick...

"Of course I'll get some time with the tech to get details on the fix."

Good luck with that. I'm pretty sure you'll get a shoulder shrug and a statement to the effect of "this issue should be cleared up in the next software update." I hope I'm wrong (please let us know), but I doubt it.

Hokie,

My check engine light has been on since the day I got the Karma. It's almost certainly a function of a software issue, not an actual problem with your vehicle. When I got mine I had the dealer pull the codes and assure me of such. The current software version, 6.14.2, resolved a lot of the spurrious CEL problems but not yet all of them. Your dealer can probably reset the CEL, but it may come back on until 6.15 or another software update. Think of it as a quirk and an idiosyncracy for now that is annoying, but in my opinion not worthy of much concern. The only drawback is not getting the digital speedo in Sport mode while the CEL is on, and of course having to look at it.

Brent

CEL might be the most common problem. I'm not taking mine back to the dealer until the next software release.

My car had an actual plumbing issue that caused the CEL to come on, but that also caused erratic engine behavior. If the drive system is behaving as you would expect, you can lower the steering wheel just enough to cover the CEL -- and problem solved. But if the car is doing anything unexpected, like the ICE running in stealth mode when it was not supposed to, then have the dealer check it out.

There is a software glitch in the EVAP test that is causing a false fail condition which turns on the check engine light. Sometimes a hard restart will clear it.

Nimisys said:

There is a software glitch in the EVAP test that is causing a false fail condition which turns on the check engine light. Sometimes a hard restart will clear it.

Click to expand...

I'm wondering if the software guys have a good simulator on which to test the software ... something like Simics, only for all the various sensors and CAN-busses and so on.

If not, someone should write one.

In this case its more of an unexpected hardware situation. Through running one of the EVAP tests they are trapping a pocket of pressure in an evap line that is greater than spring pressure of one of the solenoids, causing it to become stuck. It then doesn't see a pressure change like it should and assumes the solenoid valve is bad and flags the check engine light. A software change to prevent pressure above a certain point seems like the obvious solution, however since it's EVAP related it has to go through EPA what-not before release, so the timing takes a bit longer.

Nimisys said:

In this case its more of an unexpected hardware situation. Through running one of the EVAP tests they are trapping a pocket of pressure in an evap line that is greater than spring pressure of one of the solenoids, causing it to become stuck. It then doesn't see a pressure change like it should and assumes the solenoid valve is bad and flags the check engine light. A software change to prevent pressure above a certain point seems like the obvious solution, however since it's EVAP related it has to go through EPA what-not before release, so the timing takes a bit longer.

Click to expand...

Oh.

A stiffer spring is the other obvious answer but presumably that too would require EPA approval, plus of course all the existing cars needing retrofits (expensive).

In this case, they are using a common OEM solenoid valve (seen it on a few different manufactorer vehicles) that is mounted in an area that is fairly labor intensive to replace. I doubt you will see the need for hardware replacment, just an adjustment to the test procedure through the software to prevent it from occuring.

LonePalm,

I would, in my opinion, not drive around with the MIL illuminated as it would possibly mask any future issues that really are issues. I have the same problem with my Subaru WRX Wagon often throwing a P0420 at me because I put on an aftermarket hi-flow cat exhaust and never had it tuned for that, but everytime the MIL comes on I use my installed ECUtek monitor to read the code immediately and reset the ECU at the next stop to clear the light, so that I may see when something else goes wrong.

kabalah70 said:

LonePalm,

I would, in my opinion, not drive around with the MIL illuminated as it would possibly mask any future issues that really are issues. I have the same problem with my Subaru WRX Wagon often throwing a P0420 at me because I put on an aftermarket hi-flow cat exhaust and never had it tuned for that, but everytime the MIL comes on I use my installed ECUtek monitor to read the code immediately and reset the ECU at the next stop to clear the light, so that I may see when something else goes wrong.

Click to expand...

Kab,

I had the dealer pull the codes and confirm that the issue has nothing to do with the ICE or the exhaust system. It is a battery control module "requesting a MIL indicator" with a specific code they are familiar with. It is a sensor/reporting error only, not an inidation of an actual system fault. There's no reason to ground the car with what is confirmed to be bad idiot light.

I do agree though that if you get a CEL/MIL you should have your dealer pull the code to see why, as it may in fact be a real issue.

Brent

Are you saying that the dealer read and reset your code and it came back and they read it again and it was the same code again? Meaning that it is going to continually generate the code everytime you reset it? So they tell you not to worry about it and just keep on driving? That would be completely unacceptable to me. Either there is a communication problem in the CAN bus or you have a faulty module, IMHO, as I do not see that being a fault that everyone is reporting.
But it is your car and if you are happy with it, I just don't want something like what happened to siliconkiwi to happen to me.

There is a DTC that will be in the BECM (battery module) that causes the CEL/MIL to come on, but requires a Fisker engineer or FSR to come out for to reflash that module directly and depending on their scheduals, it can be a few days to a week for them to come out. it is a software checksum error, so it has no negative affects on driving.

Nimisys said:

There is a DTC that will be in the BECM (battery module) that causes the CEL/MIL to come on, but requires a Fisker engineer or FSR to come out for to reflash that module directly and depending on their scheduals, it can be a few days to a week for them to come out. it is a software checksum error, so it has no negative affects on driving.

Click to expand...

This.

The FSR has to reflash my module and he's getting back in Atlanta next week. At some point when my schedule aligns (probably when 6.15 drops or my floor mats arrive, which ever comes first) I'll take it in to reflash it and clear the MIL.