Recent investigations have shed light on a potential issue concerning brake faults in Nissan Leaf vehicles manufactured between November 2012 and February 2016, particularly when using OBD2 devices like FleetCarma. This article provides an update on these findings, focusing on the connection between OBD2 devices and Electronic Driven Intelligent Brake (EDIB) faults in affected Nissan Leafs.
Nissan has acknowledged awareness of EDIB faults in Nissan Leafs related to the use of OBD2 devices for an extended period. Their documentation, dating back to June 2015, along with a December 2015 notice on their Japanese Recall/Service Campaign Information website, advises against using aftermarket OBD2 “communication devices.” Nissan suggests that these devices can trigger brake faults and other system problems. Therefore, Nissan’s recommendation is clear: avoid using aftermarket OBD2 devices due to potential issues with brakes and other critical vehicle systems.
Alt text: Nissan Leaf Spy Warning document highlighting potential issues with aftermarket OBD2 devices causing brake and system malfunctions in Nissan Leaf vehicles.
Nissan’s current explanation for these EDIB faults points to them being triggered when the Nissan Leaf is in a READY OFF state (turned off) while an OBD2 device remains plugged in. This explanation emerged after presenting Nissan New Zealand with a case of a Leaf exhibiting EDIB fault mode with an OBD2 device connected. This incident suggested that the issue wasn’t solely related to sub-freezing temperatures, as Nissan had previously implied.
It’s crucial to understand that the EDIB faults under investigation appear to stem from a design flaw within the brake system’s firmware installed by Nissan during manufacturing. While using OBD2 devices isn’t the root cause of these faults, evidence suggests a significant correlation. Data indicates that having a permanently connected OBD2 device in affected Nissan Leafs considerably increases the likelihood of an EDIB fault occurring.
Examples of these permanently-connected OBD2 devices include Bluetooth/WiFi dongles used for continuous logging with applications like LeafSpy Pro, EV Black Box, FleetCarma devices, and OVMS. Telematics devices employed for fleet management, insurance monitoring, car alarms, or remote vehicle control systems, when constantly connected to the Leaf’s OBD2 port, may also elevate the risk. While modifying OBD2 device behavior to mitigate risks is a possibility, there’s currently no definitive scientific proof confirming risk reduction through such modifications. Discussions have been initiated with the developers of LeafSpy, FleetCarma, and OVMS, who are actively examining these findings. Notably, EV Black Box has been reconfigured to transmit requests only when the Nissan Leaf is powered on.
Alt text: Translation of Nissan recall information in English, warning against OBD2 device usage and potential brake system complications in Nissan Leaf vehicles.
However, it’s important to note that current information lacks verification or statistical significance to suggest that occasional OBD2 device use (like connecting a dongle briefly for monthly car scans) escalates the chances of brake faults. Furthermore, there’s no indication that OBD2 device usage in Nissan Leafs outside the affected production period increases fault risks.
For owners of affected Nissan Leafs, a proactive measure is recommended: have your 12V battery professionally checked and replaced if advised. Additionally, remain vigilant for any dashboard warning lights and refrain from driving if any lights are illuminated. Make regular checks for warning lights a routine practice.
The findings of this analysis have been communicated to the New Zealand Transport Agency, and there is a commitment to collaborate with them and other relevant parties to minimize future risks. Further updates will be shared as the investigation progresses.
In the meantime, your comments and questions are welcomed.
The team at Flip The Fleet.
