scottrobertson
Member
NFC, seems strange to me to be honest.
Hmm, what do you mean by NFC in this case?
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.
NFC, seems strange to me to be honest.
I am assuming the "phone as key" option provides for some sort of Bluetooth connectivity so your phone works exactly like the fob without having to log into the app to unlock and start the car?
In any case, I decided this morning to start using my phone instead of my fob for my weekday commutes. Having to enter a password in the app each time to start the car isn't so bad - at least not yet.
As far as this latest update, I did not see any differences with EAP on my hour-long commute this morning. 95% was highway. It still wanted to exit off a ramp to the left that was closed off. I pulled it back into the proper lane after it began searching for a lane line on the left. AP should not take an exit if there is no input from me to do so. (this was a construction zone however workers were not present)
Lane line disappears:
View attachment 286644
Car begins to straddle left lane line:
View attachment 286645
No ***** clueHmm, what do you mean by NFC in this case?
Not necessarily, in fact keyless driving shouldn't, because that makes it practically useless. Eg park in some underground P house without reception = stuck. That would be unacceptable.It will be slower. It has to make an API request over the internet. The fob goes direct to the car.
Not necessarily, in fact keyless driving shouldn't, because that makes it practically useless. Eg park in some underground P house without reception = stuck. That would be unacceptable.
The only good way to implement this is to let the Tesla mothership give each car and app some tokens on beforehand while connected that can be used to allow direct authentication and driver profile detection over bluetooth. Tokens to individual apps can ofcourse be revoked over the API (takes effect next time car is connected).
This could also work with phone in pocket without starting the app if you wanted to.
It will be slower. It has to make an API request over the internet. The fob goes direct to the car.
There haven't been any installs on AP1 vehicles yet.Any AP1 improvements?
I can confirm that from my perspective this is a significant, generational upgrade for AP2.
Using the gaming console analogy, if the earliest releases were 8-bit, and we've progressed through 16 and 32-bit consoles over the last year, this is the first 64-bit release IMO. Best way I can put it is that as a passenger, if you closed your eyes in any prior AP release, you could "feel" that it wasn't a human driving. Almost all of that is gone in this release. Vehicles ahead seem to be detected much earlier and speed adjustments are more gradual/smooth.
Lane Change: slightly slower (~8 blinker clicks where the prior releases were 7), but much more smooth and less abrupt. More comfortable to the occupants.
I have a few "torture test" areas on my regular commute, this release made a marked difference in all of them:
1) Freeway exit on a curve - There's one exit on my normal drive where the road is sweeping to the left just as the exit opens up. Prior releases would all dive for this exit before correcting, preferring the "straight" path as opposed to the curving freeway. This release mastered it perfectly.
2) One lane splitting into two - one lane gradually widens and expands into two. Prior releases would get confused, ping pong back and forth, and then aggressively swerve into one lane or the other. This release smoothly tracked to the left lane without any hesitation.
3) Two lanes merging into one - left lane ends and merges to the right. In prior releases, car failed to detect this merge, thinking the left lane kept on going - would drive right over the painted line and try to keep its course. Perfect execution in this release.
4) Hump of Death - a brief crest on an otherwise straight, flat, fast section of freeway would cause violent swerving in all prior releases. I considered this a "worst case scenario" for AP as the driver was lulled into a sense of safety and stability from the prior expanse of straight, flat, perfectly tracked roadway. 2018.10.4 handled this perfectly. The handling of these sorts of hills/crests was my largest outstanding gripe with the current state of AP2.
Be careful doing that if you don't have a key with you. If the car is getting bad cell signal you won't be able to get in it. Correct me if I'm wrong but I think it relies on cell signal instead of bluetooth.
For me it has seemed like it's the recognition part that has been unstable in previous releases. When lane defection swerves and wanders, it also causes the control outputs to fail (eg ping-pong).While obviously the quality of the NN output would have an effect, most I what I see being described would surely be down to the code that decides the driving, no? So it has to be a major upgrade in addition to 'just' the NN.
(and hopefully the improvements in the driving dynamics can also apply to us AP1 cars)
Got 10.4 as well around 1am. All 561.8 MB of it.
Freaking awesome. Hills on my test course just rock now. Prior 7 times disengaged. Today zero. Smooth in corners were speeds go from 55 to 35 suggested for curve.
This is what I wanted when I bought the car. Worth the wait.