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

Salvage Car Owners Support Group.

This site may earn commission on affiliate links.
#1,583
Have an 85D which has been down for a while. When I get in and hit the brake to start up, there's a knocking noise down by the brake pedal. I thought this might be a low 12v, but replaced the battery and still have it. Worse, it's not recognizing the key fob, even with a new battery in that.

It has 12 errors and says it 'needs service', mostly 'pack overtemp' (it's never been overtemp that I know of) and 'voltage low' (which must mean the 12v as the pack has 50 miles left). I can't seem to clear these errors in any way, and I've forgotten how to get into Service Mode (even if that would help).

Any suggestions?

Also I hear a rumor that if you have the high-voltage inspection done now, that they'll enable supercharging? Even on a Salvage?
 
#1,584
Well, you may have pack overtemps if the coolant system is not working or there are shorted cells in the pack. Voltage low could mean the HV pack has problems - depending on the exact message. With all those errors, sounds like something is seriously wrong. Service mode would likely get you a long list of error codes! I'd go through the service manual and identify what each error means - hopefully it will make more sense.

To get to service mode, Controls -> Software. Press and hold the large text "Model" for 2 seconds. At the popup, enter "service" (all lowercase).
 
#1,585
Has anyone seen this error before when doing a factory-redeploy

Code: 
2023-02-16T17:29:26.939996-08:00 cid : cid-updater:20744: check_for_vm2_match status=NULL_fgets feof=1
2023-02-16T17:29:26.941419-08:00 cid : cid-updater:21145: version_map_two_packager status=error reason=vm2_empty unmatched_hwids=,di:220397568,pm:220397568,, vhcs_for_packaging=,gtw:6,bms:84,di:220397568,pm:220397568,thc:33619968,dcdc:33619968,chgvi:83951616,chgph1:117506048,chgph2:117506048,chgph3:117506048,cp:7,epb:2,epbm:2,ic:50331648,dis:220397569,msmd:16842753,msmp:16842753,ptc:0,ptcr:16842753,rccm:0,tuner:252,epas:33619969,esp:33619970,sccm:0,tpms:16842752,park:33619968,pms:220397569,cmp:16908288,das:117506049,radc:7,bccen:83951617,bcfront:67174401,bcrear:67174401,bcfdm:67174401,bcrdm:67174401,bcfpm:67174401,bcrpm:67174401,bcs2l:50397185,bcs2c:50397185,bcs2r:50397185,bcfalcd:33685505,bcfalcp:33685505,snscll1:16777216,snsclr1:16777216,ibst:33685506,rcm:33619969,tas:67174401,cc:0,umc:16842752,plcrly:201457665,,*:*,
2023-02-16T17:29:26.942839-08:00 cid : cid-updater:21967: restage_gateway generate_gateway_release_tgz() returned -1
2023-02-16T17:29:26.943512-08:00 cid : cid-updater:15195: terminate_update at_line=23139 sid=10620 token=status=failure gw=yes activity=gw_staging invert_bank=0 reboot=0
2023-02-16T17:29:26.944217-08:00 cid : cid-updater:10639: Writing sentinel /var/spool/cid-updater/factory_redeploy_active: false
2023-02-16T17:29:26.945451-08:00 cid : cid-updater:10670: Wrote sentinel /var/spool/cid-updater/factory_redeploy_active.
2023-02-16T17:29:26.966142-08:00 cid : cid-updater:24491: reset_remotes status=starting
2023-02-16T17:29:26.967950-08:00 cid : cid-updater:17987: apeb_expected_available status=warning assuming_not_available=apeb
2023-02-16T17:29:26.969137-08:00 cid : cid-updater:18074: deploying_to_remote status=skipping host=ape reason=handshake_modules_to_skip
2023-02-16T17:29:26.972702-08:00 cid : cid-updater:18074: deploying_to_remote status=skipping host=ic reason=handshake_modules_to_skip
2023-02-16T17:29:27.023518-08:00 cid : cid-updater:10719: uiwarn /update_spool_folder_created
2023-02-16T17:29:27.024622-08:00 cid : cid-updater:10639: Writing sentinel /var/spool/cid-updater/terminated/terminated-: status=failure gw=yes reason=restage_gateway-4
2023-02-16T17:29:27.026013-08:00 cid : cid-updater:10670: Wrote sentinel /var/spool/cid-updater/terminated/terminated-.
2023-02-16T17:29:27.040127-08:00 cid : cid-updater:15113: kill_update_monitoring_sessions killing session 'keepawake' sid=7272
2023-02-16T17:29:27.041945-08:00 cid : cid-updater:14854: communicate_termination sid=10620 status=starting token=status=failure gw=yes activity=gw_staging early=0
2023-02-16T17:29:27.045702-08:00 cid : cid-updater:24650: complete_update gateway_update_relaunch (session) returned -1
2023-02-16T17:29:27.049019-08:00 cid : cid-updater:24653: gostaged status=failure reason=complete_update status=failure reason=staging_problem
2023-02-16T17:29:27.051960-08:00 cid : cid-updater: 5165:       TIMER:                   do after:        timerfd OD  parent:    0 fd:26  dtr:-1 READY:i pending: handshake cached
2023-02-16T17:29:27.054633-08:00 cid QtCar[957]: [SoftwareUpdateManager] INFO No files present in  /var/spool/cid-updater/staged
2023-02-16T17:29:27.087670-08:00 cid : cid-updater:31213: HTTP Client sid 11028 using session->xfer_filename = /var/spool/cid-updater/dv-VAPI_countryCode-response-11001.part-11001
2023-02-16T17:29:27.140149-08:00 cid QtCar[957]: [SoftwareUpdateManager] INFO No files present in  /var/spool/cid-updater/staged
2023-02-16T17:29:28.047683-08:00 cid : cid-updater: 5165:       TIMER:                   do after:        timerfd OD  parent:    0 fd:19  dtr:-1 READY:i pending: syncterm gw_staging
2023-02-16T17:29:28.047967-08:00 cid : cid-updater:34980: synchronous_termination status=starting sid=11027
2023-02-16T17:29:28.048919-08:00 cid : cid-updater:34957: synchronous_termination status=giving_up reason=no_vehicle_job_status_url sid=11027 retval=0
2023-02-16T17:29:28.053356-08:00 cid : cid-updater:10719: uinotify /update_failed?early_failure=false
2023-02-16T17:29:28.065832-08:00 cid : cid-updater:31213: HTTP Client sid 11032 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.076828-08:00 cid : cid-updater:31213: HTTP Client sid 11033 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.086898-08:00 cid : cid-updater:31213: HTTP Client sid 11034 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.095157-08:00 cid : cid-updater:31213: HTTP Client sid 11035 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.104247-08:00 cid : cid-updater:31213: HTTP Client sid 11036 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.113303-08:00 cid : cid-updater:31213: HTTP Client sid 11037 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.125298-08:00 cid : cid-updater:31213: HTTP Client sid 11038 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.132568-08:00 cid : cid-updater:31213: HTTP Client sid 11039 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.133099-08:00 cid : cid-updater:25798: clear_progress_dv type=0 rc=0

Need assistance getting past this as I've tried with skipping a handful of modules but I still can't get any success :(
 
#1,586
quak said:
Has anyone seen this error before when doing a factory-redeploy

Code: 
2023-02-16T17:29:26.939996-08:00 cid : cid-updater:20744: check_for_vm2_match status=NULL_fgets feof=1
2023-02-16T17:29:26.941419-08:00 cid : cid-updater:21145: version_map_two_packager status=error reason=vm2_empty unmatched_hwids=,di:220397568,pm:220397568,, vhcs_for_packaging=,gtw:6,bms:84,di:220397568,pm:220397568,thc:33619968,dcdc:33619968,chgvi:83951616,chgph1:117506048,chgph2:117506048,chgph3:117506048,cp:7,epb:2,epbm:2,ic:50331648,dis:220397569,msmd:16842753,msmp:16842753,ptc:0,ptcr:16842753,rccm:0,tuner:252,epas:33619969,esp:33619970,sccm:0,tpms:16842752,park:33619968,pms:220397569,cmp:16908288,das:117506049,radc:7,bccen:83951617,bcfront:67174401,bcrear:67174401,bcfdm:67174401,bcrdm:67174401,bcfpm:67174401,bcrpm:67174401,bcs2l:50397185,bcs2c:50397185,bcs2r:50397185,bcfalcd:33685505,bcfalcp:33685505,snscll1:16777216,snsclr1:16777216,ibst:33685506,rcm:33619969,tas:67174401,cc:0,umc:16842752,plcrly:201457665,,*:*,
2023-02-16T17:29:26.942839-08:00 cid : cid-updater:21967: restage_gateway generate_gateway_release_tgz() returned -1
2023-02-16T17:29:26.943512-08:00 cid : cid-updater:15195: terminate_update at_line=23139 sid=10620 token=status=failure gw=yes activity=gw_staging invert_bank=0 reboot=0
2023-02-16T17:29:26.944217-08:00 cid : cid-updater:10639: Writing sentinel /var/spool/cid-updater/factory_redeploy_active: false
2023-02-16T17:29:26.945451-08:00 cid : cid-updater:10670: Wrote sentinel /var/spool/cid-updater/factory_redeploy_active.
2023-02-16T17:29:26.966142-08:00 cid : cid-updater:24491: reset_remotes status=starting
2023-02-16T17:29:26.967950-08:00 cid : cid-updater:17987: apeb_expected_available status=warning assuming_not_available=apeb
2023-02-16T17:29:26.969137-08:00 cid : cid-updater:18074: deploying_to_remote status=skipping host=ape reason=handshake_modules_to_skip
2023-02-16T17:29:26.972702-08:00 cid : cid-updater:18074: deploying_to_remote status=skipping host=ic reason=handshake_modules_to_skip
2023-02-16T17:29:27.023518-08:00 cid : cid-updater:10719: uiwarn /update_spool_folder_created
2023-02-16T17:29:27.024622-08:00 cid : cid-updater:10639: Writing sentinel /var/spool/cid-updater/terminated/terminated-: status=failure gw=yes reason=restage_gateway-4
2023-02-16T17:29:27.026013-08:00 cid : cid-updater:10670: Wrote sentinel /var/spool/cid-updater/terminated/terminated-.
2023-02-16T17:29:27.040127-08:00 cid : cid-updater:15113: kill_update_monitoring_sessions killing session 'keepawake' sid=7272
2023-02-16T17:29:27.041945-08:00 cid : cid-updater:14854: communicate_termination sid=10620 status=starting token=status=failure gw=yes activity=gw_staging early=0
2023-02-16T17:29:27.045702-08:00 cid : cid-updater:24650: complete_update gateway_update_relaunch (session) returned -1
2023-02-16T17:29:27.049019-08:00 cid : cid-updater:24653: gostaged status=failure reason=complete_update status=failure reason=staging_problem
2023-02-16T17:29:27.051960-08:00 cid : cid-updater: 5165:       TIMER:                   do after:        timerfd OD  parent:    0 fd:26  dtr:-1 READY:i pending: handshake cached
2023-02-16T17:29:27.054633-08:00 cid QtCar[957]: [SoftwareUpdateManager] INFO No files present in  /var/spool/cid-updater/staged
2023-02-16T17:29:27.087670-08:00 cid : cid-updater:31213: HTTP Client sid 11028 using session->xfer_filename = /var/spool/cid-updater/dv-VAPI_countryCode-response-11001.part-11001
2023-02-16T17:29:27.140149-08:00 cid QtCar[957]: [SoftwareUpdateManager] INFO No files present in  /var/spool/cid-updater/staged
2023-02-16T17:29:28.047683-08:00 cid : cid-updater: 5165:       TIMER:                   do after:        timerfd OD  parent:    0 fd:19  dtr:-1 READY:i pending: syncterm gw_staging
2023-02-16T17:29:28.047967-08:00 cid : cid-updater:34980: synchronous_termination status=starting sid=11027
2023-02-16T17:29:28.048919-08:00 cid : cid-updater:34957: synchronous_termination status=giving_up reason=no_vehicle_job_status_url sid=11027 retval=0
2023-02-16T17:29:28.053356-08:00 cid : cid-updater:10719: uinotify /update_failed?early_failure=false
2023-02-16T17:29:28.065832-08:00 cid : cid-updater:31213: HTTP Client sid 11032 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.076828-08:00 cid : cid-updater:31213: HTTP Client sid 11033 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.086898-08:00 cid : cid-updater:31213: HTTP Client sid 11034 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.095157-08:00 cid : cid-updater:31213: HTTP Client sid 11035 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.104247-08:00 cid : cid-updater:31213: HTTP Client sid 11036 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.113303-08:00 cid : cid-updater:31213: HTTP Client sid 11037 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.125298-08:00 cid : cid-updater:31213: HTTP Client sid 11038 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.132568-08:00 cid : cid-updater:31213: HTTP Client sid 11039 using session->xfer_filename = /var/spool/cid-updater/set_dv_response-11027
2023-02-16T17:29:28.133099-08:00 cid : cid-updater:25798: clear_progress_dv type=0 rc=0

Need assistance getting past this as I've tried with skipping a handful of modules but I still can't get any success :(
Click to expand...
Is this installed in the car? What do you have unplugged?
 
#1,588
This is a longshot. My prefacelift model S had a rooted MCU1 that was upgraded to an MCU2 (not root capable) during a warranty rear motor replacement. The SC couldn’t get toolbox to work with the rooted MCU and wanted to exchange it. I opted into the MCU2. I have been pining to get my MCU1 back into the car and I finally gave it a shot. There was a big discrepancy between the firmware versions of these two MCUs. The MCU1 (rooted) has 2019.16.1.1 and the MCU2 (not rooted) has 2022.44.25.3. Both of these are configured for the same car. Installed the MCU1 and redeployed and the HVAC is completely unresponsive. Diagnostic mode is unable to see the status of coolant system. No matter what is selected on the screen, nothing happens. No blower, no compressor, just silence. Also the service Fakra under the MCU would’t work and had to use the one on the instrument cluster.

I wasn’t present during the MCU2 install and there was a vacant black socket without a plug (picture). Was the harness changed or the black plug cut off? I can’t find this plug anywhere behind the unit. It’s been so long since I’ve removed the MCU1, I’m not certain whether a plug was there or not. Also the service Fakra may have been altered?

I realized that I was in over my head and put the MCU2 back into the car realizing there is probably a FW mismatch. Tried several several service redeploys which did nothing, upgrades failed, and reinstalls all failed. Tried replacing both the HVAC Controller and Thermal Controllers behind the MCU and the HVAC is completely unresponsive. Checked the fuses in the frunk and could find non that were popped. The coolant pumps run constantly if the car is on. I drove the car and ended up with a turtle followed by a powering down Notification. Suspect it overheated.

I want to upgrade the firmware on the MCU1 if that will get me rolling again. I have to get it staged and setup a server to download the firmware onto the MCU1 if I can get some help. I am terrified of the cost tesla will charge to fix this.
 

Attachments

  • 3CF2F225-B55C-4962-AB30-1E6A8120881C.jpeg
    3CF2F225-B55C-4962-AB30-1E6A8120881C.jpeg
    169.7 KB · Views: 101
#1,589
While not confirmed, I understood MCU1 to MCU2 is a one-way option and it is impossible to go back. I assume all the ancillary CPUs/Modules are updated with firmware that is incompatible with MCU1. The newer firmware might not allow going back to MCU1 compatibility (but just a guess on my part).

The black connector you pointed to in MCU1 is for the various LIN buses. I assume the MCU2 retrofit comes with an adapter cable that feeds those wires into other places. Have you looked at where the female x428 (black) harness connector goes to?
 
#1,590
vcor said:
The black connector you pointed to in MCU1 is for the various LIN buses. I assume the MCU2 retrofit comes with an adapter cable that feeds those wires into other places. Have you looked at where the female x428 (black) harness connector goes to?
Click to expand...
I don't know that they always use an adapter cable, I thought sometimes they re-pin the connectors. (That may depend on the age of the original MCU1.)
 
#1,591
CB198 said:
This is a longshot. My prefacelift model S had a rooted MCU1 that was upgraded to an MCU2 (not root capable) during a warranty rear motor replacement. The SC couldn’t get toolbox to work with the rooted MCU and wanted to exchange it. I opted into the MCU2. I have been pining to get my MCU1 back into the car and I finally gave it a shot. There was a big discrepancy between the firmware versions of these two MCUs. The MCU1 (rooted) has 2019.16.1.1 and the MCU2 (not rooted) has 2022.44.25.3. Both of these are configured for the same car. Installed the MCU1 and redeployed and the HVAC is completely unresponsive. Diagnostic mode is unable to see the status of coolant system. No matter what is selected on the screen, nothing happens. No blower, no compressor, just silence. Also the service Fakra under the MCU would’t work and had to use the one on the instrument cluster.

I wasn’t present during the MCU2 install and there was a vacant black socket without a plug (picture). Was the harness changed or the black plug cut off? I can’t find this plug anywhere behind the unit. It’s been so long since I’ve removed the MCU1, I’m not certain whether a plug was there or not. Also the service Fakra may have been altered?

I realized that I was in over my head and put the MCU2 back into the car realizing there is probably a FW mismatch. Tried several several service redeploys which did nothing, upgrades failed, and reinstalls all failed. Tried replacing both the HVAC Controller and Thermal Controllers behind the MCU and the HVAC is completely unresponsive. Checked the fuses in the frunk and could find non that were popped. The coolant pumps run constantly if the car is on. I drove the car and ended up with a turtle followed by a powering down Notification. Suspect it overheated.

I want to upgrade the firmware on the MCU1 if that will get me rolling again. I have to get it staged and setup a server to download the firmware onto the MCU1 if I can get some help. I am terrified of the cost tesla will charge to fix this.
Click to expand...
Kudos for trying this n letting everyone know here it doesn't work.
Like previous poster said, yes someone mentioned here that once Tesla servers detect MCU2, u can't go back, can't recall the thread now..
Why it's not working with MCU2 now I'm not sure, maybe some failsafe built in software..
U need to get help from someone that knows about rooting n such...
Only person I know here is LayZ
Good luck!
 
#1,592
VegarHenriksen said:
Requires additional wiring from BCM which can be run through firewall+ config change from HID to LED, but the most important part is a Toolbox fw upgrade of the BCM module. Did this on mine this summer.
Click to expand...
Hi Vegar, I have no experience with Toolbox, is it simple to perform the BCM firmware upgrade? Just wanted to know how involved it is before I buy the subscription. Also, my S didn’t have the premium interior and lighting pack but I installed the fog/cornering lights + ambient lights. Would I be able to change the config to enable those in Toolbox as well? Car has mcu2 so I don’t have any other workarounds.
 
#1,593
I'll cross post here, maybe someone can help...
teslamotorsclub.com

Car died. BMS errors f123, w123, w073, w035, w142, w158

Unfortunately my 2016 MX 90D decided to surprise me with these errors :confused: We had a few days of cold/snow days and the car did fine. Last couple of days its been above freezing and everything already melted. I drove the car in the morning, then parked on driveway. Few hours later, started...
teslamotorsclub.com teslamotorsclub.com

Anyone know how to send CAN commands to the car to erase BMS codes f123/w123?
I found posts with data to send but im not sure what hardware/software i need to do it
Also, can Toolbox v2 reset BMS codes?
 
#1,594
AutomotivMedia said:
Hi Vegar, I have no experience with Toolbox, is it simple to perform the BCM firmware upgrade? Just wanted to know how involved it is before I buy the subscription. Also, my S didn’t have the premium interior and lighting pack but I installed the fog/cornering lights + ambient lights. Would I be able to change the config to enable those in Toolbox as well? Car has mcu2 so I don’t have any other workarounds.
Click to expand...
There's a menu for that in TBX2. If you have the full version of TBX2 you can change the config for those there. For TBX3 and MCU2 nor so sure,

F48cqZN.jpeg
 
  • Like
Reactions: AutomotivMedia
#1,596
I have been tinkering around with TB3 recently. It’s a very different approach for a diagnosis software, not intuitive but you’ll get a step by step instruction in the service manual.
Here is how to clear DTCs:
  1. In Toolbox 3, click the Tools tab, type "DTC" into the search field, click DTCs, and then select SDM or RCM depending on the vehicle Restraint Control Type.
  2. Click Read DTCs to display the DTCs.
  3. Power cycle the vehicle.
  4. Click Clear DTCs to clear the DTCs.

Btw. the steps in the service manual are getting kind of ridiculous. They might have to many interns. Many procedures start with,
Step 1: open driver door (big picture with the door open)
Step 2: open driver window (again a way to big picture of the window controls)
…
Step x: press button up on the lift post to lift up the car (Of course with a picture of the button)🤦‍♂️
 
Last edited:
#1,597
vcor said:
Well, you may have pack overtemps if the coolant system is not working or there are shorted cells in the pack. Voltage low could mean the HV pack has problems - depending on the exact message. With all those errors, sounds like something is seriously wrong. Service mode would likely get you a long list of error codes! I'd go through the service manual and identify what each error means - hopefully it will make more sense.

To get to service mode, Controls -> Software. Press and hold the large text "Model" for 2 seconds. At the popup, enter "service" (all lowercase).
Click to expand...
Overtemp seems to be a prior error as current errors are "Voltage low" if I remember correctly.

Can I clear these errors with TB2? Where can I get TB2? Failing that is there a Tesla guru in the US PacificNW who can advise or where I can send the car? It says, "Won't charge. Needs Service".

Also is there anyone who does CCS conversions?

Pre-facelift with MCU2.
 
You must log in or register to reply here.

Similar threads

N
SALVAGE MODEL S/X
Replies
22
Views
3K
Model S
brainhouston
brainhouston
S
Model S 2013 motor cant propulse the car
Replies
4
Views
152
Model S
Samuel Pepin
S
lolachampcar
Help with Model S rear accident damage repair costs
Replies
2
Views
427
Model S
lolachampcar
lolachampcar
Thomias
2013 Model S Large drive unit (LDU) repaired
Replies
12
Views
1K
Model S
Thomias
Thomias
F
Buyer Beware! Advice for Non-Running 2013 Model S
Replies
1
Views
303
Technical
frontporch
F
Top
Back
Blog
New
Forum list
Marketplace
Menu