You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Huh, looks like something isn't quute right with the Autopilot heat sink (or sensors). 5C in, 5C out, but only dropping from 76C to 62C on the ECU.I have a similar autopilot temperature reaching up to 90 degrees:
View attachment 1004499
View attachment 1004500
I did request service for this issue but the day before the Mobile Tech was scheduled to arrive they indicated the need to bring the car to a service center (not surprising). Since we are on holiday vacation, I choose to cancel the service request and will get the problem looked at when we get home. To my knowledge I never had Autopilot/FSD exit with an onscreen "system error" message on our 2018 Model 3. The version 3 Autopilot board was installed sometime late 2019 on our 2018 Model 3. Our new 2023 Model 3 still has the version 3 Autopilot board but there probably have been some changes to that board? The new Model 3 has the octovalve and heat pump; whereas, the 2018 had neither.Onscreen error indicated Autopilot terminated due to system error
Found the following in the service screen.
APS_w130_ECU_Thermal_Issue error occurred 19 times Dec 21 2023
APS_alertSource = TURBOB showing a temp of 80C
The service screen that shows the AP temp might only be for the heatpump Model cars, can anyone confirm? I assume the Scan my Tesla app would display the AP temp in question real-time but I have not installed the breakout cable required for SMT yet. Can anyone confirm?What service screen is giving you Autopilot temps? Is that only if you have the heat pump?
Since the holiday update, I'm getting the interior camera error, which disables FSDb. Typically happens around 45mins into a trip. I get the red steering wheel. Yay. It does seem temperature-affected, since I drove to go skiing 2hrs away, and if I don't turn on the heat, when it's 20° outside, FSDb will work the whole way! Yay. Of course, it's cold inside the car; thankfully, I'm dressed to go skiing! Not a practical long-term solution, more just testing the thermal theory. I usually don't get FSDb functionality back until my next drive, once I lose it.
What I did learn is that if I create a secondary driver profile with just EAP, and not FSDb, it will allow me to use EAP just fine. So, it's not a total annoyance, I just go back to EAP as if I wasn't testing FSDb.
Then this might be a bug/feature. If I have FSDb with my primary driver profile, and EAP with my secondary driver profile, Then turn on FSDb, and switch profiles to secondary. FSDb continues to run, but I get adjustable follow distances!
Outside of brake temps, I think this is all of the Temp readings I get on SMT:The service screen that shows the AP temp might only be for the heatpump Model cars, can anyone confirm? I assume the Scan my Tesla app would display the AP temp in question real-time but I have not installed the breakout cable required for SMT yet. Can anyone confirm?
To get to the service screen that shows the AP temp go to Thermal then coolant. My screen looks like the photo attachments from other posters above.What service screen is giving you Autopilot temps? Is that only if you have the heat pump?
Since the holiday update, I'm getting the interior camera error, which disables FSDb. Typically happens around 45mins into a trip. I get the red steering wheel. Yay. It does seem temperature-affected, since I drove to go skiing 2hrs away, and if I don't turn on the heat, when it's 20° outside, FSDb will work the whole way! Yay. Of course, it's cold inside the car; thankfully, I'm dressed to go skiing! Not a practical long-term solution, more just testing the thermal theory. I usually don't get FSDb functionality back until my next drive, once I lose it.
What I did learn is that if I create a secondary driver profile with just EAP, and not FSDb, it will allow me to use EAP just fine. So, it's not a total annoyance, I just go back to EAP as if I wasn't testing FSDb.
Then this might be a bug/feature. If I have FSDb with my primary driver profile, and EAP with my secondary driver profile, Then turn on FSDb, and switch profiles to secondary. FSDb continues to run, but I get adjustable follow distances!
Maybe this temp parameter is not even available on the can bus that the SMT adapter connects to? If it is, maybe a future update to the SMT smartphone app will have it in the future?Outside of brake temps, I think this is all of the Temp readings I get on SMT:
View attachment 1008623
Are you getting that screen on both your 2018 and 2023?To get to the service screen that shows the AP temp go to Thermal then coolant. My screen looks like the photo attachments from other posters above.
I know I did not have that screen on my 2020 without heatpump.Are you getting that screen on both your 2018 and 2023?
This evening, I drove 100km. I refrained from using Autopilot (I didn't want to upset my wife when disengagement alarme would occur), but I did use TACC (cruise control) for most of the ride. This went without problems. Afterwards, I looked in the Service menu and no alerts whatsoever were reported. Remarkable, because this morning several alerts were reported even without driving.My Tesla Model 3 Long Range AWD from 2020 has started to Disengage Autopilot due to system fault as well while using Autopilot on approx 50% of my trips during the last 7 days *).
In the Service menu alerts "APS_w130_ECU_Thermal_Issue" are shown. All alerts having "APS_sw130_currentTemperature = 80".
Is temperature 80 in Fahrenheit or in Celsius?
Even this morning, at 7C (45F) outside temp, before any distance was driven and having the car awake during for a software update, there were already 9 similar alerts visible in the service menu. All within one minute period. No new alerts before of after today as of yet.
I suspect that in these conditons not a real temperature of 80 could be reached. Would you?
A few sidenotes:
- The car is on software version 2024.2.7 since this morning before checking the service menu.
- *) Maybe it is a coincidence that this faulty behavior only started to happen after the car came out of service for an HV battery replacement?
This afternoon, on my commute back home, no single Autopilot issue occurred whereas last week multiple times " Disengage Autopilot due to system fault" occurred on exaclty the same route. The difference between now and then? Today it was cloudy with occasional light showers, last week it was dry and cloudy. Today I had climate control (A/C Auto) turned on, last week I didn't. So now I suspect climate control is of influence. My Model 3 does not have a heat pump. I don't know if and how Autopilot Processor Secondary is tempature regulated. But the heat pump circulation screenshots posted earlier certainly put me on this track.This evening, I drove 100km. I refrained from using Autopilot (I didn't want to upset my wife when disengagement alarme would occur), but I did use TACC (cruise control) for most of the ride. This went without problems. Afterwards, I looked in the Service menu and no alerts whatsoever were reported. Remarkable, because this morning several alerts were reported even without driving.