The B1964 trouble code detects a power seat potentiometer circuit malfunction.
The B1964 code is a standard OBD-II trouble code that signals a power seat potentiometer circuit error. The potentiometer is located under one of the front seats, and serves as essentially a position sensor for the power seat system. The device is responsible for relaying information about the seat position (the horizontal position, in the case of this particular trouble code) to the body control module or powertrain control module (PCM). This information serves multiple purposes, the primary one being that it can keep conflicting movements from occurring, including the convertible top from being lowered when one of the front seats is in the way. Whenever the PCM or body control module fails to receive a reading from the power seat potentiometer, then the B1964 code may be stored.
The B1964 code is usually the result of one of two things. The first common cause of the code is a defective power seat potentiometer. The second common cause is damaged electrical parts within the potentiometer system, such as blown fuses, open connectors, and shorted wires. The code may also be the result of an improperly adjusted potentiometer, though this is less common. And, while extremely uncommon, the code can also be caused by a malfunctioning PCM or body control module.
The B1964 trouble code is usually accompanied by an illuminated check engine soon warning light on your 2012 Mitsubishi Eclipse spyder's dashboard. The potentiometer will most likely not work, which can prevent the seats from automatically moving into the required position when the convertible top is put down, or the memory seat positions are engaged. In some cases, the power seat system will be entirely inoperable, so the seats will not be able to be adjusted.
The B1964 code will be diagnosed using a standard OBD-II trouble code scanner. A trustworthy technician will use the scanner to assess the code by viewing the freeze frame data. The scanner will also be used to check for any additional trouble codes that may be present. If the mechanic notes numerous codes, then they will need to be diagnosed in the order that they are displayed in. The trouble codes should then be reset, and your 2012 Mitsubishi Eclipse spyder restarted, so the technician can see if the B1964 code remains detected. If the code is no longer present, then it was likely triggered inaccurately, or is the result of an intermittent issue.
If the code is still detected, then the mechanic should visually inspect all of the electrical parts in the potentiometer and power seat system, and replace any components that are damaged or compromised in any way. The potentiometer adjustment should then be checked, followed by an inspection of the potentiometer itself.
After any components are repaired or replaced, the codes will once again be reset, your 2012 Mitsubishi Eclipse spyder again restarted, and the code again checked for. By doing this, the technician will know when the problem is resolved.
The most common mistake when diagnosing the B1964 code comes from a failure to comply with the OBD-II diagnosis protocol. The diagnosis protocol should be obeyed at all times, as it helps ensure that inspections are efficient, and repairs are accurate.
It is common for potentiometers in working order to be unnecessarily condemned because the electrical system was not first inspected.
The B1964 trouble code will not present any drivability problems, or ever keep a car from being drivable, but the potentiometer may not work. This likely means that the seat will have to be manually adjusted before a convertible top is lowered, and possibly in other situations as well. It is also possible that the seats cannot be manually adjusted at all, which can potentially cause a drivability problem depending on the position of the immobile seat, and the height of the driver.
Repairs for the B1964 trouble code include:
It is extremely rare for a defective PCM or body control module to be the result of the B1964 trouble code. Because of this, all potential causes of the code should be checked before it is assumed that there has been a controller failure.