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

Wiki Roadster VDS Messages

  • | This is a WikiPost. Members with appropriate permissions may edit.
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
0RedBattery Problem Service RequiredCritical Brick OverVoltage fault
2Battery too cold Vehicle shutting downCritical Sheet UnderTemp fault
3BlueMaintenance Service RequiredHave the car serviced or reset the service interval.
4Battery too hot Vehicle shutting downCritical Sheet OverTemp fault
6Battery Problem Service RequiredVMS: APS Failure
7Battery Service Required
8Vehicle Idle for 1 Hour Shutting Down
10Charging Problem
13RedBattery Problem Service RequiredCritical Brick UnderVoltage fault
14ESS Temperature Sensor Fault
16Battery Problem Service RequiredBMB: Sheet alarm
19Isolation resistance warning
21YellowDebug-Only MsgAPS OverTemp Warning
23SHUTTING DOWN PULL OVER SAFELYSHUTTING DOWN PULL OVER SAFELY
25BlueMemory 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.
27Memory stick transfer failure. Reinsert stick to try again.
28Transfer to memory stick has failedTransfer to memory stick has failed
29APS: APS power inhibited
30Airbag System Service requiredSRS: Airbag enabled in car, but disabled in VMS config
31SRS: Airbag deployed. Contact Tesla Service Center
32SRS: Airbag must be serviced. Contact Tesla Service Center
43RedDebug-Only MsgVMS: APS Inhibited due to low brick voltage
50RedCommunication Problem Service RequiredBMB: No data fault
51Communication Problem Service RequiredBSM: No data fault
52Communication Problem Service RequiredCSB: No data fault
53OrangeDebug-Only MsgGPS: No data fault1) 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)
54OrangeCoolant System Problem Charging restricted toHVAC: No data fault1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub)
55OrangeDebug-Only MsgIP: No data fault1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub)
56OrangeCommunication Problem Power ReducedPEM: No data fault1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub)
57SWP: No data fault
58OrangeDebug-Only MsgTPMS: No data fault
59Communication Problem Service RequiredVMSIO: No data fault
60OrangeDebug-Only MsgDFC: No data fault1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub)
61OrangePark Lock Problem Vehicle May be Free-RollingTCM: No data fault1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub)
62OrangeDebug-Only MsgPM: No data fault1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub)
63OrangeDebug-Only MsgGS: No data fault1) Check if the APS is inhibited in the service diagnostic menu under the Controls submenu (petergrub)
90Transmission error Service requiredTCM: Oil Pump Open Circuit
91Transmission error Service requiredTCM: Oil Pump Low Current
92Transmission error Service requiredTCM: Oil Pump High Current
93Transmission error Service requiredTCM: Oil Pump Driver Fault
94Park Lock Problem Vehicle May be Free-RollingTCM: Park Motor Open Circuit
95Park failed to disengage. Service required.TCM: Park Motor jammed in Park
96TCM: Park Motor jammed in Unpark
97Park Lock Problem Vehicle May be Free-RollingTCM: Park motor jammed in the middle
98TCM: Park Hall Sensor not seen
99Park Lock Problem Vehicle May be Free-RollingTCM: Unpark Hall sensor not seen
100TCM: Hall Sensors both on
101Parking System Service RequiredTCM: CRC error
102Parking System Service RequiredTCM: Lost VMS comms
103Parking System Service RequiredTCM: Lost ABS comms
104TCM: Lost DMC comms
105Parking System Service RequiredTCM: Lost DFC comms
106Parking System Service RequiredTCM: ABS error
107Parking System Service RequiredTCM: CAN error
108TCM: Watchdog timer reset
257RedDebug-Only MsgAPS output 1 (main) reset
258RedDebug-Only MsgAPS output 2 (PEM) reset1) Check if the APS input connector, RHC33, is plugged in on the right side of the PEM (petergrub)
259RedCharge Aborted/Battery Problem Service RequiredBSM: Sheet AlarmBattery is too low to charge
260Battery Service RequiredBSM: Smoke detected
261Service required Charging restrictedBSM: Smoke detector not reporting
262BSM: Immersion fault1) 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)
263RedPowertrain Problem Restart When SafeBSM: HVAC cable fault
264RedPowertrain Problem Restart When SafeBSM: PEM cable fault
265Powertrain Problem Restart When SafeBSM: V_batt too low
266BSM: V_batt too high
267BSM: Positive contactor/economizer stuck low
268BSM: Positive contactor/economizer stuck high
269BSM: Negative contactor/economizer stuck low
270BSM: Negative contactor/economizer stuck high
271RedBattery Problem Vehicle shutting downBSM: Contractor power failureHas 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.
272Powertrain Problem Restart When SafeBSM: PEM HVAC cable/pin discharge failure
273Powertrain Problem Restart When SafeBSM: V_ess too high
274Powertrain Problem Restart When SafeBSM: CSB commanded contactors to open
275Powertrain Problem Service RequiredBSM: Precharge to fast at t1
276Powertrain Problem Service RequiredBSM: V_ess too low at end of precharge
277Powertrain Problem Service RequiredBSM: V_batt too low at start of precharge
278Powertrain Problem Service RequiredBSM: V_ess too high at start of precharge
279Powertrain Problem Service RequiredBSM: Precharge resistor too hot at start of precharge
280BSM: Discharge enabled at start of precharge
281BSM: Orientation fault
282BSM: ESS OverTermp fault
283OrangeDebug-Only MsgBSM: Isolation fault
284BSM: Voltage sensor error
285BSM: Isolation fault before closing contactors
286OrangeDebug-Only MsgBSM: Isolation fault while contactors closed
287Power train Problem Service RequiredBSM: Isolation fault before charge
288OrangeBSM: V_ess too low during precharge, t2
398BlueKey must be on to select new tires
399Cannot select new tires while moving
400BlueCoast in a straight line at 20-60mph for 10 seconds
401YellowTPMS: Left front tire very softTPMS: Left front tire very soft1) 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)
402TPMS: Left front tire softTPMS: Left front tire soft1) Data field may describe which tires are soft. E.g. only a soft left front tire should show 0x00000002 (petergrub)
403YellowTPMS: Right front tire very softTPMS: Right front tire very soft1) Data field describes which tires are very soft. E.g. only a very soft right front tire shows 0x00000004 (petergrub)
404TPMS: Right front tire softTPMS: Right front tire soft1) Data field may describe which tires are soft. E.g. only a soft right front tire should show 0x00000008 (petergrub)
405TPMS: Left rear tire very softTPMS: Left rear tire very soft1) Data field describes which tires are very soft. E.g. only a very soft left rear tire shows 0x00000010 (petergrub)
406TPMS: Left rear tire softTPMS: Left rear tire soft1) Data field may describe which tires are soft. E.g. only a soft left rear tire should show 0x00000020 (petergrub)
407YellowTPMS: Right rear tire very softTPMS: Right rear tire very soft1) Data field describes which tires are very soft. E.g. only a very soft right rear tire shows 0x00000040 (petergrub)
408TPMS: Right rear tire softTPMS: Right rear tire soft1) Data field may describe which tires are soft. E.g. only a soft right rear tire should show 0x00000080 (petergrub)
409TPMS: Hardware ErrorTPMS: Hardware errorTire 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).
410TPMS: Tire over-pressure warning
411TPMS: Tire OverTemp warningTPMS: Tire OverTemp warning
412TPMS: Rapid tire pressure lossTPMS: Rapid tire pressure loss
413TPMS: Check left front tireTPMS: Check left front tire
414TPMS: Check right front tireTPMS: Check right front tire
415TPMS: Check left back tireTPMS: Check left back tire
416TPMS: Check right back tireTPMS: Check right back tire
420SWP: APS off, but no pulse from BPS
428Orange12V Battery Service RequiredSWP: Aux Battery Supply LowTurned out battery fuse was missing. Or an old Battery (0x81248884)
429SWP: Eeprom checksum error
430SWP: CAN Rx OverFlow
500VMS: Security alert, left door opened
501VMS: Security alert, right door opened
502VMS: Security alert, trunk opened
503VMS: Security alert, hood opened
504VMS: Security alert, key inserted
525ABS: Short circuit
526SWP: Radio short circuit
527YellowRight Headlight Bulb OutCheck right front high beam bulbReplace the right high beam headlight bulb
528YellowLeft Headlight Bulb OutCheck left front high beam bulbReplace the left high beam headlight bulb
529OrangeRight Headlight Bulb OutCheck right front low beam bulbReplace the right low beam headlight bulb
530OrangeLeft Headlight Bulb OutCheck left front low beam bulbReplace the left low beam headlight bulb
531Check marker light bulbs
532OrangeLeft side turn signal open/short circuit
533OrangeRight side turn signal open/short circuit
534Left window motor issue
535BlueDebug-Only MsgRight window motor issue
536YellowCheck left back turn signal bulb
537YellowCheck left front turn signal bulb
538YellowCheck right back turn signal bulb
539YellowCheck right front turn signal bulb
547Check rear fog lamps
560BlueTimed out of Range Mode (after charging)
561Timed out of Performance Mode (after charging)
600YellowAPS: Cooling issue; power limiting in effect
601ESS: MaxT brick too hot; power limiting in effect
602SHUTDOWN IMMINENT Power limitedSHUTDOWN IMMINENT Power limited
603BSM: Isolation resistance fault; power limiting in effect
604YellowBattery Low Power ReducedESS: Low State of charge: power limiting in effectYou need to recharge
605Standard range SOC floor reached. Stop & Charge.Standard range SOC floor reached. Stop & Charge.
606YellowESS: Range Mode Remaining charge uncertainYou need to recharge
607ESS: MaxT brick extremely hot; power limiting in effectESS: MaxT brick extremely hot; power limiting in effect
608YellowESS: Almost empty. Car stops in 3 milesESS: Almost empty. Car stops in 3 miles
609ESS: BSM/CSB/BMB no data fault; power limitedESS: BSM/CSB/BMB no data fault; power limited
610ESS: Almost empty. Car stops in 2 milesESS: Almost empty Car stops in 2 miles
611ESS: Almost empty. Car stops in 1 mileESS: Almost empty. Car stops in 1 mile
612Multiple Temp Sensor Faults; Vehicle entering limp modeMultiple Temp Sensor Faults; Vehicle entering limp mode
613VMS: Use MC120 to avoid trickle charge
700YellowBrake fluid lowBrake fluid low
701ABS: Service requiredABS: Service required
702ABS: Service requiredABS: Service required
703ABS: Service requiredABS: Service required
720900A discharge limit exceeded900A discharge limit exceeded
721863A discharge limit esceeded863A discharge limit exceeded
722805A discharge limit exceeded805A discharge limit exceeded
723300A discharge limit exceeded300A discharge limit exceeded
724200A discharge limit exceeded200A discharge limit exceeded
725190A charge limit exceeded190A charge limit exceeded
72675A charge limit exceeded75A charge limit exceeded
72760A charge limit exceeded60A charge limit exceeded
728Overtemp event during charge or regenOvertemp event during charge or regen
729Undertemp event during charge or regen
730750A discharge warning
731450A discharge warning; power limited
732300A discharge warning; power limited
733200A discharge warning; power limited
73475A charge warning
73560A charge warning
737CSB: Discharge Undertemp
739CSB: BMB No Data fault
880While staring, keep foot off accelerator pedalWhile starting, keep foot off accelerator pedal
881While starting, foot brake must be pressedWhile starting, foot brake must be pressed
882Before starting, charge port door must be closedBefore starting, close charge port door
883BlueBefore starting, exit Tow modeBefore starting, exit Tow mode1) 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)
884Battery empty Can't startBattery empty Can't start
885BMB No Data fault Can't startBMB No Data fault Can't start
886Battery cold Can't startBattery cold Can't start
887RedCan't start Version number mismatch1) Sometimes paired with 1553 (petergrub)
888RedDisarm vehicle with key fob before startingVMS/PEM key mismatchPress the button on the keyfob.
889Service Required. Charging restricted to storage level.Service Required. Charging restricted to storage level.
901RedDMC HW: PhaseA OverCurrent Fault
902RedDMC HW: PhaseB OverCurrent Fault
903RedDMC HW: PhaseC OverCurrent Fault
904DMC HW: Battery OverVoltage Fault
905RedPowertrain Problem Restart When SafeDMC HW: PhaseA Low Side Desat Fault
906DMC HW: PhaseA High Side Desat Fault
907RedDMC HW: PhaseA Bias Under Voltage Fault
908DMC HW: PhaseA Bus Over voltage fault
909DMC HW: PhaseB Low Side Desat Fault
910DMC HW: PhaseB High Side Desat Fault
911RedDMC HW: PhaseB Biad UnderVoltage fault
912DMC HW: PhaseB Bus OverVoltage fault
913DMC HW: PhaseC Low Side Desat fault
914DMC HW: PhaseC High Side Desat fault
915RedDMC HW: PhaseC Bias UnderVoltage fault
916DMC HW: PhaseC Bus OverVoltage fault
917DMC HW: APS UnderVoltage fault
918DMC HW: Motor OverTerm fault
919DMC HW: Pedal Monitor fault
920DMC HW: Line OverCurrent fault
921DMC HW: PhaseA OverTemp fault
922DMC HW: PhaseB OverTemp fault
923RedDMC HW: PhaseC OverTerm fault
924DMC HW: ESS Cable Interlock faultThe dealer believes this might be caused by slight corrosion on the terminals of the safety wire.
925DMC HW: Common Mode Sense fault
926DMC HW: PDP Interrupt fault
927RedDMC HW: PhaseA OverCurrent fault
928RedDMC HW: PhaseB OverCurrent fault
929RedDMC HW: PhaseC OverCurrent fault
930RedDMC FW: PhaseA OverCurrent Peak fault
931RedDMC FW: PhaseB OverCurrent Peak fault
932RedDMC FW: PhaseC OverCurrent Peak fault
933DMC FW: Line OverCurrent fault
934DMC FW: Line OverCurrent Peak Fault
935DMC FW: Line OverVoltage fault
936YellowCharging ProblemDMC FW: Line OverVoltage Peak fault
937Charge Problem Extension Cord DetectedDMC FW: Line UnderVoltage fault
938DMC FW: Battery OverVoltage fault
939DMC FW: Battery UnderVoltage fault
940DMC FW: Motor OverSpeed fault
941DMC FW: Motor Sensor1 OverTemp fault
942DMC FW: Motor Sensor2 OverTerm fault
943DMC FW: Motor Sensor1 UnderTemp fault
944DMC FW: Motor Sensor2 UnderTerm fault
945RedSystem too hot - Vehicle shutting downDMC FW: PhaseA OverTemp fault
946DMC FW: PhaseA Temp Diff fault
947RedSystem Too Hot - Vehicle Shutting DownDMC FW: PhaseB OverTemp faultPreceded 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.
948DMC FW: PhaseB Temp Diff fault
949RedDMC FW: PhaseC OverTemp fault
950DMC FW: PhaseC Temp Diff fault
951DMC FW: Ambient OverTemp fault
952DMC FW: Amvient UnderTemp fault
953Line Voltage Lost SyncDMC FW: Line OverFrequency FaultBad power; try lowering the current and restarting (or breaker tripped)
954Line Voltage Lost SyncDMC FW: Line UnderFrequency FaultBad power; try lowering the current and restarting (or breaker tripped)
955DMC FW: Line Sync Loss fault
956DMC FW: HCS Faulted
957DMC FW: PEM Vbat diff from BSM Vbat fault
958DMC FW: HCS Invalid Pilot Signal fault
959DMC FW: Line Current or Voltage Offset Too Large fault
960DMC FW: VBrickMax versus VBattery Error faultYou don't want to know.
961DMC FW: VBrickMax or VBrickLimit is invalid
962OrangeDMC FW: Line Current Error fault
963OrangePowertrain Problem Service RequiredDMC FW: Line Current Not Equal Request faultUser 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.
964DMC FW: Pilot Signal Present in Drive Mode fault
965DMC FW: Gear Selector Comms fault
966DMC FW: Invalid Shift Request Fault
967DMC FW: Press brake before shifting fault
968DMC FW: Lost VMS Comms fault
969DMC FW: Lost DFC Comms fault
970DMC FW: Lost ABS Comms (and TC) fault
971DMC FW: CAN Comms Error fault
972RedPowertrain Problem Service RequiredDMC FW: Accelerator Erorr fault
973DMC FW: Motor Encoder Error fault
974RedDMC FW: Pole Current Error Fault
975DMC FW: ABS Error fault
976DMC FW: Invalid State fault
977Car moved while charging - charge stopped.DMC FW: Moving during charge faultGot this for trying to change the wheels while charging the car! Spinning front right wheel by hand (after jacking up car) triggered the message.
978DMC FW: Invalid State request fault
979DMC FW: Invalid Mode request fault
980DMC FW: Invalid Charge Request fault
981OrangeDMC FW: Bad State Transition FaultDog tripped over charging cable. Discuss.
Charger seems to be having troubles. A reset from the chargepoint fixed it.
982DMC FW: Mode Trans Condition fault
983DMC FW: Memory Error fault
984DMC FW: Bad Argument fault
985DMC FW: Interrupt Time too Long fault
986DMC FW: MotorTemp Sensor1 fault
987DMC FW: MotorTemp Sensor2 fault
988DMC FW: MotorTemp Sensors differ fault
989DMC FW: VBrickMin Not Increasing
990DMC FW: Voltage Discharge Time fault
991DMC FW: 5V Power
992DMC FW: Lost TCM comms
993DMC FW: PCS Current Offset Too Large fault
994DMC FW: Watchdog timer reset fault
995DMC FW: TCM Refusal fault
996DMC FW: Unsafe gear transition faultPress brake before shifting
997DMC FW: CAN Rx
998DMC FW: CAN Tx
999DMC FW: CAN Overrun
1000DMC FW: SPI Open
1001DMC FW: SPI Read
1002DMC FW: VBUS Present With ILoop Open
1003DMC FW: Lost Comms With Shifter
1004DMC FW: Relay Driver
1005DMC FW: Line Contactor
1006DMC FW: Antispark Contactor
1007OrangeDebug-Only MsgDMC FW: Run Contactor
1008DMC FW: APS Undervoltage
1009DMC FW: Encoder Hardware
1010DMC FW: Fault 110
1011DMC FW: Accelerator 5V
1012DMC FW: Firmware Error
1013DMC FW: FAULT Pole Power
1029DMC HW: PhaseA OverCurrent warning
1030DMC HW: PhaseB OverCurrent warning
1031DMC HW: PhaseC OverCurrent warning
1032DMC HW: Battery OverVoltage warning
1033DMC HW: PhaseA Low Side Desat warning
1034DMC HW: PhaseA High Side Desat warning
1035DMC HW: PhaseA Bias UnderVoltage warning
1036DMC HW: PhaseA Bus OverVoltage warning
1037DMC HW: PhaseB Low Side Desat warning
1038DMC HW: PhaseB High Side Desat warning
1039DMC HW: PhaseB Bias UnderVoltage warning
1040DMC: HW PhaseB Bus OverVoltage warning
1041DMC HW: PhaseC Low Side Desat warning
1042DMC HW: Phase C High Side Desat warning
1043DMC HW: PhaseC Bias Under Voltage warning
1044DMC HW: PhaseC Bus Over Voltage warning
1045DMC HW: APS Under Voltage warning
1046DMC HW: Motor OverTemp warning
1047DMC HW: Pedal Monitor warning
1048DMC HW: Line Over Current warning
1049DMC HW: PhaseA OverTemp warning
1050DMC HW: PhaseB OverTemp warning
1051DMC HW: PhaseC OverTemp warning
1052DMC HW: ESS Cable Interlock warning
1053DMC HW: Common Mode Sense warning
1054DMC HW: PDP Interrupt warning
1055DMCFW: PhaseA OverCurrent warning
1056DMCFW: PhaseB OverCurrent warning
1057DMCFW: PhaseC OverCurrent warning
1058DMC FW: PhaseA OverCurrent Peak warning
1059DMC FW: PhaseB OverCurrent Peak warning
1060DMC FW: PhaseC OverCurrent Peak warning
1061DMC FW: Line OverCurrent warning
1062DMC FW: Line OverCurrent Peak warning
1063DMC FW: Line OverVoltage warning
1064DMC FW: Line OverVoltage Peak warning
1065DMC FW: Line UnderVoltage warning
1066DMCFW: Battery OverVoltage warning
1067OrangeDebug-Only MsgDMCFW: Battery UnderVoltage warning
1068DMC FW: Motor OverSpeed warning
1069OrangeDMC FW: Motor sensor 1 OverTemp warning. Torque limited
1070OrangeDMC FW: Motor sensor 2 OverTemp warning. Torque limited
1071DMC FW: Motor Sensor1 UnderTemp warning
1072DMC FW: Motor Sensor2 UnderTemp warning
1073DMC FW: PhaseA OverTemp warning. Torque limited.
1074DMC FW: PhaseA Temp Diff warning
1075OrangeDebug-Only MsgDMC FW: PhaseB OverTemp warning. Torque limited.
1076OrangeDebug-Only MsgDMC FW: PhaseB Temp Diff warning
1077OrangeDebug-Only MsgDMC FW: PhaseC OverTemp warning. Torque limited.
1078OrangeDebug-Only MsgDMC FW: PhaseC Temp Diff warning
1079DMC FW: Ambient OverTemp warning
1080DMC FW: Ambient UnderTemp
1081DMC FW: Line OverFrequency warning
1082DMC FW: Line UnderFrequency warning
1083DMC FW: Line Sync Loss warning
1084External Charger ProblemDMC FW: HCS Faulted warningUMC's red fault light blinking. Unplugged car & UMC, then replugged and all OK.
1085OrangeDebug-Only MsgDMC FW: PEM Vbat different from BSM Vbat warning
1086DMC FW: HCS Invalid Pilot Signal warning
1087DMC FW: Line Current or Voltage Offset Too Large warningPEM fuse(s) blown, needs to be replaced. Can show up incidentally without meaning any trouble.
1088DMC FW: VBrickMax versus VBattery Error warning
1089DMC FW: VBrickMax or VBrickLimit is invalid
1090DMC FW: Line Current Error warning
1091DMC FW: Line Current Not Equal Request warning
1092YellowDo not plug in charge cable while drivingDMC FW: Pilot Signal Present in Drive Mode warningKey left in ignition while trying to plug in?
1093DMC FW: Shifter error warning
1094DMC FW: Invalid Shift Request warning
1095Press brake pedal before shift.DMC FW: Press brake before shift.Press brake pedal and then select a gear.
1096OrangeDebug-Only MsgDMC FW: Lost VMS comms warning
1097DMC FW: Lost DFC comms warning
1098OrangeDMC FW: Lost ABS Comms (and TC) warning
1099DMC FW: CAN comms error warning
1100DMC FW: Accelerator Error warning
1101DMC FW: Motor Encoder Error warning
1102DMC FW: Pole Current Error warning
1103OrangeABS & Traction Control Problems. Service Required.DMC FW: ABS Error warningPulling out ignition key and waiting until car shutdown (15 minutes) cleared it. Tesla couldn't find issue.
1104DMC FW: Invalid State warning
1105DMC FW: Moving during charge warning
1106DMC FW: Invalid State Request warning
1107DMC FW: Invalid Mode Request warning
1108DMC FW: Invalid Charge Request warning
1109DMC FW: Bad State Transition warning
1110DMC FW: Mode Trans Condition warning
1111DMC FW: Memory Error warning
1112DMC FW: Bad Argument warning
1113DMC FW: Interrupt Time too Long warning
1114DMCFW: Motor Temp Sensor 1 warning
1115DMCFW: Motor Temp Sensor 2 warning
1116DMC FW: Motor Temp Sensors Differ warning
1117DMC FW: VBrickMin Not Increasing
1118DMC FW: Voltage Discharge Time Warning
1119DMC FW: 5V Power
1120DMC FW: Lost TCM comms warning
1121OrangeDebug-Only MsgDMC FW: PCS Current Offset Too Large warning
1124Unsafe Gear Shift Transition DeniedCar moving too fast for gear change drive/reverse
1138Voltage on Charge Port Line2 during drive with charge door open
1144Powertrain 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 contact
1146DMC 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].
1152Charge 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.
1153DMC Wear Factor Warning
1160Drivers door ajarClose the door.
1161Passenger door ajarClose the door.
1162Trunk ajarClose the trunk.
1165Key in Key Switch Door AjarDriver door opened while car is on
1166Release Parking BrakeCar is driven while parking brake (partially) engaged
1167blueHeadlights still on
1169Charge port openCharge port opened when car is on
1170Tow Mode is not available while car is on
1174Fasten SeatbeltFasten your seatbelt.
1416Low Power System Service Required
1425HVAC: Low current pump failure
1426HVAC: High current pump failure
1452orangeHVAC: Low pressure
1453Coolant System Problem Service RequiredHVAC: Refrigerant High Pressure
1463HVAC: 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
1465HVAC: Low current pump fault
1469HVAC: Compressor comms timeout
1471HVAC: Compressor DTC comms timeout
1493yellowESS: Extremely Low. Begin Charging ASAP.
1533Software 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 file
1554orangeVMS: 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.
1664yellowPM: Lost VMS comms warningBlue connector at VMS not plugged in
1900orangeCommunication 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.
1901blueN/AWindow with just text "N/A"
2005yellowNo response to request to stop chargingfollow error of ID1554
2017yellowNo response to request to change charge modefollow error of ID1554
2031yellowNo response to request to save charging timefollow error of ID1554
2033yellowNo response to request to save charge timingfollow error of ID1554
2035yellowNo response to request to save current limitfollow error of ID1554
2037yellowNo response to request to save cost/kWhfollow error of ID1554
2070yellowNo response to request to get keyfob functionfollow error of ID1554
2078yellowThere was a problem processing your requestNo response to request to enter Tow Modefollow error of ID1554
2096yellowNo response to Pin submissionfollow error of ID1554
3001SHFT: APS Voltage?
3011Drive Button Failure Vehicle May not be Able to Enter Drive
3021SHFT: Neutral switch Stuck Down
3022SHFT: DRIVE switch Stuck Down
-->
 
Last edited by Roadster
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.
 

doug

Administrator / Head Moderator
Administrator
Nov 28, 2006
17,022
1,203
SF Bay Area
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
 
Last edited:

markwj

Asia Pacific
Moderator
Apr 10, 2011
4,662
1,334
Hong Kong
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.
 

markwj

Asia Pacific
Moderator
Apr 10, 2011
4,662
1,334
Hong Kong
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.
 
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.
 

markwj

Asia Pacific
Moderator
Apr 10, 2011
4,662
1,334
Hong Kong
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.
 

Products we're discussing on TMC...

About Us

Formed in 2006, Tesla Motors Club (TMC) was the first independent online Tesla community. Today it remains the largest and most dynamic community of Tesla enthusiasts. Learn more.

Do you value your experience at TMC? Consider becoming a Supporting Member of Tesla Motors Club. As a thank you for your contribution, you'll get nearly no ads in the Community and Groups sections. Additional perks are available depending on the level of contribution. Please visit the Account Upgrades page for more details.


SUPPORT TMC
Top