Joined
·
61 Posts
Not to be confused with normal service message to clear after regular service. This "Malfunction Service Required" seems to be a symptom of something wrong. I tried searching, but the closest I've gotten was some sort of possible coolant (battery) issue someone once had.
I looked for any signs of a leak visually and found nothing.
Tried hooking up my OBD scan tool (Bluedriver and Craftsman basic reader) and none seem compatible with this car (just says nothing or error).
1) Anyone had this message before?
2) Does anyone know what kind of OBD scan tool to help me work on my own smart?
3) Does my OVMS have a way of reading errors from the car since its already hooked up to the OBD port at all times?
Update 2/1/2022 Solution- Code cleared itself after a few days. About 2 weeks before I caught the HV batt constantly charging the 12v at all times. When I checked the 12v battery with a batt tester, it needed replacing after 6 years being the original the car came with. I replaced it with the Drualast AGM Autozone equivalent of which I am a 4 past car fan of battery. I'm guessing the error had something to do with that or the extremely cold weather after. Month after the code came it has not come back.
I looked for any signs of a leak visually and found nothing.
Tried hooking up my OBD scan tool (Bluedriver and Craftsman basic reader) and none seem compatible with this car (just says nothing or error).
1) Anyone had this message before?
2) Does anyone know what kind of OBD scan tool to help me work on my own smart?
3) Does my OVMS have a way of reading errors from the car since its already hooked up to the OBD port at all times?
Update 2/1/2022 Solution- Code cleared itself after a few days. About 2 weeks before I caught the HV batt constantly charging the 12v at all times. When I checked the 12v battery with a batt tester, it needed replacing after 6 years being the original the car came with. I replaced it with the Drualast AGM Autozone equivalent of which I am a 4 past car fan of battery. I'm guessing the error had something to do with that or the extremely cold weather after. Month after the code came it has not come back.