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.
Amazing how on TMC, as the $TSLA shorts get squeezed tighter, the FUD quotient goes up dramatically. Pathetic.
Close to unsubscribing as well to select threads.
I don't own stock in Tesla, I've not sold stock I don't own either, but it's not difficult to spot those that do have stock as they defend the indefensible. If you want to know what pathetic is, it's to throw the shorting line as the only argument you have left.
Amazing how on TMC, as the $TSLA shorts get squeezed tighter, the FUD quotient goes up dramatically. Pathetic.
but it's not difficult to spot those that do have stock as they defend the indefensible.
I don't own stock in Tesla, I've not sold stock I don't own either, but it's not difficult to spot those that do have stock as they defend the indefensible. If you want to know what pathetic is, it's to throw the shorting line as the only argument you have left.
Ditto, I feel sorry to the others that this thread got hijacked (and I participated) and went on a tangent on other things that have discussed at length since the release of autopilot 1.0 (or even when Tesla decided to do OTA updates). Perhaps that discussion should be moved elsewhere and this thread be kept solely about the release of AP 2.0 and its features, which is what most people were expecting coming into this thread.I also don't own any stock in TSLA and am not shorting it. I'm just not convinced that missing their expected timeline for EAP by, so far, less than a week is the catastrophic betrayal many others are portraying it as.
Nor is it appropriate to blow up the thread discussing the rollout of some of the features(along with every single other thread even remotely related to the rollout) with complaints about how they sold the software or the timelines.
Didn't I hammer home the point that Tesla does just as much in-house and closed beta testing as other automakers and that the product is just as "ready" as any other semi-autonomous product out there (and in fact is more reliable when talking about the autosteer component you complained about)?Active learning off of consumer drivers correcting AP mistakes on the road shouldn't be a common way of "teaching" AP to do basic tasks. Tesla should only be relying on this sort of training once the system is nearly perfect and once all of the other methods of "teaching" (in-house testing, data collection from cars with AP hardware but without functionality, normal debugging) have been absolutely exhausted. This sort of on-the-road fleet learning with untrained consumer drivers really isn't fair to the safety of other drivers on the road. And we don't really know how much of this fleet learning is going on. It feels like Tesla (and only Tesla-- none of the other manufacturers is doing this) is using "fleet learning" as an excuse for releasing products before they are ready and for cutting the amount of time and money put into testing.
...As for the claim that Tesla is the only automaker to use fleet learning, that is false (as is your claim that they are using it to release unready products). Toyota announced that they are doing so during the end of 2015:..
Didn't I hammer home the point that Tesla does just as much in-house and closed beta testing as other automakers and that the product is just as "ready" as any other semi-autonomous product out there (and in fact is more reliable when talking about the autosteer component you complained about)?
The fleet learning right now that Tesla is using is the same method to generate high res maps. This is the only way to gather enough updated road data to make semi-autonomous and autonomous vehicles operate reliably (even with faded lines), which is why all the large automakers are looking to do the same. Driving with only manufacturer vehicles is not enough and will leave you with outdated data even if the test driver was able to get full coverage (Mercedes article linked above pointed that out).
Craptastic. Another update email from Tesla ServiceHelpNA. I guess no cruise control of any kind for the foreseeable future. I inquired if I can roll back to 2.50.180 but I'm not hopeful.I installed 2.50.185 update on 12/31 at 10pm and have driven 150 miles with the camera still calibrating. I contacted Tesla service (email) and after a few exchanges, here's what they said:
"The vehicle may take between 1-5 hours of driving with the features enabled for the calibration message to clear. The features will also not be enabled until the next drive cycle once calibration is complete. Calibration is quicker on well-marked roads, but road conditions (not marked, poor visibility, etc.) may significantly increase the time required. Please keep an eye on this and let us know if after 5 hours of driving you still see this calibration message."
I was primarily complaining that basic cruise control was gone while cameras were calibrating. I probably have ~4 hours of driving on SoCal freeways and well marked roads since the update. Maybe nighttime driving doesn't help with calibration. Will keep driving.
Craptastic. Another update email from Tesla ServiceHelpNA. I guess no cruise control of any kind for the foreseeable future. I inquired if I can roll back to 2.50.180 but I'm not hopeful.
"During the initial roll out, we have identified conditions that may prevent some cars from successfully completing their calibration. If you have driven your car for over 6 hours and the calibration is still in process, it is likely you will need a new software release before you can use the new features. We are working on an update that will resolve this but do not have an exact ETA on when it will be released at this time."
I was asked if I wanted to be part of EAP (Early Access Program) since I am a SpaceX employee. If that means installing pre-beta software on my car, judging by my experience with 2.50.185, I think I'm going to decline.
I don't understand this. Your situation specifically helped them identify a bug, which they'll fix, and it will be in the next attempt. What's not to like? You can complain that they shouldn't have had any bugs, but that's never true. You can complain that some other poor bastard should have gotten stuck with a failure to calibrate and it should have been fixed then, but maybe your situation is new and unusual.Needless to say, I'm no longer so happy about having received the update.
I don't understand this. Your situation specifically helped them identify a bug, which they'll fix, and it will be in the next attempt. What's not to like? You can complain that they shouldn't have had any bugs, but that's never true. You can complain that some other poor bastard should have gotten stuck with a failure to calibrate and it should have been fixed then, but maybe your situation is new and unusual.
I don't understand this. Your situation specifically helped them identify a bug, which they'll fix, and it will be in the next attempt. What's not to like? You can complain that they shouldn't have had any bugs, but that's never true. You can complain that some other poor bastard should have gotten stuck with a failure to calibrate and it should have been fixed then, but maybe your situation is new and unusual.
So sorry, this is just how it goes when you're trying to move fast. People who object to this kind of thing need to realize that what they are asking for is that Tesla's software, with all its features, get released more slowly. That's right, you want to AP 2.0 software a year from now instead of a couple months. Yeah, didn't think so. You want it soon, you get it rough and it improves over time.
I was asked if I wanted to be part of EAP (Early Access Program) since I am a SpaceX employee. If that means installing pre-beta software on my car, judging by my experience with 2.50.185, I think I'm going to decline.
Someone from your branch of the Elon Empire would know better than anyone else, the risk that with early attempts at launching stuff you may experience some slight turbulence and then - explode.
It is pretty easy to surmise that it is not possible to have normal cruise control while calibrating the camera because the two are incompatible. Its not the end of the world that you do not have it. I think that people who are upset by these things (not you) should probably not accept the earlier version of the software. One needs to be a bit of a nerd type with a sense of adventure, and want to help out the effort to be a suitable candidate for this. In the past Tesla had a set of people who tested new stuff ... the supply of people is likely more limited with the new hw, since the total number of so equipped cars is less. This is a bit of a chicken-and-egg problem for Tesla.Second, if I were to be upset about anything it'd be that the software disables normal cruise control until camera calibration is complete. It's a little baffling that people at Tesla saw that calibration was required and figured people would be fine with driving several hours without even the basic cruise control that was there before.