-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Update 17.18.50
- Thread starter rjdoc74
- Start date
-
- Tags
- Model X User Interface
HankLloydRight
No Roads
Spaces are handled properly. There was an quirk in the code. I just moved web servers and databases and there was a few things still "off", which I corrected. You should be able to now login and add a car, and then add a firmware update to that vehicle. Let me know if you have any other problems.
Thanks.
John, fyi same situation as you--100D delivered yesterday with EAP and 17.18.50 and no auto high beam.
Werid! I picked my up two days ago and I have auto high beams! However my car is a ap1. My only large issue is I can't get the focking Easter egg basket to appear
I have been trying to get my local service center to address the problems I am experiencing, with my AP 2.0 car, which was delivered 9 days ago. It has 17.18.50, lacks Auto High Beam, and other driver assistance features work only on about two-thirds of the trips I take.
For the first 50 miles the car did not offer driver assistance features but reported that it was calibrating. Once calibration completed, it has offered driver assistance on about two-thirds of trips but unlike the first 50 miles, when it is unavailable it no longer says that it is calibrating.
AP 2.0 cars with firmware 17.17.x have Auto High Beam and apparently do not have issues with driver assistance being unavailable on a significant fraction of trips. My car does not even show Auto High Beam as an option that can be set on the Controls screen.
To date, using data from ev.fw.com, over 97% of cars with 17.18.x firmware are AP 1.0 cars. Only two AP 2.0 cars reported on ev-fw (including mine) have 17.18.x firmware.
My complaints have fallen on deaf ears. My delivery specialist told me driver assistance is working on my car and they will not investigate further until I have driven 1000 miles. The car currently has about 325 miles on it.
Do I have any recourse to get this problem addressed sooner?
For the first 50 miles the car did not offer driver assistance features but reported that it was calibrating. Once calibration completed, it has offered driver assistance on about two-thirds of trips but unlike the first 50 miles, when it is unavailable it no longer says that it is calibrating.
AP 2.0 cars with firmware 17.17.x have Auto High Beam and apparently do not have issues with driver assistance being unavailable on a significant fraction of trips. My car does not even show Auto High Beam as an option that can be set on the Controls screen.
To date, using data from ev.fw.com, over 97% of cars with 17.18.x firmware are AP 1.0 cars. Only two AP 2.0 cars reported on ev-fw (including mine) have 17.18.x firmware.
My complaints have fallen on deaf ears. My delivery specialist told me driver assistance is working on my car and they will not investigate further until I have driven 1000 miles. The car currently has about 325 miles on it.
Do I have any recourse to get this problem addressed sooner?
Seattle Tom
Member
Picked up my 100D today with EAP. I also have 17.18.50 and do not have auto high beam. AP activated after about 50 miles and works reasonably well (max 35 on non freeways though...Didn't that change recently?).
I also don't have the Easter Egg menu. The thing I most looked forward to activating on my first night of ownership (the light show) wasn't available, so bummed there. It looks like 17.18.50 is a step back in some ways...
I also don't have the Easter Egg menu. The thing I most looked forward to activating on my first night of ownership (the light show) wasn't available, so bummed there. It looks like 17.18.50 is a step back in some ways...
Just because you don't have the fancy new menu didn't mean you don't have the Easter Eggs. Did you try using the passcode to activate it?
Interesting. Usually we see regressions with firmware when Tesla has merged source branches. We saw a few items like this on the first AP2 firmware that had autosteer.
It's possible 17.18.x has other not customer facing changes. Model 3? Prep for new kernel?
It's possible 17.18.x has other not customer facing changes. Model 3? Prep for new kernel?
I thought it was established upthread that 17.18.50 already has the new kernel in it.
That being the case, it's looking to me like it's a temporary build to validate the kernel doesn't do something bad, and lacks some features of 17.17.xx presumably because it forked at an earlier point.
I'm still on 17.14.35, for almost six weeks now, and I haven't seen much activity on these threads, which makes me hope the real 8.1 version merging the 17.18.50 kernel with all the other promised features is right around the corner somewhere...
Seattle Tom
Member
That's a good point. The 007 and Mars features did work via passcode - I should try modelxmas to see if that one works too!
You're not alone. Picked up a brand new 75D last week with 17.18.50. Definitely no auto high beams. Autopilot occasionally doesn't work at all (have to reset the dash computer), and when it does it is almost always limited to 35mph on local roads...so basically useless. I've had a few instances of "normal" AP2 functionality, but it's mostly either speed restricted or completely unavailable. Will try the service center tomorrow and see if they can downgrade to 17.17.4 until the next release is available.
Seattle Tom
Member
Also my situation. The lack of Autosteer in local roads above 35 mph is painful. It's clearly the wrong firmware for AP 2.0 or Tesla has decided no new AP 2.0 cars are getting the full suite of Autopilot features until the "silky smooth" release later this month. I added my car to ev-fw too, so there are four of us stuck in 17.18.50 hell.
All the Easter eggs work via code by the way (to answer my own post from above).
My local service center took a look at my car today. I don't yet know if the intermittent driver assistance is fixed but here are some things they claimed:
- My car arrived from the factory with 17.18.25 and they flashed 17.18.50 prior to delivery.
- At that time, they had some difficulty getting the firmware to flash. It eventually succeeded after three failures.
- The missing Auto High Beam is a known limitation of this firmware version, but the intermittent driver assistance features are not.
- They tested for hardware issues such as camera/sensor problems and identified none.
- Their hypothesis is that 17.18.50 had not fully installed pre-delivery and that explains the problems with driver assistance features. (I am skeptical about this.)
- They re-flashed 17.18.50 from a laptop instead of over the air today, and they think that may fix it.
- This car (and, presumably, others manufactured approximately 5/17/17 and later) cannot accept firmware 17.17.17
I will report back after I have had time to determine if the intermittent driver assistance issue has been resolved.
I think there's just a test in the code that prevents "going back" in the versions. At least I saw something that I think means this.
Similar threads
