TMC is an independent, primarily volunteer organization that relies on ad revenue to cover its operating costs. Please consider whitelisting TMC on your ad blocker or making a Paypal contribution here: paypal.me/SupportTMC

Roadster

Discussion in 'Wiki' started by Slackjaw, Aug 31, 2012.

Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
  1. Slackjaw

    Slackjaw Member

    Joined:
    Apr 12, 2011
    Messages:
    354
    Location:
    Central NJ
    #1 Slackjaw, Aug 31, 2012
    Last edited by BartJ: Apr 25, 2016
    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


    Battery Problem Service Required

    2
    Battery too cold Vehicle shutting down

    3blueMaintenance Service Required
    Have the car serviced or reset the service interval.
    4
    Battery too hot Vehicle shutting down

    6
    Battery Problem Service Required

    7
    Battery Service Required

    8
    Vehicle Idle for 1 Hour Shutting Down

    10
    Charging Problem

    13
    Battery Problem Service Required

    16
    Battery Problem Service Required

    23
    SHUTTING DOWN PULL OVER SAFELY

    25blueMemory Stick transfer in progress. ...
    Car is downloading logs to USB memory stick.
    28
    Transfer to memory stick has failed

    30
    Airbag System Service required

    50
    Communication Problem Service Required

    51
    Communication Problem Service Required

    52
    Communication Problem Service Required

    53
    GPS: No data fault

    54
    Coolant System Problem Charging restricted to

    55
    IP: No data fault

    56
    Communication Problem Power Reduced

    59
    Communication Problem Service Required

    61
    Park Lock Problem Vehicle May be Free-Rolling

    90
    Transmission error Service required

    91
    Transmission error Service required

    92
    Transmission error Service required

    93
    Transmission error Service required

    94
    Park Lock Problem Vehicle May be Free-Rolling

    95
    Park failed to disengage. Service required.

    97
    Park Lock Problem Vehicle May be Free-Rolling

    99
    Park Lock Problem Vehicle May be Free-Rolling

    101
    Parking System Service Required

    102
    Parking System Service Required

    103
    Parking System Service Required

    105
    Parking System Service Required

    106
    Parking System Service Required

    107
    Parking System Service Required

    259
    Charge AbortedBattery Problem Service RequiredBattery is too low to charge
    260
    Battery Service Required

    261
    Service required Charging restricted

    263
    Powertrain Problem Restart When Safe

    264
    Powertrain Problem Restart When Safe

    265
    Powertrain Problem Restart When Safe

    269

    BSM: Negative contactor/economizer stuck low
    271
    Battery 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.
    272
    Powertrain Problem Restart When Safe

    273
    Powertrain Problem Restart When Safe

    274
    Powertrain Problem Restart When Safe

    275
    Powertrain Problem Service Required

    276
    Powertrain Problem Service Required

    277
    Powertrain Problem Service Required

    278
    Powertrain Problem Service Required

    279
    Powertrain Problem Service Required

    281

    BSM: Orientation fault
    282

    BSM: ESS OverTermp fault
    283

    BSM: Isolation fault
    284

    BSM: Voltage sensor error
    285

    BSM: Isolation fault before closing contactors
    286

    BSM: Isolation fault while contactors closed
    287
    Power train Problem Service RequiredBSM: Isolation fault before charge
    288

    BSM: V_ess too low during precharge, t2
    398blue
    Key must be on to select new tires
    399
    Cannot select new tires while moving

    400blueCoast in a straight line at 20-60mph for 10 seconds

    401
    TPMS: Left front tire very soft

    402
    TPMS: Left front tire soft

    403
    TPMS: Right front tire very soft

    404
    TPMS: Right front tire soft

    405
    TPMS: Left rear tire very soft

    406
    TPMS: Left rear tire soft

    407
    TPMS: Right rear tire very soft

    408
    TPMS: Right rear tire soft

    409
    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).
    411
    TPMS: Tire OverTerm warning

    412
    TPMS: Rapid tire pressure loss

    413
    TPMS: Check left front tire

    414
    TPMS: Check right front tire

    415
    TPMS: Check left back tire

    416
    TPMS: Check right back tire

    420

    SWP: 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)
    429

    SWP: Eeprom checksum error
    430

    SWP: CAN Rx OverFlow
    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.
    539Orange
    Check Right Front Turn Bulb
    600

    APS: Cooling issue; power limiting in effect
    601

    ESS: MaxT brick too hot; power limiting in effect
    602
    SHUTDOWN IMMINENT Power limited

    603

    BSM: Isolation resistance fault; power limiting in effect
    604
    Battery Low Power ReducedESS: Low State of charge: power limiting in effectYou need to recharge
    605
    Standard range SOC floor reached. Stop & Charge.

    606Yellow
    ESS:Range Mode Remaining charge uncertainYou need to recharge
    607
    ESS: MaxT brick extremely hot; power limiting in effect

    608
    ESS: Almost empty. Car stops in 3 miles

    609
    ESS: BSM/CSB/BMB no data fault; power limited

    610
    ESS: Almost empty. Car stops in 2 miles

    611
    ESS: Almost empty. Car stops in 1 mile

    612
    Multiple Temp Sensor Faults; Vehicle entering limp mode

    613
    VMS: Use MC120 to avoid trickle charge

    700
    Brake fluid low

    701
    ABS: Service required

    702
    ABS: Service required

    703
    ABS: Service required

    720
    900A discharge limit exceeded

    721
    863A discharge limit esceeded

    722
    805A discharge limit exceeded

    723
    300A discharge limit exceeded

    724
    200A discharge limit exceeded

    725
    190A charge limit exceeded

    726
    75A charge limit exceeded

    727
    60A charge limit exceeded

    728
    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

    880
    While staring, keep foot off accelerator pedal

    881
    While starting, foot brake must be pressed

    882
    Before starting, charge port door must be closed

    883
    Before starting, exit Tow mode
    The car is still in tow mode, so it cannot be started.
    884
    Battery empty Can't start

    885
    BMB No Data fault Can't start

    886
    Battery cold Can't start

    887Red
    Can't start Version number mismatchPaired with 1553
    888redDisarm vehicle with key fob before startingVMS/PEM key mismatchPress the button on the keyfob.
    889
    Service Required. Charing restricted to storage level.

    901

    DMC HW: PhaseA OverCurrent Fault
    902

    DMC HW: PhaseB OverCurrent Fault
    903

    DMC HW: PhaseC OverCurrent Fault
    904

    DMC HW: Battery OverVoltage Fault
    905

    DMC HW: PhaseA Low Side Desat Fault
    906

    DMC HW: PhaseA High Side Desat Fault
    907

    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

    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

    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

    DMC HW: PhaseC OverTerm fault
    924

    DMC HW: ESS Cable Interlock faultThe 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

    DMC HW: PhaseA OverCurrent fault
    928

    DMC HW: PhaseB OverCurrent fault
    929

    DMC HW: PhaseC OverCurrent fault
    930

    DMC FW: PhaseA OverCurrent Peak fault
    931

    DMC FW: PhaseB OverCurrent Peak fault
    932

    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
    936yellowCharging ProblemDMC FW: Line OverVoltage Peak fault
    937
    Charge Problem Extension Cord DetectedDMC 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
    System too hot - Vehicle shutting downDMC FW: PhaseA OverTemp fault
    946

    DMC FW: PhaseA Temp Diff fault
    947
    System 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.
    948

    DMC FW: PhaseB Temp Diff fault
    949

    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 SyncDMC FW: Line Voltage Lost Sync or OverFrequency FaultBad power; try lowering the current and restarting (or breaker tripped)
    954
    Line Voltage Lost SyncDMC FW: Line Voltage Lost Sync or UnderFrequency FaultBad 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 faultYou don't want to know.
    961

    DMC FW: VBrickMax or VBrickLimit is invalid
    962

    DMC FW: Line Current Error fault
    963

    DMC FW: Line Curretn Not Equal Request fault
    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

    DMC FW: Accelerator Erorr fault
    973

    DMC FW: Motor Encoder Error fault
    974

    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 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.
    978

    DMC FW: Invalid State request fault
    979

    DMC FW: Invalid Mode request fault
    980

    DMC FW: Invalid Charge Request fault
    981

    DMC FW: Bad State Transition FaultDog 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 faultPress brake before shifting
    997

    DMC FW: CAN Rx
    998

    DMC FW: CAN Tx
    999

    DMC FW: CAN Overrun
    1069Orange
    DMC FW: Motor sensor 1 OverTemp warning. Torque limited
    1070Orange
    DMC FW: Motor sensor 2 OverTemp warning. Torque limited
    1073

    DMC FW: PhaseA OverTemp warning. Torque limited
    1074

    DMC FW: PhaseA Temp Diff warning
    1075

    DMC FW: PhaseB OverTemp warning. Torque limited
    1076

    DMC FW: PhaseB Temp Diff warning
    1077

    DMC FW: PhaseC OverTemp warning. Torque limited
    1078

    DMC FW: PhaseC Temp Diff warning
    1084
    External Charger Problem

    1087

    DMC FW: Line Current or Voltage Offset Too Large warningPEM fuse(s) blown, needs to be replaced. Can show up incidentally without meaning any trouble.
    1092
    Do not plug in charge cable while driving
    Key left in ignition while trying to plug in?
    1095
    Press brake pedal before shift.DMC FW: Press brake before shift.Press brake pedal and then select a gear.
    1103
    ABS & Traction Control Problems. Service Required.?Pulling out ignition key and waiting until car shutdown (15 minutes) cleared it. Tesla couldn't find issue.
    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 contact
    1146

    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 on
    1166
    Release Parking Brake
    Car is driven while parking brake (partially) engaged
    1167blueHeadlights still on

    1169
    Charge port open
    Charge port opened when car is on
    1170
    Tow Mode is not available while car is on

    1174
    Fasten Seatbelt
    Fasten your seatbelt.
    1416
    Low Power System Service Required

    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 file
    1554orange
    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 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.
    1901blue
    N/AWindow with just text "N/A"
    2005yellow
    No response to request to stop chargingfollow error of ID1554
    2017yellow
    No response to request to change charge modefollow error of ID1554
    2031yellow
    No response to request to save charging timefollow error of ID1554
    2033yellow
    No response to request to save charge timingfollow error of ID1554
    2035yellow
    No response to request to save current limitfollow error of ID1554
    2037yellow
    No response to request to save cost/kWhfollow error of ID1554
    2070yellow
    No 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
    2096yellow
    No response to Pin submissionfollow error of ID1554
    ?
    External Charger Problem?UMC's red fault light blinking. Unplugged car & UMC, then replugged and all OK.
    3011
    Drive Button Failure Vehicle May not be Able to Enter Drive

    3021

    SHFT: Neutral switch Stuck Down
    3022

    SHFT: DRIVE switch Stuck Down
    [1] I only ever saw this message in debug mode, and it was coming up a lot (several times per hour of driving). It completely stopped when I left debug mode. Not sure if this is coincidence.

    Common issues and solutions

    Q: Stock halogen headlights aren't that good. What to do?
    A: Upgrade them to Xenon HIDs.

    Q: I don't have an iPhone, what should I do with the iPhone dock?
    A: Convert it to USB

    Q: My key fob only opens the car when I'm really close to it.
    A1: Replace the battery
    A2: Extend/move the antenna cable

    More to come

    third section

     
    • Like x 1
  2. Slackjaw

    Slackjaw Member

    Joined:
    Apr 12, 2011
    Messages:
    354
    Location:
    Central NJ
    I can't work out how to add sub pages. Is it possible?
     
  3. doug

    doug Administrator / Head Moderator

    Joined:
    Nov 28, 2006
    Messages:
    15,914
    Location:
    Stanford, California
    What do you want to do? Is this supposed to be specifically about the Roadster or about the VDS?
     
  4. Slackjaw

    Slackjaw Member

    Joined:
    Apr 12, 2011
    Messages:
    354
    Location:
    Central NJ
    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.
     
  5. doug

    doug Administrator / Head Moderator

    Joined:
    Nov 28, 2006
    Messages:
    15,914
    Location:
    Stanford, California
    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.
     
  6. Slackjaw

    Slackjaw Member

    Joined:
    Apr 12, 2011
    Messages:
    354
    Location:
    Central NJ
    Got it, thanks for the help. I like your edits.
     
  7. PV-EV

    PV-EV Member

    Joined:
    Jun 3, 2011
    Messages:
    172
    Location:
    Alaska
    #7 PV-EV, Sep 27, 2012
    Last edited: Sep 27, 2012
    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
     
  8. vfx

    vfx Well-Known Member

    Joined:
    Aug 18, 2006
    Messages:
    14,792
    Location:
    CA CA
    I have been taking pictures of various screens. I can post them here over time.

    Will show with key in ignition.
     
  9. TEG

    TEG TMC Moderator

    Joined:
    Aug 20, 2006
    Messages:
    17,252
    Location:
    Silicon Valley
    Check the main page again... I just added a bunch. Got any others?
     
  10. markwj

    markwj Moderator, Asia Pacific

    Joined:
    Apr 10, 2011
    Messages:
    3,664
    Location:
    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.
     
  11. PV-EV

    PV-EV Member

    Joined:
    Jun 3, 2011
    Messages:
    172
    Location:
    Alaska
    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.
     
  12. markwj

    markwj Moderator, Asia Pacific

    Joined:
    Apr 10, 2011
    Messages:
    3,664
    Location:
    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.
     
  13. smorgasbord

    smorgasbord Active Member

    Joined:
    Jun 3, 2011
    Messages:
    2,379
    Location:
    SF Bay Area
    I just posted a bunch more. My Roadster is having some PEM cooling fan problem, so I'm getting all sorts of messages.
     
  14. Doug_G

    Doug_G Lead Moderator

    Joined:
    Apr 2, 2010
    Messages:
    15,852
    Location:
    Ottawa, Canada
    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?
     
  15. Saftwerk

    Saftwerk Member

    Joined:
    Nov 20, 2012
    Messages:
    20
    Location:
    Bavaria
    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

     
  16. CSPHD

    CSPHD Member

    Joined:
    Aug 3, 2014
    Messages:
    19
    Location:
    Alabama
    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.
     
  17. Chillout

    Chillout Member

    Joined:
    Jun 30, 2014
    Messages:
    307
    Location:
    the Netherlands
    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.
     
  18. markwj

    markwj Moderator, Asia Pacific

    Joined:
    Apr 10, 2011
    Messages:
    3,664
    Location:
    Hong Kong
    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.
     
  19. Chillout

    Chillout Member

    Joined:
    Jun 30, 2014
    Messages:
    307
    Location:
    the Netherlands
    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.
     
  20. wiztecy

    wiztecy Active Member

    Joined:
    Apr 29, 2012
    Messages:
    2,721
    Location:
    Santa Cruz, California, United States
    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."
     
    • Like x 1
Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page