Hello everyone.
We just purchased a used 2006 Commander Limited. I have about six months of warranty left. I haven't taken it to the dealer yet. I wanted to do a little research before talking with the service department. I am an automotive mechanic from the '80s and know a little about today's technology (CAN OBDII).
When I picked up the Commander, there were no issues with the "check engine" light. We tried the remote start after getting home, and the next time we drove the car, I noticed the "check engine" light was on (code U1411 - "Implausible fuel volume signal." After a few drive cycles, the light went out. I tried the remote start the next day, and low and behold; the lights were back on. I reset it manually. Next remote start, back on. See the pattern here?? I think it might occur when the ignition switch is turned "on" after entering the car. I need to analyze the time the code is set vs. the run time.
Has anyone out there experienced this issue and successfully had it fixed?
If so, what was the fix?
I am afraid this could turn into a real run around. Thanks, Jerry (smblk)
We just purchased a used 2006 Commander Limited. I have about six months of warranty left. I haven't taken it to the dealer yet. I wanted to do a little research before talking with the service department. I am an automotive mechanic from the '80s and know a little about today's technology (CAN OBDII).
When I picked up the Commander, there were no issues with the "check engine" light. We tried the remote start after getting home, and the next time we drove the car, I noticed the "check engine" light was on (code U1411 - "Implausible fuel volume signal." After a few drive cycles, the light went out. I tried the remote start the next day, and low and behold; the lights were back on. I reset it manually. Next remote start, back on. See the pattern here?? I think it might occur when the ignition switch is turned "on" after entering the car. I need to analyze the time the code is set vs. the run time.
Has anyone out there experienced this issue and successfully had it fixed?
If so, what was the fix?
I am afraid this could turn into a real run around. Thanks, Jerry (smblk)