Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

TESLA MODEL S stopped working... CAR MAY NOT RESTART

This site may earn commission on affiliate links.
No need to buy random diag tools or pay anyone ridiculous amounts of money to fix this.

Fix it by sending these CAN messages with any CAN transceiver on the powertrain CAN:

Code:
CAN_BUFFER_ITEM bms_iso_reset[] = {
    { .id = 0x602, .len=8, .data.u8 = { 2,0x27,05,00,00,00,00,00 } },
    { .id = 0x602, .len=8, .data.u8 = { 0x30,0,0xA,00,00,00,00,00 } },
    { .id = 0x602, .len=8, .data.u8 = { 0x10,0x12,0x27,0x06,0x35,0x34,0x37,0x36 } },
    { .id = 0x602, .len=8, .data.u8 = { 0x21,0x31,0x30,0x33,0x32,0x3D,0x3C,0x3F } },
    { .id = 0x602, .len=8, .data.u8 = { 0x22,0x3E,0x39,0x38,0x3B,0x3A,0x00,0x00 } },
    { .id = 0x602, .len=8, .data.u8 = { 0x04,0x31,0x01,0x04,0x0A,0x00,0x00,0x00 } }
};

Then figure out what's actually causing the isolation issue and fix that (HV blade seal, pack heater, etc). Repeatedly "fixing" this error with the above CAN messages (or with third party tools) is NOT the correct way to fix this. The car is throwing this error for a reason, and that physical issue needs to be corrected. Otherwise the car can have serious issues, including ones that can result in injury/shock/etc. There's isolation failure detection in the hardware for a reason. Don't ignore this, and don't just reset the error without actually finding and fixing the underlying issue.

In my experience the most common problem is the pack heater corrosion causing isolation failure via the coolant. Second is water ingress into the battery pack HV connector due to dry-rotted rubber seals. Beyond that, could be a bunch of things and you'll need special equipment to track that down (megaohm HV isolation testing equipment to check each component).
I just tried sending the above 0x602 CAN message to clear a HVIL fault after replacing my coolant heater to bus3 on 2012 MS (low resistance from and to b+ on the connector). Code did not clear, but I got a BMS_f011_HW_Illegal_ctr_Req back - I'm guessing my CAN message is corrupt somehow?