Once the codebase is converged (they were definitely separate in the past), it’s just a matter of setting build flags when you’re ready and you can output the same software for multiple target architectures or platforms. I do this regularly.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
2018.12 for Model 3?
- Thread starter URFIR3D
- Start date
Once the codebase is converged (they were definitely separate in the past), it’s just a matter of setting build flags when you’re ready and you can output the same software for multiple target architectures or platforms. I do this regularly.
Today, I upgraded from 2017.50.13 to 2018.12. However, there was a message that said that the upgrade was unsuccessful. So, I may have a partial 2018.12.
I'm going to get on the freeway tomorrow to see if I can detect an improvement in the autopilot. The release notes mentioned items that have already been covered by others describing 2018.10 versions. The only surprise to me was the use of scroll wheels to change TACC and mirrors, etc.
I'm going to get on the freeway tomorrow to see if I can detect an improvement in the autopilot. The release notes mentioned items that have already been covered by others describing 2018.10 versions. The only surprise to me was the use of scroll wheels to change TACC and mirrors, etc.
I had the same thing happen to me with 10.5. Install appeared to go ok but it didn’t complete fully. I called Tesla service about it and the service rep I spoke to said that autopilot probably wouldn’t work until the update is successfully installed. This was in fact the case, autopilot was not available for me to select after the failed install. Tesla ended up pushing the 10.5 update to my Model 3 again and the second time around it did install completely and autopilot was restored. You should contact Tesla service and let them know what happened.
Tony_YYZ
Tezler Guru
Yes, the update from 2017.50.13 to 2018.12 was on a Model 3. Note that I had been passed over on several updates and I had called Tesla to complain. Of course, they blamed it on cellular coverage even though I had received previous updates in December and January. I had made an appointment to have them look at it, but then I got the update that said that it had not been completed successfully. I think that I'll keep the appointment.
My car is in for service, so it might come back with the latest update since Tesla tends to push updates to cars in for service... HOWEVER that might not be the case this time seeing as it works for the S/X primarily because they connect to the Tesla Wi-Fi network at service, something which is currently disabled for the 3.
It’s 100% correct, the model 3’s perceived lack of WiFi is due to the lack of a customer facing UI to enter networks. The service SSID is hard coded, though.Are you sure? There are no settings to enable/connect to Wi-Fi on M3... If you're right though, thats better for me as I'll likely have the latest update when I get my baby back
spudnik187
Member
Have your home WiFi SSID, password, and crypto type set to match the tesla service one, and it'll join right up
spudnik187
Member
spudnik187
Member
My guess is the signal was weak (maybe only temporarily) and it fell back to LTE. Mine has connected every time I've been to the SC, which, unfortunately, has been 5 or 6 times in the first 5 weeks of ownership.
