This is a stub article [toc][/toc] Roadster VDS Messages A list of the VDS messages which can appear and if possible, some advice to the owner who sees them. The VDS can operate in Standard or Debug mode. You enter Debug mode either by tapping the VDS six times and entering a special code, or by letting MPT get in your car. IDColorText under normal circumstancesDebug text (not normally displayed)Notes / Suggestions 0 Red Battery Problem Service Required Critical Brick OverVoltage fault 2 Battery too cold Vehicle shutting down Critical Sheet UnderTemp fault 3 Blue Maintenance Service Required Have the car serviced or reset the service interval. 4 Battery too hot Vehicle shutting down Critical Sheet OverTemp fault 6 Battery Problem Service Required VMS: APS Failure 7 Battery Service Required 8 Vehicle Idle for 1 Hour Shutting Down 10 Charging Problem 13 Red Battery Problem Service Required Critical Brick UnderVoltage fault 14 ESS Temperature Sensor Fault 16 Battery Problem Service Required BMB: Sheet alarm 19 Isolation resistance warning 21 Yellow Debug-Only Msg APS OverTemp Warning 23 SHUTTING DOWN PULL OVER SAFELY SHUTTING DOWN PULL OVER SAFELY 25 Blue Memory Stick transfer in progress. ... Memory stick transfer in progress. Please do not remove. Car is downloading logs to USB memory stick. Data field shows completion percentage in hexadecimal. 27 Memory stick transfer failure. Reinsert stick to try again. 28 Transfer to memory stick has failed Transfer to memory stick has failed 29 APS: APS power inhibited 30 Airbag System Service required SRS: Airbag enabled in car, but disabled in VMS config 31 SRS: Airbag deployed. Contact Tesla Service Center 32 SRS: Airbag must be serviced. Contact Tesla Service Center 43 Red Debug-Only Msg VMS: APS Inhibited due to low brick voltage 50 Red Communication Problem Service Required BMB: No data fault 51 Communication Problem Service Required BSM: No data fault 52 Communication Problem Service Required CSB: No data fault 53 Orange Debug-Only Msg GPS: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 2) Check if the GPS antenna is plugged in at the VMS in the dash above the passenger footwell (petergrub) 54 Orange Coolant System Problem Charging restricted to HVAC: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 55 Orange Debug-Only Msg IP: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 56 Orange Communication Problem Power Reduced PEM: No data fault 1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub) 57 SWP: No data fault 58 Orange Debug-Only Msg TPMS: No data fault 59 Communication Problem Service Required VMSIO: No data fault 60 Orange Debug-Only Msg DFC: No data fault 1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub) 61 Orange Park Lock Problem Vehicle May be Free-Rolling TCM: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 62 Orange Debug-Only Msg PM: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 63 Orange Debug-Only Msg GS: No data fault 1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub) 90 Transmission error Service required TCM: Oil Pump Open Circuit 91 Transmission error Service required TCM: Oil Pump Low Current 92 Transmission error Service required TCM: Oil Pump High Current 93 Transmission error Service required TCM: Oil Pump Driver Fault 94 Park Lock Problem Vehicle May be Free-Rolling TCM: Park Motor Open Circuit 95 Park failed to disengage. Service required. TCM: Park Motor jammed in Park 96 TCM: Park Motor jammed in Unpark 97 Park Lock Problem Vehicle May be Free-Rolling TCM: Park motor jammed in the middle 98 TCM: Park Hall Sensor not seen 99 Park Lock Problem Vehicle May be Free-Rolling TCM: Unpark Hall sensor not seen 100 TCM: Hall Sensors both on 101 Parking System Service Required TCM: CRC error 102 Parking System Service Required TCM: Lost VMS comms 103 Parking System Service Required TCM: Lost ABS comms 104 TCM: Lost DMC comms 105 Parking System Service Required TCM: Lost DFC comms 106 Parking System Service Required TCM: ABS error 107 Parking System Service Required TCM: CAN error 108 TCM: Watchdog timer reset 257 Red Debug-Only Msg APS output 1 (main) reset 258 Red Debug-Only Msg APS output 2 (PEM) reset 1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub) 259 Red Charge Aborted/Battery Problem Service Required BSM: Sheet Alarm Battery is too low to charge 260 Battery Service Required BSM: Smoke detected 261 Service required Charging restricted BSM: Smoke detector not reporting 262 BSM: Immersion fault 1) Water or some other debris may be causing a short on the strip that runs horizontally along the inside of the ESS at the bottom (petergrub) 263 Red Powertrain Problem Restart When Safe BSM: HVAC cable fault 264 Red Powertrain Problem Restart When Safe BSM: PEM cable fault 265 Powertrain Problem Restart When Safe BSM: V_batt too low 266 BSM: V_batt too high 267 BSM: Positive contactor/economizer stuck low 268 BSM: Positive contactor/economizer stuck high 269 BSM: Negative contactor/economizer stuck low 270 BSM: Negative contactor/economizer stuck high 271 Red Battery Problem Vehicle shutting down BSM: Contractor power failure Has happened when starting car too soon after service plug has been inserted. Fix: Pull/insert it again and wait a few minutes before starting car. 272 Powertrain Problem Restart When Safe BSM: PEM HVAC cable/pin discharge failure 273 Powertrain Problem Restart When Safe BSM: V_ess too high 274 Powertrain Problem Restart When Safe BSM: CSB commanded contactors to open 275 Powertrain Problem Service Required BSM: Precharge to fast at t1 276 Powertrain Problem Service Required BSM: V_ess too low at end of precharge 277 Powertrain Problem Service Required BSM: V_batt too low at start of precharge 278 Powertrain Problem Service Required BSM: V_ess too high at start of precharge 279 Powertrain Problem Service Required BSM: Precharge resistor too hot at start of precharge 280 BSM: Discharge enabled at start of precharge 281 BSM: Orientation fault 282 BSM: ESS OverTermp fault 283 Orange Debug-Only Msg BSM: Isolation fault 284 BSM: Voltage sensor error 285 BSM: Isolation fault before closing contactors 286 Orange Debug-Only Msg BSM: Isolation fault while contactors closed 287 Power train Problem Service RequiredBSM: Isolation fault before charge 288 Orange BSM: V_ess too low during precharge, t2 398 Blue Key must be on to select new tires 399 Cannot select new tires while moving 400 Blue Coast in a straight line at 20-60mph for 10 seconds 401 Yellow TPMS: Left front tire very soft TPMS: Left front tire very soft 1) Data field describes which tires are very soft. E.g. only a very soft left front tire shows 0x00000001 (petergrub) 2) Data field can describe multiple very soft tires. E.g. very soft left front, left rear, and rear right shows 0x00000051 (petergrub) 402 TPMS: Left front tire soft TPMS: Left front tire soft 1) Data field may describe which tires are soft. E.g. only a soft left front tire should show 0x00000002 (petergrub) 403 Yellow TPMS: Right front tire very soft TPMS: Right front tire very soft 1) Data field describes which tires are very soft. E.g. only a very soft right front tire shows 0x00000004 (petergrub) 404 TPMS: Right front tire soft TPMS: Right front tire soft 1) Data field may describe which tires are soft. E.g. only a soft right front tire should show 0x00000008 (petergrub) 405 TPMS: Left rear tire very soft TPMS: Left rear tire very soft 1) Data field describes which tires are very soft. E.g. only a very soft left rear tire shows 0x00000010 (petergrub) 406 TPMS: Left rear tire soft TPMS: Left rear tire soft 1) Data field may describe which tires are soft. E.g. only a soft left rear tire should show 0x00000020 (petergrub) 407 Yellow TPMS: Right rear tire very soft TPMS: Right rear tire very soft 1) Data field describes which tires are very soft. E.g. only a very soft right rear tire shows 0x00000040 (petergrub) 408 TPMS: Right rear tire soft TPMS: Right rear tire soft 1) Data field may describe which tires are soft. E.g. only a soft right rear tire should show 0x00000080 (petergrub) 409 TPMS: Hardware Error TPMS: Hardware error Tire pressure cannot be monitored reliably, e.g. if you just swapped your wheels. For a while, TM was selling a "TPMS Reset Tool" which seems to be no longer available (April 2014). 410 TPMS: Tire over-pressure warning 411 TPMS: Tire OverTemp warning TPMS: Tire OverTemp warning 412 TPMS: Rapid tire pressure loss TPMS: Rapid tire pressure loss 413 TPMS: Check left front tire TPMS: Check left front tire 415 TPMS: Check left back tire TPMS: Check left back tire 416 TPMS: Check right back tire TPMS: Check right back tire 420 SWP: APS off, but no pulse from BPS 428 Orange 12V Battery Service Required SWP: Aux Battery Supply Low Turned out battery fuse was missing. Or an old Battery (0x81248884) 429 SWP: Eeprom checksum error 430 SWP: CAN Rx OverFlow 500 VMS: Security alert, left door opened 501 VMS: Security alert, right door opened 502 VMS: Security alert, trunk opened 503 VMS: Security alert, hood opened 504 VMS: Security alert, key inserted 525 ABS: Short circuit 526 SWP: Radio short circuit 527 Yellow Right Headlight Bulb Out Check right front high beam bulb Replace the right high beam headlight bulb 528 Yellow Left Headlight Bulb Out Check left front high beam bulb Replace the left high beam headlight bulb 529 Orange Right Headlight Bulb Out Check right front low beam bulb Replace the right low beam headlight bulb 530 Orange Left Headlight Bulb Out Check left front low beam bulb Replace the left low beam headlight bulb 531 Check marker light bulbs 532 Orange Left side turn signal open/short circuit 533 Orange Right side turn signal open/short circuit 534 Left window motor issue 535 Blue Debug-Only Msg Right window motor issue 536 Yellow Check left back turn signal bulb 537 Yellow Check left front turn signal bulb 538 Yellow Check right back turn signal bulb 539 Yellow Check right front turn signal bulb 547 Check rear fog lamps 560 Blue Timed out of Range Mode (after charging) 561 Timed out of Performance Mode (after charging) 600 Yellow APS: Cooling issue; power limiting in effect 601 ESS: MaxT brick too hot; power limiting in effect 602 SHUTDOWN IMMINENT Power limited SHUTDOWN IMMINENT Power limited 603 BSM: Isolation resistance fault; power limiting in effect 604 Yellow Battery Low Power Reduced ESS: Low State of charge: power limiting in effect You need to recharge 605 Standard range SOC floor reached. Stop & Charge. Standard range SOC floor reached. Stop & Charge. 606 Yellow ESS: Range Mode Remaining charge uncertain You need to recharge 607 ESS: MaxT brick extremely hot; power limiting in effect ESS: MaxT brick extremely hot; power limiting in effect 608 Yellow ESS: Almost empty. Car stops in 3 miles ESS: Almost empty. Car stops in 3 miles 609 ESS: BSM/CSB/BMB no data fault; power limited ESS: BSM/CSB/BMB no data fault; power limited 610 ESS: Almost empty. Car stops in 2 miles ESS: Almost empty Car stops in 2 miles 611 ESS: Almost empty. Car stops in 1 mile ESS: Almost empty. Car stops in 1 mile 612 Multiple Temp Sensor Faults; Vehicle entering limp mode Multiple Temp Sensor Faults; Vehicle entering limp mode 613 VMS: Use MC120 to avoid trickle charge 700 Yellow Brake fluid low Brake fluid low 701 ABS: Service required ABS: Service required 702 ABS: Service required ABS: Service required 703 ABS: Service required ABS: Service required 720 900A discharge limit exceeded 900A discharge limit exceeded 721 863A discharge limit esceeded 863A discharge limit exceeded 722 805A discharge limit exceeded 805A discharge limit exceeded 723 300A discharge limit exceeded 300A discharge limit exceeded 724 200A discharge limit exceeded 200A discharge limit exceeded 725 190A charge limit exceeded 190A charge limit exceeded 726 75A charge limit exceeded 75A charge limit exceeded 727 60A charge limit exceeded 60A charge limit exceeded 728 Overtemp event during charge or regen Overtemp event during charge or regen 729 Undertemp event during charge or regen 730 750A discharge warning 731 450A discharge warning; power limited 732 300A discharge warning; power limited 733 200A discharge warning; power limited 734 75A charge warning 735 60A charge warning 737 CSB: Discharge Undertemp 739 CSB: BMB No Data fault 880 While staring, keep foot off accelerator pedal While starting, keep foot off accelerator pedal 881 While starting, foot brake must be pressed While starting, foot brake must be pressed 882 Before starting, charge port door must be closed Before starting, close charge port door 883 Blue Before starting, exit Tow mode Before starting, exit Tow mode 1) The car is still in tow mode, so it cannot be started. 2) Select the "Exit Tow Mode" button from the touch screen, VDS (petergrub) 884 Battery empty Can't start Battery empty Can't start 885 BMB No Data fault Can't start BMB No Data fault Can't start 886 Battery cold Can't start Battery cold Can't start 887 Red Can't start Version number mismatch 1) Sometimes paired with 1553 (petergrub) 888 Red Disarm vehicle with key fob before starting VMS/PEM key mismatch Press the button on the keyfob. 889 Service Required. Charging restricted to storage level. Service Required. Charging restricted to storage level. 901 Red DMC HW: PhaseA OverCurrent Fault 902 Red DMC HW: PhaseB OverCurrent Fault 903 Red DMC HW: PhaseC OverCurrent Fault 904 DMC HW: Battery OverVoltage Fault 905 Red Powertrain Problem Restart When Safe DMC HW: PhaseA Low Side Desat Fault 906 DMC HW: PhaseA High Side Desat Fault 907 Red DMC HW: PhaseA Bias Under Voltage Fault 908 DMC HW: PhaseA Bus Over voltage fault 909 DMC HW: PhaseB Low Side Desat Fault 910 DMC HW: PhaseB High Side Desat Fault 911 Red DMC HW: PhaseB Biad UnderVoltage fault 912 DMC HW: PhaseB Bus OverVoltage fault 913 DMC HW: PhaseC Low Side Desat fault 914 DMC HW: PhaseC High Side Desat fault 915 Red DMC HW: PhaseC Bias UnderVoltage fault 916 DMC HW: PhaseC Bus OverVoltage fault 917 DMC HW: APS UnderVoltage fault 918 DMC HW: Motor OverTerm fault 919 DMC HW: Pedal Monitor fault 920 DMC HW: Line OverCurrent fault 921 DMC HW: PhaseA OverTemp fault 922 DMC HW: PhaseB OverTemp fault 923 Red DMC HW: PhaseC OverTerm fault 924 DMC HW: ESS Cable Interlock fault The dealer believes this might be caused by slight corrosion on the terminals of the safety wire. 925 DMC HW: Common Mode Sense fault 926 DMC HW: PDP Interrupt fault 927 Red DMC HW: PhaseA OverCurrent fault 928 Red DMC HW: PhaseB OverCurrent fault 929 Red DMC HW: PhaseC OverCurrent fault 930 Red DMC FW: PhaseA OverCurrent Peak fault 931 Red DMC FW: PhaseB OverCurrent Peak fault 932 Red DMC FW: PhaseC OverCurrent Peak fault 933 DMC FW: Line OverCurrent fault 934 DMC FW: Line OverCurrent Peak Fault 935 DMC FW: Line OverVoltage fault 936 Yellow Charging Problem DMC FW: Line OverVoltage Peak fault 937 Charge Problem Extension Cord Detected DMC FW: Line UnderVoltage fault 938 DMC FW: Battery OverVoltage fault 939 DMC FW: Battery UnderVoltage fault 940 DMC FW: Motor OverSpeed fault 941 DMC FW: Motor Sensor1 OverTemp fault 942 DMC FW: Motor Sensor2 OverTerm fault 943 DMC FW: Motor Sensor1 UnderTemp fault 944 DMC FW: Motor Sensor2 UnderTerm fault 945 Red System too hot - Vehicle shutting down DMC FW: PhaseA OverTemp fault 946 DMC FW: PhaseA Temp Diff fault 947 Red System Too Hot - Vehicle Shutting Down DMC FW: PhaseB OverTemp fault Preceded by error message 1152. Resolution: PEM fans replaced. Likely cause - 1152 indicative of contactor(s) sticking open, but not fatal. Moisture in the open contactors may have caused rusting, resulting in this error. 948 DMC FW: PhaseB Temp Diff fault 949 Red DMC FW: PhaseC OverTemp fault 950 DMC FW: PhaseC Temp Diff fault 951 DMC FW: Ambient OverTemp fault 952 DMC FW: Amvient UnderTemp fault 953 Line Voltage Lost Sync DMC FW: Line OverFrequency Fault Bad power; try lowering the current and restarting (or breaker tripped) 954 Line Voltage Lost Sync DMC FW: Line UnderFrequency Fault Bad power; try lowering the current and restarting (or breaker tripped) 955 DMC FW: Line Sync Loss fault 956 DMC FW: HCS Faulted 957 DMC FW: PEM Vbat diff from BSM Vbat fault 958 DMC FW: HCS Invalid Pilot Signal fault 959 DMC FW: Line Current or Voltage Offset Too Large fault 960 DMC FW: VBrickMax versus VBattery Error fault You don't want to know. 961 DMC FW: VBrickMax or VBrickLimit is invalid 962 Orange DMC FW: Line Current Error fault 963 Orange Powertrain Problem Service Required DMC FW: Line Current Not Equal Request fault User tvuolo had a similar issue that was resolved by replacing the 150A line fuse(s) in the PEM service window. Check and replace as needed. 964 DMC FW: Pilot Signal Present in Drive Mode fault 965 DMC FW: Gear Selector Comms fault 966 DMC FW: Invalid Shift Request Fault 967 DMC FW: Press brake before shifting fault 968 DMC FW: Lost VMS Comms fault 969 DMC FW: Lost DFC Comms fault 970 DMC FW: Lost ABS Comms (and TC) fault 971 DMC FW: CAN Comms Error fault 972 Red Powertrain Problem Service Required DMC FW: Accelerator Erorr fault 973 DMC FW: Motor Encoder Error fault 974 Red DMC FW: Pole Current Error Fault 975 DMC FW: ABS Error fault 976 DMC FW: Invalid State fault 977 Car moved while charging - charge stopped. DMC FW: Moving during charge fault Got this for trying to change the wheels while charging the car! Spinning front right wheel by hand (after jacking up car) triggered the message. 978 DMC FW: Invalid State request fault 979 DMC FW: Invalid Mode request fault 980 DMC FW: Invalid Charge Request fault 981 Orange DMC FW: Bad State Transition Fault Dog tripped over charging cable. Discuss. Charger seems to be having troubles. A reset from the chargepoint fixed it. 982 DMC FW: Mode Trans Condition fault 983 DMC FW: Memory Error fault 984 DMC FW: Bad Argument fault 985 DMC FW: Interrupt Time too Long fault 986 DMC FW: MotorTemp Sensor1 fault 987 DMC FW: MotorTemp Sensor2 fault 988 DMC FW: MotorTemp Sensors differ fault 989 DMC FW: VBrickMin Not Increasing 990 DMC FW: Voltage Discharge Time fault 991 DMC FW: 5V Power 992 DMC FW: Lost TCM comms 993 DMC FW: PCS Current Offset Too Large fault 994 DMC FW: Watchdog timer reset fault 995 DMC FW: TCM Refusal fault 996 DMC FW: Unsafe gear transition fault Press brake before shifting 997 DMC FW: CAN Rx 998 DMC FW: CAN Tx 999 DMC FW: CAN Overrun 1000 DMC FW: SPI Open 1001 DMC FW: SPI Read 1002 DMC FW: VBUS Present With ILoop Open 1003 DMC FW: Lost Comms With Shifter 1004 DMC FW: Relay Driver 1005 DMC FW: Line Contactor 1006 DMC FW: Antispark Contactor 1007 Orange Debug-Only Msg DMC FW: Run Contactor 1008 DMC FW: APS Undervoltage 1009 DMC FW: Encoder Hardware 1010 DMC FW: Fault 110 1011 DMC FW: Accelerator 5V 1012 DMC FW: Firmware Error 1013 DMC FW: FAULT Pole Power 1029 DMC HW: PhaseA OverCurrent warning 1030 DMC HW: PhaseB OverCurrent warning 1031 DMC HW: PhaseC OverCurrent warning 1032 DMC HW: Battery OverVoltage warning 1033 DMC HW: PhaseA Low Side Desat warning 1034 DMC HW: PhaseA High Side Desat warning 1035 DMC HW: PhaseA Bias UnderVoltage warning 1036 DMC HW: PhaseA Bus OverVoltage warning 1037 DMC HW: PhaseB Low Side Desat warning 1038 DMC HW: PhaseB High Side Desat warning 1039 DMC HW: PhaseB Bias UnderVoltage warning 1040 DMC: HW PhaseB Bus OverVoltage warning 1041 DMC HW: PhaseC Low Side Desat warning 1042 DMC HW: Phase C High Side Desat warning 1043 DMC HW: PhaseC Bias Under Voltage warning 1044 DMC HW: PhaseC Bus Over Voltage warning 1045 DMC HW: APS Under Voltage warning 1046 DMC HW: Motor OverTemp warning 1047 DMC HW: Pedal Monitor warning 1048 DMC HW: Line Over Current warning 1049 DMC HW: PhaseA OverTemp warning 1050 DMC HW: PhaseB OverTemp warning 1051 DMC HW: PhaseC OverTemp warning 1052 DMC HW: ESS Cable Interlock warning 1053 DMC HW: Common Mode Sense warning 1054 DMC HW: PDP Interrupt warning 1055 DMCFW: PhaseA OverCurrent warning 1056 DMCFW: PhaseB OverCurrent warning 1057 DMCFW: PhaseC OverCurrent warning 1058 DMC FW: PhaseA OverCurrent Peak warning 1059 DMC FW: PhaseB OverCurrent Peak warning 1060 DMC FW: PhaseC OverCurrent Peak warning 1061 DMC FW: Line OverCurrent warning 1062 DMC FW: Line OverCurrent Peak warning 1063 DMC FW: Line OverVoltage warning 1064 DMC FW: Line OverVoltage Peak warning 1065 DMC FW: Line UnderVoltage warning 1066 DMCFW: Battery OverVoltage warning 1067 Orange Debug-Only Msg DMCFW: Battery UnderVoltage warning 1068 DMC FW: Motor OverSpeed warning 1069 Orange DMC FW: Motor sensor 1 OverTemp warning. Torque limited 1070 Orange DMC FW: Motor sensor 2 OverTemp warning. Torque limited 1071 DMC FW: Motor Sensor1 UnderTemp warning 1072 DMC FW: Motor Sensor2 UnderTemp warning 1073 DMC FW: PhaseA OverTemp warning. Torque limited. 1074 DMC FW: PhaseA Temp Diff warning 1075 Orange Debug-Only Msg DMC FW: PhaseB OverTemp warning. Torque limited. 1076 Orange Debug-Only Msg DMC FW: PhaseB Temp Diff warning 1077 Orange Debug-Only Msg DMC FW: PhaseC OverTemp warning. Torque limited. 1078 Orange Debug-Only Msg DMC FW: PhaseC Temp Diff warning 1079 DMC FW: Ambient OverTemp warning 1080 DMC FW: Ambient UnderTemp 1081 DMC FW: Line OverFrequency warning 1082 DMC FW: Line UnderFrequency warning 1083 DMC FW: Line Sync Loss warning 1084 External Charger Problem DMC FW: HCS Faulted warning UMC's red fault light blinking. Unplugged car & UMC, then replugged and all OK. 1085 Orange Debug-Only Msg DMC FW: PEM Vbat different from BSM Vbat warning 1086 DMC FW: HCS Invalid Pilot Signal warning 1087 DMC FW: Line Current or Voltage Offset Too Large warning PEM fuse(s) blown, needs to be replaced. Can show up incidentally without meaning any trouble. 1088 DMC FW: VBrickMax versus VBattery Error warning 1089 DMC FW: VBrickMax or VBrickLimit is invalid 1090 DMC FW: Line Current Error warning 1091 DMC FW: Line Current Not Equal Request warning 1092 Yellow Do not plug in charge cable while driving DMC FW: Pilot Signal Present in Drive Mode warning Key left in ignition while trying to plug in? 1093 DMC FW: Shifter error warning 1094 DMC FW: Invalid Shift Request warning 1095 Press brake pedal before shift. DMC FW: Press brake before shift. Press brake pedal and then select a gear. 1096 Orange Debug-Only Msg DMC FW: Lost VMS comms warning 1097 DMC FW: Lost DFC comms warning 1098 Orange DMC FW: Lost ABS Comms (and TC) warning 1099 DMC FW: CAN comms error warning 1100 DMC FW: Accelerator Error warning 1101 DMC FW: Motor Encoder Error warning 1102 DMC FW: Pole Current Error warning 1103 Orange ABS & Traction Control Problems. Service Required. DMC FW: ABS Error warning Pulling out ignition key and waiting until car shutdown (15 minutes) cleared it. Tesla couldn't find issue. 1104 DMC FW: Invalid State warning 1105 DMC FW: Moving during charge warning 1106 DMC FW: Invalid State Request warning 1107 DMC FW: Invalid Mode Request warning 1108 DMC FW: Invalid Charge Request warning 1109 DMC FW: Bad State Transition warning 1110 DMC FW: Mode Trans Condition warning 1111 DMC FW: Memory Error warning 1112 DMC FW: Bad Argument warning 1113 DMC FW: Interrupt Time too Long warning 1114 DMCFW: Motor Temp Sensor 1 warning 1115 DMCFW: Motor Temp Sensor 2 warning 1116 DMC FW: Motor Temp Sensors Differ warning 1117 DMC FW: VBrickMin Not Increasing 1118 DMC FW: Voltage Discharge Time Warning 1119 DMC FW: 5V Power 1120 DMC FW: Lost TCM comms warning 1121 Orange Debug-Only Msg DMC FW: PCS Current Offset Too Large warning 1124 Unsafe Gear Shift Transition Denied Car moving too fast for gear change drive/reverse 1138 Voltage on Charge Port Line2 during drive with charge door open 1144 Powertrain Problem Service RequiredDMC PEM Fan ProblemCall your Tesla Shop! Alt: Check your Battery Coolant level (I got this error constantly after over-filling the coolant, once I siphoned a little off the error went away) Probably the PEM/Motor fan needs to be replaced. Also check the connectors or wiring between the fans and the PEM. Could just be a bad contact1146 DMC Motor Fan ProblemLow fan speed. Only appears in debug mode? Probably the PEM/Motor fan needs to be replaced. Also check the connectors or wiring between the fans and the PEM. Could just be a bad contact [1]. 1152 Charge time increased due to high temperatures.DMC WARNING Charge Thermal Limit(bonnie) Caused car charging rate to intermittently drop from 70amp to as low as 19amp, did not correlate to outside temp or motor temp - PEM & fans cleaned, believed to be result of massive cloud of insulation on freeway that I drove thru - if you see error, check that out first PEM fans replaced after error 947 received. No further issues.1153 DMC Wear Factor Warning 1160 Drivers door ajar Close the door.1161 Passenger door ajar Close the door.1162 Trunk ajar Close the trunk.1165 Key in Key Switch Door Ajar Driver door opened while car is on1166 Release Parking Brake Car is driven while parking brake (partially) engaged1167blueHeadlights still on 1169 Charge port open Charge port opened when car is on1170 Tow Mode is not available while car is on 1174 Fasten Seatbelt Fasten your seatbelt.1416 Low Power System Service Required 1425 HVAC: Low current pump failure 1426 HVAC: High current pump failure 1452orange HVAC: Low pressure 1453 Coolant System Problem Service RequiredHVAC: Refrigerant High Pressure 1463 HVAC: overheat warningHVAC: Compressor OverTempHVAC system will pause ~1 minute and continue cooling. Do not charge inside hot garage with closed Garage door. Only appears in debug mode. This problem appeared to me after a yearly service because the HVAC was overfilled. Check HVAC fluid level 1465 HVAC: Low current pump fault 1469 HVAC: Compressor comms timeout 1471 HVAC: Compressor DTC comms timeout 1493yellow ESS: Extremely Low. Begin Charging ASAP. 1533 Software Problem Service Required 1553RedSoftware problem, Service requiredVMS: VMS firmware version doesn't match car wide releaseDump log over usb, check flash/messages, for most recent "VMS: VMS restarted" line, compare with VMS version in flash/firmware.rc file1554orange VMS: Not receiving VDS version numberCar can drive but a full RESET is needed: In the front hood pull battery fuse and in the trunk pull the orange ESS Main switch. Then wait 3 minutes.1664yellow PM: Lost VMS comms warningBlue connector at VMS not plugged in1900orangeCommunication Problem: Service RequiredVMS-VDS comms faultHappened twice while trying to download logs to USB stick. Went away on third attempt but logs were rejected by Tesla Motors Upload. The USB stick does not seem to be faulty.1901blue N/AWindow with just text "N/A"2005yellow No response to request to stop chargingfollow error of ID15542017yellow No response to request to change charge modefollow error of ID15542031yellow No response to request to save charging timefollow error of ID15542033yellow No response to request to save charge timingfollow error of ID15542035yellow No response to request to save current limitfollow error of ID15542037yellow No response to request to save cost/kWhfollow error of ID15542070yellow No response to request to get keyfob functionfollow error of ID15542078yellowThere was a problem processing your requestNo response to request to enter Tow Modefollow error of ID15542096yellow No response to Pin submissionfollow error of ID15543001 SHFT: APS Voltage? 3011 Drive Button Failure Vehicle May not be Able to Enter Drive 3021 SHFT: Neutral switch Stuck Down 3022 SHFT: DRIVE switch Stuck Down -->[/comment] -->
I was hoping to have a tree-like structure, maybe like the section jumps in Wikipedia but without having to load the whole page. In ascii art: Roadster ----+---- Version differences \----- Charging and charging efficiency \ ---- VDS \----- ... (Edit: dammit, the leading spaces are all bring compressed to singles. But I think you see what I mean.) I haven't really got any good plan yet, but clearly the VDS messages don't belong on the front page. This level of detail is where we "add value" over a Wikipedia article.
I think you know what you mean. Look at the example edits I did to the article. Use heading tags to create some structure to the article. Different sections can be expanded or collapsed and individually edited. I used the tags [noparse]subheading title[/noparse]. which spits out: subheading title The larger the option number the further down it is in the "tree structure", as you put it. No need to ad bold or change font sizes. The heading tag does that automatically. Be sure to switch between editor modes so you can see the code.
From my notes: ID:287. Power train Problem Service Required Data :0x44000000 Solution = PEM replaced, motor mounts replaced, charge port door electronics removed and resealed (water intrusion) - - - Updated - - - More: ID:937. Charge Problem Extension Cord Detected Data:0x00000010 Self explanatory - - - Updated - - - More: ID:1092. Do not plug in charge cable while driving Data:0x80000000 Oddly, car was not being driven but was parked in garage and I was attempting to charge. This was related to ID:287 problem ID:936 Charging Problem Data:0x00000008 Just another weird problem
I have been taking pictures of various screens. I can post them here over time. Will show with key in ignition.
VMS->VDS Error Codes on the CAN bus I also went looking for a way of determining when a USB log transfer had completed, in my Tesla Roadster. This has been asked for some time ago, with a view of reminding the user to download their logs from the car before they get rotated. Along the way, I seem to have found the VDS alert mechanism. The interesting parts are the ID and Data fields. The ID identifies the screen type (so 25 is "Memory stick transfer in progress") and Data is id-specific. For ID 25, it is the percentage complete (so counting up from 0x00 to 0x64). Looking at my captured logs for this, I find something sticking out: Code: 20.3270 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 27.0199 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 34.0614 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 40.7682 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 47.4682 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 54.7250 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 61.4526 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 61.7035 100 93 15 19 00 00 00 00 00 ->VDS (message to VDS 93) 68.1515 100 93 15 19 00 01 00 00 00 ->VDS (message to VDS 93) 74.8449 100 93 15 19 00 03 00 00 00 ->VDS (message to VDS 93) 81.5926 100 93 15 19 00 05 00 00 00 ->VDS (message to VDS 93) 88.3173 100 93 15 19 00 06 00 00 00 ->VDS (message to VDS 93) 95.0345 100 93 15 19 00 08 00 00 00 ->VDS (message to VDS 93) 101.7832 100 93 15 19 00 0A 00 00 00 ->VDS (message to VDS 93) 108.5329 100 93 15 19 00 0B 00 00 00 ->VDS (message to VDS 93) 115.2333 100 93 15 19 00 0D 00 00 00 ->VDS (message to VDS 93) 121.9544 100 93 15 19 00 0E 00 00 00 ->VDS (message to VDS 93) 128.6547 100 93 15 19 00 10 00 00 00 ->VDS (message to VDS 93) 135.3657 100 93 15 19 00 11 00 00 00 ->VDS (message to VDS 93) 142.0550 100 93 15 19 00 13 00 00 00 ->VDS (message to VDS 93) 148.7466 100 93 15 19 00 14 00 00 00 ->VDS (message to VDS 93) 155.4689 100 93 15 19 00 16 00 00 00 ->VDS (message to VDS 93) 162.1574 100 93 15 19 00 17 00 00 00 ->VDS (message to VDS 93) 168.8772 100 93 15 19 00 19 00 00 00 ->VDS (message to VDS 93) 175.5805 100 93 15 19 00 1A 00 00 00 ->VDS (message to VDS 93) 182.3072 100 93 15 19 00 1C 00 00 00 ->VDS (message to VDS 93) 189.0204 100 93 15 19 00 1D 00 00 00 ->VDS (message to VDS 93) 195.7380 100 93 15 19 00 1F 00 00 00 ->VDS (message to VDS 93) 202.4180 100 93 15 19 00 20 00 00 00 ->VDS (message to VDS 93) 209.1086 100 93 15 19 00 21 00 00 00 ->VDS (message to VDS 93) 215.8086 100 93 15 19 00 23 00 00 00 ->VDS (message to VDS 93) 222.5388 100 93 15 19 00 24 00 00 00 ->VDS (message to VDS 93) 229.2495 100 93 15 19 00 25 00 00 00 ->VDS (message to VDS 93) 235.9896 100 93 15 19 00 27 00 00 00 ->VDS (message to VDS 93) 242.7136 100 93 15 19 00 28 00 00 00 ->VDS (message to VDS 93) 249.4103 100 93 15 19 00 29 00 00 00 ->VDS (message to VDS 93) 256.1020 100 93 15 19 00 2A 00 00 00 ->VDS (message to VDS 93) 262.7812 100 93 15 19 00 2C 00 00 00 ->VDS (message to VDS 93) 269.4841 100 93 15 19 00 2D 00 00 00 ->VDS (message to VDS 93) 276.2004 100 93 15 19 00 2E 00 00 00 ->VDS (message to VDS 93) 282.9480 100 93 15 19 00 30 00 00 00 ->VDS (message to VDS 93) 289.7051 100 93 15 19 00 31 00 00 00 ->VDS (message to VDS 93) 296.3843 100 93 15 19 00 32 00 00 00 ->VDS (message to VDS 93) 303.1348 100 93 15 19 00 34 00 00 00 ->VDS (message to VDS 93) 309.8240 100 93 15 19 00 35 00 00 00 ->VDS (message to VDS 93) 316.5296 100 93 15 19 00 36 00 00 00 ->VDS (message to VDS 93) 323.2851 100 93 15 19 00 37 00 00 00 ->VDS (message to VDS 93) 330.0081 100 93 15 19 00 38 00 00 00 ->VDS (message to VDS 93) 336.7280 100 93 15 19 00 3A 00 00 00 ->VDS (message to VDS 93) 343.4655 100 93 15 19 00 3B 00 00 00 ->VDS (message to VDS 93) 350.1895 100 93 15 19 00 3C 00 00 00 ->VDS (message to VDS 93) 356.8991 100 93 15 19 00 3D 00 00 00 ->VDS (message to VDS 93) 363.6032 100 93 15 19 00 3E 00 00 00 ->VDS (message to VDS 93) 370.3090 100 93 15 19 00 3F 00 00 00 ->VDS (message to VDS 93) 377.0695 100 93 15 19 00 40 00 00 00 ->VDS (message to VDS 93) 383.8307 100 93 15 19 00 41 00 00 00 ->VDS (message to VDS 93) 390.5810 100 93 15 19 00 42 00 00 00 ->VDS (message to VDS 93) 397.2783 100 93 15 19 00 43 00 00 00 ->VDS (message to VDS 93) 404.0252 100 93 15 19 00 45 00 00 00 ->VDS (message to VDS 93) 410.7490 100 93 15 19 00 46 00 00 00 ->VDS (message to VDS 93) 417.4515 100 93 15 19 00 47 00 00 00 ->VDS (message to VDS 93) 424.1598 100 93 15 19 00 48 00 00 00 ->VDS (message to VDS 93) 430.8664 100 93 15 19 00 49 00 00 00 ->VDS (message to VDS 93) 437.5613 100 93 15 19 00 4A 00 00 00 ->VDS (message to VDS 93) 444.3118 100 93 15 19 00 4B 00 00 00 ->VDS (message to VDS 93) 451.0231 100 93 15 19 00 4D 00 00 00 ->VDS (message to VDS 93) 457.7436 100 93 15 19 00 4E 00 00 00 ->VDS (message to VDS 93) 464.4456 100 93 15 19 00 4F 00 00 00 ->VDS (message to VDS 93) 471.1450 100 93 15 19 00 50 00 00 00 ->VDS (message to VDS 93) 477.8440 100 93 15 19 00 51 00 00 00 ->VDS (message to VDS 93) 484.5432 100 93 15 19 00 52 00 00 00 ->VDS (message to VDS 93) 491.2797 100 93 15 19 00 53 00 00 00 ->VDS (message to VDS 93) 497.9838 100 93 15 19 00 54 00 00 00 ->VDS (message to VDS 93) 504.7310 100 93 15 19 00 55 00 00 00 ->VDS (message to VDS 93) 511.4651 100 93 15 19 00 57 00 00 00 ->VDS (message to VDS 93) 518.1755 100 93 15 19 00 58 00 00 00 ->VDS (message to VDS 93) 524.9232 100 93 15 19 00 58 00 00 00 ->VDS (message to VDS 93) 531.6609 100 93 15 19 00 59 00 00 00 ->VDS (message to VDS 93) 538.3964 100 93 15 19 00 5A 00 00 00 ->VDS (message to VDS 93) 545.1293 100 93 15 19 00 5B 00 00 00 ->VDS (message to VDS 93) 551.8466 100 93 15 19 00 5D 00 00 00 ->VDS (message to VDS 93) 558.5722 100 93 15 19 00 5E 00 00 00 ->VDS (message to VDS 93) 565.2908 100 93 15 19 00 5F 00 00 00 ->VDS (message to VDS 93) 572.0311 100 93 15 19 00 60 00 00 00 ->VDS (message to VDS 93) 578.7234 100 93 15 19 00 61 00 00 00 ->VDS (message to VDS 93) 585.4489 100 93 15 19 00 62 00 00 00 ->VDS (message to VDS 93) 592.1719 100 93 15 19 00 63 00 00 00 ->VDS (message to VDS 93) 599.1091 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 605.8596 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 612.5599 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 619.2644 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 626.0780 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 632.7609 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 636.6933 100 93 14 19 00 64 00 00 00 ->VDS (message to VDS 93) 639.7882 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) I found that by looking for the ID 25. Didn't find it, so tried 25 (decimal) = 0x19 (hex). A decode of that would be: 612.5599 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) ID: 100 B1=93 VDS alert notification B2 is some indication of whether this is 'opening' or 'closing' B3(LSB),B4(MSB) is ID B5(LSB),B6,B7,B8(MSB) is data So, I'm happy. I can look for "100 93 15 19 00 64 00 00 00" as an indication that someone did a log transfer and it got to 100%. But, what was interesting, is I then wondered where else '100 93' appears (in particular without the idle condition '100 93 00 FF FF'). Here's what I found: Code: $ fgrep -r '100 93' *|grep -v '93 00 FF FF' 20120218.charge/20120218.charge.breakerstop.txt: 73.1820 100 93 01 BA 03 00 00 20 00 ->VDS (message to VDS 93) 20120218.charge/20120218.charge.breakerstop.txt: 76.2779 100 93 00 BA 03 00 00 20 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 61.7035 100 93 15 19 00 00 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 68.1515 100 93 15 19 00 01 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 74.8449 100 93 15 19 00 03 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 81.5926 100 93 15 19 00 05 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 88.3173 100 93 15 19 00 06 00 00 00 ->VDS (message to VDS 93) … 20130303-vehiclelogtousb/vehiclelogs.txt: 619.2644 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 626.0780 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 632.7609 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 20130303-vehiclelogtousb/vehiclelogs.txt: 636.6933 100 93 14 19 00 64 00 00 00 ->VDS (message to VDS 93) charge.20111108.txt: 1.2849 100 93 05 8D 04 20 00 00 00 ->VDS (message to VDS 93) charge.20111108.txt: 8.0259 100 93 05 8D 04 20 00 00 00 ->VDS (message to VDS 93) charge.20111108.txt: 13.1271 100 93 04 8D 04 20 00 00 00 ->VDS (message to VDS 93) charge.20111108.txt: 1242.8707 100 93 05 A6 03 02 00 00 00 ->VDS (message to VDS 93) charge.20111108.txt: 1244.8822 100 93 04 A6 03 02 00 00 00 ->VDS (message to VDS 93) trip.20111108.txt: 2.9815 100 93 05 8D 04 20 00 00 00 ->VDS (message to VDS 93) trip.20111108.txt: 9.7319 100 93 05 8D 04 20 00 00 00 ->VDS (message to VDS 93) trip.20111108.txt: 10.0843 100 93 04 8D 04 20 00 00 00 ->VDS (message to VDS 93) A few of those stand out like sore thumbs. 20120218.charge.breakerstop.txt Note in the log file there is: Code: 71.3999 NOTE A second or two before breaker stop 73.1820 100 93 01 BA 03 00 00 20 00 ->VDS (message to VDS 93) Conclusion: ID 0x03BA data 0x00002000 is 'breaker tripped'. Or lost line sync, or whatever the message is (I forget). 20130303-vehiclelogtousb/vehiclelogs.txt This is my vehicle log dump to USB. ID 0x0019, data is percentage complete. charge.20111108.txt No notes on this. It appears to be a log testing various charging scenarios. The ID was 0x048D and data 0x00000020. Later on we get another ID 0x03A6 and data 0x00000002. trip.20111108.txt No notes. Just a drive. The ID was 0x048D and data 0x00000020. My conclusion is that '100 93' is an instruction to the VDS to tell it to display an error screen to the user. The textual message is derived from the error code (probably a lookup table in the VDS). I am not sure how these messages are 'cleared'. You can tap-to-dismiss on the VDS, which removes the alert but leaves a "(!)" on the VDS to show the alert is still a problem. That "(!)" goes away when the cause of the alert goes away. Somehow this is encoded in that B2. We could reverse the textual messages from ID by spoofing the message and seeing what the VDS displays,, but that would mean sending 65,535 errors to my VDS and I'm not comfortable doing that The list here is the next best thing, and I'll continue to add what I find. It would be very cool to have these alerts popping up on the App displays, or appearing as push notifications.
Nice work Mark. Push notifications of alerts would be awesome. I recently had error 287 - Power train problem service required. First error since getting a new PEM last June. Circumstances this time: Driving in heavy blowing snow for 100 miles car would not charge after arriving home and plugging in. I suspected a lot of snow packed up in the rear of the car. I have the new 'snow dam' blowers (or is that damn snow?). I left car to thaw out in garage and it went to charging normally in the morning. No problems since. Tesla engineers reviewed logs and said nothing to worry about. I did not get a definitive answer to whether or not the fans being frozen could have caused the error.
I've got enough data on this to know what is going on now. VDS alert messages are definitely on ID#0x100 B1=0x93. B1 = 0x93 B2 = On, Off, Severity, etc, indication B3,B4 = Error code B5,B6,B7,B8 = Data Regarding B2, I've seen: 0x01 = 00000001b = Show Alert 0x00 = 00000000b = Cancel Alert 0x05 = 00000101b = Show Alert 0x04 = 00000100b = Cancel Alert 0x15 = 00010101b = Show Message 0x14 = 00010100b = End Message I'm assuming that the least significant bit is set when the alert is raised, and cleared when it is resolved. The rest is probably a severity level, or something like that. Examples: 1) USB log transfer Code: 20.3270 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 27.0199 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 34.0614 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 40.7682 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 47.4682 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 54.7250 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 61.4526 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 61.7035 100 93 15 19 00 00 00 00 00 ->VDS (message to VDS 93) 68.1515 100 93 15 19 00 01 00 00 00 ->VDS (message to VDS 93) 74.8449 100 93 15 19 00 03 00 00 00 ->VDS (message to VDS 93) 81.5926 100 93 15 19 00 05 00 00 00 ->VDS (message to VDS 93) 88.3173 100 93 15 19 00 06 00 00 00 ->VDS (message to VDS 93) 95.0345 100 93 15 19 00 08 00 00 00 ->VDS (message to VDS 93) 101.7832 100 93 15 19 00 0A 00 00 00 ->VDS (message to VDS 93) 108.5329 100 93 15 19 00 0B 00 00 00 ->VDS (message to VDS 93) 115.2333 100 93 15 19 00 0D 00 00 00 ->VDS (message to VDS 93) 121.9544 100 93 15 19 00 0E 00 00 00 ->VDS (message to VDS 93) . . . . . . . . 578.7234 100 93 15 19 00 61 00 00 00 ->VDS (message to VDS 93) 585.4489 100 93 15 19 00 62 00 00 00 ->VDS (message to VDS 93) 592.1719 100 93 15 19 00 63 00 00 00 ->VDS (message to VDS 93) 599.1091 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 605.8596 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 612.5599 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 619.2644 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 626.0780 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 632.7609 100 93 15 19 00 64 00 00 00 ->VDS (message to VDS 93) 636.6933 100 93 14 19 00 64 00 00 00 ->VDS (message to VDS 93) 639.7882 100 93 00 FF FF 00 00 00 00 ->VDS (message to VDS 93) 2) Charge interrupt (breaker trip) Code: 93.7174 100 93 01 BA 03 00 00 20 00 ->VDS (message to VDS 93) 98.7568 100 93 01 BA 03 00 00 20 00 ->VDS (message to VDS 93) 100.7281 100 93 00 BA 03 00 00 20 00 ->VDS (message to VDS 93) 3) Drive-time alert Code: 40.2862 100 93 05 78 03 00 01 00 00 ->VDS (message to VDS 93) 46.9766 100 93 05 78 03 00 01 00 00 ->VDS (message to VDS 93) 53.6772 100 93 05 78 03 00 01 00 00 ->VDS (message to VDS 93) 60.3577 100 93 05 78 03 00 01 00 00 ->VDS (message to VDS 93) 63.2089 100 93 04 78 03 00 00 00 00 ->VDS (message to VDS 93) I also found the following, and will update the wiki document in a few minutes: 888 Disarm vehicle with key fob before starting. 1084 External Charger Problem. 1165 Key in Key Switch Door Ajar. 1169 Charge port open 1166 Release Parking Brake 1124 Unsafe Gear Shift Transition Denied 03BA (charge breaker tripped) Regards, Mark.
I just posted a bunch more. My Roadster is having some PEM cooling fan problem, so I'm getting all sorts of messages.
Excellent. When I have a moment I'll update the TeslaGLOP. Would you mind sending me a copy of your log so I can test it?
I got this one: Unknown Error 01 04 0C 00 02 06 10 00 00 00 00 00 00 00 00 40 = ID1554 (orange) VMS: Not receiving VDS version number
Received these two messages today (in debug mode) while charging: 904 Battery overvoltage fault 925 DMC HW: Common mode sense fault I was attempting a standard charge. The charge cycle put the normal amount of miles in but did not give the green "complete" signal.
I added some more error codes. I wonder if VDS-actions like certain settings can be seen on the CANbus as well, like changing PIN (which would make it possible to remotely change pin), enabling the VDS debug mode, etc.
Any interactions where the VDS is communicating with the VMS can be seen. That is pretty much everything (including pin changes), as the VDS is really just a smart display for the VMS. For example, when you call up a diag screen, a command goes VDS->VMS to tell it to start transmitting that data. Then,when you switch to another screen, another command goes VDS->VMS to tell it to stop. It is possible to reverse-engineer all the error codes by just transmitting then in the same way the VMS does. The VDS just displays the text as if it was a real alert.
That's good to know So that means we would be able to get more data towards OVMS, and maybe allow to change pin remotely.
Adding reference from friend's Roadster. Issue: Battery Problem Power Reduced with ID:600 and Data:0x0000001 error code. It also lit up the yellow "fault" word/light in the speedometer. Fix: " ....problem was low coolant flow, they replaced the coolant pump."