-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
f-stop
Active Member
Late 2015 70D with AP1 here - updated to 2017.42 a couple days ago. Just checked and auto lane changes are working fine/same as before.
whttiger25
Member
It is is using machine learning to replicate actual human behavior then it could result in hugging the driver's side lane.
I don't think the explanation needs to be that complicated. It's a lot easier just to program in such a bias, considering the system already tracks curvature radius.
gjunky
Trifecta: Solar and both cars are EVs
Just installed on my AP1 car which was on .32 before. It all seems a little smoother, even on AP1. The car didn't bounce much between the lines before but now even less.
I can confirm, lane change works on this update in AP1
Pinot.Noir
Member
I didn't read all 18 pages of this thread (I need to sleep at some point), but I want to report a strange behavior since this update. Every time I shut down the car and come back my Slacker Radio station is off and it's playing FM Radio. I need to go into the music icon and start Slacker again. WTF? Why would they change shiit that didn't need changing?
Off Shore
Off Topic Member
Eighty percent of the ghosts in the entertainment system rotate through every third update.
On-topic, I had five days with the update in my now-5000 km-distant car. The difference was noticeable. It still panics powering through a curved intersection at 45 mph, but overall it makes me hope for a better future!
After a couple of days of the same old erratic AP, all of a sudden it became so solid. When the sun is low, AP used to lose track of the lane markings and drive like a drunk. Now, no problem at all. It also recognized adjacent lanes and showed as the white lines next to the blue ones. Very neat.
whttiger25
Member
Can’t wait for it to see cars in those adjacent lanes like AP1!
Ever since I updated to .42, my TACC and EAP have been rendered unusable. After a maximum of 5 minutes, it randomly shuts down and I get a message stating "Cruise Control Disabled". I have to do a reboot of the car to get it back, only to have it disable again. I had to be on the phone with Tesla Service for 2 hours "trouble-shooting" before I finally got someone who said that it was a known issue with the early AP 2.0 cars (I am a 12/16 build) and they are pushing another update on Monday. Hope this helps others who have been as frustrated with this update as I have been.
HookBill
Member
Just finished a weeks worth of driving with the .42 and I must say it is looking more and more promising. There are a couple of negatives and they are:
- Having issues with auto lane change going from left to right. Many times the road is clear but the car refuses to change lanes unless forced to do so. Have had a couple of stalled lane changes going the other way also but the left to right request is the one that requires take-over the most. This, I'm sure, can be frustrating to those behind me as they must be wondering when the car is going to move over.
- Had a few warnings with no indications on the IC what they could be. Most of the time they appear to take place when there is a large concrete barrier/soundwall on my right and when I am in the middle of a typical freeway curve. Hasn't been a problem with previous releases.
- Car remains centered for the most part but have had it drift into an adjacent lane when the lane is involved in a 'S' type lane curve. Doesn't matter what the speed is and how gradual the 'S' curves are. It takes the first curve fine but as it begins to curve the other way the car is late in sensing what is happening. Have had to take over as by the time the car realizes what is going on it has already started entering the other lane. This is at freeway speeds (55-65) in well marked travel lanes.
- In stop and go traffic, car speeds up much quicker than before and brakes much harder. Caught me totally off guard when this first happened as the previous version (.34) had pretty much nailed the behavior I wanted.
Another negative I’ve noticed with .42 is that after a bump or hilly curve, it’s a lot more prone to misbehaving (eg pulling to one side, oscillating), even compared to earlier releases.
But seeing how they are collecting snapshots for slopes, I have a feeling they know.
But seeing how they are collecting snapshots for slopes, I have a feeling they know.
Been working well for me, but today the car started hugging the left of the lane way more than before. I've only ever had .42 and I swear it is less centered than before. It was so close today that I turned it off for fear of hitting the median. The sensors were showing yellow and red, and the car image was showing it was way to the left, so it seems like the car was aware of what it was doing.
Homelink failed to actuate exiting my garage today, even though it said it was going to. Had to manually hit it.
It also likes to trigger the homelink at an intersection almost a kilometer from my house. This glitch has happened before but seems more frequent with this release.
It also likes to trigger the homelink at an intersection almost a kilometer from my house. This glitch has happened before but seems more frequent with this release.
bishoppeak
Member
Same with my 12/16 delivery. I'm headed 125 miles to the service center Monday, perhaps I should wait for that update?
I have the same problem too, except the roads I have problems with have cones from contruction. I override AP and did not take a chance.
I think this might be the new design on purpose to fix the car from going out every freeway exit.
Based on what I was told, I probably would. Wouldn't hurt to call them and confirm that an update will be pushed out on Monday.
More time on .42, I've found it negotiates all but one of my favorite trouble spots very well. It handles the barriers on US 101 in Palo Alto (southbound) perfectly. Northbound, same construction area, I still jump in - it's confusing even for me, and I don't consider that a valid test.
The one area that is a real problem is on the southbound exit off 101 to San Antonio avenue. The exit takes a relatively sharp right curve, and right at that curve point is an arrow painted in the road. Apparently the car thinks that arrow is the right side lane line, so instead of taking the curve to the right, it dives left, attempting to go over the embankment. If allowed to continue, it gets to the very edge of the road then sounds the immediate takeover alarm (too late, if you aren't paying attention...).
I hope they are gathering data on that. I abort the AP every time, sometimes allowing it to go into the alarm state. But I do it every time on AP, in the hope that they are collecting data and this is useful for them. (For others that might try this, I reduce AP speed on the approach to exactly 45mph before entry to the turn, which is the posted warning speed. Be alert, try it at your own risk. It's pretty dicey.)
The one area that is a real problem is on the southbound exit off 101 to San Antonio avenue. The exit takes a relatively sharp right curve, and right at that curve point is an arrow painted in the road. Apparently the car thinks that arrow is the right side lane line, so instead of taking the curve to the right, it dives left, attempting to go over the embankment. If allowed to continue, it gets to the very edge of the road then sounds the immediate takeover alarm (too late, if you aren't paying attention...).
I hope they are gathering data on that. I abort the AP every time, sometimes allowing it to go into the alarm state. But I do it every time on AP, in the hope that they are collecting data and this is useful for them. (For others that might try this, I reduce AP speed on the approach to exactly 45mph before entry to the turn, which is the posted warning speed. Be alert, try it at your own risk. It's pretty dicey.)
Similar threads
