Software Update Required, APS_w160, Schedule Service

[Sean.]

Car updated to 32.4 yesterday. No issues.

However this amber warning came up a few minutes ago. Any idea what it means?

 

[kelvin 660]

Did you try a 2 button reset?

 

[Durzel]

One of the ECUs probably failed to update properly.

Do you know how to get into Service Mode? Press and hold your finger on the "Model X" on the page that shows details about your car, then when you get a popup asking for a password, type "service". You should end up in Service Mode with a red border around the screen.

Once you're in that there is an option somewhere (can't remember off hand - sorry) to reinstall the software (32.4). That ought to fix it.

You will probably get more info in Service Mode about that and other non-customer facing alerts that might exist.

In 32.4 (new feature) you can also check Infotainment - ECU Update Status. I'm betting one or more of the ECUs will be under "Failed ECUs" or something like that.

 

[Sean.]

Thanks @Durzel. Yes getting a SW mismatch error…will try a reinstall when I get home.

 

[Sean.]

Yes Autopilot functions not working.

Tesla service have pushed out a firmware update just now and looks to have cleared the error.

Will complete a full reinstall of of 32.4 later today which the car is asking for again.

Thanks for all the help.

 

[Sean.]

Sorted now. Firmware push from service and reapplying 32.4 did the trick.

 

[Viejo66]

I had same APS_w160 problem. Went into service mode and viewed notifications. A little bit more detail about APS_w160 showed there:

Autopilot Processor Backup (APB) firmware version does not match the Autopilot Processor Secondary (APS) FW version, making Autopilot features unavailable.

In service mode I went into Software and chose Full Re-install. Exited service mode, waited 5 minutes like it said, then it offered to install same firmware version, chose yes, came back an hour later and drove the car -- autopilot worked fine and no APS_w160 error messages now.

Not sure why car couldn't do its own software re-install if it detects firmware mismatch between modules.

 

[Durzel]

I had same APS_w160 problem. Went into service mode and viewed notifications. A little bit more detail about APS_w160 showed there:

Autopilot Processor Backup (APB) firmware version does not match the Autopilot Processor Secondary (APS) FW version, making Autopilot features unavailable.

In service mode I went into Software and chose Full Re-install. Exited service mode, waited 5 minutes like it said, then it offered to install same firmware version, chose yes, came back an hour later and drove the car -- autopilot worked fine and no APS_w160 error messages now.

Not sure why car couldn't do its own software re-install if it detects firmware mismatch between modules.

At a guess - an error that impacts a secondary function of the car (i.e. not driving) should be left for the owner to remedy at a convenient time & place.

Imagine the alternative where the car decides itself to update, is undriveable for 30+ mins and you need it for an emergency situation or appointment, etc.

You could argue that if it fails to update the first time then it does a full reinstall immediately, but that would result in a very long period of downtime.

I think the current system of “notify the owner and let them arrange remediation at their convenience” is the correct one.

 

[Billbrown1982]

At a guess - an error that impacts a secondary function of the car (i.e. not driving) should be left for the owner to remedy at a convenient time & place.

Imagine the alternative where the car decides itself to update, is undriveable for 30+ mins and you need it for an emergency situation or appointment, etc.

You could argue that if it fails to update the first time then it does a full reinstall immediately, but that would result in a very long period of downtime.

I think the current system of “notify the owner and let them arrange remediation at their convenience” is the correct one.

I agree - except that remedy should be made clearer such as a regular software update. Instead of having to dive into the service menu.

 

[Sean.]

I agree - except that remedy should be made clearer such as a regular software update. Instead of having to dive into the service menu.

To be fair the car was perfectly drivable throughout - although no AP functionality.

It was resolved via Tesla service pushing a separate update out to my car, which then automatically re-applied 32.4 (at the time)

[The service menu stuff was interesting for diagnostics - but not a necessary part of the remedy]

 

[FistsOfTinsel]

In service mode I went into Software and chose Full Re-install. Exited service mode, waited 5 minutes like it said, then it offered to install same firmware version, chose yes, came back an hour later and drove the car -- autopilot worked fine and no APS_w160 error messages now.

I'm in the service menu now, and I don't see the options you're talking about. What do you mean by "went into Software"? There is no submenu called "Software", just the "Software Reinstall" button under the "Vehicle Info" section. If I choose that, it just immediately starts reinstalling, it doesn't give me an option to exit service mode or mention firmware versions.

 

[Billbrown1982]

I'm in the service menu now, and I don't see the options you're talking about. What do you mean by "went into Software"? There is no submenu called "Software", just the "Software Reinstall" button under the "Vehicle Info" section. If I choose that, it just immediately starts reinstalling, it doesn't give me an option to exit service mode or mention firmware versions.

My understanding of what he said to do.

Do the software reinstall button. THEN exit service mode when its completed and leave the car alone for 5 minutes and you should (they did) get a update available notification from the regular car interface.