Let's not go down that rabbit hole!!!lol go figureand no I meant Fox News.
We get enough of that conversation in the news, FB, etc, etc.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
We get enough of that conversation in the news, FB, etc, etc.
d21mike
Active Member
2018 = year
6 = week of year - EVEN
1 = a dot change to the week version
Look here to see all of the past versions.
http://firmware.teslafi.com
i.E. 2017.50.n was the prior Major roll out. and 50 = even week of 2017.
They skipped 2017.52.
Then it was 2018.2 for week 2 in 2018 and then 2018.4 and 2018.6 and NEXT is 2018.8.
You can also see the ODD Weeks of 2018.5 and 2018.7 which some are saying is a SPECIAL BETA TEST Version that only a very few are getting.
d21mike
Active Member
I did not get my car until Sept. 2017. But in looking at the history did things change after the New Head of AP Development took over in mid 2017? I.E. More regular updates?
The real (original) release number is/was 2018.6 but they found something and released a new version as 2018.6.1. There haven’t been that many ‘subweek’ releases over the past year or so.
They start off as only the year and week.
They start off as only the year and week.
Yeah, ditto.
I was updated this morning to 6.1 and during my morning commute, the car hugged left so hard the proc sensors were dark red on the car in the lane next to me. I had to take control of the vehicle. Despite knowing how close it was to another object, the car still hugged way left, and even the binacle showed the car to be far left.
While changing lanes is far better, as others have indicated, this particular incident was the closest I've ever come to an collision while utilizing EAP. Luckily I was very engaged. Hopefully this release addresses this issue, it seems to be pretty widely observed .
To copy the info I posted in the 'other' thread in the S forum (where most people seem to look, since we have to have several copies of these...), the two cars we have info on that got 2018.7 also had 2018.5 before. Seems to imply they are 'beta, test, whatever' cars.
Also interesting that some of these people don't sign up for such plebeian entertainments as ev-fw.com. Maybe that is in the NDA? Who knows? As I said elsewhere, the first rule of NDA is N.
NDA that allows them to report the software on a platform like teslafi?
Good point but TeslaFi may be allowed for statistical purposes. It’s interesting that there are virtually no reports of ‘odd’ releases on ev-fw.com and we have these two on TeslaFi. Or it could be two new beta program members that were in TeslaFi before and didn’t remove themselves!
Shock-On-T
⚡️⚡️⚡️⚡️⚡️
Useful tip:
If you rapidly tap on the 2:00 minute countdown it goes straight to 0:03 and starts the updated straight away.
If you rapidly tap on the 2:00 minute countdown it goes straight to 0:03 and starts the updated straight away.
Reciprocity
Active Member
I have not noticed any hugging when there are lane markings. Only time I notice it is when on a curve or only on side of the lane had good markings. Maybe I just don't notice it but I have never had the car drive with red ultrasonic sensors. I even noticed my car would adjust to cars that where to close to my lane, maybe I'm crazy. I don't drive a lot on the freeway so my experience is not the best. My experience is that freeway driving is nearly flawless. Good weather or bad. Maybe I'm just not that sensitive to the cars location in the lane.
Xtek
Member
It seems like they moved to the bi-weekly release cycle towards the end of 2017.
FlyF4
Son of a MX
The is almost always due to losing WiFi or cellular connection during the download. Try it again. If in the garage and your car is not connected to WiFi then pull the car outside the garage to get a slightly better cellular signal.
Xtek
Member
I thought the update didn't even start until the file was fully downloaded. And surely they are doing an integrity check on the download before starting.
Look at the 4th column in the table I created here in this *specific* POST: 2018.7 a3159ea
Many many odd release reports.
Last edited:
FlyF4
Son of a MX
Xtek
Member
FlyF4
Son of a MX
Sorry, I am probably misunderstanding the question ;-) I'll try to clarify. Most often the failure message occurs right after the download when a Cyclic Redundancy Check is being done on the firmware and before it replaces the existing firmware. Then other system checks come after that.
Similar threads
